Privacy policy

Draft for review by a lawyer before launch. Highlighted items in brackets still need filling in. Last updated October 22, 2026.

1. Who we are
2. What we collect
3. How we use it
4. Who else handles it
5. Cookies and browser storage
6. How long we keep it
7. Your choices and rights
8. Security
9. Children
10. Changes

1. Who we are

This policy explains what Sealed Calls (sealedcalls.com), run by [company legal name], collects and why. Contact: [contact email, e.g. support@sealedcalls.com].

2. What we collect

• When you request access: your email, and the name and note you choose to give.
• Readers: your email and your access link, stored only as a one-way hash, kept in an access cookie (sc_access) for up to 180 days.
• Analysts: your handle, name, bio, link, email, and your caller key stored only as a hash. Your calls, handle, name, bio and link are public and permanent: they are published in the ledger and can't be deleted, because the ledger has to stay complete to be checkable. Your email is never published.
• Technical data: like any website, our host Cloudflare processes your IP address, browser type and request details to serve and protect the site.

3. How we use it

• To run the service: let approved readers in, publish and score calls, and answer API calls.
• To keep it secure and working, and to enforce our terms.
• To contact you about your access or your caller account.
• We don't sell your data, we don't use it for advertising, and we don't run analytics or ad trackers on the site.

4. Who else handles it

• Cloudflare hosts the site and its database.
• Resend sends our emails, once email is turned on for this site.
• Google Fonts serves the site's typefaces, so Google sees your IP address when a page loads.
• OpenTimestamps calendar servers receive only hashes of ledger entries, never your details.
• Price data providers receive only ticker symbols and dates.
• We may also share data if the law requires it, to protect people's safety or our rights, or as part of a sale or merger of the business, in which case this policy keeps applying.

5. Cookies and browser storage

Readers get one cookie, sc_access, which keeps them in. Analysts' keys are kept in their own browser's storage when they sign in to post. We don't use tracking or advertising cookies.

6. How long we keep it

Reader and request data is kept while your access is active. When you ask us to delete it, we delete your email and access records within 30 days, except where the law requires us to keep something.

Analysts' published calls and public profile stay in the ledger permanently. On request we will delete your email and turn off your key. [lawyer: confirm this works with deletion rights where analysts live]

7. Your choices and rights

To get a copy of your data, correct it, or delete what can be deleted, email [contact email, e.g. support@sealedcalls.com]. Depending on where you live (for example California, the UK or the EU), you may have further rights, and we will honor them as the law requires. [lawyer: confirm which laws apply and add any required sections].

8. Security

Everything travels over HTTPS, and access links and caller keys are stored only as hashes. If we learn of a breach affecting your data we will tell you as the law requires.

9. Children

Sealed Calls isn't meant for anyone under 18.

10. Changes

If we change this policy in a material way we will tell readers and analysts by email before the change takes effect.

See also the terms of service.