Subprocessors
Version 2026-11-draft-2
[LEGAL ENTITY NAME] uses the providers below to run Lyra. Each processes personal data on our behalf under a data processing addendum (DPA) with us. This list forms part of the privacy policy and takes effect on [EFFECTIVE DATE]. We update it before adding a provider; questions go to [LEGAL EMAIL].
The list
| Provider | Purpose | Data it receives | Region | DPA |
|---|---|---|---|---|
| Anthropic | the language model behind the assistant in the desktop app, AI design and review, and AI import | your messages to the assistant, the files you drop into the chat (such as floor plans, spec sheets and pictures) and the parts of the open project it reads to answer or act; the design data of the areas you ask AI design to work on; the URL, datasheet or photo you give AI import | [REGION] | https://www.anthropic.com/legal/data-processing-addendum |
| Supabase (its DPA names Supabase Pte. Ltd.) | the database, sign-in and private file storage behind the platform | every record in the data model: accounts, companies, gift invitations, projects and versions, images, private items, licences, AI metering, support transcripts, logs, newsletter and telemetry | [REGION] | https://supabase.com/legal/dpa |
| Railway | hosting of the website, the platform's servers (the desktop app's API, client 3D links, legal pages, email and payment return pages, the staff admin panel) and scheduled jobs | everything that passes through the servers in transit, including requests, sessions and logs | [REGION] | https://railway.com/legal/dpa |
| Resend | transactional email: invitations to a company or to gifted access, renewal reminders, support and contact-form messages, the newsletter | email address, name, the message content and delivery events | [REGION] | https://resend.com/legal/dpa |
| Stripe | subscription payments, invoices and the billing portal | billing name, address, email, VAT number, card details entered on Stripe's pages (we never hold card numbers), payment history | [REGION] | https://stripe.com/legal/dpa |
Each provider has its own subprocessors, listed on its site: Anthropic at https://trust.anthropic.com/subprocessors, Supabase at https://supabase.com/legal/customer-resources/subprocessor-list, Railway at https://trust.railway.com, Resend at https://resend.com/legal/subprocessors and Stripe at https://stripe.com/service-providers/legal.
What was verified, and what was not
Checked on 2026-11-04 by fetching each page:
- Anthropic: the DPA page loaded with the title "Data Processing Addendum", effective 24 February 2025; it points to the subprocessor list for its own providers. The subprocessor list page (anthropic.com/subprocessors redirects to trust.anthropic.com/subprocessors) loaded only its title without a browser, so its contents were not read; check it in a browser.
- Supabase: the DPA page loaded with the title "Data Processing Addendum", version dated 1 August 2026, naming Supabase Pte. Ltd.; its subprocessor page loaded and links to PDF lists (latest 12 October 2026) that were not opened. The hosting region is chosen per project when the database is created; put the chosen region in the table.
- Railway: the DPA page loaded with the title "Data Processing Addendum"; it states that primary processing takes place in the United States on Google Cloud Platform. The trust centre loaded and lists its subprocessors.
- Resend: the DPA page loaded with the title "Data Processing Addendum", last updated 31 December 2025; it states that primary processing takes place in the United States. The subprocessor page loaded (last updated 27 August 2026).
- Stripe: the DPA page loaded with the title "Data Processing Agreement", last updated 28 September 2026, and links to the sub-processor list, which loaded with entity countries.
Not verified: the exact contracting entity for each provider under our own account (it can depend on where [LEGAL ENTITY NAME] is registered), the regions in the table, and whether each DPA is accepted automatically with the account or needs to be signed. The lawyers should confirm each before publication and set [REGION] per row.
Changes
We add a provider to this list before it starts processing personal data and note the date of each change here.
| Date | Change |
|---|---|
| [EFFECTIVE DATE] | first published |