Privacy

Last updated 12 August 2026

The short version

SharePad has no accounts, so it never learns who you are. It stores what you write, for as long as you choose, and deletes it afterwards. It shows no adverts and sells nothing to anyone.

It is also not end-to-end encrypted. Please read what this is not before pasting anything genuinely sensitive.

What gets stored

  • The title and text of your notebook and its pages.
  • The last ten drafts of each page, so an edit can be undone.
  • Comments, with whatever name was typed alongside them.
  • A count of how many times a notebook has been opened. Just a number — no record of who or when.
  • The settings you choose: expiry date, paper, typeface, whether editing is open.

This lives in a Postgres database run by Supabase, hosted in Mumbai (ap-south-1).

What is never collected

No email address, no name, no password for an account, because there are no accounts. No IP address is stored against a notebook, and nothing you write is read for advertising or sold on.

How a notebook can be yours without an account

Creating one produces a secret edit link. Only a SHA-256 hash of that link is stored, so the database holds no copy of the link itself — which also means it cannot be recovered or emailed to you if it is lost.

If you set a password on a notebook, it is hashed with bcrypt and never stored as typed.

What sits on your own device

  • Your edit links. The browser keeps a list so notebooks appear on the home page. It stays on your device and is only ever sent back when you save a change. Removing one with the Forget button erases it.
  • A preference for whether the editor panes scroll together.
  • One cookie, and only if you unlock a password-protected notebook. It records that you got the password right, lasts a day, and cannot be read by scripts.

Analytics

Visits are counted using PostHog, to see which pages people arrive on and whether anything is broken. Three deliberate limits:

  • No analytics cookie is set, so there is no banner asking you to accept one.
  • Session recording is switched off inside notebooks. A recording of the editor would be a recording of you typing a private note.
  • Events carry counts and settings only. Note contents, titles, addresses and edit links are never sent.

Who else is involved

  • Supabase — stores the database.
  • PostHog — receives the analytics events described above.
  • The hosting provider — serves the site and keeps ordinary request logs, as every web host does.
  • Ko-fi — only if you follow the donate link, and then their terms apply, not these.

Deleting things

Open your notebook with its edit link, go to settings, and delete it. Every page, draft and comment goes at the same time and the shared link stops working immediately.

Notebooks also delete themselves. Ten days is the default; it can be anything from a day to a year, or never. A scheduled job removes expired notebooks from the database three days after the date passes, and read-once notebooks a day after they are opened.

If you have lost the edit link there is no way to prove the notebook was yours, so it cannot be deleted on request — waiting for it to expire is the only route. If something needs taking down for another reason, open an issue.

What this is not

Notebooks are unlisted, not secret. Anyone holding the link can read one, and an address is guessable if you choose a simple one.

Content is not encrypted end-to-end. It is stored so that the server can render it, which means whoever operates the database can technically read it. Nobody goes looking, but the honest position is that this is the wrong place for passwords, financial details, health records or anything you would be harmed by losing.

Changes and contact

If this policy changes, the date at the top changes with it. The whole application is open source, so the behaviour described here can be checked against the code rather than taken on trust.

Questions go to the issue tracker.