Legal
Privacy Policy
Privacy Policy pursuant to Art. 13 GDPR (English)
Version 0.4
1. Who we are and who looks after your data (Controller)
Responsible for data processing in the app “two mo” (Art. 4(7) GDPR):
Zuhörraum UG (haftungsbeschränkt), Haushamer Str. 3, 81547 Munich, Managing Director: Michael Spitzenberger, Munich, Germany.
Feel free to reach us at: support@twomo.app.
2. Technical data (what happens in the background when you open the app)
When you open the app, we automatically collect some technical data necessary for stable and secure operation. We do this based on our legitimate interest (Art. 6(1) sentence 1 lit. f GDPR):
- Your IP address, date and time of the API call, your device ID, operating system, and volume of data transferred.
Retention: Technical log data for up to 90 days (see Section 4, Cloud Logging).
3. Our core services (why we need your data & how long we keep it)
To fulfil our contract with you (Art. 6(1) sentence 1 lit. b GDPR), because you have given us your voluntary consent (Art. 6(1) sentence 1 lit. a GDPR), or based on our legitimate interest (Art. 6(1) sentence 1 lit. f GDPR), we process the following data:
- Your registration data (email address, password – only as a hash –, first and last name, language): Required to create your account, enable secure login and send you our emails in your language. Nobody but us sees your last name; we need it to identify you unambiguously, for example in an incident between two people who do not know each other, for your access and erasure requests or towards authorities. What your counterpart sees of you is set out in the next item.
Retention: Until you permanently delete your account. If you do not confirm your email address after registering, we delete the registration at the earliest 72 and at the latest 96 hours afterwards. If you don't sign in for 36 months, we delete your account; after 24 months we remind you by email first.
Legal basis:- Art. 6(1) lit. b GDPR (performance of contract);
- Art. 6(1) lit. f GDPR for the last name (legitimate interest: investigating incidents and attributing requests to the right person).
- Your first name for your counterpart: In a momolog your counterpart sees you on video and your first name; nothing else — no last name, no email address, no profile. The same first name appears in your counterpart's momolog overview and list of blocked people for as long as your account exists; afterwards only a placeholder without a name remains.
Retention: Until you delete your account.
Legal basis:- Art. 6(1) lit. b GDPR (part of the momolog);
- Art. 6(1) lit. f GDPR (legitimate interest in a personal encounter and in recognising your counterpart).
- Optional details about you (gender, age group): In Settings you can state your gender (female, male, diverse) and your age group. Both are optional, the default is 'not specified', and your counterpart never sees them. We use these details for anonymous statistics about who uses two mo (totals only, no individual values, never fewer than ten accounts per group) and — once two mo offers it — for a matching preference you switch on yourself (for example a counterpart of the same gender). Until then the details do not influence matching.
Retention: You can reset the details to 'not specified' at any time; they are then deleted immediately, at the latest with your account.
Legal basis:- Art. 6(1) lit. a GDPR (your voluntary entry);
- Art. 6(1) lit. f GDPR for the anonymous statistics;
- Art. 6(1) lit. b GDPR for a preference you have switched on.
- Your session data (video call metadata): Session duration, timestamps, QoS metrics and technical drop-off status, to provide the real-time video call and improve connection quality. No audio or video content is stored.
Retention: Deleted or fully anonymised 24 months after the video call at the latest; if there was a safety reason, a block or a support request, a minimal record is kept with restricted access until the end of the third calendar year after the video call; what remains after an account deletion is set out in Section 7 — anonymous aggregates (no personal reference) are retained permanently for quality statistics.
Legal basis:- Art. 6(1) lit. b GDPR (performance of contract);
- Art. 6(1) lit. f GDPR (legitimate interest: improving connection quality and creating anonymous quality statistics; for the minimal record, investigating incidents and defending against legal claims)
- Your app usage data (onboarding steps, crash reports, navigation behaviour): Used to fix bugs and improve app stability.
Retention: Maximum 90 days, followed by full anonymisation.
Legal basis:- Art. 6(1) lit. f GDPR (legitimate interest: error diagnosis and app stability).
- Your onboarding inputs (goEMMA AI companion, not yet available): This step only exists once we introduce goEMMA; until then this processing does not take place. From then on goEMMA, our AI companion, processes your voice and text inputs during onboarding live — only with your consent and exclusively for this introductory step.
Retention: No persistent storage.
Legal basis:- Art. 6(1) lit. a GDPR (consent). Further details and your right to withdraw: AI Consent
- Your comment after STOP (voluntary): If you end a momolog with STOP and choose the reason “something else”, you can write us a comment. We read it to improve two mo across several app versions and to check later whether the cause has been fixed. Your counterpart never sees it. Because a comment can contain details about your health and about your counterpart, we store it only with your explicit consent (“agree and send”).
Retention: 12 months from sending; if you withdraw your consent in Settings or delete your account, we delete all your comments at once.
Legal basis:- Art. 9(2) lit. a GDPR in conjunction with Art. 6(1) sentence 1 lit. a GDPR (explicit consent).
- Blocking, bans and safety reports: After every momolog you can block your counterpart; you will then no longer be matched until you lift the block in Settings. For this we store both account identifiers and the time. If you choose a safety reason when you press STOP, we store this reason with the session. If our team bans an account for violating the Community Guidelines, we store the reason and the date. You will not find out who blocked you; a person who is blocked is not notified.
Retention: Blocks until you lift them or delete your account; safety reasons like the session data; bans until they end. What remains of them after an account deletion is set out in Section 7.
Legal basis:- Art. 6(1) lit. b GDPR for the person who blocks;
- Art. 6(1) lit. f GDPR for safety reasons, bans and their continued effect (legitimate interest: protecting users from unwanted contact and misuse, investigating incidents).
- Protecting your account against misuse (sign-in protection): When you register, sign in or renew your session, we count requests and failed attempts to fend off password-guessing attacks and overload. After several failed attempts we temporarily block sign-in for the email address entered; if one IP address sends too many requests, we briefly slow it down. For this we never store email or IP addresses in plain text, only as a pseudonymised check value (hash), together with counters and timestamps. This also applies to email addresses that have no account.
Retention: IP check values a few minutes after the last request (15 minutes at the latest); failed attempts for an email address until 24 hours after the last failed attempt or the end of a block, immediately upon successful sign-in or account deletion.
Legal basis:- Art. 6(1) lit. f GDPR (legitimate interest: security of your account and our service).
- Checking new passwords against known data breaches: When you choose a new password when registering, resetting or changing it, we check whether it appears in a known data breach; if so, we reject it. For this our server computes a check value (hash) of the password and sends only its first five characters to the “Pwned Passwords” service of Have I Been Pwned (Superlative Enterprises Pty Ltd, Australia; infrastructure from Cloudflare and Microsoft Azure). The service answers with a list of check values that begin with the same five characters; only our server checks whether your password is among them. Have I Been Pwned receives neither your password nor your email address nor your IP address.
Retention: None: the password, the check value and the five characters are neither stored nor logged.
Legal basis:- Art. 6(1) lit. f GDPR (legitimate interest: security of your account and our service, recital 49 GDPR).
- Log of our sign-in service: Our sign-in service records every sign-up and sign-in with your email address, every new sign-in session with its identifier and your activity, each with your user ID and the time, without IP address. This lets us trace sign-ins and sessions and investigate misuse.
Retention: The sign-in service deletes the entries month by month, at the latest 63 days after the entry, even if you delete your account before then.
Legal basis:- Art. 6(1) lit. f GDPR (legitimate interest: security of your account and our service).
- When you change your email address (protection against account takeover): We keep your previous email address, never in plain text, only as a pseudonymised check value (hash) linked to your account. This lets our support find your account by the previous address too, for example if someone else changed your address and you want your account back.
Retention: Until the end of the third calendar year after the change, even if you delete your account before then.
Legal basis:- Art. 6(1) lit. f GDPR (legitimate interest: security of your account and recovery after an account takeover).
4. Who else receives your data (recipients & third-country transfers)
Your counterpart in the momolog: sees your video and your first name (Section 3).
We work with processors bound by our instructions. Some of our processors process data exclusively within the EU; others may transfer data to countries outside the EU/EEA. Such transfers rely on EU Standard Contractual Clauses (SCC, Art. 46(2) lit. c GDPR) or, for certified US recipients, on the adequacy decision for the EU–U.S. Data Privacy Framework (DPF, Art. 45 GDPR). You can get a copy of the Standard Contractual Clauses on request at support@twomo.app. The processors in detail:
- goAVA GmbH (Essen, Germany), only once goEMMA is introduced: Operates the AI avatar goEMMA, which you will then interact with in the app. goAVA processes your voice and text inputs as well as technical session metadata (timestamps, duration) exclusively during onboarding. Processing takes place exclusively on ISO 27001-certified EU servers (Open Telekom Cloud & OVH) — no data transfer outside the EU/EEA. We will only use goAVA once the data processing agreement pursuant to Art. 28 GDPR has been concluded.
Legal basis:- Art. 6(1) lit. a GDPR (consent, see AI Consent) for your voice and text inputs;
- Art. 6(1) lit. b GDPR (performance of contract) for technical session metadata (service delivery and billing).
- GetStream (Stream.io, Inc., USA): Routes our real-time video calls (MOMOLOGs) live over a globally distributed edge network — no audio or video content is stored. Technical call metadata (timestamps, connection quality) is processed to deliver the service. EU users are typically routed via European server locations. Secured via DPF and SCCs (DPA).
Legal basis:- Art. 6(1) lit. b GDPR (performance of contract).
- Scaleway SAS (Paris, France): Sends our emails to you, such as confirmation codes and notices about your account (Transactional Email service). For this, Scaleway processes your email address, the content of the email and delivery data (time, delivery status); Scaleway keeps the delivery logs (your address as recipient, subject, time and delivery status, no message body) as proof of sending, at the latest until the end of the third calendar year after sending. Processing exclusively in the EU (Paris region) — no data transfer outside the EU/EEA. DPA pursuant to Art. 28 GDPR in place.
Legal basis:- Art. 6(1) lit. b GDPR (performance of contract) for confirmation codes and notices about your account;
- Art. 6(1) lit. c GDPR (legal obligation, Sections 312f(2) and 356a(4) BGB) for the contract confirmation with our Terms of Service and the confirmation of receipt of your withdrawal from the contract;
- Art. 6(1) lit. f GDPR (legitimate interest: security of your account) for the notice to your previous address after a change;
- Art. 6(1) lit. f GDPR (legitimate interest: proof of sending) for the delivery logs.
- Google Cloud Logging (Google Ireland Ltd., Ireland): Stores technical application logs for error diagnosis and IT security. Log data may include IP addresses, pseudonymised user IDs, API request paths, and timestamps. Retention period: 90 days, then automatically deleted. Processing in EU region europe-west3 (Frankfurt). DPA pursuant to Art. 28 GDPR in place.
Legal basis:- Art. 6(1) lit. f GDPR (legitimate interest: IT security and operational stability).
- Google Cloud SQL — PostgreSQL (Google Ireland Ltd., Ireland): Primary database of the app — stores the app's user data (such as profile and registration data, session metadata, app usage data), including the data of our sign-in service: your sign-in data (email address, password only as a hash, email verification status, time of sign-up and of your last activity), your sign-in sessions (session identifiers and tokens, including one-time tokens such as for a password reset) and the log of the sign-in service (Section 3). We run the sign-in service ourselves with the open-source software SuperTokens in our Google Cloud project; its maker receives no data. Processing in EU region europe-west3 (Frankfurt). DPA pursuant to Art. 28 GDPR in place (Google Cloud DPA).
Legal basis:- Art. 6(1) lit. b GDPR (performance of contract).
- Jira Service Management (Atlassian Network Services Inc.): Processes your support requests (name, email address, message content, device information) submitted via the in-app support function. Data stored exclusively in Germany (Atlassian Data Residency, region: Germany). DPA pursuant to Art. 28 GDPR in place (Atlassian DPA).
Legal basis:- Art. 6(1) lit. b GDPR (performance of contract).
- Apple Inc. (Cupertino, CA, USA): Delivery of push notifications via the Apple Push Notification Service (APN). Data transfer to the USA on the basis of EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) pursuant to the Apple Data Transfer Agreement.
Legal basis:- Art. 6(1) lit. b GDPR (performance of contract).
5. Your rights (Art. 15–20 GDPR)
You have the right at any time to access, rectification, erasure (“right to be forgotten”), restriction of processing, and data portability. Your right to object is set out separately in Section 6.
6. Your right to object (Art. 21 GDPR)
You have the right to object at any time, on grounds relating to your particular situation, to the processing of your data that we base on our legitimate interest (Art. 6(1) sentence 1 lit. f GDPR; stated in each case in this Privacy Policy). An informal message to support@twomo.app is enough. We will then no longer process the data concerned unless we can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims (Art. 21(1) GDPR).
7. Your right to withdraw consent (Art. 7(3) GDPR)
You can withdraw any consent you have given us (e.g. for comments after STOP or, once available, for the AI companion goEMMA, Section 3) at any time with effect for the future — directly in the app settings or by email to support@twomo.app. This does not affect the lawfulness of processing before the withdrawal; only the processing you consented to ends, and your account stays open.
Your acceptance of the Terms of Service (including the Community Guidelines) and your confirmation of the therapeutic disclaimer, by contrast, are not consents but part of our contract with you (Art. 6(1) sentence 1 lit. b GDPR). If you withdraw one of them, correct your age confirmation (18+) or no longer want the processing our contract requires, we can no longer provide two mo to you: once you confirm, our contract ends and we delete your account. We also delete your account when you withdraw from the contract (§ 5 of the Terms of Service; in the app: Settings → Legal & privacy → “Withdraw from contract”).
What remains after deletion: After any account deletion we delete the personal data relating to your account. Only the following data remain stored, with restricted access and each only for the stated purpose:
- Records of your acceptances, acknowledgements, consents and withdrawals, your age confirmation, the version of this Privacy Policy shown to you and the deletion (with a check value of your email address instead of the address), so that we can prove them and defend against legal claims: until the end of the third calendar year after your account ends.
- Log entries on your account (such as creation, password and email changes, acceptances, deletion), including the check value of a previous email address (Section 3), so that we can prove them and defend against legal claims: until the end of the third calendar year after each entry, the IP address in them for 12 months only. Security events (such as sign-in attempts with IP address), to investigate misuse: until 12 months after the event.
- Support requests and correspondence on your requests under Section 5, so that we can prove how they were handled and defend against legal claims: until the end of the third calendar year after they are closed.
- Blocks against you, safety reports about you and bans, so that they stay in force to protect other users from unwanted contact and misuse if you register again with the same email address: at the latest until the end of the third calendar year after the last account involved has ended, earlier if a temporary ban expires or a block ends. After a correction of your age confirmation they do not carry over; your own blocks end with your account.
- Session data (Section 3) that also concern your counterpart: for as long as their account exists, at most 24 months after the video call. If there was a safety reason, a block or a support request, a minimal record remains, to investigate incidents and defend against legal claims, until the end of the third calendar year after the video call.
- Technical data, for operation and IT security: technical log data for up to 90 days (Section 2), app usage data for up to 90 days (Section 3), the log of our sign-in service until 63 days after the entry at the latest (Section 3), call records at the video provider for calls with a counterpart who still has an account, until 30 days after the video call, and delivery logs of our email service provider (your address as recipient and the subject, no message body) as proof of sending, at the latest until the end of the third calendar year after sending.
- Backups, which we read only to restore data after an outage or data loss: for 2 years at most. If we restore a backup, we delete your account again before two mo can be used again.
- Legal hold: If our management orders in writing, because of a specific incident or proceeding, that certain records be kept, exactly those records remain stored to establish or defend legal claims until the order is lifted; the order itself until the end of the third calendar year after that.
The legal basis is in each case our legitimate interest in the stated purpose (Art. 6(1) sentence 1 lit. f GDPR), and for backups Art. 6(1) sentence 1 lit. c in conjunction with Art. 32(1)(c) GDPR.
Already anonymised aggregates (see Section 3) will remain without personal reference.
8. If something goes wrong (your right to lodge a complaint pursuant to Art. 77 GDPR)
You have the right to lodge a complaint with a data protection supervisory authority. The one responsible for us is:
Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 27, 91522 Ansbach, Germany.
9. No cold profiling (automated decisions)
Automated decision-making or profiling with legal effect concerning you (Art. 22 GDPR) does not take place. The matching function serves purely to connect two people in a video call for the MOMOLOG. The temporary sign-in block after several failed attempts (Section 3) is not such a decision: it ends automatically and has no legal effect on you.