What Uncle Lee keeps, and what he can't

Secret Lee is a one-time secret sharing service operated from Singapore. This policy covers secretl.ee and its apps (CLI, Raycast and Slack). Questions or requests go to lee@secretl.ee.

The short version

Secrets are encrypted in your browser before they reach us. The key lives in the link after the #, which browsers never send to a server, so we cannot read what you share. The security whitepaper explains how.
We keep only what is needed to run accounts, deliver secrets once and stop abuse.
No ads, no analytics or tracking cookies, and we never sell or rent personal data.

What we collect

When you share a secret without an account

The encrypted secret (ciphertext only), its expiry and view count. Encrypted files are stored under a random name. All of it is deleted when the secret is read for the last time, burned, or expires.

When you have an account

Your email address, and your name and profile picture if you sign in with Google.
Metadata about secrets you create: an optional label you type, the kind and size, how many views were used, and timestamps. Never the contents.
Organisation membership, invitations, branding, request links and an audit log of actions.
For apps you connect: hashed API tokens, and for Slack, your workspace and user IDs and an encrypted bot token.

Technical data

To limit abuse, we count requests against a salted, daily-rotated hash of your IP address (never the address itself), and those counters expire within a day. Our hosting provider keeps standard request logs (paths without the # key, IP addresses and timings) under its own retention policy.

We never collect: secret contents, link keys, passphrases, or original file names.

Google sign-in

If you choose “Continue with Google”, we receive your Google account's email address, name and profile picture (the openid, email and profile scopes). We use them only to create and sign in to your Secret Lee account and to show who you are in the dashboard. We request no other Google data. We do not share it, sell it, use it for advertising, or use it to train AI models. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can remove Secret Lee's access at any time in your Google account settings.

How we use it

To sign you in, including emailing magic links.
To store, deliver and then delete secrets, and to show you their status.
To send notices you turned on, such as read receipts in Slack.
To prevent abuse and keep the service secure.

Who processes it

We rely on these providers to run the service. Each only processes data on our behalf.

Provider	Purpose	Region
Vercel	Hosting, encrypted file storage	United States
Upstash	Encrypted secrets until read, rate-limit counters	United States
Neon	Accounts and metadata database	United States
Resend	Sign-in and invitation emails	Japan
Google	Sign-in, if you choose it	Global
Slack	The Slack app, if your workspace installs it	Global

Cookies

We set only the cookies sign-in needs: a session cookie, Auth.js security cookies, and a small lee_in cookie that tells our pages to show the signed-in header. There are no analytics, advertising or third-party tracking cookies.

How long we keep it

Encrypted secrets and files: until last read, burned, or expired, whichever comes first.
Account data, secret metadata and audit logs: while your account exists.
API tokens and Slack links: until you revoke or unlink them.
Rate-limit counters: at most one day.

Your choices

You can ask for a copy of your account data, have it corrected, or have your account and its metadata deleted by emailing lee@secretl.ee. We handle requests in line with Singapore's Personal Data Protection Act and, where it applies to you, the GDPR. We may ask you to confirm the request from your account's email address.

Changes

If this policy changes, we will update the date at the top and, for material changes, tell account holders by email. See also our terms of service.