This policy covers the hosted service at hushdrop.dev, its API, the remote MCP server at hushdrop.dev/mcp, and the hushdrop CLI and MCP packages when they talk to hushdrop.dev. If you self-host Hushdrop, your drops go to your own Vercel account and this policy doesn't apply to them.
What you publish
Locked drops (the default in the CLI and the local MCP server) are encrypted on your machine before upload. We store ciphertext and can't read the page or the password. Locked drops published through the remote MCP server at hushdrop.dev/mcp are encrypted on our server before they're stored: the server handles the page once while locking it and keeps only ciphertext. Unlocked drops, and pages published without an account, are stored as you sent them and can be read by anyone with the link. Anonymous drops are deleted after 24 hours. Burn-after-read drops are deleted on first view. Drops in an account stay until you delete them or they reach the expiry you set.
What the Claude and ChatGPT connector receives
When you use Hushdrop as a connector in Claude, ChatGPT or another MCP app, we receive only the arguments of the tool your assistant calls, such as the HTML of a page you asked it to publish or the slug of a drop. We don't receive or store your conversation, your chat history, your assistant's memory or your other files. The connector signs in with OAuth and holds an API key labelled with the app's name, which you can revoke at any time.
Your account
If you sign in, we store your email address, your handle, and the API keys you create. Sign-in links are sent by email.
Viewing data
When someone opens a hosted drop, we record that it was opened, the viewer's country, the referring site and whether it was a phone, so the owner can see view stats. If the owner requires an email before viewing, the email the viewer enters is shared with the owner.
Product analytics
We use PostHog to understand how Hushdrop is used: page views on hushdrop.dev, and events such as publish, sign-in and share. The CLI sends a random install id, its version, your operating system and which AI agent ran it. These events never include the content of your drops or your passwords. Self-hosted deployments don't send drop uploads through us.
Service providers
- Vercel: hosting and file storage.
- Supabase: account and drop records.
- PostHog: product analytics.
- Resend: sign-in and notification emails.
- Stripe: payments, if you buy a paid plan. We never see your card number.
We don't sell personal data and don't use your drops to train AI models.
How long we keep data
- Drops without an account: deleted after 24 hours.
- Drops in an account: kept until you delete them or their expiry passes. Earlier versions of a drop are kept so you can roll back, and are deleted with the drop.
- Account records and API keys: kept while the account exists, and deleted when you ask us to delete the account.
- View stats: kept with the drop and deleted with it.
- Product analytics events: kept in PostHog under its standard retention, then deleted.
- Payment records: kept as long as tax law requires.
Your choices
Delete any drop with hush rm <slug>. To delete your account and its drops, email support@hushdrop.dev. To keep everything inside your own infrastructure, self-host.
Contact
Questions or deletion requests: support@hushdrop.dev. To report a security issue, see our SECURITY.md.