Leverine privacy policy
Last updated: 2026-11-05 · Effective: 2026-11-05 Controller: DTRH (dtrh.net) ("we", "us") · Contact: support@leverine.com
This policy describes what the Leverine browser extension and the Leverine licence service do with data. It is written to be read, not to be survived. Questions: support@leverine.com.
1. The short version
- Bring your own API key: the extension sends page content from your browser directly to the AI provider you configured. It does not pass through us. We never see it.
- Leverine Cloud: page content passes through our licence service to the same provider, because we hold the API key. We do not store request or response bodies.
- We do not run analytics or telemetry in the extension. There is no tracking pixel, no session recorder, no crash reporting service.
- Payment card data is handled entirely by our merchant of record. We never see a card number.
2. What the extension stores on your device
Stored in Chrome's extension storage, encrypted at rest only if you enable the passphrase vault:
| Data | Why | Retention |
|---|---|---|
| AI provider API keys you enter | to call the provider | until you delete them |
| Licence key and licence token | to unlock paid features offline | until you deactivate |
| Cloud session token (opaque) | to call the Cloud proxy | until you sign out or it expires |
| Conversations and messages | chat history you asked for | last 10 (free) or as pruned by your settings |
| Capability policy, grants, audit log | so you can see and control what was done | audit log capped at 500 entries |
| Settings, prompt templates, installed version | to run the product | until you clear data |
You can delete all of it at any time: Settings → Data & security → Delete all API keys / Delete all conversations, or uninstall the extension (which removes its storage).
3. What leaves your device, and to whom
Only when you send a message, or attach page content:
| Recipient | What | Purpose |
|---|---|---|
| The AI provider you selected (OpenAI, DeepSeek, Anthropic, a local Ollama server, or any endpoint you configured) | your message, plus whatever page content you attached | to generate a reply |
| Leverine licence service (Cloud only) | your message and attached content, forwarded to the provider named above | managed inference, metering |
| Leverine licence service (licensing only) | licence key, a random device id, extension version | activation and refresh |
| Leverine licence service (account only) | email address, device id, login-code attempts | sign-in, credit balance |
| Paddle (payment provider) | your email and purchase details | payment, invoicing, tax |
| Resend (email delivery) | your email address and the code or licence key | delivering that email |
Provider data handling is governed by that provider's own terms. If you configure a local Ollama server, the content does not leave your machine.
4. What the licence service stores
- Licences: a hash of the licence key (not the key itself), a short prefix for support, plan, status, seat/device limits, the email on the purchase, and activation timestamps.
- Devices: a random device identifier and its timestamps. It is not a fingerprint and does not identify a person.
- Accounts (Cloud): email address, credit balance, an append-only credit ledger, hashed session tokens, and a daily usage counter.
- Events: operational records such as
activate,deactivate,fulfilment.sent,revoke. These contain no page content.
We do not store prompts, model responses, screenshots, or page text. Requests are metered in memory and only token counts are recorded.
5. Payments
Purchases are processed by Paddle as merchant of record. Paddle collects and handles payment data, tax and invoices under its own policy. We receive only what is needed to issue your licence or add credits: an email address, a plan, and a transaction reference.
6. Cookies and tracking
The extension sets no cookies and contains no advertising, analytics or fingerprinting code. The landing page has no third-party scripts. We do not sell data and we do not "share" it for advertising.
7. Security
- Licence tokens are signed with Ed25519 and verified on your device; they work offline for up to 14 days.
- API keys never leave the extension's service worker and are never shown to a web page.
- Keys and tokens can be encrypted at rest with AES-256-GCM under a passphrase you enter (PBKDF2-SHA256, 600,000 iterations).
- Cloud credit balances and API keys are held server-side so they cannot be tampered with locally.
- Transport is TLS throughout.
No system is perfect. If you believe you have found a vulnerability, contact support@leverine.com before disclosing it publicly.
8. Legal bases and your rights (EEA/UK)
Where the GDPR applies, we rely on contract (providing the licence or Cloud service you asked for) and legitimate interests (keeping the service working and preventing abuse). You may request access to, correction of, export of, or deletion of your personal data, and object to processing, by writing to support@leverine.com. Deleting your account removes your email, balance and ledger within 30 days; transaction records required for tax are retained for the statutory period.
9. Retention
| Data | Retention |
|---|---|
| Licence and device records | while the licence is active, then 12 months after last use |
| Cloud account, balance, ledger | while the account exists; deleted within 30 days of a deletion request |
| Email delivery records | as held by the email provider's own retention |
| Payment records | as required by tax law |
10. Children
Leverine is not directed at children under 16 and we do not knowingly collect their data.
11. Changes
Material changes will be announced in the extension's changelog and on the landing page, with a new "last updated" date. Continuing to use the service after a change means you accept the updated policy.
12. Sub-processors
| Processor | Purpose | Location |
|---|---|---|
| Cloudflare (Workers, D1) | licence service, database, CDN | global edge |
| Paddle | payments, tax, invoicing | EU/UK/US |
| Resend | transactional email | US/EU |