Privacy · Last updated October 2026
Only the text you choose leaves the page.
Distl does not collect full page URLs or browsing history. When you request a summary, the selected text—or supported chat reply and preceding question, or open email content—is sent to Distl’s server and then to enabled AI providers to generate the result.
What Distl processes
- Text you select, or the open chat reply and the question before it, or the open email (sender, subject, body)
- Your length preference (short or more detail)
- A device identifier and signed session token for credits and rate limits
- A keyed hash of your network address for free-activation abuse prevention. IPv6 addresses are grouped by network prefix. Raw network addresses are not stored in these activation counters.
- Your verified email and account identifier when you sign in, plus session and billing records needed to manage access and purchases
What we do not collect
- Full page URLs or browsing history
- Passwords, payment card numbers, or bank details in the extension
- Selected text in server logs
Storage
Free guest activation limits allow up to five new installations per network per UTC calendar month. Existing installations keep their credit allowance. Network activation counters expire at the month boundary and renewal-rate timestamps expire after one hour; periodic cleanup removes expired counters. Shared networks may reach these limits.
Settings and an optional summary history stay in Chrome local storage on your device. History is off by default.
The service caches recent summary responses for about 10 minutes, with request text represented by a hash in cache keys. Completed summary output is also stored in account-scoped operation records with a 24-hour expiry to avoid charging twice for retries. Expired operation records are removed on access or by periodic cleanup, normally within a further six hours. Cache hits are not billed.
Sign-in codes expire in 10 minutes and are stored as keyed hashes. Account sessions expire after 30 days and can be revoked sooner. Email delivery is handled by Resend. Your email is sent to Resend to deliver a code; your selected text is not included in that email.
When enabled, Cloudflare Turnstile checks signup requests for automated abuse. CAPTCHA verification data is sent to Cloudflare and validated by our server before a sign-in email is sent. Gmail dot and plus aliases share one account quota. Account quota records survive deletion and recreation so the monthly free allowance cannot be reset using the same inbox.
Deleting an account removes its email and sessions. Pseudonymous account identifiers, quota state and billing audit records are retained to prevent repeated free grants and payment replay. Active subscriptions or unused paid credits must be resolved before self-service deletion. Contact support for questions about retained records or legacy device-bound purchases.
Third parties
When Google sign-in is enabled, Google verifies your identity. Distl requests only OpenID and email identity, not permission to read Gmail messages. We keep a keyed hash of Google's stable account identifier to preserve account ownership and quota history. Google OAuth credentials and provider access tokens are not shipped in the extension.
Summaries are generated by AI providers called from our server. Requests may be distributed across configured providers, and retried with another provider after a failure. Providers may include Google Gemini, OpenRouter, Cohere, Groq, Cerebras, Cloudflare Workers AI, Mistral, NVIDIA, Hugging Face, Ollama Cloud, OpenCode, Kilo Gateway, Pollinations, SiliconFlow, Zhipu, B.AI, Electron Hub, Sail Research, Septor Labs, and Dahl. Only enabled providers receive summary text. Provider API keys never ship in the extension.
Payments, when enabled, are handled by Lemon Squeezy.
Contact
Email: hello@distl.online
Your data and requests
You can ask to access, correct, or delete your personal data by emailing hello@distl.online. Use your account email where possible so we can verify ownership. Do not send passwords, sign-in codes, payment card details, or private documents. We may ask for the minimum information needed to verify your request.
You can also use the deletion controls on the account page. If an active subscription or paid balance prevents self-service deletion, email us to resolve it. Deletion does not automatically cancel a subscription. Some billing, security, and anti-abuse records may need to be retained; we will explain applicable limits when responding to your request. We handle requests within the deadlines required by applicable law.
AI services and other providers may process data in countries outside your own and under their own retention terms. Avoid submitting sensitive information or text you are not entitled to share. Contact us if you need details about processing before using Distl.
For browser storage and third-party services, see cookies and local storage. For the deletion steps, see request data deletion.
Optional website analytics
With your permission, Distl uses Google Analytics to measure visits, returning browsers and traffic sources on public website pages. Google Analytics uses first-party cookies; a browser count is not an exact count of people. We do not send account details, document text or URL query strings through this integration. Advertising personalization and automatic form tracking are disabled.
You can decline, withdraw consent or exclude this browser using Analytics settings in the footer. Declining does not affect Distl. Your choice is stored in this browser for up to 180 days. Analytics identifiers are configured to expire after 30 days. Clearing cookies or using another browser can make you appear as another visitor. See how Google uses information from sites that use its services.