Hi HN!<p>I want to share a service we’ve been working on called 2Secured and ask for feedback. It's a tool to send sensitive information using end-to-end encryption.<p>Here's a link to our landing page: <a href="https://2secured.link/" rel="nofollow">https://2secured.link/</a><p>I’ve worked at several companies where the standard for sending or receiving secrets inside and outside the company (passwords, api credentials, documents, ...) was to send/receive them in an email or in slack. Secrets not only lived in their final destination, but were also persisted in many different third party communication services in clear text. It was a common practice and a compliance nightmare.<p>2Secured ensures that the secrets you send and collect remain private and secure. We’ve abstracted away the pipes for sending and collecting secrets, allowing you to collect and send e2ee data with simple secure links, user friendly customizable forms, and in the future, easy integrations with your backends via SDKs and APIs. We’re also layering in features such as customizable link expiration and email confirmation to view the secrets.<p>You can share confidential documents, personal data, and other sensitive information without worrying about leaving plain text secrets in intermediate services. You also don’t have to worry about implementing your own internal tools or pages for fulfilling common data requests from clients or partners. It's made for companies or professionals who need handle private information regularly, such as legal documents, medical records, financial data, API keys, pass-phrases, etc.<p>Has anybody else come across this issue in any of the organizations you've worked in? How have you approached solving the problem?<p>Please ask any questions or share your experiences! Any feedback on the tool would be greatly appreciated!<p>Cheers!
the templates concept is a good one (different vs some alternatives ive tried), bc i find myself sending the same 'structure' to clients at work (eg API name / public key/private key)