Privacy

What we collect

Everything here comes from you using the service. We do not buy member data and we do not scrape it from anywhere.

• Your contact details. The email address and phone number you sign up with, your name, and whatever else you choose to tell your assistant about yourself.
• Your conversations. What you say on calls, the messages you exchange over WhatsApp, SMS, and email, and the notes and summaries your assistant writes from them.
• Call metadata. When a call happened, how long it ran, which number it came from, and the transcript of what was said.
• The work itself. The tasks you hand over, their status, and what your assistant did about them, including the calls they made on your behalf.
• Payment details, if you give us one. A card goes straight from your browser to Stripe. We keep Stripe's reference to it and never see or store the card number.
• Basic website analytics. Page views on airmond.com, counted by an analytics tool we host ourselves and serve through our own domain. No advertising trackers, no ad networks.

Where it is stored and processed

Your profile, tasks, messages, and call notes live in a Postgres database on European Union infrastructure. That is where your record sits at rest, and it is why we can say your account data is stored in Europe.

Voice is the one honest exception, and we would rather say it plainly than bury it in a list. When you or your assistant speak on a call, the audio and the transcript are not just passing through a US server on their way to our EU database: they are processed and stored by ElevenLabs, our voice provider, on their US infrastructure. European data residency exists as an option from ElevenLabs, but only on their Enterprise plan, which we are not on today. If keeping voice inside the EU matters to you, email us and ask where that stands; we would rather you hear it from us than assume otherwise.

Everything else that touches your data outside the EU database does so in passing, not at rest: a server function reads or writes it, a model thinks about it and is not allowed to learn from it, a message carrier relays it. We would rather name every one of these than say “trusted partners”.

