1. Who holds the data
Sentinelleai (a registered sole proprietorship), established in Quebec, Canada — the full postal address is provided on request, and to any authority that asks. Questions and requests go to info@sentinelleai.app.
2. What is collected
- Your account. An e-mail address, a password stored only as a hash, session records, the addresses you last signed in from, and — if you turn it on — a two-factor secret.
- What you ask us to examine. The targets you submit, and the findings produced about them: severity, file, line, and the reasoning behind each one.
- What an agent you install sends. If you deploy the host agent, the events it reports about that host — file changes, process and network observations, alerts.
- Actions taken. Every protective action, with the identity that ordered it and the reason given, in the evidence ledger.
- Your acceptance of these pages. When you accept the terms and this page, we record which version you accepted, when, how (the sign-up form or the acceptance page), and the network address and browser identifier the request came from — the evidence that you agreed to that text.
- Billing. Stripe holds your payment details. We receive the subscription state and the invoices, never your card number.
3. What is deliberately not kept
A repository cloned for a scan, or an archive uploaded for one, lives in a temporary directory for the duration of that scan and is removed when it ends, whether it succeeded or failed. The findings stay; the source does not.
There is no analytics script, no advertising pixel and no third-party tracker on this site. The only cookie set is the session cookie, which is HttpOnly, restricted to same-site navigation, and exists so that being signed in survives a page load.
4. Where it is processed
The service runs in the United States. For a real incident, analysis of a mid-sized or larger case bursts to a graphics processor rented in the European Union for the duration of that analysis and no longer. No hyperscaler and no model of Chinese origin sits anywhere in that path.
5. Who else processes it
- Stripe — payments, invoicing and the billing portal.
- Model providers — Anthropic, and OpenRouter as a router to other vendors, for the multi-model review that runs after the deterministic scanners and for the assistant on the public site. The assistant is given the published documentation and your question, nothing from any account.
- A rented graphics processor in the EU — only for incident analysis, only for its duration.
- Our hosting and e-mail delivery — the servers that run the service and send you reports and alerts.
Where a scan reads a public source on your behalf — a chain explorer, a vulnerability feed, a certificate transparency log — that source sees the request. It is told what is being looked up, not who asked.
6. How long it is kept
Findings and reports stay while your account exists, because their value is the comparison between one scan and the next. Material submitted for an incident is kept briefly and deleted after the analysis. Ledger entries are kept for as long as the record has to be verifiable. The record of your acceptance of these pages is kept while your account exists and for three years after it is closed; the network address and browser identifier in it are not copied into the ledger.
7. What you can ask for, and one honest limit
You can ask for a copy of what we hold about you, a correction, or deletion of your account and its data. Write to info@sentinelleai.app.
The limit, stated plainly: the evidence ledger is append-only and chained, which is exactly what makes it worth anything as evidence. Entries recording that a protection acted cannot be edited or removed after the fact, including by us. Deleting your account removes your account data and stops the service; it does not rewrite that record.
8. How it is protected
Passwords are stored as hashes with a slow key-derivation function, sessions are cookie-based and expire, two-factor authentication is available, and administrative actions are recorded. Sensitive values held on your behalf are encrypted at rest when an encryption key is configured on the installation.
9. Changes
The current version is always at this address, with its effective date at the top. A material change is announced to your account address before it applies.