Effective from 23 October 2026
This translation is provided for convenience. In case of any discrepancy, the Czech version prevails.
This policy describes what personal data the Discussion application and website (the “service”) process, for what purpose, for how long, and what rights you have. The service is a personal project and puts emphasis on privacy – we do not sell the content of your messages or misuse it for advertising. The rules of using the service are governed by the separate Terms of Use.
The controller of personal data is Bc. Michal Trnka, Company ID (IČO) 14118971 (a natural person, Czech Republic), operator of the Discussion service. Contact: mitrnka@gmail.com.
| Category | Data | Purpose |
|---|---|---|
| Account data | E-mail address, nickname, password (stored in encrypted/hashed form) | Creating and securing the account, sign-in, password recovery |
| User content | Private messages, reactions, attachments (photos, videos, files), and on the web also discussion posts, comments and votes | Providing chat and discussions between users |
| Contacts / friendships | List of friends and friendship requests | Contact list, controlling visibility and communication |
| Meeting-people details (optional) | Year of birth (the year only, never the full date – used to compute an approximate age), gender, a short “About me” text and the “I want to meet people” option. Filling them in is voluntary and they can be changed or deleted at any time in your profile settings. Logged-in users see your approximate age and gender on your profile; the “About me” text is visible to anyone who can see your profile. A message attached to a friend request is stored encrypted, is visible to the sender and the recipient (the recipient also sees it in the notification on their device) and is deleted once the request is approved or declined. | Listing in the search for people who want to meet others (only when the option is ticked) and display on your profile; not used for advertising |
| Loyalty cards (optional) | When you save a loyalty card in the mobile app: its name, card number or code, code format (e.g. EAN-13 or QR), colour, note, the store brand chosen from the list (if any) and the order of your cards. This data is stored with your account so that your cards sync between your devices; it is transmitted encrypted (HTTPS) and we do not share it with third parties or other users. Photos, images and screenshots you read a card from, and the camera image while scanning, are never sent to the server – they stay on your phone. | Showing your cards on all your devices; not used for advertising |
| Technical and security data | IP address, sign-in time and history, time of last activity | Account security, abuse prevention and audit |
| Notification identifiers | Push notification registration token (Firebase Cloud Messaging), on Apple devices a token for incoming calls (Apple PushKit) | Delivering push notifications and incoming calls |
| Error diagnostics (mobile app) | Anonymous technical data sent when the app fails/crashes: platform type (Android/iOS), operating system version, device model, app version and error description. They are not linked to your account or identity and are not used for tracking. | Detecting and fixing errors, improving app stability |
| Data processed by artificial intelligence (AI) features | Text you yourself submit to the spell-check or rephrasing feature (“magic pencil”), the description you enter to generate a profile picture (avatar) or a group chat icon, and – only when a participant of a conversation turns on automatic translation – the text of all participants’ messages in that conversation, which is translated into each recipient’s language. Turning translation on is announced to all participants in the conversation and any of them can turn it off at any time. Without translation turned on, regular message and discussion content is never sent to AI. | Spell-check and rephrasing of text, profile picture generation, automatic translation of conversation messages |
| Purchase of credits in the mobile app | Purchase confirmation from Google Play or the App Store (transaction identifier, package, time, any refund). We do not process payment card details – the payment is processed by the app store. | Crediting purchased credits, handling refunds, compliance with legal obligations |
Voice calls take place directly between devices (peer-to-peer, WebRTC technology) – our servers do not store the content of calls. In difficult network conditions the audio is relayed through our relay (TURN) server, but it is not stored there either.
Group calls with a larger number of participants (experimental mode) are transmitted through our server, which only forwards the audio to the other participants; the content of the call is neither recorded nor stored.
When you report objectionable content or block another user, we keep a record of the report or block (who, whom/what and any reason given). The legal basis is the operator's legitimate interest in content moderation and the safety of the service; without this processing a report cannot be handled within 24 hours.
We do not sell personal data. We use the following processors to run the service:
You can delete your account and the data connected to it directly in the service: on the web in My Account → Delete account (you can reach your web account from the mobile app as well). You can also request deletion by e-mail at mitrnka@gmail.com. After deletion, the user's data (messages, attachments, friendships, posts) are removed.
In accordance with the GDPR you have the right of access to your data, rectification, erasure, restriction of processing, data portability and the right to object. You can exercise your rights using the contact below. You also have the right to lodge a complaint with the Czech Office for Personal Data Protection (uoou.gov.cz).
The service is not intended for persons under 15 years of age (the age from which a child in the Czech Republic can give consent to the processing of data in relation to information society services). If we find out that we have processed a child's data without proper consent, we will delete the data.
Communication with the servers is encrypted (HTTPS). Passwords are stored in hashed form. Access to data is restricted and protected.
Chat message texts are stored in the database encrypted (AES-256-GCM); the encryption key is not part of the database or its backups. This is not end-to-end encryption – the operator is technically able to read message contents (e.g. when handling a report or for the translation and text-correction features).
We may update this policy; the current version is always available at this address.
Bc. Michal Trnka – mitrnka@gmail.com
Web: discussion.cz