What we store

If you do not sign in

Nothing is stored anywhere but your own browser. Saved companies, saved filings, your theme and your filters live in that browser's localStorage and are never sent to us. Clearing your browser data clears them. There is no account and no cookie that identifies you. One script does count page views, and it is not ours — it is described below rather than denied here.

If you do sign in

Three things are stored, and they are the whole of it:

• Your email address. It is the only way to sign you back in, because there is no password to remember and no username to look you up by.
• The scrip codes you save. Six-digit BSE codes, and the date each was added. That is what makes your lists follow you to another browser or another device.
• The names you give your lists. Up to ten of them, and you wrote them, so they say whatever you typed. Nothing reads them but the page that shows them to you.

Alongside those, a sign-in link is stored as a hash until it is used or expires, and a signed cookie keeps you signed in. Both are mechanics of signing in, not facts about you.

One more, added because somebody could otherwise stop anyone else signing up. While an address is waiting to be confirmed — and only then — the row carries a keyed hash of the network address the sign-in form was submitted from. It is not the address itself, it cannot be turned back into one without a secret that is not in the database, it is never written for an account that has confirmed, and it is erased the moment you click your link. If nobody clicks, the whole row goes within fifteen minutes. It exists so that one machine cannot fill the queue of unconfirmed sign-ups and lock everybody else out, and it is used for nothing else.

What is not stored

No name. No password. No profile, no photo, no phone number. No advertising and no tracking pixel. We do not record which pages you read, which filings you open, or when you visit — the database holds six tables, one of which is public filings and has no column that refers to anyone, and its whole schema is short enough to read in a sitting. There is nowhere for anything else to go.

Said carefully, because the earlier version was not. This paragraph is about our database, and it used to deny keeping request logs without saying so — true of us, false of the stack you actually meet. Cloudflare terminates every request to this site and necessarily sees your address and your browser's identifier, as any host does. Nothing there is joined to anything you saved. The one place a network address reaches our own code is the keyed hash described above, on an unconfirmed sign-up, which is discarded when the sign-up completes or expires.

One thing that does count page views, and it is not ours

This site is hosted on Cloudflare Pages, and Cloudflare injects its own Web Analytics script into every page: a request to static.cloudflareinsights.com and a page-view beacon. It is switched on by default at the hosting layer rather than chosen here, and nothing on this site reads it.

It is cookieless and does not follow you between sites, which is why it is described separately from the tracking above rather than lumped in with it. It is still a third party seeing that a page was loaded, and this page said "no tracking" while it was running, which was not accurate. The sentence changed rather than the claim being defended. The only other third parties your browser contacts are fonts.googleapis.com and fonts.gstatic.com, for the two typefaces.

Why

So that a list of companies you care about survives a new laptop. That is the entire purpose, and nothing collected here is used for another one.

How long

• Your account and list: until you delete it. There is no expiry and no automatic purge, because a list you built two years ago is exactly the list you would be annoyed to lose.
• An address that never confirms: fifteen minutes. If someone types your address into the sign-in form and you never click the link, the row is deleted once the link expires. It does not sit there.
• Sign-in links: fifteen minutes, once. Used or expired, the hash is deleted on the next sign-in request anyone makes.
• The session cookie: 90 days, or until you sign out — and signing out ends it everywhere, not just in the browser you pressed it in. Deleting your account does the same. A cookie issued before either is refused from that moment, whoever is holding it.

Who else sees it

Your email address and your saved lists are never sold, rented, shared or handed to a third party for any purpose. There is no advertising on this site and no arrangement under which there could be. Two providers necessarily touch them in passing: Cloudflare, which hosts the site and the database, and the email provider that delivers your sign-in link. Neither is given anything beyond what is needed to do that, and neither is given your saved list.

How to delete it

Sign in, go to your list, and use Delete my account. One confirmation, and it is done immediately: your email address, your lists and every sign-in token for them are removed from the database in the same request. There is no soft delete, nothing is flagged and retained, and there is no backup we would restore you from. The build's own self-test asserts that the row count across all five tables that can refer to you is zero afterwards, counted against the identifiers captured before the delete rather than through the rows it was supposed to remove.

If you cannot sign in and want your address removed, write to [email protected] from it.

Changes

If what is stored ever changes, this page changes in the same commit as the schema. It is not a summary of the policy — it is the policy.