Privacy guide
How to share code privately with the right visibility
“Not public” can mean several different things. An unlisted link, a password-protected paste and an account-only private paste solve different access problems. Picking the right mode before sharing is more important than trying to fix visibility later.
Public: for content you are comfortable making discoverable
Public pastes are the right choice for examples, demos and snippets you intentionally want to share broadly. They can appear in public discovery surfaces and are the only visibility mode that should be treated as search-indexable content.
Unlisted: link-only sharing, not true secrecy
An unlisted paste is useful when you do not want the snippet in public listings but still want frictionless access for anyone who has the URL. That makes it convenient for quick collaboration, but the URL itself becomes the access token. If it is forwarded, the recipient can usually open it too.
Protected: require both the link and a password
Password protection adds a second piece of information before the paste can be revealed. It is useful when a shareable URL is still desirable but link possession alone should not be enough. Share the password separately from the paste URL whenever possible.
Private: keep the paste tied to account access
Private pastes are intended for account-only use rather than public sharing. They are the better fit for personal snippets or material that should remain inside your own authenticated workspace.
Burn-after-read: use when persistence is the problem
Burn-after-read is designed for cases where the paste should not remain available after a successful reveal. It reduces persistence, but it is not a replacement for deciding whether the content should be shared through a paste service at all.
Keep secrets out of ordinary code snippets
API keys, session tokens, private keys and credentials deserve dedicated secret-management tools. Even when a paste is restricted, avoid treating a general code-sharing service as a long-term secret vault. If a secret was accidentally exposed, rotate or revoke it rather than relying only on deleting the paste.
Private sharing and search indexing should agree
A restricted paste should not become discoverable through a sitemap, public archive, social preview or duplicate raw URL. Wklejka keeps public indexing behavior separate from restricted paste modes and applies access rules to related routes.
Read the general code sharing guide →Choose visibility when you create the paste
Start with the narrowest mode that still fits the task. You can use public for intentionally discoverable material, unlisted for link-only sharing, protected for password access or private for account-only content.
Create a pasteFAQ
Is an unlisted paste private?
No. Unlisted means the paste is not intended for public discovery, but anyone with the URL may still be able to open it. Use stronger access controls when the content is sensitive.
When should I use a password-protected paste?
Use password protection when link possession alone should not be enough to reveal the paste and you can share the password through a separate trusted channel.
Are restricted Wklejka pastes indexed by search engines?
Wklejka is designed so public content is the indexable mode, while restricted paste modes are excluded from public discovery and search indexing behavior.