Privacy Policy
Last updated: September 22, 2026
This document is only available in English. It governs how Legate handles data regardless of the language you read it in.
This Privacy Policy explains how Legate (“the Software”) handles data. It is a separate document from the End User License Agreement, which governs your right to use the Software - this document governs data.
The short version
Legate runs entirely on your own computer. The developer (Valentin Alekseev) does not receive, store, or have access to your mailbox content, your conversation history, your credentials, or any other data you process with the Software. The exceptions are the narrow, mechanical ones described under “The update check” and “License activation” below - neither involves your mailbox, conversation, or provider-credential data.
You, not the developer, are the controller/operator of any personal data you choose to route through Legate to a third-party AI, mail, task, or notes provider you configure. Legate’s role is limited to running that connection locally, using credentials you supply. This distinction matters under data protection law (see “Regional notices” below) and is the basis for everything else in this policy.
The Software does send data to third-party AI and productivity services - but only the ones you configure, using your own account and API key/credentials for each. That is a deliberate architectural choice (“bring your own key”): Legate never intermediates, resells, or has its own commercial relationship with any AI provider on your behalf.
What this means in practice
You are a direct customer of every service Legate connects to
When you configure a provider in Settings (Anthropic, Z.AI/GLM, Microsoft Azure AI Foundry or Azure OpenAI, TypeSafe, or a self-hosted LiteLLM proxy), Legate uses the API key or login credential you supplied to talk to that provider directly from your machine. You are a direct customer of that provider under their own terms of service and privacy policy, not an indirect user of a service the developer resells or intermediates. By configuring a provider, you are confirming you have your own account with, and have accepted the privacy terms of, that provider. Relevant policies as of this writing:
- Anthropic: https://www.anthropic.com/legal/privacy
- Z.AI: https://z.ai (see their own privacy policy)
- Microsoft Azure: https://www.microsoft.com/en-us/trust-center/privacy
- TypeSafe: https://typesafe.ai (see their own privacy policy)
The same applies to any mail, calendar, task, or notes server you connect via MCP (Exchange/Microsoft 365, Jira, OmniFocus, Obsidian, or any other server you add) - Legate connects to them with your own credentials, and your relationship with that service’s own terms and privacy practices is unaffected by your use of Legate.
What actually gets sent to a configured AI provider: whatever content is relevant to the request you make - typically message subject/sender/ body text for triage, routing, or summarization, and any other content you explicitly ask the Software to work with. Legate does not send your data to any AI provider you have not explicitly configured, and does not send data to more than one provider for the same request.
What stays local
Everything else lives only on your own device, in your own workspace directory:
- Your provider configuration and API keys (in
.envandconfig.jsonunder your workspace’s.claude-sdkfolder). - Conversation history and captured-item references (local SQLite databases in the same location).
- Call statistics (Settings -> Stats) - token/call counts used to show you your own usage; never transmitted anywhere.
You can inspect, back up, or delete these files directly - Legate does not encrypt them against you, the owner of the machine, and does not sync them to any server it operates.
Legate does not call home, with two narrow exceptions
- No analytics or telemetry SDK is built into the Software. (This project’s marketing website, a separate static site, is covered on its own under “The marketing website” below - it is unrelated to the desktop application and never runs inside it.)
- No crash reporting service is wired in.
- The update check. Legate can be built with automatic update checking (an unset build-time setting; as of this document’s date, no build the developer has published has this enabled). When it is enabled, the app periodically makes a plain HTTP request to a static file host to check the latest available version number - it does not send mailbox content, credentials, conversation history, or any other personal data in that request. Like any HTTP request, it necessarily discloses your IP address and basic client information (OS, app version) to whichever server the developer has pointed that check at, as an ordinary and unavoidable side effect of making the request - the same way loading any web page discloses your IP address to that page’s host. If a future release enables this, the developer will update this policy to name the actual host it points at.
- License activation. If you purchase a paid license, Legate sends a one-time activation request to a server the developer operates, containing the signed license blob you paste in and a hashed, non-reversible device identifier derived from your machine (used only to enforce the number of devices your license permits - never your mailbox, conversation, or provider-credential data). Like any HTTP request, this discloses your IP address to that server as an ordinary and unavoidable side effect of making the request. Separately, when your purchase is processed, the developer’s payment processor (Paddle) shares your email address and transaction details with the developer so a license can be minted for you - this is the same email you gave Paddle at checkout, governed by Paddle’s own privacy policy (available on Paddle’s website). The developer stores your email, a device count, and the device identifiers you’ve activated - hosted on Vercel (compute) and Upstash (data storage) - for as long as needed to administer your license (e.g. to help you if you need a device reset). This data is not used for marketing and is not sold or shared beyond what’s needed to run Vercel/Upstash as infrastructure providers. This exception does not apply if you never purchase or activate a license.
Third-party service outages, breaches, or policy changes are not the developer’s responsibility
Because Legate does not intermediate your usage of any third-party service, the developer has no visibility into, and no responsibility for, how those services individually handle, secure, or process the data you send them. If you have concerns about a specific provider’s data handling, review that provider’s own privacy policy and terms directly, or choose not to configure that provider.
The marketing website
The Legate marketing website (a separate static site from the desktop app, at the domain where you downloaded Legate) uses Vercel Web Analytics to count page views. Per Vercel’s own documentation, this does not use cookies and identifies a visit only via a daily-rotating hash derived from the request’s IP address, user agent, and host - it is not used to build a profile of you or to track you across sites or across days. See Vercel’s own privacy documentation for the current technical detail: https://vercel.com/docs/analytics/privacy-policy. This is the only data collection the website itself performs; it does not run inside, and is unrelated to, the desktop application covered by the rest of this policy.
Regional notices
The “short version” above - Legate itself processes essentially nothing, and you are the controller/operator of what you route through it to a provider you configure - is the basis for how each of the regimes below applies:
European Economic Area / UK. For the data flows described above (your content going to a provider you configured), you are the controller and Legate is best understood as outside that controller/processor relationship entirely - similar to how a text editor isn’t a controller for a document you later email to someone. You retain full GDPR/UK-GDPR rights (access, rectification, erasure, restriction, portability, objection) against each provider you directly configure, under that provider’s own privacy policy - not against the developer, who holds none of your data to act on. You also retain the right to lodge a complaint with your local supervisory authority at any time. For the narrow IP-address disclosure under “The update check” (if and when enabled), for license-activation data (email, device identifiers, device count), and for the marketing website’s analytics, the developer is that (much smaller) processing activity’s controller, and can be contacted using the details below. You retain the same GDPR/UK-GDPR rights against the developer for license-activation data as you would for any other controller.
United States (including California). The developer does not sell or share personal information for cross-context behavioral advertising, and does not knowingly meet the revenue/volume thresholds that trigger CCPA/CPRA “business” obligations. This policy is nonetheless intended to give the plain, accurate disclosure of practices that California’s Online Privacy Protection Act (CalOPPA) expects from any operator with California users, regardless of size.
Russia. Federal Law 152-FZ’s data-localization requirement attaches to whichever entity actually collects and stores personal data. For the data you route through a configured AI, mail, task, or notes provider, that entity is the provider itself, not the developer - the same responsibility-shifting logic as the other sections of this policy. This is not true, however, of license-activation data: if you are a purchaser in Russia, the developer does collect and store your email and device identifiers (see “License activation” above), outside Russia, on infrastructure the developer operates. Whether 152-FZ’s localization requirement attaches to the developer for this narrow dataset is an open legal question the developer has not resolved (see the note at the end of this document) - it is flagged here rather than asserted away.
Children’s privacy
The Software is not directed at children under 16, and the developer does not knowingly collect data from them, nor knowingly process a license purchase on behalf of one.
Changes to this policy
The developer may update this policy from time to time; material changes will be reflected in a new “Last updated” date above.
Contact
Questions about this policy can be sent to valentin.alexeev@valabs.space.
This document is a template and has not been reviewed by a lawyer. Have it reviewed by qualified counsel before relying on it for a commercial launch. Specific open questions flagged during drafting, not yet resolved: (1) whether an EU representative must be designated under GDPR Art. 27 once Legate is sold to EU/EEA users on more than an occasional basis; (2) whether Vercel Web Analytics’ cookieless model is fully exempt from the EDPB’s October 2024 guidance broadening ePrivacy Art. 5(3)‘s scope beyond classic cookies (Vercel’s own position is that it is exempt; this is a genuinely contested reading, not settled case law); (3) Russian 152-FZ’s actual extraterritorial reach against a foreign solo developer with no Russia-directed infrastructure is untested - the position taken above (that the obligation attaches to the provider the user configures, not the developer, for data routed through a third-party provider) is the best-supported reading, not a guarantee a Russian regulator would agree with it; (4) whether 152-FZ’s data-localization requirement applies to the developer’s own storage of Russian purchasers’ email/device data for license activation has not been resolved and needs specific legal review before this feature is sold to Russian customers. Confirm the actual production value of the update-feed host (see “The update check” above) before relying on this document’s description of it.