Match the control to the risk
Why it matters: Unlisted limits discovery, a password adds a check, and browser encryption changes what storage can read.
Pastebin privacy and security guides
Discovery controls, access controls, encryption, and expiration solve different problems. These guides explain each boundary plainly so you can choose a setting based on the content and its recipients - Not a reassuring label.
Privacy & Security at a glance
Classify the data first, remove secrets, then choose separate controls for discovery, access, storage, and retention.
Remove secrets before upload
Why it matters: Redact tokens, personal data, signed links, internal hosts, and live credentials even when access is limited.
Plan for copies
Why it matters: Expiration and burn-after-read stop later access to the source link, but they cannot erase a recipient’s copy.
Privacy & Security learning path
Encryption, secret scanning, expiration, access control, and safer handling of sensitive text in pastebin workflows.
Pastebin Privacy: Public, Unlisted, Passworded, or Encrypted?
Compare public, unlisted, passworded, owner-only, and browser-encrypted pastes by discovery, application access, storage readability, and recovery.
Read guide →How to Password-Protect a Paste
Add a second access check to a paste, share the password safely, and understand when browser encryption is the stronger choice.
Read guide →Paste Expiration Guide: 10 Minutes to Forever
Choose paste retention from ten minutes through permanent availability, match it to the review window, and understand why expiration cannot recall copies.
Read guide →Burn-After-Read Pastes: How One-Time Links Work
One successful retrieval can trigger deletion, but delivery systems still require careful threat modeling.
Read guide →Secret Scanning Before You Share Code or Logs
Use a repeatable pre-publish review for tokens, credentials, private keys, cookies, connection strings, personal data, and contextual secrets.
Read guide →Pastebin API Token Security Guide
Automate paste workflows without putting permanent credentials in scripts, logs, or source repositories.
Read guide →Public vs unlisted vs private pastes
Compare public, unlisted, owner-only, password-protected, and encrypted pastes by discovery, authentication, server readability, sharing, and retention.
Read guide →How to redact logs before sharing
Find and replace credentials, personal data, session identifiers, internal hosts, and signed URLs while preserving the diagnostic relationships a reviewer needs.
Read guide →How to share environment files safely
Turn a real .env file into a synthetic example by removing credentials, rotating exposed values, documenting required variables, and sharing only safe placeholders.
Read guide →Direct answers for this topic
Does unlisted mean confidential?
No. It limits discovery but does not encrypt content or stop a recipient from forwarding the URL. Read the complete explanation.
What can client-side encryption protect?
It keeps readable content out of the normal storage request; it cannot protect a compromised browser, exposed complete link, or recipient copy. Read the complete explanation.
What should happen after a secret leaks?
Revoke or rotate the credential at its issuing system first, then remove the paste and inspect logs for unauthorized use. Read the complete explanation.
How to use these guides
Begin with the privacy comparison, select a control for the actual threat, and verify it using non-sensitive text. Use a secret manager when the material is a live credential.
Try the paste editor →