Rethinking data residency for the AI era
For most of the SaaS era, data residency meant one thing - where your data was stored. For a modern AI tool, storage is only part of the answer. You also need to know where AI processing happens, what Account Data crosses borders to run the service, and how data moves when you connect other tools.
We were inspired by WorkOS's article Why authentication doesn't need to stay local, which describes how large software companies split their data by what it contains. Our answer has two parts:
Customer Data is stored and processed in Europe. Account Data may be processed globally.
Europe is defined as the European Economic Area (the 27 EU member states plus Iceland, Liechtenstein and Norway) and Switzerland. The GDPR applies across the EEA, and the European Commission recognises Switzerland as giving personal data an adequate level of protection, so data can move between them without extra safeguards. Microsoft's EU Data Boundary and OpenAI's European data residency draw the same line.
Why Europe? Jamie started in Europe and focuses on regulated industries, so we want to give our European customers strict compliance guarantees.
Content, processing and the control plane
A modern software product works on three planes:
The content plane holds what you put into the product and what it creates for you. In Jamie, that means meeting audio, transcripts, summaries, notes and tasks.
The processing plane is where the computing happens. In Jamie, that means speech-to-text, the AI models that write your summaries and answer your questions, and search.
The control plane runs the account itself: sign-in, billing, support and diagnostics.
Many vendors keep content in the region but say little about where it is processed. Jamie keeps both content and processing in Europe. Your meetings are transcribed, summarised and searched in the same region where they are stored. Only the control plane may run globally.
Customer Data
Customer Data is all data you and your team submit to Jamie, or that Jamie creates from it, such as:
meeting audio, transcripts, summaries, notes and tasks
meeting titles, dates and calendar events
the names and email addresses of the people in your meetings
the questions you ask Jamie's AI and the answers it gives
speaker profiles, including voiceprints, and speaker clips
search indexes built from any of the above
Account Data
Account Data is the information we need to run, secure, bill and support your account. For example:
Identity: your name and the email address you sign in with.
Technical: IP address, browser and device, app version, sign-in and security events, and operational logs. Operational logs only record system identifiers and do not contain Customer Data.
Subscription and workspace: workspace name, plan, seats and billing information.
Usage: the features you use, counts, durations and error codes, such as the number of meetings recorded.
Settings and consents: records of the settings you choose and the consents you give.
An email address can fall on either side of this line. The address you sign in with is Account Data. The addresses of the people in your meetings are Customer Data.
Why the control plane runs globally
Account Data is a different kind of information from Customer Data. Your email address and the time you signed in show that you use Jamie. They do not show what was said in a meeting or what your team decided.
Like the control plane of any modern online service, ours relies on services that run globally. Signing in with Google, Microsoft or Apple, paying by card, contacting support and receiving an email about your account all depend on them. Running the control plane globally lets these services work, while the content of your meetings stays in Europe.
Large providers draw the same line in their European offerings. Microsoft's EU Data Boundary keeps its customers' data in the EU, and its documentation says that Microsoft "may replicate limited Microsoft Entra directory data (including username and email address) outside the EU Data Boundary to provide the service". Microsoft also processes sign-in logs centrally so that it can detect attacks that span several regions.
Other providers also keep content in the region and let some of the data that runs the account leave it:
Slack stores messages, files and search indexes in your chosen region and keeps member profiles and usage data outside it. Slack also states that "login requests will be sent to the U.S."
OpenAI keeps prompts, responses and model inference in Europe. Workspace names, billing information and user logins may be stored elsewhere, and OpenAI notes that "authentication, routing, and analytics may still occur outside the selected region".
GitHub keeps code, pull requests, issues and user data in the EU. Billing information, support requests and pseudonymised telemetry may be stored outside it.
Integrations and sharing
Jamie is most useful when your notes reach the tools your team already works in. Customer Data stays in Europe by default and only moves to another service when you choose to send it there.
When you connect a CRM, Slack, a calendar, a webhook, the API or the MCP server, Jamie sends that tool the data you choose.
When you email a summary, share a link or export a file, Jamie delivers it to the recipient you choose.
When you sign in with Google, Microsoft or Apple, or pay by card, those providers handle your sign-in or payment under their own terms with you.
You decide which tools to connect and what they receive. Once the data reaches a service you chose, that service decides where it is stored.
Subprocessors
Every vendor that processes data on our behalf is listed at trust.meetjamie.ai/subprocessors, with what it does and where. Several of them are global companies, so for each one that handles Customer Data, we use its European region and have agreements in place that keep storage and processing there.
For even stricter compliance requirements
If you have concerns about the US CLOUD Act, the Enterprise plan lets you bring your own encryption key (BYOK / CMEK). In 2027, we'll be adding a bring-your-own-cloud (BYOC) option and a US region alongside our European region.