Privacy

Authentication

Signing in uses the platform's managed authentication. Your email address and sign-in timestamps are stored so the account can work. If you sign in with Google, no password is stored for this product.

Your workspace data

Radars, detection terms, evidence, clusters, scores, validation notes and briefs are stored against your account and protected by per-account access rules enforced in the database. Other users cannot read them. Custom research text you write is private by default and is never automatically shared with other users.

RSS and Atom processing

When you add a feed, the server fetches that address and stores matching items as evidence in your workspace, together with the item link, title, publication date and text as published. Feed addresses are checked before fetching to prevent requests to private network locations.

AI-assisted analysis and scoring

When you ask for classification, cluster suggestions or an AI-assisted score component, the relevant text is sent to the platform's managed AI service to produce that analysis. Results are stored separately as derived analysis and are labelled as such. Nothing is sent to an AI service unless you or your own automation settings trigger it.

Automation

Automatic collection and automatic classification are optional. When enabled, a scheduled server job collects from your feeds on your behalf and records the outcome of each run in your workspace. Daily AI usage is capped per account.

Feedback

Feedback you send is stored with your account so you can see its status. Administrators can read it to act on it and may add internal notes, which are not part of your record's user-facing content. Your wording is never published. Publication requires your explicit consent plus a separate, generalised suggestion written by an administrator, and you can withdraw consent at any time before publication.

Privacy-safe usage events

To improve the ready-made choices, the product records small structured events such as “a radar was created”, “a catalog problem with this identifier was selected”, or “a source was tested”. An event contains only your account id, a controlled event type, an existing catalog identifier, a coarse page category, a success or failure marker, a small number and a timestamp.

Events deliberately do not contain your custom problem text, search phrases, detection terms, exclusions, evidence content, validation notes, brief content, full URLs, IP addresses, browser fingerprints, tokens or any other browser-supplied data. There is no free-text field an event could hide such content in. These events are analytics only — never used for access decisions or charging.

Retention: events are kept while they are useful for improving the choice library and are removed manually when they are not. No automatic deletion schedule is implemented yet, and none is claimed.

No third-party tracking

There is no Google Analytics, no advertising pixel and no third-party tracker anywhere in the product.

Export and control

You can export your workspace, including your feedback and your own usage events, from Settings. Exports contain only your own data; internal administrator notes and other accounts' data are excluded. Scheduler tokens and credentials are never included.

Not yet covered

Company identity, registered address, governing jurisdiction, retention periods, subprocessor lists and compliance statements are intentionally absent because they have not been established. They will be added before public launch.