Last updated: 25 October 2026
Third parties that receive the text you submit to Lenz, or data derived from it. Applies to the website, the API, the connector for AI assistants and WhatsApp.
Text you submit
These providers receive the text you submit, or text that can contain it. SendGrid and WaSenderAPI apply only to checks submitted on the website or WhatsApp, never to the API.
| Provider | What it receives | Purpose | How long it keeps it1 | Location |
|---|---|---|---|---|
| Google Cloud (Google LLC) | Everything Lenz stores and processes: submitted text, results, Word documents you upload, account data, logs | Hosting, database, file storage, task queues, caching, logs | Set by Lenz, see the Privacy Policy; Google’s backup and deletion schedules apply on top | United States |
| Anthropic | Submitted text and text derived from it: claims, search queries, source passages, follow-up questions | Claim analysis | Served on Google Cloud Vertex AI, where the text Lenz sends is not stored. Accounts set to zero retention run on Vertex AI with zero data retention. Other accounts: if a call falls back to Anthropic directly, up to 30 days; up to 2 years if flagged as breaking its usage policy | Any Google Cloud region worldwide (Vertex AI); stored in the United States and processed in the US, Europe, Asia or Australia when routed to Anthropic directly |
| Google (Gemini, via Vertex AI) | Submitted text and text derived from it: claims, search queries, source passages, follow-up questions | Claim analysis | The text Lenz sends is not stored. Accounts set to zero retention run with zero data retention: grounded checks use Web Grounding for Enterprise, which logs nothing. Other accounts: the queries and context sent to Google Search in a grounded check, up to 3 days, not linked to Lenz or you | Any Google Cloud region worldwide |
| OpenAI | Submitted text and text derived from it: claims, search queries, source passages, follow-up questions | Claim analysis | Up to 30 days for abuse monitoring; longer where the law requires | United States |
| Perplexity | Submitted text and text derived from it: claims, search queries, source passages, follow-up questions | Claim analysis | Each request and reply is stored. Not used for accounts set to zero retention | North America |
| xAI | Submitted text and text derived from it: claims, search queries, source passages, follow-up questions | Claim analysis | Not kept: Lenz’s xAI calls on xAI directly and Google Cloud Vertex AI run with zero data retention. xAI logs timing, token count and model for billing, never the text | Global (xAI directly); any Google Cloud region worldwide (Vertex AI) |
| SendGrid (Twilio) | The claim, its summary and answers to your follow-up questions, in emails about your checks | Sending email; used only for checks you submit on the website or WhatsApp | Not yet confirmed | United States |
| WaSenderAPI | Messages you send to and receive from the Lenz WhatsApp number, and your phone number | Connecting the Lenz WhatsApp number; used only if you use Lenz on WhatsApp | Not yet confirmed | Not yet confirmed |
¹ The provider’s own period after it has answered. How long Lenz keeps text is in the Privacy Policy.
Global and Any Google Cloud region worldwide mean the provider’s global endpoint: it may run a request in any region it operates in and gives no data-residency guarantee.
Anthropic, Google, OpenAI, Perplexity and xAI do not train their models on what Lenz sends them.
Data derived from your text
These providers never receive the body of the text you submit. They receive something written from it, such as a search query or a name to look up, or the link itself when you submit a link. For a citation check: the cited links and DOIs, and the page of a statute, regulation or EU instrument the draft cites, not the draft. The timestamping services receive only a hash.
| Provider | What it receives | Purpose | Location |
|---|---|---|---|
| Web search providers: Exa, Firecrawl | Search queries derived from the claim, links you submit or that sources point to, the links a checked draft cites, the page of a statute, regulation or EU instrument it cites, and the opinion page of a case it cites | Web search and reading web pages | United States |
| International DOI Foundation (doi.org) | The DOI only; no account data or submitted text | Checking that a DOI cited in a checked draft is registered | United States |
| Crossref | The DOI only; no account data or submitted text | Looking up the registry record of a DOI cited in a checked draft | United States |
| OpenAlex (OurResearch) | The DOI only; no account data or submitted text | Looking up the registry record of a DOI cited in a checked draft | United States |
| CourtListener (Free Law Project) | The case citation only, when Lenz’s own index does not hold it; no account data or submitted text | Checking that a case cited in a checked draft exists, and reading its opinion | United States |
| Wikimedia Foundation (Wikidata) | Names of the people, organisations, places and events a claim mentions | Telling apart entities that share a name | United States |
| Webshare | Requests to fetch YouTube transcripts; it does not see the video or the transcript | Network proxy; used only when you submit a YouTube link | United States |
| Namirial (qualified trust service provider) | A SHA-256 hash of a warranty certificate: no text and no personal data | Fixing the time a certificate was issued; used only when one is issued | European Union (Italy) |
| OpenTimestamps calendars | The same SHA-256 hash, which they publish permanently | A second, public record of the time a certificate was issued; used only when one is issued | Public servers run by independent operators |
Account data
These providers process account data: your email address, billing details, usage, errors and the messages you send us. They do not receive the text you submit for checking.
| Provider | What it receives | Purpose | Location |
|---|---|---|---|
| Stripe | Billing details and payment information | Payments and subscriptions | United States |
| WorkOS | A pseudonymous account identifier and connection details | Authorization when you connect an AI assistant | United States |
| HubSpot | Your email address, plan and usage of Lenz, contact-form messages and chat messages | Customer support and account management | European Union (Germany) |
| SendGrid (Twilio) | Your email address and the emails we send you | Sending sign-in codes and account email | United States |
| Discord | Account events and contact-form messages | Notifications to the Lenz team | United States |
| Sentry | Error reports: error type, where in our code it happened, which request it came from, your account identifiers. Built from a fixed list of fields, none of which carries submitted text | Error monitoring | European Union (Frankfurt, Germany) |
Error reports Sentry stored before 25 September 2026 can contain the text being processed when the error happened. They are deleted when Sentry's retention period ends.
Changes
Updated when a provider is added or removed, or when what it does with your text changes. See the Privacy Policy and, for the API, Data We Process in the Terms of Service. Questions: contact.