Preview · Updated 5 October 2026
Privacy in this preview
What the current app collects, and what still needs to be settled before launch.
Reading reports
Public reports do not require an account. Following a source link takes you to another website with its own privacy practices. The application does not include an advertising or audience-analytics integration; hosting services may keep technical request logs.
Issue reports
The issue form stores your message, optional source URL, category and the report edition involved. It also stores a hash for duplicate detection. It does not ask for your name or email. Anything you type may identify you, so avoid personal or confidential information. Reports and editor notes are private, not public comments.
Editor sign-in
The private workspace uses a session cookie and stores the editor account and a password hash. This is separate from reading the public site.
Research services
OpenAI processes research material to generate and critique analyses. Tavily receives search queries used to find sources. Reader issue submissions are stored for editorial review; submission does not automatically send them to either research provider.
Storage and retention
The database and its backups contain reader reports and editorial records. Automatic deletion of reader reports has not been implemented, so they remain stored until an editor removes them. Backup copies can persist separately. Retention periods, the production hosting location and a privacy-request contact must be confirmed before public launch.
Operator and privacy contact
[Name or organisation to be confirmed] · [contact email to be confirmed]. This preview notice describes the current implementation; those placeholders must be replaced before accepting public users.