Three steps, then it is gone.
An API key, a config block, a password, a note. Up to 1 MB, encrypted on the way in.
One hour to thirty days, or burn it the moment it is read. Optional password on top.
The storage layer deletes it when the timer ends. No backups, no content logs, nothing left to hand over.
Sharing an API key securely, in about a minute.
Loads from YouTube when you press play. Nothing is requested until then.
Four things that follow from not keeping your data.
Expiry runs in the storage layer on a fixed schedule, so nobody here has to remember to delete anything. No backups and no logs of what you shared. Why permanent storage is a liability.
One-time secrets are destroyed on reveal, behind an explicit confirmation so a link preview can never spend them. When to use burn-after-reading.
A REST API and npm i -g zerohost-cli for CI pipelines and scripts,
instead of pasting credentials into chat.
The problem with keys in Slack.
Encrypted in transit and at rest. Analytics are aggregate only, never run on share pages, and honour DNT and GPC. How this simplifies GDPR.
The honest version, including where the others are fine.
| Capability | ZeroHost | Pastebin | GitHub Gist | Slack or email |
|---|---|---|---|---|
| Deletes itself | Always | Optional | Never | Never |
| Ads | None | Yes | None | None |
| Burn after reading | Yes | No | No | No |
| Leaves an audit trail | No | Yes | Yes | Yes, forever |
| Account required | No | No | Yes | Yes |
The longer version, with PrivateBin and others, is in our Pastebin alternative comparison.
Start free. Upgrade when the free limits start getting in the way.
Free
$0/ month
Everything you need to share a secret today.
Pro
$7/ month
For developers who share secrets every week.
Team: $25/month for 5 people. Shared dashboards, audit logs and role-based access. Not shipped yet.
Register interestNo account needed. It takes about ten seconds.
Create a secure share