LexAI publishes this list of sub-processors in accordance with Art. 28(2) GDPR. We notify you at least 30 days before engaging a new sub-processor.
Last updated: June 2025

LexAI Technologies, s.r.o. (hereinafter "LexAI") publishes this current list of sub-processors -third parties that process personal data of users in the course of providing the LexAI platform -in accordance with Art. 28(2) GDPR and the commitments made in the Privacy Policy and Data Processing Agreement (DPA).
Change notification: We will notify you by email at least 30 days in advance of engaging a new sub-processor or making a material change to an existing one. Controllers (enterprise customers) with a DPA in place with LexAI have the right to raise a reasoned objection within 14 days of notification.
| Sub-Processor | Jurisdiction | Data Location | Purpose | Data Processed | Transfer Mechanism |
|---|---|---|---|---|---|
| Anthropic, PBC | USA | USA | AI query processing (Claude API) | Conversation content, documents submitted for analysis | Standard Contractual Clauses (SCCs) under Art. 46 GDPR |
| Supabase, Inc. | USA | EU – Frankfurt | Database and user authentication | All user data (stored in encrypted form only) | Standard Contractual Clauses (SCCs) |
| Vercel, Inc. | USA | USA / EU | Serverless hosting and edge functions | Request logs, API calls | Standard Contractual Clauses (SCCs) |
| Hetzner Online GmbH | Germany (EU) | EU – Frankfurt | Proprietary servers (vector database, security logs, document processing) | Security logs, document processing for export/import | Within EEA -SCCs not required |
| Qdrant | EU | EU – Frankfurt (self-hosted on Hetzner) | Vector database for public legal sources | Embeddings of public legal sources -no user data | Within EEA -SCCs not required |
| Sub-Processor | Jurisdiction | Data Location | Purpose | Data Processed | Transfer Mechanism |
|---|---|---|---|---|---|
| Stripe, Inc. | USA | USA (EU compliance) | Payment gateway, subscription management | Payment details, billing information, subscription ID | Standard Contractual Clauses (SCCs); EU–U.S. Data Privacy Framework |
| Sub-Processor | Jurisdiction | Data Location | Purpose | Data Processed | Transfer Mechanism |
|---|---|---|---|---|---|
| Twilio SendGrid | USA | USA | Transactional email communication (notifications, account verification) | Email addresses, content of notification emails | Standard Contractual Clauses (SCCs) |
| Sub-Processor | Jurisdiction | Data Location | Purpose | Data Processed | Transfer Mechanism |
|---|---|---|---|---|---|
| SerpAPI | USA | USA | Web search within legal research | Search queries (without personal user identifiers) | Standard Contractual Clauses (SCCs) |
| Brave Search | USA | USA | Alternative web search | Search queries (without personal user identifiers) | Standard Contractual Clauses (SCCs) |
| IPInfo | USA | USA | IP address geolocation for security purposes | User IP addresses | Standard Contractual Clauses (SCCs) |
Some sub-processors are located or process data outside the European Economic Area (EEA), in particular in the USA. All such transfers are safeguarded by one or more of the following mechanisms:
A copy of the relevant SCCs can be provided upon request to controllers with a DPA in place with LexAI. Requests should be sent to support@lexaitechnologies.com.
Anthropic (AI processing): Conversation and document content is transmitted to Anthropic's AI models via a commercial API. Anthropic does not use data submitted via the API to train its models. Due to LexAI's zero-knowledge architecture, data is encrypted directly on the user's device before being sent to LexAI's servers -it is transmitted to the Anthropic API in decrypted form solely for the duration of query processing.
Qdrant: This vector database is operated as a self-hosted instance on Hetzner infrastructure (EU – Frankfurt) and contains exclusively embeddings of publicly available legal sources (Czech case law, legislation, EU sources). No user data is stored here.
Supabase: Data is stored exclusively in encrypted form in accordance with LexAI's zero-knowledge architecture. Supabase has no access to unencrypted conversation or document content.
| Version | Date | Change |
|---|---|---|
| 1.0 | June 2025 | Initial publication |
This document is updated on an ongoing basis. The date of the last update is indicated in the header. Archived versions are available upon request at support@lexaitechnologies.com.