Privacy
What this site records — and what it never does.
NeuralRing sells the absence of unnecessary data collection, so we hold ourselves to it here. This page states plainly what the site and the service record, where each runs, and how long anything is kept. It describes facts, not legal conclusions.
The front door — visitor measurement
We measure our own site with self-hosted Umami running on our own Postgres in the EU — no Google, no hosted analytics service, no external operator. It is cookieless: it uses a hash of your IP address and user-agent salted with a key that rotates daily, and the raw IP is never stored. It records anonymous pageviews and visitor counts, the referrer's host (never the full referring URL), the page's route pattern (for example /verify/[requestId], never a real request id), and up to five campaign parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term). Any other query parameter is dropped before the event is sent. The admin console is never measured. White-label tenant sites are never measured — that is their operator's business, not ours. Site-measurement rows are kept 365 days.
Your API requests and inference
Prompts and completions are NOT logged by default — the same default OpenRouter uses; your org admin may opt your org in, for your org only. What is always recorded for every request is attestation metadata — where inference ran, under whose jurisdiction, at what assurance level, the routing decision, and token counts — and never the content itself. That record is kept in the EU, in a tamper-evident hash-chained store, for at least six months, so an operator's compliance team has an audit substrate. Site measurement is entirely separate from this and is never part of it.
Signing up
When you create an account we read, only at the moment you submit the form, the referring site's host and any campaign parameters in the URL, and store them once against your organisation so we understand where sign-ups come from. We set no cookie and store nothing on your device for this — which means it is last-touch only: if you arrived on a campaign link earlier and sign up later, it records as direct.
Where it runs
Everything here runs on EU infrastructure we operate ourselves, with no US processor in the path. The analytics container is on an internal-only network with no route to the internet, its update-check and telemetry are switched off, and it makes no outbound connection.
Deletion and questions
To request deletion of your account and the data associated with it, or to ask anything about this page, email privacy@neuralring.eu. There are two ways we can act on it, and which one applies depends on what your account has done. If nothing has been metered and no money has moved, we delete the account outright: the user, the organisation, its API keys, provider credentials, sessions, sign-in history and sign-up attribution all go. If your account has metered usage, credits, payments or invoices, we erase the identity instead and keep those records: the email, name and password are replaced so the account can no longer be signed into, every session and credential is removed, and every key is revoked — while the usage rows, the credit ledger, the payments and the invoices remain, because they are the billing record. In both cases the attestation trail stays exactly as it was: those records are content-free, hash-chained and signed, and removing one would break the chain for everyone else who relies on it. We tell you which of the two we did.
This page describes what the site records and where. Whether your particular use of NeuralRing requires a specific consent control is a question for your own counsel; we set out the facts so they can make that call.