Legal
Subprocessors
Every provider that processes personal data for sōtem, what it receives and where.
Draft. This text is a draft. Our lawyer is still reviewing it, and it becomes final once the company is registered in the United Kingdom. This page is in English for now. A translation is coming.
Last updated: 7 November 2026
sōtem is provided by Mondaily Ltd, United Kingdom. Placeholder until the company is registered: Company number: to be added after registration in England and Wales. Registered address: to be added after registration.
The list
These providers process personal data for sōtem. Where a provider may process data outside the EU, the entry says so. We add a provider here before it receives any data, and the date above changes with every change.
No AI company processes your data for sōtem: the sōtem engine is run by us. If a space owner adds the space's own AI key, that provider works under the space's own agreement with it and is not our subprocessor.
Public data sources (not subprocessors)
These public services receive no personal data, only the items named:
- OpenStreetMap, Wikidata, TED, GDELT and official company registers: Search words for the Prospecting Agent (an industry, a place, a date range) or a found company's public name or number.
- Public search engines used by our own search server: Search words, sent from our server in Frankfurt, never with your name.
- Common Crawl and public job boards: A found company's own website domain or job board name.
| Provider | What it does | Data it receives | Where | When |
|---|---|---|---|---|
| Supabase | Database and file storage for sōtem | Your account and profile, chats, files, sōtem Studio clips, voice consents and voice history, website assistant conversations, connections and Data Lab work | EU: Frankfurt, Germany (AWS eu-central-1) | Always |
| Vercel | Hosting for sotem.io, app.sotem.io and the API behind them | All data passing through the service while it is served | EU: the API runs in Frankfurt (fra1); public pages are cached on Vercel's global edge network | Always |
| Amazon Web Services | Machines we run on AWS: the sōtem AI engine, our operations machine (incoming mail, outgoing mail through Amazon SES, our own web search, search memory) and the nightly database backup (Amazon S3) | Chat text and tool results the engine answers from; the email sōtem sends and receives; search words; a full encrypted copy of the database in the backup | EU: Frankfurt, Germany (AWS eu-central-1) | Always for backups; the engine and search when you use them |
| Infomaniak (Swiss Backup) | A second, encrypted copy of the nightly database backup | An encrypted copy of the whole database. Infomaniak cannot read it without our key | Switzerland | Every night; each copy is kept 35 days |
| Inngest (Inngest Cloud) | Runs background jobs: scheduled agents, reminders, record enrichment | Job payloads, which can include the content of your records | Inngest's cloud; region set by the provider, may be outside the EU | Always |
| Resend | Backup delivery of sōtem's email: sign-in, notices, trial reminders and messages your agents send after you approve them | Sender and recipient addresses, subject and message | Resend's cloud; region set by the provider, may be outside the EU | Only when our own mail server on AWS in Frankfurt (Amazon SES) cannot take a message; sōtem sends through that server first |
| Google Maps Platform (Places API) and OpenStreetMap Nominatim | Business lookups for the Prospecting Agent in sōtem Team | Search words and company names, never your records or contacts | Google's cloud and the OpenStreetMap Foundation's servers; region set by each provider | Only when you use the Prospecting Agent |
| Brave Search | Backup web search while our own search is offline | Search words with emails, phone numbers, ids, bank and card numbers removed first. Brave keeps query logs up to 90 days | Brave's cloud; region set by the provider | Only if switched on for your space and only while our own search is not available |
| Google (Sign in with Google, Gmail, Google Calendar) | Optional sign-in, and the optional Gmail and Google Calendar connection | Sign-in: your name, email address, Google account id and picture. Connection: the mail and calendar data you allow | Google's cloud; region set by the provider | Only if you sign in with Google or connect a Google account |
| GitHub (Sign in with GitHub) | Optional sign-in with GitHub | Your GitHub id and primary verified email | GitHub's cloud; region set by the provider | Only if you sign in with GitHub |
| Social platforms you connect (LinkedIn, X, Meta, TikTok, YouTube and Google Business Profile, Pinterest, Telegram, Bluesky, Mastodon, Snapchat) | Publishing the posts you approve with sōtem Team | From the platform: your account's name, picture and id. To the platform: only the posts, images and videos you confirmed | Each platform's cloud; region set by the provider | Only for a platform you connect yourself; each post is sent only after you confirm that exact post |
| PayPal | Paying Data Lab contributors for approved work | The PayPal email address a contributor gave us and the amount | PayPal's cloud; region set by the provider | Only when a contributor's requested payout is sent |
| Stripe | Payment for Pro and Team, and the card check for the Pro trial | Billing name, email address and payment details. Card numbers go straight to Stripe's own form; sōtem never sees or stores them | Stripe's cloud; region set by the provider | Only when you start a trial or buy a plan |
Questions or problems? Email support@sotem.io.