Privacy
Privacy
Secret Sharing is built privacy-first. The application does not require an account and does not collect personal data.
What we store
- Encrypted ciphertext (AES-GCM) and a random IV.
- A non-secret Argon2id salt (needed to re-derive the key from the passphrase; not sensitive).
- An expiry timestamp and a creation timestamp.
- A ULID as a payload identifier.
That's it. We do not store the decryption passphrase, the plaintext, your email, your IP (beyond transient server logs controlled by your hosting provider), or any metadata tying a secret to an identity.
How long data lives
Records are deleted the first time they are read, or at the latest 15 minutes after their expiry. There is no soft-delete, no backup, no “archive” - the row is hard-deleted from the table.
Cookies & tracking
Secret Sharing does not set cookies and does not load third-party scripts. There is no analytics SDK, no advertising pixel, no fingerprinting library. The Referrer-Policy is set to no-referrer so outbound links do not leak your URL.
No account required
Secret Sharing does not require an account and does not offer login. There is no sign-up, sign-in, user profile, or per-user data store. The tool is a free public utility.
No advertising or third-party tracking
Secret Sharing does not load Google Analytics, advertising scripts, session-recording tools, or third-party marketing scripts. There are no third-party trackers on the page.
Server request logs
When you load the site, your browser requests the static HTML, JavaScript, CSS, and image assets that make up the application. Standard web server request logs may record the URL, time, IP address, and user agent of those asset requests. These logs do not intentionally capture the content you process, because that content is never transmitted to the server.
Avoid sensitive data on shared devices
Because processing is local, you should avoid processing sensitive data on shared or untrusted devices. Browser history, extensions, or device management software outside our control could retain information you enter.
Use two-channel delivery. Don't paste secrets into the URL bar. Don't forward the decrypted plaintext to anyone you don't trust. Verify you are on the correct domain before entering a passphrase.
Contact
For privacy questions, contact WebF1 through webf1.com/contact.
See also the how it works page.