Privacy

This page explains, in plain words, what Noticer keeps and why. The full privacy notice for buyers is on the service: https://noticer-mpp-ee54698-production.up.railway.app/purchase/privacy.

This website

noticer.dev is a set of static pages. It runs no scripts, sets no cookies and has no sign-in. Links to Start, the API docs and the terms go to the Noticer service.

What the service stores

• For each check: the public URLs you submit, the declared scope, source snapshots, observation times, the verdict, and order and payment identifiers. These are needed to run the check and give you its evidence package.
• For a self-service account: an account ID, your consent to the terms and their version, the time you enrolled, and a record of which free checks were used. Your private buyer key and enrollment key are stored only as one-way hashes.
• To limit sign-ups, the service counts enrollments per hour per network address. The address is stored only as a keyed hash, and these counters are removed after about two hours, at the next sign-up.
• Card details go to Stripe, not to Noticer. Noticer keeps order and payment identifiers to match a payment to its evidence package.

Submit only public records you are allowed to read. Do not put passwords, access tokens or private data in a check.

How long data is kept

Unpaid orders that were prepared but never started are deleted after about 10 minutes. Sign-up counters are removed after about two hours, at the next sign-up. Other check and account records have no automatic deletion period; they are kept so evidence packages stay retrievable and free-check limits stay consistent.

Deletion and questions

To ask for deletion, or with any privacy question, email hello@noticer.io. Include your order ID or account ID. Never email your access token, buyer key, card details or other credentials.