Privacy Policy

1. Who is responsible

The controller of any personal data processed in connection with Tickertail is [operator entity: to be completed at incorporation; see the imprint in the Terms of Service].

2. The short version

• Accounts are optional. You can read the site without signing up. An account is your email address plus whatever you choose to add to it (a display name, a timezone, saved follows) - sign-in is a one-time emailed link, and no password ever exists to steal.
• No tracking cookies. Signing in sets the strictly necessary session cookies that sign-in requires; the site sets no other cookies. Traffic is measured with a cookieless counter.
• Your watchlist stays in your browser unless you move it. Personalization (watchlists, reading preferences) lives in your browser's local storage and is not transmitted to us. The one exception is always your explicit choice: signed-in readers can save follows and desk tickers to their account so they sync across devices (section 3).
• No sale of personal data. We do not sell or share personal data for advertising, and never will.
• One honest caveat:the site's fonts load from Google, which means your IP address reaches Google's servers. Details in section 3.

3. What we collect today

Server logs. The site is served by our hosting provider (Vercel). Like every web server, it keeps standard access logs: IP address, browser user agent, requested page, and timestamp. We use these only for security and operations (spotting abuse and outages), and they are retained briefly by the provider, not compiled into profiles.

Aggregate traffic analytics. We measure page views with Vercel Web Analytics, a cookieless counter. It sets no cookies, stores no persistent identifier on your device, and does not follow you across other sites. What we see is aggregate: which pages are read, roughly from which countries, on what kinds of devices; never a profile of you.

Fonts, and the IP address that comes with them.The site's typefaces currently load from Google Fonts. When your browser requests a font file, your IP address necessarily reaches Google's servers (which may be outside your country, including in the United States). Google states that its Fonts service does not use that data for profiling or advertising, but we name the transfer here because it is the one piece of your data that leaves our infrastructure today. We plan to self-host the fonts, at which point this section shrinks.

What stays on your device.Reading preferences and watchlists are stored in your browser's local storage by default. We receive them only when you are signed in and choose to save them to your account: following something while signed in, or accepting the one-time offer to copy this browser's saved follows. Local data is never uploaded silently, and clearing your browser data removes the local copies entirely.

Account data, only if you sign up. Creating an account stores your email address, sign-in timestamps, and your plan tier, in our database (hosted by Supabase; section 5). If you use them, it also stores your display name and timezone, and the follows and desk tickers you choose to save to the account. Sign-in works by one-time emailed link, so there is no password to store, and the only email we send is the sign-in link you request. Two forms on the site collect personal information: the sign-in form (your email) and the optional profile form in Settings (display name and timezone).

That is the complete list. There is no email marketing list and no payment data - and when subscriptions open, card details will go to the payment processor directly, never to us (section 11).

4. What we deliberately do not collect

• No brokerage anything. We never ask for brokerage credentials or account numbers, and we never connect to a brokerage. The desk list of tickers you can keep is optional and self-typed, and it stays in your browser unless you save it to your account (section 3); we never treat it as proof of what you own.
• No ad tech. No advertising trackers, no third-party marketing pixels, no data brokers.
• No sale or sharing.We do not sell personal data, and we do not "share" it for cross-context behavioral advertising as the California CCPA/CPRA defines that term.
• No profiling. We build no individual profiles and make no automated decisions about you.

5. Who processes data for us

Current processors and infrastructure:

• Vercel (USA): hosting, server logs, and the cookieless analytics above. Transfers are covered by the EU-U.S. Data Privacy Framework and/or standard contractual clauses.
• Supabase: hosts the database of filings and prices the site is rendered from, and the account records described in section 3 (email, sign-in timestamps, plan tier, and any profile details or saved follows you add) for readers who sign up. Pages are rendered on the server, so your browser never connects to the database directly.
• Google Fonts (USA): font delivery; receives your IP address as described in section 3. Google operates the Fonts service as an independent controller rather than as our processor, and Google LLC is certified under the EU-U.S. Data Privacy Framework.
• Marketstack: supplies end-of-day market prices to our ingestion jobs. It receives no data about visitors.

Planned, not yet in use: a payment processor (Stripe), transactional email (Resend), and messaging alerts (Telegram) are planned features. None of them processes anything today; each will be added to this policy before it goes live (section 11).

6. Cookies

Reading the site sets no cookies. Signing in to an account sets the strictly necessary session cookies that keep you signed in (httpOnly, unreadable to page scripts) - the one purpose the law does not require a banner for, which is why there is none. Our standing commitment: only ever strictly necessary cookies plus cookieless analytics. If that ever changes, we will ask for consent before any non-essential cookie is set, not after.

7. Purposes and lawful bases (GDPR Art. 6)

• Serving the site and keeping it secure (server logs): legitimate interest, Art. 6(1)(f).
• Understanding aggregate readership (cookieless analytics): legitimate interest, Art. 6(1)(f).
• Font delivery (the Google Fonts request): legitimate interest in rendering the site as designed, Art. 6(1)(f), pending the planned self-hosting, which will remove this transfer entirely.
• Accounts and sign-in email (the account data in section 3): contract, Art. 6(1)(b) - we process your email because you asked for an account that works.
• Future features (billing, alerts): contract, Art. 6(1)(b), and consent, Art. 6(1)(a), as each launches (section 11).

8. Retention

Server logs are retained briefly by the hosting provider on rolling windows measured in days to weeks, then deleted. Analytics data is aggregate and contains no personal identifiers to retain. Local storage data lives on your device until you clear it. Account data is kept while your account exists and deleted when the account is deleted - delete your account yourself in Settings (with a paid subscription active, cancel it first; deletion opens once the paid period ends), or ask via section 13 and it is done. We hold no other personal data.

9. Your rights

Under the GDPR (and similar laws elsewhere) you have the right to access, rectify, and erase personal data concerning you, to restrict or object to its processing, to data portability, and to lodge a complaint with a supervisory authority in your country. California residents have the rights to know, delete, and correct, and to be free of discrimination for exercising them; we do not sell or share personal data, so there is nothing to opt out of.

In practice, exercising most of these rights against us is short work: apart from transient server logs and the account you may have created (email, sign-in timestamps, plan tier, and any profile details or saved follows you added - all of which we can show you or erase on request), we hold no personal data about visitors. Contact details for requests are in section 13.

10. Children

Tickertail is not directed at children under 16. Accounts require you to be at least 18 (Terms, section 3), and we knowingly process no children's data.

11. When features launch

Accounts have launched: sections 3, 6 and 7 above cover exactly what they add (an email address, a session cookie, and the profile details and follows you choose to save). Still ahead: subscriptions add a payment processor (Stripe, which will handle card details on its own pages so that we never see them - our database will only mirror whether a subscription is active), and messaging alerts add the messaging identity you choose to connect. Before each launch, this policy will be updated, the dateline at the top will move, and material changes will be announced on the site.

12. Changes

When this policy changes, the dateline at the top moves; material changes are announced on the site before they take effect.

13. Contact

[a dedicated privacy contact (privacy@ on the production domain) will be published here once the mail domain is live; the controller's postal address will appear with the imprint in the Terms of Service]