• Supabase (Postgres) (Ireland today, moving to Frankfurt). The database that holds your profile, tasks, messages, and call notes. This is where your data lives at rest. We are moving between two backends, one member at a time rather than all at once, and both sit on European Union infrastructure: the current one in Ireland, the one replacing it in Frankfurt.
• Vercel (United States, Washington D.C.). Hosts the website and runs our server functions. Every request to airmond.com is handled by a server function running in the United States. That is where a request sits while it reads from or writes to the EU database.
• ElevenLabs (United States, on our plan). Runs the voice on every call: what you say and what your assistant says back, on the phone, in the browser, and in the app. This is the one to read carefully. ElevenLabs stores customer data in the United States by default, and offers European data residency only as an Enterprise-tier feature. We are on ElevenLabs' self-serve plan, not Enterprise, so your call audio and transcripts are processed and stored in the US, not the EU.
• LiveKit (Not published by either vendor for our plan). Carries the live audio, as the underlying transport for every ElevenLabs call. ElevenLabs' own voice product is built on LiveKit's technology to move audio in real time. Neither company publishes which region handles our plan's traffic, and ElevenLabs does not list LiveKit among its own disclosed providers, even though the dependency is real. We are naming it here because we found it.
• Vonage (United States, Virginia). Carries phone calls as the telephony provider, since 2026-08-05 (Telnyx as a fallback). Vonage's default routing places a call leg in the United States, and we have not configured the EU routing option it does offer. Vonage carries the call; ElevenLabs is still the one doing the listening and speaking.
• Twilio (United States, Twilio's default region). Carries WhatsApp messages to and from your assistant. Twilio's default region is the United States, and we could not confirm that Twilio's optional EU data residency feature is available for WhatsApp specifically, so we are not claiming it. Twilio carries WhatsApp only on our original backend; as accounts move to the new backend, their WhatsApp goes directly to Meta instead (see the Meta entry), and this entry will be retired with the system it describes.
• Meta (WhatsApp Cloud API) (Meta's infrastructure; no regional residency commitment for the Cloud API). Carries WhatsApp messages to and from your assistant, for accounts on our new backend. Accounts on our new backend exchange WhatsApp messages directly with Meta's Cloud API. Meta does not document a regional residency commitment for this API that we could verify, so we list it conservatively.
• Hetzner (Falkenstein, Germany). Runs the servers of our new backend. The new backend's compute runs in Hetzner's Falkenstein data centre in Germany.
• Sentry (European Union (de.sentry.io)). Receives crash reports and errors from our new backend so we can fix them. Errors from the new backend go to Sentry's EU region (de.sentry.io).
• Google (Google's global infrastructure). When you connect your Google calendar or mail, or sign in with Google, Google processes that sign-in and our access to what you connected. Connecting Google services (or signing in with Google) involves Google's own global infrastructure. What we store about that connection lives encrypted in the EU; Google's side is Google's. What we do with what we read is set out under “What we do with your Google data” above.
• Anthropic's Claude models, via the Vercel AI Gateway (United States, no EU option found). The thinking behind drafted replies, task planning, and meeting research. Anthropic does not train its models on this content, and automatically deletes it within 30 days. Both the request and the reply pass through United States infrastructure to get there; we found no European option for this specific step.
• Recall.ai (Frankfurt). The meeting bot that joins a call to record and transcribe it, when you ask your assistant to. Configured on Recall's Frankfurt region, which Recall's own documentation describes as a separate, data-isolated deployment from its US regions.
• Resend (Ireland). Sends and receives email for the airmond.com domain. The airmond.com email domain is configured in Resend's EU region.
• Apple Push Notification service (Apple's global infrastructure). Delivers the alert when your assistant has written something, and rings the app for a call. A push notification is held only briefly for delivery, not stored afterward.
• Stripe (United States by default). Would handle an optional saved card, if that step is ever turned on. The code for an optional saved-card step exists but is not switched on: there is no live key for it in production, so Stripe is not processing anything for Airmond members today.

The honest summary: your account data is stored in the EU, your voice data is stored in the US on our current plan, and the providers in between process only what their part of the job needs, under their own terms and their own security. We do not sell your data and we do not share it for marketing.

What we do with your Google data

If you connect Google, or sign in with it, some of this is required wording and some of it is ours. We have written both, rather than pasting the required part and hoping you skim it.

The required part. Airmond's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

What that means here. Your Google data is used to provide the features you connected it for, and for nothing else. We do not use it to train or improve any general model, we do not sell it, we do not transfer it to anybody except as the service you asked for requires, and no human reads it except where you ask us to, where it is needed for security, or where the law compels it. Disconnecting Google stops the reading; deleting your account removes what we kept.

Who can access it

Your assistant. They are scoped to you. They work with your information and nobody else's, and members never see each other's data.

A small Airmond team. This is the part most privacy pages leave out, so here it is plainly: our operators can access member data through an internal admin tool. That is how we run the service, look into a call that went wrong, and answer you when you write in. We keep that team small, and we look at member data to operate and support the service, not for anything else.

Our providers. The companies listed above can technically access what they process for us, under their own agreements. We choose them carefully, and we are not going to tell you they are incapable of seeing anything.

Nobody else. We do not sell member data, and we do not share it with advertisers or data brokers. If a law or a court ever compelled disclosure we would comply, and we would tell you unless we were legally barred from doing so.

How long we keep it, and deletion

We keep your data for as long as you are a member, because that memory is the point. An assistant who forgets everything each week is not much of an assistant.

When you want it gone, email hello@airmond.com and say so. That address reaches our team, a person picks it up, and we delete your account and the data we hold about you and confirm when it is done. Two honest caveats: backups roll off on their own cycle rather than instantly, and our providers keep operational logs for their own retention periods, which we do not control.

Google data, and what we may do with it

If you connect a Google account, Google shows you the exact list of what Airmond is asking for before you agree, and that list is the real limit rather than a promise we make about ourselves. Read it: it is the truth about what your assistant can reach, it is shown to you every time the request changes, and a token cannot do anything that list does not say, however hard something tried to talk it into it. What we ask for grows as the product does, so we would rather send you to the screen that is always current than print a list here that quietly stops being true.

What we do with it. Your assistant reads your calendar and your inbox to learn who you work with, what you have agreed to, and what is coming. When you ask her to write an email she leaves it in your own Gmail drafts, and pressing send is always yours: she does not do it for you. What she learns is kept as notes and facts against your account, in the same European database as everything else on this page, and it is used to do your work and for nothing else. Where a model does the reading, that is Anthropic’s Claude through the Vercel AI Gateway, listed above: it does not train on this content and deletes it within 30 days.

Limited Use. Airmond’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms: we do not sell it, we do not use it for advertising, we do not use it to train generalised AI models, and no person at Airmond reads it except with your permission, to fix something you have told us is broken, for security, or where the law requires it.

Taking it back. You can disconnect at any time from Settings inside Airmond, which also removes Airmond from your Google account. You can do the same from your own Google account instead, under the third-party apps section of your Google security settings. Either way, email hello@airmond.com and we will remove what we stored from the connection as well.

Your rights

Whether or not the GDPR applies where you live, we will treat you as though it does. You can ask us to show you what we hold, correct something that is wrong, send you an export, delete your account and its data, or stop a particular kind of processing.

Ask at hello@airmond.com. We are a small team, so we answer as quickly as we can and we aim to be finished within 30 days. If there is ever something we cannot do, we will tell you why rather than go quiet.

This is a beta

Airmond is early. The product changes most weeks, the providers behind it may change too, and this page changes with them. If we make a change that materially affects your data, we will tell members rather than quietly edit this page. The date at the top is always the last time it changed.