Privacy policy
This policy describes what pastesite.com actually stores, why each item exists, and how to get rid of it. It is written to be read, not to be survived. If something here is unclear, that is a documentation bug — tell us.
The short version: pastes are stored so they can be read, accounts are stored so you can manage your pastes, and IP addresses are stored only as salted hashes used for rate limiting.
What is stored when you create a paste
| Data | Purpose | Notes |
|---|---|---|
| Paste content and title | To show the paste | Stored until deleted or expired |
| Language and visibility | Rendering and feed inclusion | Public or unlisted |
| Password hash | To check the password | bcrypt hash only — the password itself is never stored |
| Screenshot | To show the attached image | Inline JPEG data, only when you capture one |
| Timestamps and view count | Expiry, ordering and trending | View counts are de-duplicated per network per day |
| Account id | To attach the paste to your dashboard | Only when you are signed in |
| Folder and revision history | Organisation and undo | Up to 20 revisions per paste |
Accounts and API keys
Signing up stores your email address and a profile with a username and optional display name. Passwords are handled by Supabase Auth and stored as hashes — we never see them. Confirmation and password-reset emails are sent by Supabase.
API keys are stored as a salted hash plus a short prefix so you can recognise a key in your dashboard. The key itself is shown once at creation and cannot be recovered. Key metadata — label, scopes, creation, last use, expiry — is stored so you can audit and revoke keys.
IP addresses
Rate limits and abuse prevention need to tell one network from another. We take your IP address, combine it with a server-side secret salt and store only the SHA-256 hash. The raw address is not written to the database. Hashes are used for paste-create limits, read limits, password-attempt limits, report limits and per-paste view de-duplication.
Because the salt is secret, the stored hashes are not usefully reversible to an IP address by someone who obtains the database alone.
Abuse reports
A report stores the paste id, the reason you write, an optional email address, a salted hash of your IP, and status timestamps. The email is only used to follow up on the report; it is not shown to the paste owner and is not added to a mailing list.
Analytics
Page views are measured with a self-hosted Umami instance at stats.pastesite.com. It is first-party: the data goes to our server, not to an advertising network. It is used to see which pages are slow or broken, not to build a profile of you.
A session recorder may capture anonymised interaction data such as clicks, scrolling and page transitions. It is not used for advertising, is not shared with third parties, and there are no advertising or cross-site tracking cookies on the site. If you would rather not be measured, any content blocker that blocks stats.pastesite.com works — the site functions normally.
Service providers
| Provider | Role | Data involved |
|---|---|---|
| Netlify | Hosting and serverless functions | Requests, including the IP Netlify forwards to the API |
| Turso | SQLite database | Everything listed above except passwords and raw IPs |
| Supabase | Authentication and email | Email address, password hash, session tokens |
| Cloudflare Turnstile | Human verification | Interaction signals used to decide you are human |
| Umami (self-hosted) | Analytics | Page views and interaction events |
None of these providers receive data to sell. We do not operate an advertising network, a data broker or a paste archive for crawlers.
Retention and deletion
- Pastes stay until an expiry passes, until a burn-after-read paste is opened, or until the owner deletes them.
- Anonymous pastes cannot be deleted by their author because there is no author identity. Ask us with the link and we will remove it.
- Rate-limit events are pruned on a rolling basis; the table is cleaned as it is used.
- Abuse reports are kept while open and afterwards as needed to recognise repeat abuse.
- Accounts are deleted on request, which removes the profile and unlinks your pastes from it.
Your choices
You can read and write without an account, which means most use of the site stores no identity at all. If you have an account you can ask for a copy of your data or for deletion by emailing support@pastesite.com from the account address. Blocking the analytics script changes nothing about how the site works.
Children and changes
The site is not directed at children under 13, and accounts should not be created by them. If the data practices change, this page is updated with a new effective date; material changes will be noted on the site rather than announced by email, because most users have no account.
Questions about this policy: support@pastesite.com or the contact page.
Frequently asked questions
Are my pastes encrypted?
Traffic is encrypted with HTTPS and the database encrypts data at rest, but paste content is not end-to-end encrypted. The service can read a paste in order to display it, so do not paste secrets.
Do you use cookies?
Signing in requires a session token stored by Supabase in your browser. Analytics is self-hosted and does not use advertising cookies. There are no third-party ad or cross-site tracking cookies.
Can you delete a paste I made anonymously?
Yes, if you send the link or paste id. There is no author identity to verify, so the request is handled as a removal request on the content.
Do you sell data?
No. There is no advertising, no data brokerage and no paste archive provided to crawlers.
How do I opt out of analytics?
Block stats.pastesite.com in your browser or content blocker. Nothing on the site depends on it.