Privacy.

Last updated: October 12, 2026

I run CoralTicker by myself. This page says what the site keeps about you, why, and how to get a copy, have it corrected or have it removed. I keep it up to date with what the site keeps.

Questions and requests go to coralticker@gmail.com. On this page, "I" means the person who runs CoralTicker.

Browsing without an account

You can read the guides, the findings pages and the public parts of the site without signing up.

Visits are counted with a privacy-focused analytics service that sets no cookies and reports totals: pages viewed, countries, browsers and the sites that linked here.

My hosting provider keeps server logs, including IP addresses. I use those logs and the hosting provider's security tools to run the site and to detect and block abuse. Logs are kept for a limited time, or longer when I need them to investigate or enforce the terms.

Cookies

The site sets these cookies, and none of them follows you to other sites:

No other company collects information through CoralTicker about what you do across other sites. Because nothing here tracks you across sites, a browser's Do Not Track setting doesn't change anything.

The email digest

If you sign up for the daily digest, I keep your email address, when you signed up and when you confirmed, and which version of the terms you agreed to. Mail goes out through Resend.

Every digest has an unsubscribe link. Unsubscribing stops the mail straight away. I keep the address marked as unsubscribed so it isn't mailed again by mistake. If you want it removed entirely, email me and I'll delete it.

The digest is separate from an account. Deleting your account does not unsubscribe you, and unsubscribing does not delete your account.

An account

To make an account I keep:

New passwords are checked against a public list of passwords that have already leaked. The password itself never leaves the site.

When you sign up and while you're signed in, I keep a record of what the account reads and technical details of the connection, such as network address and browser. I use it to run accounts and their limits, enforce the terms, protect the site and its data, and bring or defend legal claims. I can limit or end an account that is used against the terms, and I keep a record of what I did and why.

Failed sign-in attempts are kept for a limited time, to protect accounts from password guessing.

Getting a copy, or a correction

Email me from the address on the account and ask. I'll send you a copy of the personal information I hold about you, or correct anything that's wrong. Where a record was made to detect or investigate misuse, I may describe it rather than send it in full, as far as the law allows. There is no download button or export page.

Deleting your account

You can delete your account from the account page. When you do, I delete your email address, password and sessions. Records of how the account was used are kept for a limited time after that, or longer where I need them to enforce the terms or protect the site, and are then deleted or reduced to totals that don't identify you. If I ended the account for breaking the terms, I keep a record of that, including after the account is deleted, so the terms can be enforced.

Who else sees anything

Only the services that run the site: Vercel (hosting), a database provider, Resend (email), Cloudflare (visit counts) and Have I Been Pwned (the leaked-password check). I don't sell data, share it for advertising, or hand it to vendors.

I also share information when the law requires it, or when I need to in order to enforce the terms or protect the site, for example with a lawyer, a court, or a service hosting a copy of data taken from CoralTicker.

Changes

If I change what the site keeps, I update this page and the date at the top. If a change means I'll use information I already hold about you in a materially different way, I'll email account holders before it applies to that information.