Take Da Chat

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:

4. What data is stored on the server

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.

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

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:

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.

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.

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.

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.

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.

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.

10g. Reports: groups, communities, media and profile

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.

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).

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".

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.

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

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".

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.