Subprocessors
The companies that process personal data for Laze on behalf of Reasoning Engine B.V., and the services you can connect yourself.
Subprocessors
Each one processes personal data for us under a data processing agreement.
| Name | Purpose | Data | Location | Transfer mechanism |
|---|---|---|---|---|
| Scaleway SAS | Hosting: the servers that run Laze, its databases, files, vault, apps and agent sandboxes | All account data and workspace content | France (Paris) | None, stays in the EU |
| Scaleway SAS | Backups: daily backups in Object Storage, encrypted before they leave the server | All account data and workspace content, encrypted | the Netherlands (Amsterdam) | None, stays in the EU |
| Cloudflare, Inc. | DNS, TLS and network protection for laze.so and app addresses; all traffic passes through it | IP addresses and the requests and responses in transit | Global network, United States company | EU-US Data Privacy Framework, standard contractual clauses |
| Scaleway SAS | Sending service email through Scaleway Transactional Email: sign-in links, email verification, invitations, password resets | Email address, name and the content of the email | France (Paris) | None, stays in the EU |
| Google LLC | Sign in with Google, when you choose it | Name, email address, profile picture and Google account id | United States, Google Ireland Limited for the EEA | EU-US Data Privacy Framework, standard contractual clauses |
| OpenAI, L.L.C. | Model inference for agents on Laze's own models (GPT-5.5 and GPT-5.4 mini), reached through the LangWatch AI gateway | What an agent sends to the model for a turn: messages, files and tool results it works with, and the answers | United States | EU-US Data Privacy Framework, standard contractual clauses |
| PostHog Inc. | Product analytics: in the browser, visits counted without cookies until you accept Product analytics, then with a first-party cookie and your account id; from our servers, account and workspace milestones such as signing up or creating a workspace | A random id or your account id, your workspace id, how you use the site, such as pages, clicks, scrolling and navigation, with all text hidden, and where your first visit came from; IP addresses are discarded | Germany (Frankfurt), PostHog's EU cloud, United States company | None for the data, which stays in the EU; standard contractual clauses for support access |
| Proxy-Cheap | Dedicated IP: a static home internet address, only for people who turn on a dedicated IP, for the domains they list | That person's agent and browser traffic to the listed domains, encrypted in transit; the IP vendor sees the address and the domain names, not the pages | United States (its terms are governed by Delaware law), the address in the country the person picks | Standard contractual clauses |
| LangWatch (Reasoning Engine B.V.) | LLM tracing, only for workspaces whose admin turns on the LangWatch integration: the traces of the agents Laze hosts go to the LangWatch project the admin picks. A self-hosted LangWatch endpoint is the workspace's own, not a subprocessor | Each agent turn's steps, tool calls, tokens, cost, timings and errors; at the Full level also the inputs, outputs and tool results, with vault values masked | European Union (LangWatch Cloud) | None, stays in the EU |
| Meta Platforms Ireland Limited | Measuring which ads bring sign-ups: the Meta Pixel in the browser and the Conversions API from our servers, only while Advertising is allowed | The pages you visit with the Meta Pixel's cookie ids, and at sign-up an event with your email address as a SHA-256 hash | Ireland, with transfers to Meta Platforms, Inc. in the United States | EU-US Data Privacy Framework, standard contractual clauses |
The LangWatch AI gateway
Agents on Laze's own models reach them through the LangWatch AI gateway, which Reasoning Engine B.V. runs itself, so it is not a third party. The gateway passes each request to the model provider listed above and keeps a record of what each agent used, for budgets and billing. Agents on your own Claude Code or Codex plan do not use it.
Services you connect yourself
These services are not our subprocessors: you or your workspace choose them, connect your own account, and they process the data under their own terms. You can disconnect any of them in Laze at any time.
| Service | What Laze does with it | Whose terms |
|---|---|---|
| Google Workspace (Gmail, Google Calendar, Google Drive) | Your agents read mail, write drafts, manage events and read files, with the access you approve | Your Google account's terms; Laze follows Google's Limited Use requirements |
| GitHub | Your agents read and change the repositories you give them access to | Your GitHub account's terms |
| Anthropic (Claude Code) | Claude Code on your own Claude plan, from your machine or on your agent computer, sends its requests to Anthropic | Your Claude plan's terms |
| OpenAI (Codex) | Codex on your own ChatGPT plan, from your machine or on your agent computer, sends its requests to OpenAI | Your ChatGPT plan's terms |
| WhatsApp Business (Meta) | Your workspace's own WhatsApp Business number and Meta app send and receive your customers' messages | Your Meta / WhatsApp Business terms |
| MCP servers you add | Any MCP server you connect, including the vendor servers in Laze's list, such as Notion, Linear or Atlassian, receives the requests your agents send it | That vendor's terms |
Changes to this list
We announce a new subprocessor on this page and by email to workspace owners at least 14 days before it starts processing personal data, so they can object. A data processing agreement under Article 28 of the GDPR is available on request from rogerio@langwatch.ai.
Contact
Reasoning Engine B.V., Gustav Mahlerplein 5, 1082 MS Amsterdam, the Netherlands. rogerio@langwatch.ai
Last updated 30 October 2026.