What momo reads
momo reads the scheduling details, not your mailbox.
The text of an inbound mail is processed to recognise the request and only the extracted parameters — time, participants, modality — are kept, with the one exception in block 3.
See the Privacy Policy, section 2.1.
What calendar access means
momo reads when you are busy and writes the meetings it books — nothing else.
The calendar scopes are free/busy read and event write.
AI and your email
We never use your emails to train general-purpose AI models. When momo fails to understand a scheduling request, a redacted copy of that message is kept for up to 14 days to improve momo's own intent recognition.
See the Privacy Policy, section 2.1, Improving intent recognition.
Where it runs, and who else is involved
Core processing and storage operate on EU infrastructure (Hetzner, Germany). Calendar sign-in with Google or Microsoft involves those providers in the US under Standard Contractual Clauses.
Paid plans use Stripe Payments Europe (Ireland).
For CalDAV you supply the server. Availability checks go to that server, which may be outside the EEA.
Google returns busy times and nothing else. Microsoft and your own CalDAV server can return more — the subject of an entry, for example — and momo keeps only its start and end.
momo.ai UG (haftungsbeschränkt), Germany, operates momo.ai.
See the Privacy Policy, section 3.