Privacy at Friendstime
This privacy policy explains which personal data we process when you use Friendstime, what we need it for, how long we keep it, which service providers are involved and what rights you have. It applies to the website friendsti.me, the Android app and access via our onion service in the Tor network. Our own servers are located in Germany.
Short version: We process the data needed for your account and the features. The text of private chats is end-to-end encrypted (hybrid with X25519 and ML-KEM-768) – our server only stores ciphertext of it. Under the conditions described in section 2.3 this also applies to images, voice messages, groups and calls. We do not use analytics or advertising trackers from third parties and do not create advertising profiles. Some features use external services (e.g. payments via Stripe) – they are listed in section 8. You can export your data and delete your account at any time.
1. Data Controller (Art. 4 No. 7 GDPR)
Alexander Krauskopf
Klingerstr. 33
95615 Marktredwitz
Germany
Data protection email: datenschutz@friendsti.me
General contact: support@friendsti.me
2. What data we process
2.1 Account (required)
- Email address – for signing in, account recovery and messages about your account
- Username – publicly visible
- Password – stored only as a hash (bcrypt via PHP
password_hash), never in plain text - Date of birth – for age verification and youth protection; your birthday is visible to friends by default (birthday reminders) – you can change this in the privacy settings to “Everyone”, “Friends only” or “Only me”
2.2 Profile (optional)
- First and last name, profile and cover picture, bio, place of residence, pronouns, links and other details you enter yourself
- You decide who sees what in the privacy settings; you can hide your name from others
2.3 Content, messages, calls
- Posts, comments, reactions, stories, photos, videos, group, page and marketplace content – visible according to the visibility you choose. Public posts only appear in search engines if you allow it (e.g. under Settings → Data).
- Private chats: The text is end-to-end encrypted (hybrid key exchange with X25519 and ML-KEM-768 according to FIPS 203, content with AES-256-GCM; our server no longer accepts messages using older schemes – RSA-OAEP only or ML-KEM-768 only). Our server only stores ciphertext of it. For delivery we process sender, recipient, time and read status.
- Group chats: The text is end-to-end encrypted (hybrid, as in private chats) if the group is encrypted; this requires all members to have hybrid keys. In groups that were never encrypted, it is transmitted encrypted (TLS) and stored readable on our server.
- Images, videos, voice messages and files in chats: end-to-end encrypted in one-to-one chats and encrypted groups (hybrid, as in private chats) if all participants have hybrid keys. Our server then only stores the encrypted file and sees its size, the time and the participants. In groups that were never encrypted, they are transmitted encrypted (TLS), stored on our servers and delivered only to the participants of the chat.
- Voice and video calls: run via our own media server. They are end-to-end encrypted if all participants support it (the key is exchanged with the hybrid scheme, as in private chats); otherwise they are only encrypted in transit, and the call shows a notice. Text messages and reactions within a call are only encrypted in transit. Captions in calls are not end-to-end encrypted: their text passes through our server and is deleted there after about 60 seconds.
- Live streams: run via our own media server; they are encrypted in transit, but not end-to-end encrypted.
- Other end-to-end encrypted areas: live location, shared places, moments in chats, new uploads to your vault and your notes about people (on the web; in the app from version 5.57.770) are also encrypted with the hybrid scheme. Our server sees who shares with whom, times and sizes.
- Not end-to-end encrypted are in particular: public and other non-private content (e.g. posts – including posts for friends only –, comments, profiles), captions in calls and the metadata of communication (who with whom, when, size). They are transmitted encrypted (TLS).
2.4 Location (only for features you use yourself)
- Sharing your location in a chat, live location, places: coordinates are only sent when you start the feature. For live location we remove the coordinates as soon as the chosen duration has expired (at the latest 24 hours after the last location point).
- Route: When you have a route shown on the map (car, bicycle, on foot; train only as an estimate), our own server at netcup in Nuremberg calculates the route from the rounded start and destination coordinates. No external service is integrated and nothing is stored.
- Device list: For the overview of your signed-in devices we store an approximate location (city, region, country). It is only more precise than the IP address if you switch this on (app: Permissions → “Device location in the device list”, off by default); the coordinates are then rounded to about 10 km and deleted 30 days after the last report.
- Maps: We load map tiles via our own server; your device has no contact with the map providers (see section 8).
- For publicly uploaded images we remove location and other metadata (GPS/EXIF) from the image file.
2.5 Device and log data
- IP address and browser/device identifier (user agent) – when signing in, registering, for security-relevant actions and in security logs
- Signed-in devices and sessions – for the “Active sessions” view and to sign out individual devices
- Push identifier of your device or browser – so that we can deliver notifications
- App error reports – device model, app version, affected screen and error message; they only go to our own server
2.6 Payments and payouts
- Purchases (e.g. Premium, storage, coins) are processed by Stripe. You enter card details directly with Stripe; we receive the amount, time, status and a payment reference.
- For payouts we store the name and – depending on your choice – the IBAN or the PayPal address.
2.7 Verification and imprint service
- If you apply for a verification badge or the imprint service, our team checks the submitted documents (e.g. images of an ID document) manually. We delete the files 30 days after the review has been completed.
2.8 Youth protection and parental consent
- Under the age of 16, use requires the consent of a parent (Art. 8 GDPR). For this we process the parent’s email address and the status of the consent.
- As long as consent is missing, we block the device for a new registration: for this we store a check value (hash of browser and screen characteristics, time zone, a drawing test and the IP address range) together with the IP address and browser identifier for one year and set the cookie
ft_minor_status. - For the family area (linking a parent and a child account) the separate section “Family & parental area” below applies.
2.9 AI features
- FriendsBot and other AI features run exclusively on our own AI model Teimi, on the operator’s own computers in Germany. No data is sent to Google or other AI providers. Only your messages in the FriendsBot chat are sent to Teimi. AI translation, reply, hashtag and caption suggestions, the automatic AI fact check and the AI image check are currently switched off. For troubleshooting and to protect against misuse, we log AI calls with short excerpts of the request and the response together with your user ID; we delete this log after 7 days. Completed FriendsBot jobs are also deleted after 7 days, and conversations in the FriendsBot window 90 days after the last activity.
2.10 Advertising
- We show ads that are selected according to the text of the surrounding posts – not according to a user profile. With Premium you see no ads.
- We log impressions and clicks with user ID and IP address in order to bill ads and detect click fraud.
2.11 Identity check on suspicion of fake profiles, bot networks or fraud
- Purpose and legal basis: protection against fraud and abuse (fake profiles, bot networks, circumvention of bans) – Art. 6(1)(f) GDPR (legitimate interest). Details of the procedure are set out in the Terms of Service.
- Which data: your profile details, timestamps (registration, request, reminder, deadline, decision), the number of your contact requests and contacts, and the evidence you submit. Notes that an account is “conspicuous” are only visible internally and are never published.
- Copies of ID documents are processed only with your consent (Art. 6(1)(a) GDPR) when you upload them on the verification page. You may mark the copy as a copy and redact all details that are not needed (e.g. document number, access number).
- Decisions by people: whether a check is requested, whether the evidence is sufficient and whether an account is deleted after a missing or rejected confirmation is always decided by a person from our team. There is no automated decision-making within the meaning of Art. 22 GDPR. You receive a statement of reasons and can lodge an objection (Art. 17, 20 DSA).
- Deletion: we delete submitted evidence once the check has been completed, at the latest 30 days afterwards. The check itself (without the evidence) is logged like other moderation decisions.
- Protection against circumvention of bans: to detect second and replacement accounts of banned or restricted accounts, we store an irreversible check value (hash) of a device identifier of the app or of a random browser identifier, as well as a check value of the IP address; no MAC addresses. The legal basis is Art. 6(1)(f) GDPR (protection against fraud and abuse). Retention: as long as the restriction or ban exists, at most 12 months. A match does not automatically lead to a ban but to an identity check by a person.
3. What we do not do
- ✓ No analytics or tracking services from third parties (no Google Analytics, no Facebook pixel) and no advertising ID in the app
- ✓ No advertising profiles and no ads based on user profiles
- ✓ No selling of data and no disclosure to third parties for advertising purposes
- ✓ No analysis of the encrypted text of private chats – our server only stores ciphertext of it
4. Legal bases
- Art. 6(1)(b) GDPR – performance of a contract (account, Friendstime features, delivery of messages and notifications, payments, features at your request)
- Art. 6(1)(c) GDPR – legal obligations (e.g. retention of invoices and payment records)
- Art. 6(1)(f) GDPR – legitimate interest (security, protection against abuse and spam, identity checks on suspicion and protection against circumvention of bans (section 2.11), security logs, error reports, moderation and fact checks of public content, billing of ads)
- Art. 6(1)(a) GDPR – consent (e.g. push notifications in the browser, newsletter, optional profile details); you can withdraw it at any time with effect for the future
- Art. 8 GDPR – parental consent for children under 16
- Section 25(2) No. 2 TDDDG – storing and reading information on your device insofar as this is strictly necessary for the features you use (see section 9)
5. Your rights (Art. 15–22 GDPR)
- Access (Art. 15) and data portability (Art. 20): data export as a ZIP file of JSON files under Settings → Data (in the app once every 24 hours)
- Rectification (Art. 16): you can change your profile and settings yourself at any time
- Erasure (Art. 17): delete your account under Settings → Data; a cancellation period of 7 days applies, after which we delete the account
- Restriction (Art. 18) and objection (Art. 21): to processing based on legitimate interests
- Withdrawal (Art. 7(3)): of consent given, at any time with effect for the future
- Complaint (Art. 77): to a data protection supervisory authority, e.g. the Bavarian State Office for Data Protection Supervision (BayLDA)
- Requests to datenschutz@friendsti.me
6. Retention period
- Account and content: as long as your account exists
- Account deletion: after the 7-day cancellation period we delete the account together with the data linked to it; invoices and payment records are kept for up to 10 years under commercial and tax law
- Security and audit logs (with IP address): we automatically delete the security log and the log of security-relevant account actions after 90 days. In the other audit logs (e.g. on actions of our team in administration and moderation) we automatically shorten the IP address after 90 days so that it can no longer be attributed to a connection; the entries themselves are kept as proof. In records kept as proof (consents, contracts, payments, notices under the Digital Services Act, deletion requests) we shorten the IP address after 3 years
- Failed sign-in attempts: 24 hours; registration attempts: 7 days
- Email sending logs: 90 days
- App sign-ins: become invalid after 90 days without use
- IP address of registration and last sign-in, device list, advertising logs: full IP address for 7 days, then automatically shortened (no longer attributable to a connection); other details as long as the account exists. Exceptions: security and audit logs (see above) as well as records kept as proof (e.g. consents, contracts, payments, reports) and block lists, for as long as they are needed for that purpose
- Verification documents: 30 days after the review has been completed
- Youth protection device block: 1 year
- Identity check on suspicion: submitted evidence at the latest 30 days after the check has been completed; check values against ban circumvention (hash of device/browser identifier and IP address): as long as the restriction or ban exists, at most 12 months
- Live location: coordinates until the sharing ends (at the latest 24 hours after the last location point)
7. Security measures
- Transmission: encrypted throughout (HTTPS/TLS). Since 9 November 2026 your device connects to our own front server in Germany (netcup, Nuremberg). There, TLS 1.3 is negotiated with the hybrid post-quantum scheme X25519MLKEM768; browsers and apps that do not offer this scheme connect classically (e.g. with X25519). From the front server to the web hosting (php-friends GmbH, Germany) the connection uses classic TLS with certificate verification; your IP address is passed on to the web hosting in the process.
- Private chats: text end-to-end encrypted (hybrid: X25519 and ML-KEM-768, content AES-256-GCM). Your private key is also stored on our server – encrypted with your password – so that you can use it on new devices; a strong password protects it. The private keys for the hybrid scheme are currently still wrapped with an RSA key (RSA-OAEP, 2048 bits) for this; a change is planned.
- Passwords: stored only as a bcrypt hash
- Database: prepared statements; individual particularly sensitive stored items (e.g. access keys to services) additionally encrypted with AES-256-GCM
- Sign-in: optional two-factor authentication (TOTP) and passkeys
- Tor: Friendstime is also reachable as an onion service; we do not see your IP address then
8. Recipients, service providers and external services
Within Friendstime, only the people who need access for their task get it (e.g. the moderation team for reported content). In addition, the following service providers and services are involved:
8.1 Servers
- php-friends GmbH (Germany) – web hosting, database and email sending; processor
- netcup GmbH (Germany, data centre Nuremberg) – our own server for calls, live streams, connection relaying (TURN), file storage, route calculation and search; since 9 November 2026 every connection to friendsti.me also runs through it as a front server (see section 7). We operate the software on it ourselves (e.g. LiveKit, Valhalla, Meilisearch, MinIO); no further service providers are involved; processor
8.2 External services
- Push notifications: The app is woken via our own wake-up service on our server in Nuremberg. The wake-up signal contains no title, no text and no sender; the app then fetches the notification itself from our server. Google Firebase Cloud Messaging and the push services of the browser manufacturers are switched off. Older app versions (before build 1288) still contain Google’s Firebase component and register with Firebase on start-up; if we switch this route back on for such versions, we will only send a wake-up signal without content through it.
- Stripe (payments): only when paying; Stripe’s payment script is only loaded on pages with a payment function (e.g. wallet, checkout).
- YouTube and Vimeo: We do not embed players of these services. We load preview images of YouTube videos via our own server. Only when you open the link to a video yourself do you leave Friendstime, and the provider receives your IP address.
- OpenTopoMap and official aerial imagery services (maps): the standard map and the satellite image are stored on our own server. Our server fetches the terrain map from OpenTopoMap and aerial images from official geodata services in Germany, Austria, the Netherlands, Belgium, Luxembourg, France, Spain, Poland and the Czech Republic. Only the map section and the address of our server are sent there; your device has no direct contact.
- Place names: the place name for places and the device list is determined by our own place-name service on our server at netcup – with coordinates rounded to about 1 km or your search term. No third-party service is queried for this.
- Search engines (IndexNow): if a public post may appear in search engines, our server reports its web address to the search engine Seznam (Czech Republic); under the IndexNow protocol, Seznam passes the address on to other search engines. Only the address of the post is transmitted, no information about your account or device.
- Discord (optional): if you link your Discord account, we receive your Discord ID, your username and the ID of your profile picture from Discord; your profile shows a note about the linked account.
- PayPal (payouts): only if you choose a payout to a PayPal account.
- QR code scanner of the app: Recognition runs entirely on your device; no data is transmitted to third parties in the process.
8.3 Transfers to third countries
On our part, personal data only reach a country outside the EU and the EEA when you pay via Stripe. According to its own information, Stripe is certified under the EU-US Data Privacy Framework; to that extent, the transfer to the USA is based on the adequacy decision of the European Commission of 10 July 2023 (Art. 45 GDPR). Otherwise the standard contractual clauses of the European Commission apply (Art. 46(2)(c) GDPR), which Stripe provides for in its data processing agreement. You can obtain a copy of the safeguards on request to datenschutz@friendsti.me.
Beyond that, data only leave the EU if you expressly trigger this yourself: if you link your Discord account, choose a payout to a PayPal account, open a link to an external service (for example a video on YouTube) or use FriendsTime Mail to write to recipients at a provider outside the EU. The privacy policy of the respective provider then applies. The website and the current app do not load any content from such services without your action.
9. Cookies and storage on your device
We do not set analytics, statistics or advertising cookies. We only store what is necessary for the features you use or what you set yourself:
| Name | Purpose | Duration |
|---|---|---|
PHPSESSID | session and sign-in, protection against forged requests (CSRF) | until the end of the session |
remember_selector, remember_token | “Stay signed in” – only if you choose it | 30 days |
ft_api_token | sign-in when the app opens a website page | 30 days |
ft_lang | chosen language | 1 year |
cookie_consent | remembers that you have seen the cookie notice | 1 year |
ft_header | chosen header design | 30 days |
ft_tor_banner_dismissed | dismissed Tor notice | 30 days |
ft_minor_status | youth protection device block (only in this case, see 2.8) | 1 year |
ft_dm | random browser identifier to protect against abuse and against the circumvention of suspensions | 400 days |
ft_feed_order, ft_timezone, ft_auto_translate | your settings: feed order, time zone, automatic translation | 1 year |
In addition, the website and app use the local storage of your device (local storage, IndexedDB, service worker cache or app storage) for: the keys of your encrypted chats, your display settings (e.g. design, language, dismissed notices), the status of push notifications, call settings and offline caches. This data stays on your device until you delete it; you can remove it at any time via your browser or app settings. Details are in the cookie policy.
10. Right to object and further mandatory information
Your right to object (Art. 21 GDPR)
You have the right to object, on grounds relating to your particular situation, at any time to the processing of your personal data which we base on Art. 6(1)(f) GDPR (legitimate interests); this also applies to profiling based on that provision. We will then no longer process these data 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.
Where your data are processed for direct marketing purposes (e.g. a newsletter), you can object at any time without giving reasons; we will then no longer use your data for that purpose.
An informal message is enough to object; the easiest way is an e-mail to datenschutz@friendsti.me.
Data protection officer
We have not designated a data protection officer. For all questions about data protection and about exercising your rights, you can reach the controller directly at datenschutz@friendsti.me.
Do you have to provide your data?
No law obliges you to provide us with data. To enter into the user contract, the account details are required (e-mail address, username, password, date of birth) and, if you are under 16, the e-mail address of a parent; without these details we cannot create an account. Individual features need further details, for example payment data for purchases or account details for payouts; without them you simply cannot use that feature. All other details are voluntary.
Data we do not obtain from you yourself
Most data you provide yourself, or they arise when you use Friendstime. From others we receive: the e-mail address of a parent (entered by the child when registering), the name and e-mail address of a trusted person (entered by the parents in the parents’ area), the amount, time, status and identifier of a payment (from Stripe), the identifier, username and profile picture identifier of your Discord account (from Discord, if you link it), reports by other people about your content or your account and – if you use FriendsTime Mail – e-mails that others send you.
Automated decision-making and profiling (Art. 22 GDPR)
We do not take any decisions which are based solely on automated processing – including profiling – and which produce legal effects concerning you or similarly significantly affect you. Account suspensions, reports, appeals and identity checks are always decided by a human on our team. We do not create an interest or advertising profile.
Only these procedures work automatically:
- Feed order “Recommended”: it depends on the time of a post and the number of its interactions, not on a profile of your interests. You can switch to a purely chronological order at any time.
- Ads: they are selected according to the text of the surrounding posts, not according to a user profile.
- Word list: it replaces individual words with asterisks or prevents a post containing a blocked word from being sent.
- Protection against attacks and abuse: a program blocks IP addresses that deliberately search for security vulnerabilities, and limits excessive login or registration attempts. If our team has permanently suspended an account, no new account can be created from the same device.
- Age rules: your date of birth automatically determines whether the consent of a parent is needed (under 16) and which protective rules apply to accounts under 18 (for example, no advertising). If consent is missing, the device block described in the section on the protection of minors applies.
- FriendsTime Mail: incoming and outgoing e-mails are automatically checked for spam.
If you think one of these procedures affects you wrongly, write to us at datenschutz@friendsti.me; a human will then look at your case.
Children and age of consent (Art. 8 GDPR)
Friendstime may only be used from the age of 13. Art. 8 GDPR allows the Member States to set the age for a child’s own consent between 13 and 16 years. We apply the highest limit uniformly in all countries: under 16, the consent of a parent is needed. In individual countries a higher minimum age for use may apply; this is stated in the section “Data protection in your country”.
Error reports from the website
If a program error occurs in your browser, the website sends an error report to our own server: the error message, the address of the page concerned, the browser identifier and – if you are logged in – your user ID. The legal basis is Art. 6(1)(f) GDPR (finding and fixing errors).
All data protection supervisory authorities in the EU and the EEA (Art. 77 GDPR)
You can lodge a complaint with any data protection supervisory authority, in particular in the Member State where you live or work or where the alleged infringement took place. For the controller’s place of establishment (Bavaria, Germany), the competent authority is the Bavarian State Office for Data Protection Supervision (Bayerisches Landesamt für Datenschutzaufsicht, BayLDA). The authorities of the individual countries:
- België / Belgique: Autorité de la protection des données – Gegevensbeschermingsautoriteit (APD-GBA)
- Danmark: Datatilsynet
- Deutschland: Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
- Eesti: Andmekaitse Inspektsioon
- España: Agencia Española de Protección de Datos (AEPD)
- France: Commission Nationale de l'Informatique et des Libertés (CNIL)
- Hrvatska: Agencija za zaštitu osobnih podataka (AZOP)
- Ireland / Éire: Data Protection Commission
- Italia: Garante per la protezione dei dati personali
- Latvija: Datu valsts inspekcija
- Liechtenstein: Datenschutzstelle Fürstentum Liechtenstein
- Lietuva: Valstybinė duomenų apsaugos inspekcija
- Lëtzebuerg: Commission Nationale pour la Protection des Données (CNPD)
- Magyarország: Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH)
- Malta: Office of the Information and Data Protection Commissioner (IDPC)
- Nederland: Autoriteit Persoonsgegevens
- Norge: Datatilsynet
- Polska: Urząd Ochrony Danych Osobowych (UODO)
- Portugal: Comissão Nacional de Proteção de Dados (CNPD)
- România: Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP)
- Slovenija: Informacijski pooblaščenec
- Slovensko: Úrad na ochranu osobných údajov Slovenskej republiky
- Suomi: Tietosuojavaltuutetun toimisto
- Sverige: Integritetsskyddsmyndigheten (IMY)
- Ísland: Persónuvernd
- Österreich: Österreichische Datenschutzbehörde (DSB)
- Česko: Úřad pro ochranu osobních údajů (ÚOOÚ)
- Ελλάδα: Αρχή Προστασίας Δεδομένων Προσωπικού Χαρακτήρα
- Κύπρος / Kıbrıs: Γραφείο Επιτρόπου Προστασίας Δεδομένων Προσωπικού Χαρακτήρα
- България: Комисия за защита на личните данни (Commission for Personal Data Protection)
Source: list of members of the European Data Protection Board (EDPB) and the authorities’ websites, as at November 19, 2026.
This section was last updated on: November 19, 2026
11. Individual services, storage on your device and backups
Live recordings
Raw recordings of livestreams are deleted automatically after 24 hours. Replays that have been saved or published are kept until they are deleted.
Clip buffer
To make clips possible, our media server keeps the last minute of a livestream in memory (not on disk). This buffer is deleted when the stream ends. Only what someone saves as a clip is stored permanently – until it is deleted.
Sealed inbox
Messages delivered through the sealed inbox are stored without any link to an account: the stored entry names neither sender nor recipient, and we cannot assign it to an account on the basis of the stored data.
Media sent through the sealed inbox (for example images and voice messages) are encrypted by your device before they are uploaded. For this, our server stores only the size, checksum and expiry time, but no account. If such a media item is reported, we keep it for up to 180 days for review. We delete messages in the sealed inbox that have not been collected after 30 days, and collected messages no later than 30 days after collection.
FriendsTime Mail
FriendsTime Mail is our own email service: a mailbox with an address at @friendsti.me, usable on the web and in the app, through the standalone access point post.friendsti.me and with mail programs (IMAP and SMTP). The controller is the operator named in Section 1. We process the data in order to provide the mailbox, to accept, deliver, display and send emails, and to protect the service against abuse.
Data processed: your mail address, the content of your emails including attachments, the header data (sender, recipient, subject, date and technical delivery notes), your folders, flags, filter rules, blocked senders, your signature and settings, and the usage of your storage space (currently 1 GB per mailbox; an email may be no larger than 25 MB).
“Mail only” account: through post.friendsti.me you can create a mailbox without a profile in the social network. For this we collect the address name you want, a password (stored only as a hash), your date of birth for the age check – the same age rules apply as for FriendsTime – and the country, which we derive from your IP address on our own server. We do not ask for a name, a phone number or another email address. You receive a recovery code once; we store only a hash of it. Internally we create a technical account with a random identifier; it cannot be used to sign in to the social network.
Protection of registration: when you create the account, your browser solves a proof-of-work task; no third-party Captcha service is involved. In addition, we limit registration and sign-in attempts per IP address; we delete the entries with the IP address stored for this purpose after 8 days.
Storage location: the mailboxes are kept on our own server at netcup GmbH in the data centre in Nuremberg (Germany) – not with an external email provider. Web and app access them through our web server. Mail programs connect directly to the mail server (IMAP over port 993, SMTP over port 465, in each case encrypted only) and use a separate app password for this, which we store only as a hash.
Encryption on the server: stored emails are encrypted on the server, with a separate key for each mailbox. The index cache of the mail server is currently not encrypted: it contains header data such as sender, recipient and subject in plain text.
No end-to-end encryption: email is an open standard. Our server processes sender, recipient, subject and content in order to accept, check and deliver emails and to display them to you. The mailbox keys are within our sphere of responsibility: they are protected with a secret that is kept on our web server, and additionally with an emergency key that the operator keeps separately from the mail server. The operator could therefore technically access mailboxes. The administration interface of our team blocks access to user mailboxes. We do not read users’ emails unless we are legally obliged to do so.
Encryption in transit: connections to our mail server are protected with TLS (at least version 1.2, preferably 1.3); where the remote side supports it, with hybrid post-quantum key exchange (X25519MLKEM768). We hand over outgoing emails only over encrypted connections. We also accept incoming emails if the sending server does not offer encryption. On the further route and at the recipient, the protection of the respective other provider applies.
Spam filter: incoming and outgoing emails are checked automatically by a filter program (Rspamd) on our own server; no person reads them in the process. For this we send neither emails nor checksums to external filter services, and we do not query external blocklists. The filter learns from word statistics. Suspicious emails from unknown senders may be accepted with a delay; emails identified as spam go to the spam folder or are rejected. The sender authentication records SPF, DKIM and DMARC are also checked; for this our server queries the name system (DNS) of the sender domain.
Sending and recipients: we sign outgoing emails with DKIM; SPF, DMARC and MTA-STS (currently in testing mode) are published for our domain. We remove the IP address of your device from the header lines before an email leaves our server. Your emails go to the mail servers of the recipients you choose – including outside the European Union if a recipient uses a provider there. Beyond that, we do not pass on data from your mailbox to third parties.
Sending limits against abuse: in the first 14 days no more than 50 recipients per day, after that no more than 200. For this we count the number of recipients per mailbox and day; we delete these counters after 3 days.
Welcome email and notifications: after creating the mailbox you receive a single automatic welcome email from noreply@friendsti.me; replies go to support@friendsti.me. The app informs you about new emails by means of a wake-up signal from our own service; it contains neither sender nor subject nor content.
Storage period: emails remain stored until you delete them. The server automatically deletes emails in the trash and in the spam folder after 30 days. If a mailbox is closed, it stops accepting emails immediately; we delete contents and keys 30 days afterwards. The address is not assigned again, so that nobody receives emails that were meant for you; for this purpose the address itself remains stored.
Logs: the mail server logs the time, sender and recipient address, the IP address of the remote side or of your mail program, and the result of the delivery or sign-in – not the content. We delete these logs after 7 days at most. We log administrative events (for example mailbox created, blocked or closed) with address and time for 400 days.
Storage in the browser: so that the message list appears quickly, the webmail stores list data in your browser (IndexedDB): sender, recipient, subject, date, flags and a short preview – not the complete emails and no attachments. This storage is deleted when you sign out and when you switch accounts.
External images in emails are not loaded automatically. This way the sender does not learn whether and when you open a message.
Forwarding: we do not offer automatic forwarding to other addresses for user mailboxes; it is reserved for role addresses of FriendsTime.
Legal bases: Art. 6(1)(b) GDPR (provision of the mailbox, delivery and sending), Art. 6(1)(f) GDPR (security, defence against spam and abuse, logs, backups) and Art. 6(1)(c) GDPR (age check). The content and detailed circumstances of your emails are subject to the secrecy of telecommunications (Section 3 of the German TDDDG).
Backups
We back up our systems daily and in encrypted form: the database (7 daily, 4 weekly and 6 monthly backup states are kept), the mailboxes of FriendsTime Mail (14 daily backup states; in addition, the operator fetches an encrypted second copy to a computer of its own and keeps the last 7 fetched copies there), and the file storage and configuration of our own server (7 daily, 4 weekly and 3 monthly backup states). These backups are kept on our server in Nuremberg. Data that you delete may still be contained in backups until these periods have expired. We use backups only to restore data after a disruption.
Protection against overload (rate limiting)
For calls and for uploads to storage, we count how often an account or a connection uses a function within a short time (time windows between 5 minutes and 24 hours). Only a key, the start of the time window and a counter are stored. The key consists of the account number – for calls, additionally that of the called account – or of a check value of the IP address that is formed with a secret key (HMAC); we shorten IPv6 addresses to the /64 network beforehand. We do not store the IP address itself here. Entries older than 25 hours are deleted continuously.
Data export
Before we create a data export on the web, you have to confirm your password. The export file is kept in a folder that is not publicly accessible. We store the download key only as a hash; it is valid for 24 hours and only for your account. We delete expired export files automatically. Passwords and keys are not included in the export. A maximum of 3 exports in 24 hours is possible.
Stories
Expired stories are no longer visible. We delete the associated image and video files automatically, at the earliest 48 hours after expiry – unless they are still needed, for instance because you have kept the story as a highlight or because a report about it is being reviewed.
GIFs
Your device no longer calls third-party GIF services (Tenor, Giphy). You upload your own GIFs to our own server; in doing so we remove metadata from the file. For this we store your account, the age rating of the GIF, its visibility and the review status. A GIF becomes publicly visible only after review by our team. When a GIF is retrieved, we check on the basis of your country and your age whether it is approved for you; we show content for ages 18 and over only with proof of age.
Background images
Background images for profiles, designs and groups are loaded only from our own servers; we do not allow addresses of external servers for this.
Local chat storage in the app
The Android app (from build 1304) additionally stores your chats on your device so that they can be read faster and also without a connection. This storage is encrypted (AES-256-GCM); the key is kept in the protected key store of Android and cannot leave the device. Whatever has been deleted on the server or has expired is also removed from the device. When you sign out, the app deletes the entire local chat storage.
13. Family & parental area
In the family area an adult account (parent) and an account under 18 (child) can be linked. The link is only created if both agree: the parent creates a code, the child enters it in their own account and confirms it. Age is taken from the date of birth stated in the account; no age verification takes place.
Which data is processed
- the link (which accounts, since when) and invitation codes,
- the parents’ settings (e.g. quiet times, allowed usage times, daily limit, breaks, turned-off areas, contact rules, content filter),
- the child’s usage time per day (total in seconds, measured via the existing activity signals of the app and the website),
- counters: number of new friendships, number of reports by or against the child, number of blocks, attempts during locked time,
- a log of the steps in the family area (who set what and when) with a shortened IP address,
- for trusted persons: name, relationship, e-mail address, language, confirmation status and – if the person chooses so – the linked FriendsTime account.
Purpose
The data is used to enforce the rules set by the parents on our servers (for example locking the app and the website outside the allowed time), to give the parents an overview in numbers and to detect misuse of the family area.
Who sees what
- Parents see the settings, the usage time per day and the counters mentioned. They do not see message contents, chat partners of private chats or the names of people who reported or blocked. For friendship approval requests and – if switched on – alerts about new friendships they see the other person’s username. They only see the child’s friends list (names and profile pictures only) if they switch on this option – the child sees in their own view whether it is switched on.
- The child sees that parents are linked, all settings, the trusted persons added and the log.
- Trusted persons cannot change anything. They only get the e-mail report selected by the parents (numbers only) and – with a linked account – alerts; the child can write to them in the private chat.
- The team only sees links and the log with the youth-protection permission, for example when a child reports a problem with a link.
Messages between child, parents and trusted persons
Even during a break or outside the allowed time, the child can write to their linked parents and confirmed trusted persons with a FriendsTime account in the normal private chat; they read and reply there as usual. During locked time only the chat functions with exactly these persons remain available (sending, loading, read receipts, keys, typing indicator, voice messages and attachments); groups and all other chats stay locked. The text of private chats is end-to-end encrypted: AES-256-GCM for the content, for the key exchange the hybrid scheme of X25519 and ML-KEM-768 (post-quantum scheme per FIPS 203); the server only stores ciphertext of it. For pictures, voice messages and files the information on the private chat in this privacy policy applies. In the family area itself parents do not see chat contents or the child’s chat partners.
E-mail report and trusted persons
Parents can switch on an e-mail report for each child – daily or weekly. It contains numbers only: usage per day, attempts during locked time, number of new friendships (usernames only if the option “friends list visible to parents” is switched on), number of reports and blocks and the number of changed settings – no messages, no chat partners, no posts. Every report e-mail contains a link to unsubscribe; it can also be switched off at any time in the family area. Trusted persons can receive the report as well (numbers only, without names). The e-mail address of a trusted person is only used after the person has opened the link in our confirmation e-mail and agreed (double opt-in). If they decline, the entry is deleted immediately; without confirmation after 30 days.
Retention
Usage times per day, log entries, expired or used invitation codes, completed approvals, notifications of the family area and unconfirmed trusted persons are deleted automatically after 30 days. The link and the settings apply as long as the link exists. If it is removed and no linked parent remains, we delete usage times and trusted persons immediately. The link and the settings themselves are deleted 30 days after removal. Chat messages between the child and parents or trusted persons are normal private chat messages; the information on the chat in this privacy policy applies to them.
Removing the link and your rights
Parents can remove the link at any time; a child immediately once they are of age, before that with the consent of a parent – or they report a problem to our team. Under “Family & parental area” (/family.php) parents, child and trusted persons with a linked account can download their family data as a file. For access, rectification and erasure, the ways described in this privacy policy apply as well (for example data export and account deletion in the settings).
Legal basis
Art. 6(1)(b) GDPR (providing the function set up jointly by parent and child), for the e-mail report and trusted persons Art. 6(1)(a) GDPR (consent, revocable at any time), for the log to protect against misuse Art. 6(1)(f) GDPR.
Version of this section: 23 Oct 2026
14. Data protection in your country
This section adds country-specific information to the policy above. If the country is wrong, select your country.
How we determine the country
If you state a country in your account, we store it. We use it for this section and for age limits that apply in individual countries. You can change it in the settings. Legal basis: Art. 6(1)(f) GDPR (complying with the rules that apply in your country and showing you the relevant information).
Otherwise we suggest the country based on your language setting. If you select a country, we remember the selection in a strictly necessary cookie ("ft_land") that contains only the country code and is deleted when you close the browser. The selected country also appears in the address of this page and, like any address requested, may appear in the usual server log (see the section on storage periods).
Sources: member list of the European Data Protection Board (EDPB) and the authorities' websites, as of November 19, 2026.
Digital Services Coordinator
The Digital Services Coordinator at FriendsTime's registered seat is:
Bundesnetzagentur – Koordinierungsstelle für digitale Dienste (DSC)
Website
Consumers: withdrawal and dispute resolution
For contracts that consumers conclude online, a uniform withdrawal period of 14 days applies in the EU and the European Economic Area. Details and exceptions are set out in the terms of use.
Sources: European Data Protection Board (list of members), European Commission (list of Digital Services Coordinators), European Consumer Centres Network; as of November 17, 2026.
15. Changes to this policy
We update this policy when features or service providers change. The date and version are shown at the top of this page. In the event of significant changes we will notify you on the web and in the app.
This privacy policy applies to the website, the Android app and the onion service of Friendstime.