Back to overview
⚠ Notice: This translation is provided for better understanding. For legal questions, the German original version is authoritative.

Privacy Policy

Last updated: 17.11.2026 Version 2.3 EN

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. push notifications via Google Firebase, payments via Stripe, AI features via Google Gemini) – 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 1 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

  • At your request: translating, reply suggestions in chats and text suggestions (e.g. for captions) send the text concerned to Google (Gemini API). For reply suggestions these are the latest unencrypted text messages of the chat (at most 500 characters per message); end-to-end encrypted text cannot go to the AI because our server cannot read it. In the app you can switch off the AI features under “Allow AI features”.
  • Fact check: We automatically check public posts with at least 50 characters of text with Google Gemini for verifiable factual claims. Non-public posts never go to the AI provider.
  • Image review for moderation: Images in posts may be assessed by Google Gemini to support our moderation team. The result is only a hint; only a human can decide and block.

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 TDDG – 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): 90 days, then automatic deletion
  • 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: as long as the account exists
  • 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

  • Google Firebase Cloud Messaging (push notifications): The app registers with Firebase at start-up and receives a push identifier; in the browser this only happens once you allow notifications (then via Firebase or the push service of your browser vendor). Notifications about encrypted messages only contain a general notice; for unencrypted messages the sender’s name and a preview of up to 80 characters.
  • Stripe (payments): only when paying; Stripe’s payment script is only loaded on pages with a payment function (e.g. wallet, checkout).
  • Google Gemini API (AI features): texts and, where applicable, images as described in section 2.9.
  • Tenor (Google) (GIF search): your search terms go to Tenor via our server; your device loads the GIF images directly from Tenor servers (your IP address is transmitted in the process).
  • YouTube (Google) and Vimeo (embedded videos): the player is only loaded when you start a video (YouTube via youtube-nocookie.com). We load preview images of YouTube videos via our own server.
  • STUN servers of Cloudflare and Google (calls, live guests): when establishing a connection, your device may ask these servers for its public IP address; they see your IP address in the process.
  • OpenStreetMap / OpenTopoMap (maps): our server fetches the map tiles; your device has no direct contact.
  • Nominatim (OpenStreetMap Foundation) (place names): for places and the device list our server looks up the place name – with coordinates rounded to about 1 km or your search term, without your IP address.
  • 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.
  • ipapi.co (country detection): only during a registration phase with a country waiting list; then your IP address is sent to this service during registration to determine the country.
  • PayPal (payouts): only if you choose a payout to a PayPal account.
  • Google Fonts (fonts): most pages of the website load the fonts Inter and Roboto from Google servers (fonts.googleapis.com, fonts.gstatic.com); your IP address is transmitted to Google in the process. The start page for visitors who are not signed in uses a self-hosted font and loads nothing from Google for it.
  • QR code scanner of the app (Google ML Kit): recognition runs on the device; the software package may send technical usage and performance data to Google.

8.3 Transfers to third countries

Google, Stripe, Cloudflare, Discord, Vimeo and PayPal are companies with their registered office or parent company outside the EU, in particular in the USA. For the services mentioned, personal data may therefore be transferred to third countries.

Legal basis for the transfer: According to their own statements, Google LLC (Firebase Cloud Messaging, push notifications) and Stripe (payments) are certified under the EU-US Data Privacy Framework. To that extent, transfers to the USA are based on the European Commission’s adequacy decision of 10 July 2023 (Art. 45 GDPR). Where no certification exists or data reach other third countries, the European Commission’s standard contractual clauses apply (Art. 46(2)(c) GDPR), which these providers include in their data processing agreements. You can obtain a copy of the safeguards on request from datenschutz@friendsti.me.

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:

NamePurposeDuration
PHPSESSIDsession 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 it30 days
ft_api_tokensign-in when the app opens a website page30 days
ft_langchosen language1 year
cookie_consentremembers that you have seen the cookie notice1 year
ft_headerchosen header design30 days
ft_tor_banner_dismisseddismissed Tor notice30 days
ft_minor_statusyouth protection device block (only in this case, see 2.8)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. 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

11. 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 12, 2026.

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