Legal

Where your data lives

Where Mondaily stores your data and where it runs, part by part. Written from our code and hosting settings.

Last checked: 7 November 2026. This page is in English for now. A translation is coming.

At a glance

In Frankfurt, Germany (EU)

  • Database and files
  • Website, app and API
  • Our operations machine
  • AI engine
  • Email
  • Nightly backup

In Switzerland

  • Second backup copy

Outside services: region set by the provider

  • Background jobs
  • Backup email delivery

Part by part

PartWhereWhat happens there
Database and filesFrankfurt, Germany (AWS eu-central-1)Supabase runs our database and file storage in Frankfurt. It holds your account, your workspace's records and files, and call recordings.
Website, app and APIFrankfurt, Germany (Vercel fra1), with a worldwide edge networkVercel hosts Mondaily's website, the app and the API. The API, which reads and writes your data, runs only in Frankfurt. Your browser reaches Vercel at its network point nearest to you, which passes each request on to Frankfurt; the public pages and the app's own files are also cached on that edge network so they load fast.
Our operations machineFrankfurt, Germany (AWS eu-central-1)A server we run ourselves on Amazon Web Services. It takes incoming mail, sends outgoing mail, runs our own web search and page reader, and holds search memory: a small model on the same server turns text into numbers for search, so that text never goes to an outside AI company. It also makes the nightly backup.
AI engineFrankfurt, Germany (AWS eu-central-1)Our own AI engine runs on a GPU server we operate in Frankfurt. It starts when it is needed and stops when idle. Today it answers chat only for our own internal workspace: switching it on for every workspace is a setting we have not changed yet. Until then, chat in your workspace is answered by our rules engine, which runs inside the API in Frankfurt. Our internal test workspaces may also use a hosted test engine; customer workspaces can never reach it. No outside AI company receives your workspace data. The one exception is your own choice: if an owner or admin adds the workspace's own AI key (Claude, OpenAI, Gemini or Mistral), masked chat text goes to that provider under your own agreement with it.
EmailFrankfurt, Germany (Amazon SES, eu-central-1)Mondaily's email goes out through our own mail server, which hands each message to Amazon SES in Frankfurt. If our server cannot take a message, Resend delivers it instead (see below). If our server cannot take mail your workspace sends to its own contacts, it goes out through the Gmail account you connected, if there is one, before Resend.
Nightly backupFrankfurt, Germany (Amazon S3, eu-central-1)Every night our operations machine saves a full copy of the database to Amazon S3 in Frankfurt, encrypted, and keeps each copy 30 days.
Second backup copySwitzerland (a Swiss cloud)A second copy of the same backup is encrypted on our machine before it leaves AWS, then stored in a Swiss cloud and kept 35 days. The Swiss cloud only ever holds the encrypted file and cannot read it without our key.
Background jobsInngest's cloud; region set by the provider, may be outside the EUInngest Cloud starts our scheduled and background work. It receives job payloads, which can include the content of workspace records.
Backup email deliveryResend's cloud; region set by the provider, may be outside the EUResend delivers Mondaily's email only when our own mail server cannot take it. It then receives sender and recipient addresses, subject and message body.

Other outside services

Used only for the features named, and only when you use them. What each one receives is on the Subprocessors page.

ProviderWhereWhen
LiveKit (LiveKit Cloud)LiveKit's cloud; calls connect through servers near the participants, which may be outside the EUOnly when you use calls
Google Maps Platform (Places API)Google's cloud; region set by the provider, may be outside the EUOnly when you use the Prospecting Agent or enrichment
OpenStreetMap Nominatim (public service)The OpenStreetMap Foundation's public serversOnly when you use the Prospecting Agent
Google (Sign in with Google, Gmail, Google Calendar)Google's cloud; region set by the providerOnly if you sign in with Google or connect a Google account
LinkedInLinkedIn's cloud; region set by the providerOnly if you connect your own LinkedIn account; a post is sent only after you click Confirm
XX's cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
Meta (Facebook, Instagram, Threads)Meta (Facebook, Instagram, Threads)'s cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
TikTokTikTok's cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
Google (YouTube, Business Profile)Google (YouTube, Business Profile)'s cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
PinterestPinterest's cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
TelegramTelegram's cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
BlueskyBluesky's cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
Mastodon (your chosen server)Mastodon (your chosen server)'s cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
SnapchatSnapchat's cloud; region set by the providerOnly if you connect your own account; a post is sent only after you confirm that exact post
PayPalPayPal's cloud; region set by the providerOnly when a Mondaily administrator sends a contributor's requested payout
StripeStripe's cloud; region set by the providerOnly when you buy a plan or credits