A private pastebin — encrypted in your browser, gone in 24 hours
Classic pastebins are publishing tools: a paste gets a public URL, crawlers find it, and years of forgotten pastes full of connection strings are a well-documented source of leaked credentials. This is the same idea turned inside out — a paste nobody can open without your approval, encrypted before it is uploaded, excluded from every search index, and destroyed 24 hours after the last activity.
- Not public
- Not indexed
- Not stored in plaintext
Start a paste
Enters automatically once all six digits are in
Content is encrypted in your browser before upload — the server never sees plaintext. Destroyed after 24 hours of inactivity.
How to paste text privately
Create a clipboard
No account, no email, no “sign in to make this private”. Your browser generates the key; the server hands you a 6-digit code.
Paste whatever you need to move
Logs, snippets, configuration, a wall of JSON. Each item can run to 10,000 characters and newlines survive intact.
Give the code to the one person who needs it
Six digits, said out loud or typed into a chat. There is no URL that grants access on its own.
Approve them, and watch it expire
You see the request and approve it. 24 hours after the last activity the whole thing is gone, with nothing to clean up.
What “private” means here, precisely
The server cannot read it
Every item is encrypted with AES-256-GCM in your browser first. “Private” is not a visibility flag on a row in someone's database — it is ciphertext.
No public URL to leak
There is no unlisted-but-guessable address. Reaching the content requires a request you approve, so a leaked link is not a leaked paste.
Crawlers are kept out
Clipboard routes are disallowed in robots.txt and are never linked from any page, so there is nothing for a search engine to find and archive.
Expiry you cannot forget to set
24 hours after the last activity, always. There is no “never expire” option to leave selected by accident.
Both sides can edit
Unlike a static paste, the other person can add items and delete them. It behaves like a shared surface while you are working, then it is gone.
Nothing to sign up for
Most pastebins put private pastes behind an account. Here there is no account tier, because there is no account.
Versus a public pastebin
Both are “paste text, get it to someone else”. They differ on every question that matters afterwards.
| — | A public pastebin | This clipboard |
|---|---|---|
| Who can read it | Anyone with the URL — and URLs leak, get logged and get shared | Only people you approve, one request at a time |
| Search engines | Public pastes get crawled, indexed and archived | Disallowed in robots.txt and never linked — nothing to crawl |
| What the server stores | Your plaintext, readable by the operator | Ciphertext — the key never leaves your browser |
| Default expiry | Frequently “never” | 24 hours after the last activity, not configurable |
| Account required | Usually, for private pastes | None, for anything |
| Best at | Publishing a snippet you want people to find | Handing something to one person and having it disappear |
When a public pastebin is still the right tool
If you want a durable, linkable address for a code sample — one you can drop into a bug report, a forum answer or documentation and expect to still resolve next year — use a gist or a public pastebin. Permanence and discoverability are features there, and this tool deliberately has neither.
The split is simple: publishing versus handing over. A paste meant for strangers to find should be public. A paste meant for one colleague, containing a log with customer identifiers in it, should not be sitting at a guessable URL forever.
Why old pastes are a security problem
Credential scanners have been mining public paste sites for years, because debugging output is where secrets hide. Somebody pastes a stack trace to get help, the trace carries a database URL with the password in it, the thread is resolved, and the paste stays up. Nobody goes back.
The fix is not discipline; it is defaults. Making the content unreadable to the server, and making expiry mandatory rather than optional, removes the failure mode instead of asking you to remember.
Questions about private pastes
Is this really a pastebin?
It does the paste-and-share part and skips the publish part. There are no public pastes, no syntax-highlighted permalinks and no archive — just text moved privately from one person to another and then deleted.
Can I get a link to send instead of reading out digits?
You can copy a link to the clipboard, but it only gets someone to the door. They still have to request access, you still have to approve, and the decryption key only travels after you do.
Will Google index what I paste?
No. Clipboard routes are blocked in robots.txt, and no page ever links to one, so crawlers have no path to it in the first place.
How long does a paste last?
24 hours from the last activity. Every new item or change resets the timer, so a clipboard you are actively using stays up until you stop.
Can I paste code and keep the formatting?
Yes. Line breaks and indentation are preserved exactly, and each item is shown in a monospaced card you can copy with one tap.
Is there a size limit?
10,000 characters per item, 200 items per clipboard. For something larger than that you want a file transfer, not a clipboard.
Do you keep logs of what people paste?
There is nothing readable to log — the server receives ciphertext. Operationally it sees that a clipboard exists, how big each blob is and when it arrived, which is the metadata any server needs to function.
Can I delete a paste before it expires?
Yes. Delete a single item, clear the whole clipboard, or remove everyone from it. Deletion is immediate on both sides.
Keep reading
- Phone ↔ computeriPhone to Windows, Android to Mac — any pair, in a browser.
- Share a passwordHand over a credential without leaving it in a chat log.
Ready when you are
Create a clipboard, read the six digits to the other side, approve, and paste.