Privacy Policy
Last updated: 7 August 2026
This Privacy Policy explains how Rafael Luis Jacober Werlang (“Asserte”, “we”, “us”) collects, uses, and protects personal data when you use the Asserte service (the “Service”). We are the data controller. For any privacy question, contact hello@asserte.ai.
We sell confidence on high-stakes work, and privacy is core to that promise. This policy describes our actual practices.
1. What we collect
- Your task and any documents you provide. The text you submit and any files you upload (e.g. contracts, financials) so the Service can produce your audit. These are held only in memory for your session and are never written to disk — no database row, no file, no temporary copy.
- Your audit (the deliverable). The report the Service generates for you. It lives in server memory only, long enough to deliver: we email it to you as a PDF and keep it downloadable from the page for one hour, in case that email is slow to arrive. Then it is gone — no copy, and no record of what it said.
- Contact details and your account. The email address you give us to deliver your audit. Verifying that email with a sign-in code creates your account — your email is your key; we store no password. Your account holds your subscription and audit allowance only, never your documents or their reports. Sign-in codes are short-lived and single-use; a signed-in device holds a revocable token.
- Payment information. Processed by our payment provider (Stripe). We do not receive or store your full card details.
- Usage analytics. Content-free data about how the Service is used and how it performs — for example which step of the funnel you reached, timing, and conversion events. We do not store the content of your task in analytics. To recognise returning use without keeping your email in analytics, we may attach a pseudonymous identifier derived from a one-way, salted hash of your email — it cannot be reversed to your email and is not shared with third parties.
- Technical data. A session cookie to keep your session, and your IP address — which we anonymise (we discard the host portion, keeping only the coarse network prefix) before storing it for analytics.
- Coarse device information. Non-identifying buckets
— device type (mobile/desktop), browser family, operating system,
viewport size, and your browser’s preferred language
(e.g.
en-US) — derived in your browser and used only to understand how the Service performs across devices and languages. We do not collect or store a device fingerprint.
2. How we use it, and our legal bases
- To provide the Service — produce and deliver your answer (performance of a contract).
- To take payment (performance of a contract).
- To improve conversion and the product using content-free, IP-anonymised analytics (legitimate interests).
- To sign you in and keep your account — send sign-in codes, keep your devices signed in, and track your monthly audit allowance (performance of a contract).
- To send service and lifecycle messages and, where you opted in, product updates (consent / legitimate interests).
We do not sell your personal data, and we do not use your task, documents, or audit to train AI models.
3. Retention
- Your task and uploaded documents are held only in server memory for the duration of your session and are purged when the session expires. We never write your raw input to disk — not to our database, not to a file.
- Your audit report is never written to disk on our servers. It exists in server memory for one hour after it is generated: we email it to you as a PDF and keep it downloadable from the page for that hour, in case the email is slow to arrive. Then the download stops serving and the bytes are released. The copy we emailed is out of our hands — your mail provider and the relay that carried it may keep it, under their policies and not ours. That is what sealing is for.
- Sealing your report. Set a secure password or passphrase before the audit runs and the PDF is encrypted with AES-256 as it is built, so every copy is the same locked file: the one we hold for the hour, the one we email, and any that outlives it elsewhere. None of them opens without your password — including for us. We never store that password. It is dropped the moment the report is sealed, so we cannot reset it, recover it, or open a sealed report; there is no back door, and the seal is only as strong as the password you pick. Leave it blank and we send an ordinary, unencrypted PDF, which those providers may retain in the clear. Lose the file or the password, and the remedy is the same: run the audit again.
- Provenance, not retention. Each report includes a page listing a SHA-256 fingerprint of your inputs, so you can later verify exactly what was audited — this fingerprint is computed at generation time and printed into your report; we do not keep your inputs.
- Allowance records are content-free. To count your monthly audits we keep a metering row per run (timestamp, status, cost) with no task text, no title, and no report in it.
- Sign-in records. Sign-in codes expire within minutes and are stored only as hashes; a signed-in device’s token expires after ~30 days of inactivity and is deleted on sign-out.
- Analytics data is content-free (structure, timing, and an anonymised IP prefix) and may be retained to understand and improve the Service.
- Email and account records are retained while relevant to the purpose you provided them for, then deleted on request.
4. AI subprocessors and how your input is processed
To generate your audit, your task (and any documents) are sent to a panel of frontier AI models through OpenRouter, an AI model routing provider. OpenRouter engages the model providers that serve each request and is bound to handle your data under the limits we set on every call. The panel is built from models by leading AI labs and changes as we track and run whichever frontier models are strongest at any time.
Those limits are enforced on every request: it may reach only zero-data-retention endpoints — endpoints that do not store your input or output and do not train on it — and never a provider that would collect your data for its own use. Which provider serves a given request is chosen by OpenRouter at request time within those limits, so we record that choice as routing metadata — the provider’s name and nothing of your content — and can tell you which providers processed a specific audit.
Other processors we use:
- Stripe — payment processing.
- Postmark — outbound email relay.
- Hetzner — EU-based hosting.
Authentication is our own passwordless email-code sign-in — no third-party auth provider receives your identity data.
A current list of our processors — including the model providers reached through OpenRouter — is available on request at hello@asserte.ai.
5. Where your data is processed
We host in the European Union (Hetzner). Some AI and service subprocessors may process data outside the EU; where they do, we rely on appropriate safeguards such as Standard Contractual Clauses.
6. Your rights
Subject to applicable law (including the GDPR), you may request access to, correction of, deletion of, or a copy of your personal data, and you may object to or restrict certain processing. To exercise these rights, contact hello@asserte.ai. You may also lodge a complaint with your local data protection authority.
7. Cookies and local storage
We use two strictly necessary cookies: a session cookie to maintain your session, and — once you sign in — a persistent sign-in cookie so your devices stay signed in (revoked on sign-out). When you dismiss our cookie notice, a single flag in your browser’s local storage remembers only that choice — it never leaves your device. We do not use advertising or cross-site tracking cookies.
8. Security
We host in the EU on hardened infrastructure, encrypt data in transit, and minimise what we store. Your input and your report never enter long-term storage at all — they live only in memory for your session and are delivered, not retained. Where you set a password, your report PDF is sealed with AES-256 — a password we never store, cannot reset, and cannot recover.
9. Changes
We may update this policy; the “Last updated” date reflects the latest version. Material changes will be notified where appropriate.
10. Contact
Rafael Luis Jacober Werlang, Viale Leopoldo Muzii, 77 — Piano 3, 65123 Pescara (PE), Italy. Email: hello@asserte.ai.