Privacy policy
Last updated: 15 November 2026 · Version 1.5
The German version (Datenschutzerklärung) prevails in case of doubt.
1. Controller
The controller for Take Da Chat – server, apps, web access, these pages and the service accounts – is:
Sven Berger (sole proprietorship)
c/o Online-Impressum 13024, Europaring 90, 53757 Sankt Augustin, Germany
E-mail: support@takeda.chat
All provider details are in the legal notice.
No data protection officer has been appointed (no obligation under Art. 37 GDPR and Section 38 of the German Federal Data Protection Act, BDSG).
2. These pages and e-mail to us
What does not happen here
These pages are hosted on our own server in Germany at web.takedachat.com. They are plain HTML files: they set no cookies, run no JavaScript and embed no third-party content – no fonts from other servers, no maps, no videos, no analytics. That is why there is no consent banner.
The web access to the messenger lives at the same address. It needs JavaScript; section 7 applies to it.
Access logs
When a page is requested, our web server processes technically necessary access data: IP address, time, requested address, response code, amount of data transferred and browser identification. Before that, the connection passes through our own network distributor, which records IP address, time, the requested host name and the amount of data. We run both ourselves; no service provider is involved. The legal basis is Art. 6(1)(f) GDPR – legitimate interest in secure and uninterrupted operation. The web server log is deleted after 90 days at the latest, the network distributor's log after 8 days at the latest.
Requests for map tiles (section 10c) and GIFs (10a) are not logged, nor are addresses containing an access token – invitations, group links and call links (10e, 10i).
The address takeda.chat only redirects to these pages; the legal texts are kept exclusively on our own server. If the redirect is carried out not by our server but by a web hosting provider, that provider processes the technically necessary access data of the request (IP address, time, requested address).
Legal notice, post and contact form
For the postal address in the legal notice we use the service Online-Impressum.de (Clear-Media UG, Europaring 90, 53757 Sankt Augustin, Germany). The service accepts post sent to this c/o address, scans it and forwards it to us; in doing so it processes sender, content and date of receipt of the item. If you write to us through the "Second contact channel" form of the service (link in the legal notice), your device only retrieves that page from the service after you click; the service then processes the technically necessary access data (IP address, time, requested address) and is itself responsible for its page. Its privacy policy applies. The form forwards your message to us.
E-mail to us
If you write to us – for example to support – we process your address and the content in order to reply (Art. 6(1)(b) or (f) GDPR). The message is deleted once it is no longer needed and no retention obligation applies. The mailbox is kept on our own mail server on a computer in Germany, behind a mail filter that we also run ourselves. No external provider is involved.
3. Encryption – what we see and what we don't
Messages, pictures, voice messages, videos, files, status updates as well as your profile picture and profile info are end-to-end encrypted (Signal protocol): your device encrypts them, and only the recipient's device decrypts them. Our server only ever sees encrypted data; it never has the private keys. Calls are encrypted between the devices.
What the server does need to know in plain text for the service to work – who you are, whom you are connected with, where a message has to go – is listed in full in section 4. Content reaches us or third parties in plain text only in the following cases, and only if you trigger them:
- you report a message, a status, an account or a group, optionally with pictures, videos or files (section 4, "Reports", and 10g); if a contact is reported for their name or profile picture, we also receive that contact's profile picture (10g);
- you switch on translation for a conversation (section 4, "Translations");
- you write in a bridge group – your text then goes to another service;
- you search for a GIF – the search term goes via our server to the GIF provider (10a);
- you create a link preview – our server fetches the link address (10b);
- with service accounts, their notifications exist in plain text at the provider of the service account before they are encrypted.
4. What data is stored on the server
- Phone number – it identifies the account and is confirmed by text message (SMS) during setup. You decide who sees it in your profile (everyone, contacts, contacts with exceptions, nobody).
- Display name, username, profile picture, info, if you set them. Display name and username are stored in plain text on the server; profile picture and info are stored there only end-to-end encrypted (see Profile info). The username is unique; anyone searching for it does not learn whether it exists – only you decide on a contact request. Certain terms – the operator's brands and domains, including the names of the service accounts – cannot be used in names; this protects against deception and is not used for analysis.
- Postal address (company, name, street, postcode, town, country), only if you enter it yourself. It is not verified; it is shown to others expressly as your own, unverified statement. You decide who sees it, as with your phone number (default: nobody). You can change or delete it at any time.
- Operator badge ("Official"): whether the operator has marked an account as its own. Only the operator can assign this badge and records the time and reason in the operations log; nobody can give it to themselves.
- Service account badge: whether an account is a service account, its role and who runs it ("Operated by"). This, too, is assigned only by the operator.
- E-mail address, if you add one, as a way back into your account. It is confirmed with a code; an unconfirmed address is deleted after 24 hours. A confirmed address can belong to one account only. You decide who sees it in your profile (everyone, contacts, contacts with exceptions, nobody; default: nobody); an unconfirmed address is visible to nobody but you. With a confirmed address, service accounts can find you as long as you allow it (section 9).
- Devices: name, platform, time of registration and of the last connection; in addition, web sessions (section 7). Devices left unused for a long time receive a warning after 60 days and are signed out after 90 days.
- Public keys of your devices for encryption. The private keys never leave your devices.
- Contacts, contact requests, blocks and group memberships; plus your own notes on contacts (name, note, further numbers), which only you can see, and from whom you hide parts of your profile. The name and description of a group, member tags and the name, description and picture of a community are stored in plain text on the server (10e, 10f).
- What happens in a group: who added, invited or removed someone, who left, who became an admin, when the group was renamed. All members see this in the conversation history.
- Group links and join requests, passkeys, call links and waiting room and – once switched on – guests: details in sections 10e, 10h, 10i and 10j.
- Stickers: encrypted copies of your stickers used to synchronise your devices, in the media store – section 10l.
- Messages, encrypted, until your devices have collected them; the server then deletes them immediately. What remains is a delivery record without content. Pictures, voice messages, videos and files are kept encrypted in a media store.
- Delivery and read notices (the ticks): whether and when a message was delivered and read – without content. You can switch read receipts off in the settings (default: on); if you switch them off, you won't see them from others either. In groups this setting does not apply.
- Online status and "last seen": only if you switch them on (default: off). It works both ways: if you switch it off, you won't see it from others either.
- Status (text, photos, short videos for 24 hours): end-to-end encrypted like messages; the server sees that it is a status and to whom it goes, not its content – see Status.
- Notes (copies you make of messages) so that they are available on all your devices: encrypted with a key that only your devices have. The server only sees how many there are, roughly how large they are and when they were last changed.
- Pinned, favourites and lists: which conversations you have pinned or marked as favourites, and your lists – in plain text, so that they are the same on all your devices.
- Chat backup, only if you switch it on in the app and choose "Our server" as the destination: an encrypted backup of your chat texts – without pictures, voice messages, videos and files. It is encrypted on your device with a key derived from your password; we cannot read the content. We only see the size and time of the backup and its unencrypted file header (program version, creation time and the key envelope locked with your password). There is exactly one backup per account, at most 50 MB; a new one replaces the old one. Without your password it cannot be restored – not even by us.
- Invitations: to whom (phone number or e-mail address) and from whom, as well as the invitation chain (who invited whom). An invitation by e-mail contains the name of the person inviting.
- Security events: device sign-ins, sign-outs, unlock requests, phone number changes. They are kept so that an account takeover can be traced.
- Verification attempts with phone number and IP address, to prevent abuse; in addition, the dispatch order of the confirmation SMS (phone number and text).
- Suspension data, if we suspend an account: time, suspension reason from the catalogue in the terms of use and any note to you.
- Reports: if you report a message or an account, we see the reported message in plain text, who reported it and whom. If you report a status, your device uploads its encrypted file to us again and gives us the key with the report – only then can we view it. Group reports and media in reports: section 10g. The person reported is not notified by us automatically; your data report in the app lists the reports you have made yourself. If a reported person requests access under Art. 15 GDPR, we tell them that and what was reported about them, but not who reported it (Art. 15(4) GDPR: protection of the rights and freedoms of others).
- Translations, only if you switch them on for a conversation yourself: the texts you receive in that conversation are then sent to our server and translated there by a translator we run ourselves (LibreTranslate). They are not stored and not passed on to third parties; the operations log only records length, languages and duration. Your own messages and all other conversations are not affected. You can switch translation off again at any time in the chat info or the conversation menu ("Translate chat"). Notifications from service accounts are not translated automatically.
- Notification routes: if you have switched on notifications in the browser, the destination address at your browser's push service (see section 8).
- Operator's operations log: every sign-in to the operations console and every intervention (suspending, unsuspending, registration stop, changes to the domain lists, creating service accounts) is recorded with time, author and reason – as is every search for an account by the operator, together with the search value (phone number, username or e-mail address). The operator is shown only the account's ID, registration date, state and suspension history – no messages, no contacts. The automatic matching for service accounts (section 9) is not such a search and is not logged with the address.
- Operating metrics: every ten seconds the server measures load, connections, messages per hour and the like – exclusively as figures without personal reference ("12 accounts online", never "who"). This includes the number of GIF requests per provider.
- Call quality feedback, only while the switch "Report call quality" is on in the app (default: on; can be switched off in the settings at any time): after hanging up, the app sends a summary of the call as figures – type (one-to-one or group call), number of participants, whether video was used, duration rounded to ten seconds, send and receive rate, packet loss, round-trip time, smallest picture size and frame rate sent and received, share relayed via the relay server, time until the connection was established, whether the line was already prepared when answering, any throttling reason, the platform of the app and the role in the call. The feedback contains no account ID, no phone number, no other party, no IP address and no timestamp of the call; the server immediately merges it with all other feedback of that minute into averages and maxima. Who reported is not stored.
- Error reports, only if you send them from the app yourself.
- Server access log (IP address, time, requested address) for uninterrupted operation – without map tiles, GIF requests and addresses containing an access token (section 2).
- Deletion markers of deleted accounts: when an account is deleted, the server keeps for each of its devices only a random device ID and the checksum of its credentials – no phone number, no name, no account ID – so that a device that was offline at the time wipes itself the next time it connects.
Not stored: your phone's address book (matching uses checksums only, for the comparison only – 10d), location data (a shared location is encrypted message content; map requests are not logged – 10c), GIF search terms, link preview addresses, usage statistics with personal reference, advertising IDs. Blocked e-mail domains are a list of domains, not of people.
5. Status
You can share text, photos and short videos as a "status" – with all your contacts, with everyone except certain people, only with certain people or with one of your lists. Blocked contacts and service accounts never see your status. Like every message, a status is end-to-end encrypted: our server sees that you are sending a status and to whom, but not its content.
After 24 hours it is gone. The server deletes the encrypted file after 24 hours, as well as any status that could not be delivered by then; your contacts' devices remove it from view. Before that, you can withdraw a status at any time.
Who has seen it. If both of you – you and the person viewing your status – have read receipts switched on, that person appears as "seen" on your side. This feedback is sent encrypted to you only. Anyone who switches read receipts off reports nothing back and does not see who has seen their own status either.
Anyone who has seen your status can report it for up to 30 days. For this, their device keeps an encrypted copy, even if the status has expired or you have withdrawn it. This copy can only be reached via "Report contact": it is not visible, not searchable, not exportable and not part of the history transfer to a new device. If nothing is reported, the device deletes it after 30 days. If it is reported, the device uploads the encrypted file to us again and gives us the key with the report – only then can we view the reported status. A status that nobody has opened cannot be reported by anyone. Before you share your first status, the app points this out to you.
No saving, no forwarding. Nobody can save or forward someone else's status in the app; on Android the app does not allow screenshots while a status is open. We cannot prevent a screenshot on other devices or a photo of the screen. If someone replies to your status, this becomes a normal message to you with a small preview picture or a text excerpt; this quote remains in your conversation even after the 24 hours.
6. Profile info
In your profile you can enter a line of "info". Like your profile picture it is end-to-end encrypted, with your profile key. The server stores only the encrypted line and the time of the last change and releases it only to the people allowed to see it. Unlike the info, your display name is stored in plain text on the server.
You decide who sees your info, as with your phone number (everyone, contacts, contacts with exceptions, nobody); the default is your contacts. You can change or delete the info at any time. Service accounts receive neither your profile picture nor your info.
7. Web access in the browser
At web.takedachat.com you can use Take Da Chat in the browser. The browser does not become a device of your account, but a web session that you approve with one of your devices (QR code or short code), with a passkey (section 10h) or – if you have allowed this on a device – with your ID and password.
- Everything stays in the browser's working memory. The keys of the web session and the messages that your phone or computer hands over to the browser in encrypted form are kept only in the memory of this page – not in cookies, not in the browser's local storage, not in a file. Closing or reloading the page deletes everything; you then sign in again.
- Time limits: after 60 minutes without input the session ends, after 7 days at the latest in any case. A web session is only possible as long as one of your devices has been connected within the last 30 days.
- On the server, the web session is stored like a device, marked as a web session, with the time of sign-in and of the last input. For security reasons, data reports, account deletion and device management are only available in the apps, not in the browser.
- Browser notifications are optional – see section 8.
8. Notifications and third countries
The apps for Android and Windows keep their own connection to our server. They do not use any notification service of Google, Apple or Microsoft. From version 1.53.0, the Android app contains components from Google for passkeys (section 10h); our app calls them only when you create a passkey.
In the browser you can switch on notifications with the bell. Your browser then registers with us a destination address at the push service of its manufacturer – depending on the browser, for example Google (Chrome), Mozilla (Firefox), Apple (Safari) or Microsoft (Edge). If the web session is not connected at the moment, we send a wake-up signal via that service. It is encrypted and only says "new message" – no sender, no text. The push service sees the destination address, the time and size of the signal as well as our server and our contact address. Some of these providers are based outside the EU, in particular in the USA; this data is transferred there. The legal basis is Art. 6(1)(b) GDPR (you switched the notifications on yourself). The transfer to the USA is based on the European Commission's adequacy decision on the EU-US Data Privacy Framework, insofar as the provider is certified under it; otherwise on Art. 49(1)(b) GDPR. You can switch the notifications off at any time with the bell or in your browser's settings.
For the iPhone app, notifications are delivered via Apple's push service (APNs). Apple Inc. (USA) receives a device token, the time and a wake-up signal without content. Legal basis and transfer basis as above.
Further transfers to third countries happen only via bridge groups and – only with your consent – in the GIF search (section 10a): it sends search terms via our server to GIPHY and KLIPY (both USA). Link preview, map and address book matching run only via our server. If you create a passkey, it is kept by a password manager on your phone – on phones with Android 9 to 13, Google's. If its provider is based outside the EU (Google LLC: USA), it processes the data there under its own responsibility (section 10h). Otherwise our server is located in Germany and no data is transferred to third countries.
9. Service accounts
Besides accounts of people there are specially marked service accounts ("Service account") through which a provider sends you notifications you have ordered from it – for example payment and expiry notices of a rental system. Service accounts are assigned solely by the operator of Take Da Chat. Who runs a service account and how to reach them is shown in its profile under "Operated by".
How a service account finds you
A service account can send you a contact request only if you have confirmed the same e-mail address with that provider as with us and switched on delivery via Take Da Chat there. For this our server compares the address handed over by the provider with the addresses confirmed with us; this happens even if you have set your address to "nobody" for other members. The provider does not learn whether an account exists for the address – the reply it gets is always the same. Only when you accept the request does the service account connect to your account. Addresses without an account are neither stored nor logged; we only count how often a service account sends requests per hour, without addresses. The number of requests per service account is limited.
If you are already connected with the service account and it requests the address confirmed with us, the server tells it immediately that the address belongs to your account.
With the switch "Service accounts may find me by my confirmed e-mail" (default: on) you decide whether this matching takes place for you. If it is off, no service account can find you by your address, and you will not receive such requests.
Accept, decline, block
- Accept: the service account becomes your contact and may send you notifications.
- Decline: the same service account may not ask you again for 30 days.
- Do nothing: an unanswered request expires after 30 days.
- If you decline, block the service account before accepting, or delete your account while the request is still open, the provider learns nothing about it; its request expires on its side after 30 days. The record of a closed – declined or expired – request is deleted after 60 days at the latest.
- Blocking is your objection, at any time: the service account can then no longer reach you, and a new request is excluded as long as the block is in place. If you had already accepted and you block the service account, remove the contact or delete your account, the provider only learns that the connection has ended – so that it can delete your address.
What a service account sees of you
A service account receives neither your phone number, e-mail address or postal address nor your profile picture or profile info – not even after you accept. Like any contact it sees your display name, your account ID, whether and when its notifications were delivered and (if you have read receipts switched on) read, your online status (if you share it) and when you last changed your profile or your number; in addition, the public keys of your devices, without which it could not encrypt. Once you have blocked it, it no longer receives your display name or notices of changes to your profile; it then only knows your account ID, since when you were connected and when you last changed your phone number.
Content and encryption
Service accounts may only send notifications you have ordered from the provider, and no advertising. Messages you send directly to a service account are not accepted by our server; a service account only reads along in its bridge groups. Its notifications are end-to-end encrypted between the device of the service account and your devices. The device of the service account is a program of the provider (the "messenger bot"), which runs on a computer of the operator in Germany. There the notifications exist in plain text before they are encrypted for your devices – only for the duration of the dispatch. The bot does not store notification texts and writes neither e-mail addresses nor notification texts to its log. As with all messages, our server only sees encrypted content.
Legal basis and objection
The legal basis for the matching is Art. 6(1)(f) GDPR – your interest in receiving the notifications you ordered and our interest in a working service. You originally gave us the address as a way back into your account; the matching is a further purpose that is compatible with it, because it can only be triggered by someone who has confirmed the same address with the provider, and because the result is merely a request that you can decline or block (Art. 6(4) GDPR). You can object at any time: beforehand with the switch, afterwards by blocking, or informally by e-mail to support@takeda.chat. For the connection itself – delivering the notifications after you have accepted – the legal basis is Art. 6(1)(b) GDPR.
The service accounts of apollosys Let
Currently there are two service accounts of the rental system apollosys Let:
- "ApolloLet" – notifications about your rentals (payments, expiry, meter status);
- "ApolloLet Support" – relays support chats from the rental system (bridge groups).
For the connection, the bot stores only the mapping of your confirmed e-mail address to your account – before you accept, to the open request, which it forgets after 30 days. It is deleted when you switch delivery off in apollosys Let, block the service account, remove the contact or delete your account. What the notifications say comes from apollosys Let; its privacy notes apply to that.
Both services are technically separate: apollosys Let and the bot learn nothing about your account from the Take Da Chat server as long as you have not accepted.
10. Bridge groups
A service account can create a group whose messages are relayed as text to another service (bridge): messages arriving there appear in the group; replies go back to the other service as text. Such groups are marked as bridge groups in the app and carry a fixed description that nobody can change. You only become a member if you have accepted that service account's contact request.
- What you write in a bridge group is decrypted by the service account's device and handed to the other service. There it appears as a message from a bot; the transmission runs via the servers of the operator of the other service (currently a provider in the USA), and their rules and privacy terms apply there. Pictures, voice messages and files are not relayed.
- In a bridge group the service account sees what you write there, when you are typing and what you have read – like any member of a group.
- As with all groups, the name and description of the group are stored in plain text on our server. Once a case is finished the group is closed and deleted 90 days after closing.
- The legal basis is Art. 6(1)(b) GDPR (you answer requests from the other service for which you accepted the bridge). The transfer to the USA is based on Art. 49(1)(b) GDPR.
10a. GIF search
GIF search is off until you switch it on yourself – in the GIF tab or under Settings → Privacy → Outside services. If you then search for a GIF, the search term and your language setting go to our server. It uses them to query GIPHY (Giphy, Inc., USA) or KLIPY (Kikliko, Inc., USA) and passes the results on; the app also loads the selected GIF via our server.
- The provider receives the search term, the language and our server's address – not your IP address, no account, no device, no identifier, no cookies. What it does with the search term is governed by its privacy policy (GIPHY, KLIPY). According to its policy, KLIPY uses search terms for purposes including improving its service and advertising.
- We store none of this; we only count the number of requests per provider. On your device, the app remembers when you consented.
- Only content rated "G" (GIPHY) or passing the strict filter (KLIPY) is shown; KLIPY advertising is switched off.
- The legal basis is your explicit consent (Art. 6(1)(a) and Art. 49(1)(a) GDPR). Both providers are based in the USA. We do not rely on the adequacy decision on the EU-US Data Privacy Framework for either of them. There is therefore no protection equivalent to that in the EU and there are no appropriate safeguards; in particular, authorities there may access the data, and your rights are harder to enforce there. A search term is personal data only if it reveals something about a person.
- Withdrawal: switch it off again there. After that nothing is sent to the providers; everything else works without GIF search. The operator can switch the search off per provider at any time; the app then says "not available".
10b. Link preview
When you insert a link into a message, you can create a preview (title, description, small picture) before sending. The target page is fetched by our server, not by your device; the target server only sees our server's address.
- Our server sees the link address only at that moment and only for the sender; it neither stores nor logs it. It never fetches internal addresses or network ranges.
- The preview becomes part of the encrypted message; the recipient fetches nothing.
- Link preview is switched on. You can switch it off under Settings → Privacy → Outside services; our server will then no longer fetch pages for you. At your first link, the app points this out – in the apps once per account on the device, in the browser once per session, because nothing stays stored there. The operator can switch the feature off. Legal basis: Art. 6(1)(b) GDPR.
10c. Map and location
When the app shows a map – for example when sharing or viewing a location – the map tiles come from our server, not from a third-party map service. Which tiles a device loads roughly reveals which area it is looking at; that is why neither the server nor the upstream web server logs tile requests.
- The access key for tiles is bound to your device; the server keeps it only as a checksum in working memory for one hour.
- The shared location itself is message content and end-to-end encrypted.
- Live location: you start it yourself for 15 minutes, 1 hour or 8 hours and can stop it at any time (in the chat or under Settings → Privacy → Location). The positions are end-to-end encrypted. Our server only sees that, and how often, your device sends messages to the chat during that time – not where you are.
- On Android, a visible service with a notification runs for as long as you share.
- Location for your address (small map in the profile): if you set a location for your address in your profile, it is sent end-to-end encrypted only to contacts who may see your address; our server does not see it. If no location is set, the app shows "No location on the map"; nothing is sent to others.
- Map data © OpenStreetMap contributors, Open Database License (ODbL); processing: Protomaps. The attribution is also shown in the app.
- Legal basis: Art. 6(1)(b) GDPR. The operator can switch the map off.
10d. Address book matching
Only when you press the button ("New" → "Add contact or invite" → "Find contacts"), and only in the Android app. The app first tells you what will happen ("Take Da checks which of your contacts are already on it."); only then does your phone ask for access to your contacts. You can refuse – without any disadvantage.
- On your device, the app computes a checksum (SHA-256) for each phone number and sends only these checksums to our server – no names, no phone numbers in plain text, no e-mail addresses. A checksum is not a secret: anyone who knows a phone number can compute it. It does not make the number anonymous.
- The server compares them in working memory with the phone numbers of accounts whose discoverability by phone number is set to "Everyone". "Everyone" is the default for every account – including yours. You can change it under Settings → Privacy → Who can find me. The server returns the matches (account, display name, username), never a phone number.
- Neither the checksums nor the matches are stored. For each run the log contains: your account, the number of checksums and the number of matches. The app does not store your address book.
- At most 3 runs per day; the first 2000 numbers are checked per run. Numbers without a country code are treated as German numbers.
- The phone numbers in your address book belong to other people. Legal basis: for your matching, your consent by pressing the button (Art. 6(1)(a) GDPR, section 25(1) TDDDG) – you withdraw it by not starting another run and by revoking the app's access in your phone's settings; for third parties' phone numbers, our legitimate interest and yours in finding people you know on the service (Art. 6(1)(f) GDPR), with the comparison taking place in working memory only. Anyone who does not want to be found changes their discoverability; anyone without an account is never found, and their checksum is discarded immediately. The operator can switch matching off.
10e. Group links, join requests, member tags
- Group link and QR code: an admin can create an invitation link (valid for 7 days, at most 30 days). The server stores only a checksum of the link, who created it and its validity – never the link itself. Group name and member count are shown only after signing in in the app; the public invitation page does not show the group name.
- Join request: anyone who wants to join via a link sends a request; they become a member only once an admin approves. Stored are account, group, source (link or community), time, decision and who decided.
- Member tag: admins can give members a short label (up to 30 characters, e.g. "Granny"). Like the group name, it is stored in plain text on the server, visible to all members and removed with the membership.
- Anyone who has a valid link and is signed in to the app sees the group name, the number of members and – if the group belongs to a community – the community's name, even before an admin approves. So only give a link to people you know. An admin can revoke the link at any time.
- With your request, the group's admins see your display name – not your phone number and not your e-mail address.
- Member tags are assigned by admins only, not by you. You see your tag like all members. If you want it changed or removed, contact an admin or us.
- Links beginning with takeda:// are opened by the app itself; nothing is sent to third parties.
- Retention: links up to 30 days after expiry or revocation; decided requests 30 days after the decision; open requests are withdrawn after 30 days. Legal basis: Art. 6(1)(b) GDPR.
10f. Communities
A community links several groups and has an announcement group. Members of the community are the members of the announcement group; admins are its admins. In the announcement group only admins can write; everyone can react.
- The name, description and picture of the community are stored in plain text on the server, as with groups; the picture is that of the announcement group. In addition, the server sees which groups belong to which community and join requests to its groups (as in 10e). Content remains encrypted.
- Your communities are shown in the chat list (filter "Communities"); you create a new one via "New" → "New community".
- Other members see your name and profile picture according to your visibility levels – never your phone number or e-mail address unless you are contacts.
- A community has at most 50 groups and 500 members. Leaving the community means leaving the announcement group; you leave the other groups one by one.
- A community can be reported like a group (10g); what is reported is its announcement group.
- Retention: a dissolved community is deleted 90 days after dissolution; memberships end with the group. Legal basis: Art. 6(1)(b) GDPR.
10g. Reports: groups, communities, media and profile
- Reporting a group: members can report a group (reasons as for contacts, plus "profile"). The server records the group name, description and admins at the time of the report, together with the reason, free text and the messages the reporting person releases as evidence. Those reported are not told about the report.
- Media in reports: up to 5 pictures, videos, voice messages or files can be attached to a piece of evidence, at most 10 per report. For this, the server makes a copy of the encrypted file and receives the key from the reporting person. Decryption happens only manually by the operator when reviewing the report, never in the running service.
- What you select for a report – messages and media – is sent to the operator unencrypted: it leaves end-to-end encryption, and the operator can read it. The app tells you so before you send. No message and no attachment is included without your selection.
- Name and profile picture as evidence: if you report a contact for the reason "Name or profile picture", the name under which your device shows the contact and the contact's profile picture are also sent – more precisely, the identifier of the picture and the key with which the operator can open it. Otherwise the report could not be examined. The same key also encrypts the info in the contact's profile (section 6); the operator can therefore read that info as well. The app shows you in the report window that name and profile picture are sent along, before you send. For every other reason, no profile picture is sent – not for reports concerning the endangerment of children either.
- Reported media may show people other than the person reported; we use these data, too, only to examine the report.
- Endangerment of children: for reports concerning the endangerment of children, the app sends no media – no pictures, videos, voice messages or files, and no profile picture as evidence. The report itself (reason, your text, selected text messages) goes to the operator. Please also contact the police about such content. If a media file, or a key to one, nevertheless reaches the operator for this reason (older app version), the media file is not viewed but only kept for a report to the police or the Federal Criminal Police Office (BKA).
- Proof: for every reported message, a proof goes to the operator that allows checking that the message is genuine. For reports concerning the endangerment of children, this proof contains no keys that could open a picture, a video, a voice message or a file. The text, the type of message, the time and the identifiers remain. What can still be verified is who the message came from and when; whether its content is unchanged can no longer be verified for such a message.
- Retention: reports that have been dealt with – including reports of messages and contacts – are deleted together with evidence and media copies 90 days after being dealt with; open reports remain until dealt with.
- Legal basis: Art. 6(1)(f) GDPR – protecting members and preventing abuse; for passing on to authorities Art. 6(1)(c) GDPR where there is an obligation, otherwise (f).
10h. Passkeys
For signing in to the web access you can register a passkey (WebAuthn) instead of the web password – in this version it can be created only in the Android app, not from a web session; at most 10 per account. Passkeys are optional.
- Set up and manage: Settings → Security → Passkeys. In this version you can create a passkey only in the Android app (Android 9 or later, with a screen lock); renaming and deleting also work on a computer, not in the browser. Signing in with a passkey works only in the browser at web.takedachat.com.
- We store the public key, an identifier of the passkey, a name you choose, an identifier of the type of your passkey store (AAGUID), the transports (e.g. "internal", "usb"), whether it is synchronised, a counter and timestamps. No biometrics: your fingerprint or face never leaves your device; the server only learns that the key was released.
- Who keeps the passkey: not us, but a password manager on your phone. From Android 14 you choose it yourself – Google's, your phone maker's or another one you have set up. On phones with Android 9 to 13 it is Google's password manager; the passkey is then stored in your Google Account, and you need a Google Account on the phone for this. Android shows you a window of its own before saving; if you cancel there, nothing is saved.
- What the password manager receives: the address takedachat.com, the label "Take Da Chat", an internal identifier of your account and the newly created key; it also sees which app is asking. It does not receive your phone number, your name or your username from us.
- Whether the password manager keeps the passkey on the phone only or transfers it to your other devices via its account is determined by its settings and terms; we have no influence on this. If the provider is based outside the EU – Google LLC, for example, in the USA – it may also process the data there. The provider is responsible for this; its privacy notice applies.
- Google components in the Android app: for this window, the Android app contains components from Google from version 1.53.0 (libraries for Google Play services and Android's Credential Manager). On phones with Android 13 or earlier, creation runs through the phone's Google Play services; from Android 14, through Android itself. Our app calls these components only when you tap "Create passkey". What Google Play services and the password manager transmit to their provider in the process is determined by their providers.
- So that your phone can associate passkeys for takedachat.com with this app, a public file is fetched from our website (takedachat.com/.well-known/assetlinks.json) – depending on the phone, by a Google service. It contains only information about the app, no data about you.
- If you sign in with a passkey in the browser, your browser requests it – on this device or, via a QR code, from your phone. The connection between browser and phone is established by the browser and the operating system, not by us; servers of their makers may relay it. We receive only the confirmation that the key was released and – as with every sign-in – your IP address.
- Without a passkey everything stays as before (QR code, short code or password). If you delete a passkey in the app, it is no longer valid with us; you also delete it yourself in the password manager. With us it is deleted with your account at the latest.
- Legal basis: Art. 6(1)(b) GDPR; for access to your device, section 25(2) no. 2 TDDDG (necessary for the feature you requested). Our server does not transfer any data to Google or another provider in the process; the password manager on your phone receives the details above from the app.
10i. Call links and waiting room
You can create a call link (valid for up to 30 days) and pass it on. Anyone who opens it knocks and waits; you admit or decline. An admission is valid for 30 minutes. The call itself is encrypted like any call, if necessary via our relay server (section 12).
- Stored are a checksum of the link, its label, whether with video, and its validity; when someone knocks, the account (or the guest, 10j), the time and your decision. The server hands out the link itself only once, when it is created.
- The public invitation page shows neither your name nor the label.
- Retention: deleted immediately when you delete the link; otherwise 7 days after expiry or last change at the latest. Legal basis: Art. 6(1)(b) GDPR.
10j. Guests without an account – currently switched off
Once the operator switches this feature on, someone with a call link but without an account can knock as a guest – in the browser or in the app – and join the call after being admitted. Nothing else: no conversations, contacts, groups, media, no profile, no notifications. In the waiting room a guest is marked as "Guest".
- Stored for a guest are the freely chosen display name, the keys of their device, a checksum of the credentials, an internal substitute number (it is never shown outside), the assignment to this one link and the times in the waiting room; to prevent mass sign-ups, also a checksum of their IP address with a daily changing secret, deleted after 2 days.
- Retention: guest access lasts at most 24 hours or until the link expires; it is deleted 1 hour later at the latest, immediately on decline or when the guest ends it.
- The invitation page shows a short notice under Art. 13 GDPR. A guest has no data report in the app; they exercise their rights by e-mail (section 15).
- Legal basis: Art. 6(1)(b) GDPR (joining the call at their own request); for preventing mass sign-ups (f).
10k. View once
Messages for viewing once, including their media, are kept encrypted on the server for up to 14 days if the recipient does not collect them sooner. The server only sees that it is such a message, not its content. Legal basis: Art. 6(1)(b) GDPR.
10l. Stickers
You can make stickers from your own pictures, from text or from a short recording of your own, and send them. The app only has stickers you made yourself – no sticker packs, no sticker service.
- A sticker is a message like a picture: end-to-end encrypted. Our server sees its size and time, not its content.
- Your sticker collection is kept on your devices, encrypted. If you have several devices or use the web access, the app synchronises the collection between them – end-to-end encrypted. To do so, it uploads each sticker to our server in encrypted form, like a picture you send. At most one such copy of each sticker is kept there; it is not uploaded anew for every web session. Only your devices have the key; we cannot view your stickers. We see your account, the size and the time.
- If you delete a sticker, the app also deletes this copy on our server; if that does not succeed right away, it catches up at the next start. Otherwise the copy stays at most until the retention period for media ends (section 13, currently 90 days); if your devices need it again after that, the app uploads it anew. In the browser, the collection exists only in the memory of the page. There, the page fetches a sticker's encrypted picture only when it is shown or sent – also for a suggestion while you type; our server sees when a copy is fetched, not its content.
- Suggestions while you type an emoji are produced on your device only. Cropping is done by hand on your device; no picture is sent to a service for it.
- You are responsible for what you turn into a sticker: only use pictures you made yourself or are allowed to use (copyright). If other people can be recognised in a picture, you generally need their agreement before you turn it into a sticker and send it (right to one's own image). Much the same applies to another person's voice in a recording. A sticker can be reported like any message (10g).
- Legal basis: Art. 6(1)(b) GDPR.
10m. Animated emoji
The animated emoji are part of the app; nothing is loaded from the network when they are shown. Source and license are listed in the app under "Licenses and sources". You can switch the animation off in the settings.
10n. Avatars
Instead of a photo, you can use an avatar made of a background colour and a character (an emoji or your initials) as your profile picture. The app draws it on your device; it is treated like any other profile picture (sections 4 and 6).
11. Purposes and legal bases
| Account, contacts, groups, message delivery, media, status, invitations, web access | Art. 6(1)(b) GDPR – without this data the service cannot exist |
| E-mail address as recovery route, username, profile picture, info, postal address, visibility levels, notes, pinned/favourites/lists, read receipts, online status | Art. 6(1)(b) GDPR – voluntary, set by you, can be removed or switched off at any time |
| Chat backup on our server | Art. 6(1)(b) GDPR – voluntary, switched on by you, can be switched off at any time |
| Browser notifications (the browser's push service) | Art. 6(1)(b) GDPR – switched on by you; third countries see section 8 |
| Matching the confirmed e-mail address for contact requests from service accounts | Art. 6(1)(f) GDPR; objection with the switch or by blocking the service account |
| Delivering a service account's notifications after you accept; relaying in bridge groups | Art. 6(1)(b) GDPR; third country for bridge groups see section 10 |
| SMS verification, rate limiting, security events, registration lock, expiry of unconfirmed addresses, deletion markers of deleted accounts | Art. 6(1)(f) GDPR – protection against abuse and account takeover |
| Suspending accounts, registration stop, blocked e-mail domains, handling reports | Art. 6(1)(b) and (f) GDPR – enforcing the terms of use and protecting the other members |
| Copy of a viewed status on the viewer's device (30 days), upload again when reporting | Art. 6(1)(f) GDPR – protecting members: a reported status must be provable even after 24 hours |
| Operator's operations log, operating metrics, call quality feedback, access logs | Art. 6(1)(f) GDPR, Art. 32 GDPR – traceable, secure operation; interventions must be verifiable |
| Translation on our server | Art. 6(1)(b) GDPR – only if you switch it on for a conversation |
| GIF search | your consent (Art. 6(1)(a), Art. 49(1)(a) GDPR) – see section 10a |
| Link preview, map and location sharing, group links and join requests, member tags, communities, passkeys, call links and waiting room, guests, view once, stickers, animated emoji, avatars | Art. 6(1)(b) GDPR |
| Address book matching | Art. 6(1)(a) GDPR (pressing the button); for third parties' phone numbers (f) – see section 10d |
| Group reports, media in reports, name and profile picture as evidence | Art. 6(1)(f) GDPR – protecting members; passing on to authorities (c) or (f) – see section 10g |
| Preventing mass sign-ups of guest access | Art. 6(1)(f) GDPR |
| Support requests | Art. 6(1)(b) or (f) GDPR – answering your request, including an objection to a suspension |
12. Recipients
Confirmation text messages are sent exclusively via our own SMS device – a mobile phone with a SIM card of the operator; no SMS service provider is involved. The text message itself is transmitted by the network operator of that SIM card over its mobile network, as a telecommunications service. The phone number and the text are transmitted.
E-mails (invitations, confirmation codes) are sent via our own mail server on a computer in Germany; no external mailing service is involved. The e-mail is delivered to the mail provider of the recipient address; the address and content of the e-mail are transmitted.
Calls that cannot be connected directly run via a relay server (TURN) that we operate ourselves. It sees IP addresses and encrypted data packets, no content. We also run the translator ourselves.
Push services of browser manufacturers, only if you switch on notifications in the browser (section 8). The operator of the connected service (currently in the USA), only for texts in bridge groups (section 10). Service accounts receive what is set out in section 9.
GIPHY and KLIPY receive the search term and language of the GIF search from our server (section 10a). The target server of a link only sees our server's address and the requested address when a preview is created (section 10b). Police and law enforcement authorities receive reports including evidence if we report a criminal offence or are obliged to (section 10g).
The password manager on your phone – on phones with Android 9 to 13, Google's – receives the details set out in section 10h when you create a passkey. This happens on your device; our server does not transfer anything to the provider in the process.
Beyond that, we do not pass on any data.
13. Retention
- Account data (phone number, name, username, confirmed e-mail address, postal address, info, visibility levels, operator and service account badges, contacts, groups, pinned/favourites/lists): as long as the account exists.
- Unconfirmed e-mail address: 24 hours.
- Messages in transit: collected messages are deleted by the server immediately. Messages not collected expire after 45 days. Delivery records (without content): 30 days; send receipts: 7 days.
- Encrypted pictures, voice messages, videos, files: 90 days.
- Status (encrypted file, undelivered status): 24 hours. The copy for reporting on the viewer's device: 30 days. A file uploaded again for a report: like other media, at most 90 days.
- Notes: as long as you keep them; of a deleted note only a deletion marker without content remains for 90 days.
- Chat backup: as long as you have it switched on. If you switch it off, remove your password or delete your account, it is deleted immediately.
- What happened in a group: 90 days on the server. It remains in your app's history – your device has remembered it.
- Verification attempts (phone number, IP address): 24 hours. A redeemed code is deleted immediately. Dispatch order of a confirmation text message: phone number and text are cleared after 30 days; a booking line without either remains.
- Everyday events in the account log (new contacts, requests, device warnings): 90 days. Security events: as long as the account exists.
- Invitations: until redeemed or 14 days. The invitation chain: 12 months; if you have invited others, your account ID remains there until it expires – even after your account has been deleted, to protect against abuse.
- Reports – including group reports – together with the text disclosed for them and attached media copies: 90 days after the report has been dealt with.
- Web session: ends after 60 minutes without input, after 7 days at the latest; in the browser everything is gone when the page is closed.
- Requests from service accounts: an unanswered request expires after 30 days. The record of a closed – declined or expired – request is deleted after 60 days at the latest. An accepted connection remains until you end it. Counts of a service account's requests (without addresses): 2 days. Addresses without an account: not stored.
- Bridge groups: 90 days after closing.
- Group links: 30 days after expiry or revocation. Join requests: 30 days after the decision; open requests are withdrawn after 30 days. Member tags: as long as the membership exists.
- Communities: 90 days after dissolution.
- Call links and waiting room: 7 days after expiry or last change; immediately when you delete the link. Guest access: at most 24 hours, deleted 1 hour after expiry at the latest; checksums of IP addresses: 2 days.
- View-once messages including media: at most 14 days.
- Passkeys: until you delete them, at the latest with the account.
- Sticker collection: on your devices for as long as you keep it. The encrypted copy of a sticker used to synchronise your devices: until you delete the sticker, at most 90 days, like other media.
- GIF search, link preview, map requests, address book matching: nothing is stored; for address book matching, the log contains one line per run with the account and counts (section 10d).
- Deletion markers of deleted accounts: 90 days.
- Suspension data: until the suspension is lifted. A suspended account that remains unresolved for twelve months is deleted.
- Operator's operations log: 12 months.
- Operating metrics and call quality feedback (without personal reference): raw values 24 hours, per-minute values 7 days, five-minute values 90 days, hourly values 2 years.
- Error reports: 90 days.
- Server access log: 90 days.
14. Minimum age
You may use Take Da Chat from the age of 16. From 13 to 15 years only with the consent of your parents (or other legal guardians); there are no accounts for children under 13. The limit follows the age limit of Art. 8 GDPR, which is 16 years in Germany. Section 2 of the terms of use says the same. We do not ask for a date of birth.
If we learn – for example through a tip-off – that an account belongs to a child under 13, or to a child aged 13 to 15 without parental consent, we suspend it and check back; if this is confirmed, we delete the account together with all server data. Parents can request the deletion of their child's account at any time, informally by e-mail to support@takeda.chat.
Guests without an account (section 10j) do not state an age; the host decides whom to admit to the call.
15. Your rights
Access (Art. 15), rectification (16), erasure (17), restriction (18), data portability (20) and objection (21) – to be addressed to the address given above; this also applies to guests without an account (section 10j). You can withdraw consent (sections 10a, 10d) at any time with effect for the future. You also have the right to lodge a complaint with a supervisory authority.
16. Data report and account deletion
Both are available directly in the app, not in the browser: the data report under Settings → Account → "My data", deletion under Settings → Account → "Delete account".
- Data report: "Request report" fetches everything the server has stored about your account. The app shows it in readable form, with a short sentence per section saying what it is – and, where there is a separate period, how long it is kept. It also includes group links, join requests, communities, passkeys and call links with their waiting room, with guests who knocked marked as "Guest". You can save it as a report (HTML) – for reading and printing, and your browser can also save it as a PDF – or, for experts, as a JSON file. Not included are message contents (they are end-to-end encrypted and stored only on your devices), password and PIN checksums, encrypted content such as notes, profile info or backup (only counts, sizes and times) and reports other people made about you.
- Deletion: "Delete account" removes your account together with all server data. You leave all groups. Your profile photo is deleted from the server right away; your other media there expire within 7 days at the latest – until then, recipients can still download them. The device on which you delete is wiped, including your backup file; so are your other devices – right away if they are online, otherwise as soon as they reconnect (for up to 90 days).
You can also request both informally by e-mail to support@takeda.chat. What other members have received from you is stored on their devices and is not removed by your deletion.
17. If your account has been suspended
The app shows you the date, reason and any note. Your conversations remain readable on your device; nothing is deleted. How to object and how long a suspension lasts is set out in section 4 of the terms of use.
18. Changes to this policy
If we change this policy, the new date will appear here. We announce significant changes in the app: after starting, it shows you the notice "Privacy Policy and Terms of Use updated" once, with links to this page and to the Terms of Use – in the apps, not in the browser.
Changes in version 1.2: new sections 10a–10k (GIF search, link preview, map, address book matching, group links, communities, group reports, passkeys, call links, guests, view once); sections 2, 3, 4, 8 and 11–16 supplemented.
Changes in version 1.4: GIF search only with consent (10a); link preview is switched on (10b); address book matching: discoverability is the default (10d).
Changes in version 1.5: new sections 10l–10n (stickers, animated emoji, avatars); passkeys are available – created in the Android app, which contains components from Google for this purpose (10h, 7, 8, 12); reports: name and profile picture as evidence, reports concerning the endangerment of children without media (10g); supplemented: link preview (10b), map and location (10c), address book matching (10d), group links (10e), communities (10f) and sections 3, 4, 11, 13, 16 and 18.
Last updated: 15 November 2026 · Version 1.5 · Periods as of server version 0.56.1+1, apps 1.53.0+245. German version: Datenschutzerklärung.