Privacy
What this site keeps about you
Reading Helix Reader needs no account. The list below is everything the site stores about a visitor.
Waitlist sign-ups
If you join the new-question waitlist in the footer, we store your email address, the time you joined and a random removal token. No email is being sent yet. The removal link shown after you join deletes the address at once.
Contact messages
The contact form stores the email address you give, an optional name, your message and the time it arrived, so the editor can read it in the admin area. Messages are kept for at most 12 months and then deleted. They are never sold or shared.
Abuse limits
To slow down spam, the server keeps the network address of a waitlist or contact request in memory for up to one hour. It is never written to the database.
Stored in your browser
- primer_depth: the reading depth you picked (glance, read or deep).
- primer_theme: your light or dark page choice.
- primer_token: only for the editor who signs in to the admin area.
These are local storage entries, not cookies, and they never leave your browser. Clearing your site data removes them.
Services that see your requests
Requests to the site pass through Cloudflare, which delivers and protects it and handles your IP address and browser details under its own privacy policy. Fonts load from Google Fonts, so Google receives your IP address and browser details when a page asks for them. Source links open journals and regulators, which have their own policies.
What we do not do
No cookies, no analytics or tracking scripts, no ads and no profiles. Question pages count how often they are opened as a plain number, with nothing about who opened them.
Your choices
To remove a waitlist address, use its removal link. To have a contact message deleted, or to ask what we hold, write through the contact page from the same address.
Last updated 28 Oct 2026. See also the editorial policy, the privacy policy and about Helix Reader.