1. Summary
- We do not sell your data, show ads, use advertising SDKs or track you across other companies' apps and websites.
- Private 1:1 chats are protected by end-to-end encryption: we cannot read their content. Group chats, communities, stories and posts are not end-to-end encrypted.
- Users aged 13–17 and adults do not see each other and cannot communicate with each other (the only exception is the general support chat, section 6).
- At any time you can download a copy of your data («Налаштування» → «Приватність» → «Завантажити мої дані» [Settings → Privacy → Download my data]), delete your account («Налаштування» → «Видалити акаунт» [Settings → Delete account]) and turn off usage statistics.
- Some features pass data to providers — hosting, Firebase, Cloudflare, Anthropic (for AI features, only on request) and others. The full list is in section 12.
This Privacy Policy (the “Policy”) explains how the «Друзі» service (in Latin script — Druzi; the “Service”, “we”, “us”) processes personal data. We aim to describe everything specifically: what data, why, on what basis, who receives it, how long it is kept and how you can control it. If anything is unclear, write to us (section 21).
This Policy supplements the Terms of Use (in Ukrainian). Capitalised terms have the meanings given in the Terms.
2. Who we are (data controller)
The controller of the personal data processed in the Service is the developer and operator of the «Друзі» app (the “Operator”). The Operator determines the purposes and means of processing and is responsible for it under the Law of Ukraine “On Personal Data Protection” and, for users in the EEA, the United Kingdom and Switzerland, under the GDPR, the UK GDPR and the Swiss FADP to the extent they apply.
Contact for all personal data matters, including exercising your rights: druzi.support@gmail.com. No separate Data Protection Officer (DPO) has been appointed: data requests are handled directly by the Operator.
3. Scope
This Policy covers:
- the «Друзі» mobile apps for iOS and Android;
- the web version of the app and the website druziua.com, including public pages (invitations
/i/…, profiles/@username, links to listings); - the server side (
api.druziua.com), file storage and the call media server these apps run on; - correspondence with our support.
This Policy does not cover third-party services we link to or that you connect yourself (Steam, Twitch, YouTube, Apple Music, App Store, Google Play, etc.). They process data under their own policies.
4. What data we process
We collect only the data without which the features you use would not work. All categories are listed below, grouped by feature.
4.1. Account and sign-in
- Email address and password (the password is stored and checked by Firebase Authentication; we never see it).
- Sign in with Apple or Google: account identifier, email (for Apple — your real address or a private relay address, as you choose), name, if the provider passed it.
- User identifier (UID), account creation and last sign-in dates, a service flag showing that onboarding is complete.
- Acceptance of the Terms and the Policy: the version of the documents you agreed to at sign-up and the time of acceptance.
4.2. Profile
- Name (you may use a nickname) and username (
@username; it is unique and people can find you by it). - Date of birth. It is needed to show your age and to place you in an age group (13–17 or 18+). The date itself is not shown to others. Once saved, it cannot be changed in the app; corrections are made only through support.
- City and country.
- Profile photo.
- About me, interests (including those marked as most important), who you are looking for, lifestyle answers (for example, sport, attitude to alcohol or smoking). These answers are optional.
- Profile theme and the Ambassador badge, if you have them.
We do not ask for your gender, sexual orientation, religion, political views, health, phone number or documents. Do not add such information to your profile or posts if you do not want other people to see it (section 6).
4.3. Media libraries and connected services
- Libraries: books, films, series, anime, manga, games, music, channels. For each item — title, cover, catalogue identifier, your rating, review, status (“reading”, “watching”, “playing”, etc.), “favourite” mark.
- Steam (sign-in via Steam OpenID): Steam ID, public name and avatar, list of games and playtime, if your Steam profile is public.
- Twitch (scope
user:read:follows) and YouTube (scopeyoutube.readonly): OAuth tokens, account name, channels you follow. - Apple Music: permission to access the media library on the device (iOS) or sign-in via MusicKit (web). The app reads the tracks and artists you have chosen to add to your «Друзі» library.
You can disconnect a service in your profile, in the services section. After disconnection we revoke the token where the provider supports it, and the items you have already added to your library stay until you delete them.
4.4. Messages, chats and calls
- Private 1:1 chats: text and attachments (photos, voice messages, GIFs) are encrypted on your device. Only the ciphertext is stored on the server (section 14).
- Group chats: text, attachments, polls (including votes; in an anonymous poll other members do not see who voted how), group name and avatar, member list. These chats are not end-to-end encrypted.
- Message metadata (both in 1:1 and in groups): who sent a message to whom and when, delivery and read statuses, reactions, replies, edit and deletion marks, pins, forwards, attachment type and size, per-chat sound settings.
- Message requests: request status, author, number of messages sent before acceptance. Also requests to delete a conversation “for both”.
- Calls, voice channels and screen sharing: participants, start and end time, duration, status. Voice and screen images are transmitted live and never recorded.
- Replies to stories arrive in the chat as ordinary messages.
- “Online” status: the app shows the people you chat with 1:1 and your friends whether you are online right now (the app is open in the foreground) and when you were last online. You can control this in «Налаштування» → «Приватність» → «Хто бачить, коли я в мережі» [Settings → Privacy → Who sees when I'm online]: “Everyone”, “Friends” or “Nobody”. By default it is “Friends” for users aged 13–17 (and when the age is unknown) and “Everyone” for 18+. If you choose “Nobody” (or “Friends” — for people who are not your friends), your contacts see only an approximate status: “recently”, “this week”, “this month” or “a long time ago”; and then you also see other people's status only approximately. People do not see each other's status if there is a block between them (in either direction); on both sides of a message request until it is accepted; across age groups (13–17 and 18+). If your age is unknown, you do not see other people's status and they do not see yours. The status of banned and deleted accounts is not shown. The last activity time is kept in Redis for up to 30 days, and the moment you were last online is kept in the profile database until the account is deleted.
4.5. Communities, “Companies”, stories
- Communities: communities you created, membership, role, notification level, when you last opened a community, acceptance of its rules. Also answers to the joining questionnaire (they are deleted as soon as the request is approved), posts, photos, comments, likes, poll votes (only totals are visible), “Going / Maybe” replies to events, invitations, reports, bans.
- “Companies” («Компанії», listings for joint activities and meetups): name, tag, description, time, place, number of spots, responses from other people.
- Stories (posts that last 24 hours): photo, caption, context (for example, a library item, a question, a listing or a map pin), audience (“everyone” or “friends only”), views, reactions and “Me too” marks.
4.6. “Happiness Nearby”, places and geolocation
The “Happiness Nearby” («Щастя поруч») section is available only to users aged 18 and over.
- Pin: tag, note, place or venue name, exact coordinates of the point you chose, time, number of spots, who pays. Also “Going” responses. The pin's point is visible to all adult users of your age group who open the map. Put a pin in a public place, not near your home. A pin is active for 3 to 12 hours.
- Venues: your ratings and reviews (visible to your age group), “Venue closed” reports together with the coordinates you sent them from.
- Your current location. If you allowed location access, the device uses it in two cases: to detect your city while filling in your profile (only the city name is sent to the server) and to show “My location” on the map. The coordinates of “My location” stay on the device and are not sent to the server. To search for venues, the centre of the map you are viewing is sent to the server. We do not track your location in the background.
4.7. Friends, interactions and recommendations
- Friends: friend requests, their statuses and dates.
- Search: filters (age, city, interest, “Looking for”), people you have hidden, candidates shown to you (so as not to repeat them).
- Profile views: who fully opened someone else's profile and when (no more than one record per day for each pair of people). See section 4.11 for details.
- Notifications: notification centre entries and your notification settings (including opting out of nearby invitations and new-people digests).
4.8. Safety and moderation
- Reports: who and what was reported, the reason, your description, identifiers of the message, conversation or post, time of the report and, optionally, one screenshot. The reported person does not find out who filed the report.
- Blocking and hiding: whom you blocked or hid and when.
- Moderation measures: warnings, restrictions, account suspension and their grounds.
4.9. Technical data
- Push notification tokens: FCM/APNs, on iOS — a separate VoIP token for incoming calls. In the browser — a Web Push subscription (delivery address, encryption keys, browser type).
- Device: a service identifier of the device or browser tab, platform, app version, language. We do not collect the advertising identifier (IDFA/AAID), and on Android the permission for it has been removed from the app.
- Public encryption key for 1:1 chats. The private key stays on your devices (section 14).
- Server logs: IP address, time, request address without parameters (that is, without coordinates, search queries or codes), response code, browser or app type; error logs also contain the UID. They are needed for security, abuse prevention and debugging and are kept for 14 days. For rate limiting, the IP address is stored only as a hash and only for a few minutes.
- On-device cache: profiles, lists, decrypted messages and chat photos are stored locally so that the app works fast (section 10).
4.10. Usage statistics
To understand which parts of the Service work and which do not, we collect usage statistics. The iOS and Android apps use Google Analytics 4 (Firebase Analytics) for this. On the website and in the web version the same set of events goes to Google Analytics 4 and Amplitude. The statistics are pseudonymised: they contain no name, email or message content. At the same time they are linked to your UID, so legally they are not anonymous.
- What we collect: screen views, sign-up and onboarding steps, the fact of actions (for example, “message sent”, “story created”) but not their content. Also the traffic source of the website visit, device or browser type, app version, country.
- What we do not collect: content of messages and posts, names, email, usernames, exact age, city, “about me” text, identifiers of people, conversations and communities you interact with. Page addresses are cleaned of parameters that could contain codes or identifiers (for example, an invitation code or a username in the address).
- Aggregated traits: age group (for example, “18–24”), profile completeness, platform.
- IP address: it is not passed to Amplitude. Events go through our server on
druziua.com, which instead of the IP address adds only the country, region and city. Google Analytics 4 uses the IP address only to determine the approximate location and does not store it. - Consent: in the EEA, the United Kingdom and Switzerland, and also when the country could not be determined, statistics are enabled only after your explicit consent (a banner on the website or a prompt in the app). Before consent the website does not load Google Analytics or Amplitude scripts and does not contact their servers, and after a refusal it sends them nothing. Consent is valid for 13 months, after which we ask again. In other countries statistics rely on our legitimate interest in improving the Service: the mobile apps have a checkbox at sign-up that you can untick, and in the web version statistics are on by default and can be turned off in settings. Refusing does not restrict access to the Service in any way.
- How to turn off: «Налаштування» → «Приватність» → «Статистика використання» [Settings → Privacy → Usage statistics] (iOS, Android, web). After that no new events are collected.
- Retention: 14 months, after which the data is deleted automatically. If you delete your account, we immediately ask Google Analytics and Amplitude to delete the statistics linked to your UID; they process such requests within their own timeframes (usually up to a few weeks). Events collected before signing in are not linked to a UID and are deleted under the general period.
- Advertising: Google Signals, personalised advertising and Google advertising signals are turned off in all regions.
4.11. Ambassador status, purchases and invitations
Purchases. The subscription and the one-time “Forever” purchase can be made only through the App Store or Google Play. Payment is processed by Apple or Google, and we do not receive your card details. To verify purchases we use RevenueCat and store:
- your UID as the customer identifier (without name, email or profile data);
- store, plan, product and transaction identifiers, purchase date, end of the paid period, auto-renewal state, signs of billing issues, pauses or refunds;
- data the RevenueCat SDK receives from the device and the store for verification: store country, currency, price, app and OS version, IP address at the time of the request.
Inviting friends. To credit invitations and prevent abuse, we process:
- your invitation code, and who invited whom, when and whether the invitation was credited;
- a service identifier of the invited person's device, so that one invitation cannot be credited several times from the same phone;
- on iOS — a one-time clipboard check at first launch. If it contains a
druziua.com/i/…link placed there by the invitation page, the app fills in the code. iOS shows a paste prompt, and other clipboard content is neither read nor transmitted; - on Android — the invitation code from the Google Play Install Referrer, if you installed the app from an invitation link;
- in the browser — the invitation code in local storage until sign-up is complete.
The person who invited you sees your name, photo and whether the invitation was credited in their list.
“Who viewed my profile”. An Ambassador sees which users from their own age group viewed their profile in the last 30 days: name, photo, badge and day of the view. An Ambassador aged 13–17 sees only peers, an adult only adults. A view is not shown if, on the day of the view or now, one of the two people belongs to the other age group (for example, after turning 18). Other users see only the number of views. Views between people who have blocked each other are not shown. You can hide your views: «Налаштування» → «Приватність» → «Приховувати мої перегляди» [Settings → Privacy → Hide my views]. Then they do not appear in other people's lists, and you see only the number of your visitors without names.
4.12. Features using artificial intelligence
Some features run on the Claude model by Anthropic. They are available only to users aged 18 and over: data of users under 18 is not sent to Anthropic. The features are switched on only on request, that is, when someone taps the corresponding button. We pass the model a concise text description, but never the name, username, date of birth, photo, email, identifiers, coordinates or chat messages. Under Anthropic's terms, data sent via the API is not used to train models.
- Ambassador portrait (on your request, no more than once a month): age, city and country, “about me”, interests, who you are looking for, lifestyle answers, library items with ratings and reviews, your listings, pins, community names, your own posts and comments in them. Only you see the portrait.
- “Recommendations of the week” (for Ambassadors, on request): age, city, “about me”, interests, library items with ratings, hours in games, previous recommendations and your reaction to them.
- “What to write?” («Що написати?») — first-message suggestions in an empty private chat. A concise description of both people is passed: age, city, who the person is looking for, “about me”, interests, shared and highlighted library items with ratings, statuses and reviews, names and topics of the other person's active listings, names of public communities they belong to. To make the suggestions sound like you, a few of your own comments, posts or reviews and your hours in shared games are added. So if another person asks for a suggestion for a chat with you, your data from this list may be included in the description. All of it is visible to other users in your profile anyway. Only the person who asked sees the suggestions. The suggestion text is kept for up to 7 days. For up to 90 days we keep service marks: when the suggestions were generated, whether one of them was sent, what type it was and whether it was edited. To assess the usefulness of the feature, we match these marks with whether the other person replied — by sender and message time, without the content. There are no suggestions if one of you has blocked the other or you are in different age groups.
Matching people in “Search” and recommendations in the feed run on our own server. For this we compute numerical “fingerprints” of interests and libraries using a language model that runs locally. This data is not passed to third-party services.
4.13. Support requests
When you write to us, we receive your email, the text of your message, attachments and anything you decide to tell us, and we see your UID if you included it.
4.14. Public pages and guest view
- A link to a “Companies” listing shared by its author opens without signing in. The page shows the name, description, time and the author's name (only for authors aged 18+), but not the exact address.
- The
/@usernamepage shows a profile only to signed-in users who are allowed to see you under the rules of the Service. - The guest view of the app on the website (if enabled) may show visitors without an account excerpts of data of adult users: name (first word only), age, city, photo, short description, interests, a few library items, “Companies” listings (without address and links), public communities and “Happiness Nearby” pins (without author, note and custom place name, with the point shifted by 150–300 m; a venue name from the map may be shown). Usernames, messages, exact addresses, data of users aged 13–17 and of people who hid their profile from search are not included.
4.15. What we do not collect
Contacts from your address book, phone number, advertising identifiers, background location, biometric data (Face ID or fingerprint is checked by the device's own system; we receive only a “yes” or “no” result), the content of your calendar (the app only adds an event to it when you tap “Remind me”) and call recordings.
5. Where we get data from
- From you: everything you enter, upload or publish.
- Automatically: technical data, message metadata, statistics (with consent or the checkbox), server logs.
- From other users: messages to you, reports, responses to your listings, invitations, and the data needed for the “What to write?” feature in a chat with you.
- From services you connected: Apple, Google, Steam, Twitch, YouTube, Apple Music, App Store, Google Play, RevenueCat.
6. What other people see
«Друзі» is a social service, so part of your data is visible to others. Such data is visible only to people in your age group, and users you have blocked or who have blocked you do not see it. Exceptions: public pages and the guest view (section 4.14) and the general support chat, which can be joined from settings. It brings together users of both age groups, and blocking does not remove participants from it, so do not share personal data there.
| What | Visible to |
|---|---|
| Name, username, age, city, photo, “about me”, interests, “Looking for”, lifestyle, libraries with ratings and reviews, Ambassador badge and theme, number of friends | Users who open your profile (from search, a chat, a community, by username). Your profile is not shown in the “Search” deck if you turned on “Hide me from friend search” |
| 1:1 messages | Only the other person |
| Group messages, votes in non-anonymous polls | Group members |
| Posts, comments, replies to events in a community | Depending on the community settings: everyone in your age group (open) or members only (closed, hidden). Posts of open communities may be recommended to people outside the community |
| Stories | Your age group or friends only, depending on the chosen audience. Only you see the list of views and reactions (for community stories — its administrators) |
| “Companies” listings and responses to them | Your age group. Only participants see the exact address |
| “Happiness Nearby” pins | Adult users on the map, together with the exact point |
| Venue reviews | Your age group |
| The fact that you viewed a profile | The Ambassador from your age group whose profile you viewed (if you have not hidden your views) |
Anyone who sees your content can take a screenshot or forward a message, and we cannot prevent it. Share responsibly.
7. Purposes and legal bases
We process data only for a specific purpose and on a lawful basis: under Article 11 of the Law of Ukraine “On Personal Data Protection” and, for users in the EEA, the United Kingdom and Switzerland, under Article 6 of the GDPR or the UK GDPR.
| Purpose | Data | Basis |
|---|---|---|
| Creating an account, signing in, operating the profile, search, chats, calls, communities, stories, “Companies”, “Happiness Nearby”, libraries and notifications | Sections 4.1–4.7, 4.9 | Performance of a contract (the Terms of Use) |
| Matching people and feed recommendations | Profile, interests, libraries, city, age group, filters | Performance of a contract; legitimate interest |
| Separating age groups and restricting 18+ content | Date of birth | Legal obligation and legitimate interest in protecting minors |
| Safety, moderation, preventing spam, fraud and invitation abuse | Section 4.8, logs, device identifier | Legitimate interest; legal obligation |
| Device location, camera, microphone, photos, calendar, notifications | Section 9 | Consent (system permission), which can be withdrawn |
| Connecting Steam, Twitch, YouTube, Apple Music | Section 4.3 | Consent |
| AI features | Section 4.12 | Performance of a contract (user request); for the other person's data in “What to write?” — legitimate interest, limited to data the person has made visible themselves |
| Usage statistics | Section 4.10 | Consent (EEA, United Kingdom, Switzerland); in other countries — consent or legitimate interest |
| Ambassador status, purchases, invitations | Section 4.11 | Performance of a contract; legitimate interest (protection against abuse) |
| Support, answering requests | Section 4.13 | Performance of a contract; legitimate interest |
| Complying with the law, defending rights in court | The necessary minimum | Legal obligation; legitimate interest |
When we rely on legitimate interest, we balance it against your rights and expectations. You can object to such processing (section 18).
8. Automated processing and AI
- Matching people and recommendations. The Service automatically orders candidates in “Search” and posts in the community feed by shared interests, libraries, city and age. This affects only the display order and has no legal effects for you.
- Age groups. Users aged 13–17 see only peers and communicate only with them; adults — only with adults. The group is determined by the date of birth. 18+ content (for example, venues and tags related to alcohol, as well as “Happiness Nearby”) is hidden from minors.
- Language filter. Profiles, posts, stories, listings and pins are checked against a list of unacceptable words before publication.
- Automatic restrictions. If several different people have reported an account, the system may temporarily hide it from others and suspend sign-in until a moderator reviews it. Likewise, a post or community reported by at least two people is not recommended to others.
- AI features (section 4.12) only suggest text. They do not make decisions about you.
Decisions that significantly affect you (account suspension, content removal) are finally made by a human. You can ask for an explanation of a decision, challenge it and express your point of view: write to druzi.support@gmail.com.
9. Device permissions
The app requests each permission only when a feature needs it. Refusing a permission disables only the feature that needs it.
| Permission | Why | How to turn off |
|---|---|---|
| Location (iOS — “while using”; Android — approximate, and precise for “My location”) | Detect your city while filling in your profile; show “My location” on the “Happiness Nearby” map (the coordinates stay on the device). The city can be entered manually | iOS: Settings → Privacy & Security → Location Services → Друзі. Android: Settings → Apps → Друзі → Permissions |
| Camera | Photos for the profile, chat, stories; scanning a book barcode (recognition happens on the device) | iOS: Settings → Друзі. Android: Settings → Apps → Друзі → Permissions |
| Photos | Choosing images in the built-in gallery (full or limited access — your choice in the system prompt) or via the system photo picker; saving photos from a chat | iOS: Settings → Друзі → Photos. Android: Settings → Apps → Друзі → Permissions |
| Microphone | Voice messages, calls, voice channels. Only while you are recording or in a call | iOS: Settings → Друзі. Android: Settings → Apps → Друзі → Permissions |
| Screen sharing | Show your screen to call participants. Turned on only by your action, not recorded | Stop sharing or end the call |
| Notifications (including VoIP on iOS and Web Push in the browser) | New messages, requests, incoming calls, community events, reminders | Device or browser settings; individual types — in the app: «Налаштування» → «Сповіщення» [Settings → Notifications] |
| Calendar (iOS) | Add an event or meetup as a reminder when you tap. We do not read the calendar content | Settings → Друзі → Calendars |
| Apple Music library (iOS) | Add your tracks and artists to your library, if you want to | Settings → Друзі → Media & Apple Music |
| Face ID / Touch ID (iOS) | Confirm moving the encryption key to another device. We do not receive biometric data | Settings → Face ID & Passcode |
Withdrawing a permission does not affect the lawfulness of processing carried out before.
10. Cookies and browser local storage
In the browser we use cookies and the browser's local storage (localStorage, sessionStorage, IndexedDB). Cookies are set only by Google Analytics and only after your consent where it is required; everything else is stored as local storage entries.
- Strictly necessary (no consent needed): the Firebase sign-in session, your choice regarding statistics, the chat encryption key, the conversation and screen cache, message drafts, interface settings (collapsed menu, sound, tips already seen), a tab identifier for notifications, an invitation code until sign-up is complete.
- Statistics (only after consent where it is required): Google Analytics cookies (
_ga,_ga_*) and Amplitude's local device identifier. In the EEA, the United Kingdom, Switzerland and when the country is not determined, the Google Analytics script loads only after consent. Consent is valid for 13 months; if you withdraw it, the Google Analytics cookies are deleted and the Amplitude identifier is reset. - There are no advertising cookies.
The conversation cache contains decrypted messages, so it is cleared when you sign out. If you use someone else's or a shared computer, always sign out. The mobile apps likewise keep a cache (including decrypted messages and chat photos) in the app sandbox. It is removed by signing out or deleting the app.
11. Who we share data with
We do not sell or rent out personal data and do not share it for advertising. Data may be received by:
- Other users — within the limits described in section 6.
- Service providers (processors) — hosting, storage, authentication, notification delivery, analytics, purchase verification, AI (section 12). They process data only on our instructions or under their own terms that ensure adequate protection.
- Services you connected yourself and app stores — under their policies.
- Public authorities — only on a lawful basis (a court decision, a lawful request) or when necessary to prevent a threat to life or health. We check the lawfulness of every request and disclose only the necessary minimum.
- A successor — in the event of a reorganisation, sale or transfer of the Service. We will notify you in advance, and the level of protection will not decrease.
12. List of providers
| Provider | Purpose | What data |
|---|---|---|
| Hetzner Online GmbH (Nuremberg, Germany) | API server, databases, call media server (LiveKit, self-hosted), encrypted backups | All data stored on the server |
| Cloudflare, Inc. (USA, global network) | Hosting of the website and web version, protection and proxying of the API, R2 file storage: avatars, story and post photos (public CDN cdn.druziua.com), chat attachments and report screenshots (private storage) | IP address, technical request data, files |
| Google LLC — Firebase (Authentication, Firestore, Cloud Messaging, Storage) | Sign-in, account service document, push notifications, old avatars | Email, UID, sign-in data, push tokens, notification text (for group chats — up to 120 characters of the message; for 1:1 chats — only “New message”) |
| Google LLC — Google Analytics 4 | Statistics (section 4.10) | Pseudonymous UID, events without content, device data, approximate location by IP |
| Google — Block Store (Android) | Backup of the encryption key in your Google account, to restore history on a new phone | E2EE private key (section 14) |
| Amplitude, Inc. (USA; website and web version only) | Product analytics | Pseudonymous UID, events without content, browser data, country and city (without IP) |
| RevenueCat, Inc. (USA) | Verifying Ambassador purchases | UID, purchase data, store country, versions, IP at the time of the request |
| Apple Inc. / Google LLC (App Store, Google Play) | Payment, Sign in with Apple / Google, push delivery (APNs) | Under their policies |
| Anthropic, PBC (USA) | AI features on request (section 4.12) | A concise text description without name, photo, identifiers or coordinates |
| Telegram (Telegram FZ-LLC / Telegram Messenger Inc., Dubai, UAE) | Internal moderators' channel: prompt notification about new reports. Also importing posts from a Telegram channel into a community and publishing community posts to the channel — only if the community administrator connected the channel themselves | For reports: reason and text of the report; names and @usernames of the reporter and of the reported person (for child-safety reports — also age); identifiers; a screenshot, if attached. For the channel: content of the posts published to the channel and the Telegram account through which the channel was connected |
| OpenFreeMap | “Happiness Nearby” map tiles | IP address and the visible map area (without account data) |
| Apple MapKit JS (web), OpenStreetMap Nominatim (Android), the device geocoder (iOS/Android) | Searching and detecting a city or address | Search text or coordinates for detecting the city, IP address |
| KLIPY | GIF and sticker search (through our server) | Only the search query, without identifiers |
| unpkg.com (CDN for open-source libraries; web version only) | Loading the voice message encoding library into the browser | IP address and technical request data (without account data and without the messages themselves) |
Catalogues: TMDb, Google Books, Open Library, Yakaboo, IGDB, Steam, iTunes Search, MyAnimeList, Hikka (hikka.io, anime and manga catalogue), Twitch, YouTube; for book search — Jina Reader and search engines (Bing, Yahoo, DuckDuckGo) | Searching items and covers for libraries | Search query or ISBN; IP address, if the request comes from the device |
| Steam, Twitch, YouTube (Google), Apple Music | Services you connected | Section 4.3 |
13. International data transfers
The main server and databases are located in the EU (Germany). Some providers (Google, Cloudflare, Amplitude, RevenueCat, Anthropic, Apple) process data in the USA or other countries. For such transfers we rely on adequacy decisions of the European Commission, in particular the EU–US Data Privacy Framework for certified companies, on standard contractual clauses (SCCs) included in our agreements with providers and, where the law allows, on the transfer being necessary for the performance of the contract with you. A copy of the relevant safeguards is available on request.
- Ukraine. The Operator is located in Ukraine and accesses data from there: server administration, support, moderation. There is no European Commission adequacy decision for Ukraine. For users in the EEA, the United Kingdom and Switzerland the Operator continues to comply with the GDPR (UK GDPR, FADP) in full, and access from Ukraine is necessary to provide the Service to you (Art. 49(1)(b) GDPR). Ukrainian personal data protection law is based on Council of Europe Convention 108.
- Telegram (UAE). There is no adequacy decision for the UAE. Only the data described in section 12 is transferred there: reports for moderation (necessary for users' safety and for the establishment, exercise or defence of legal claims, Art. 49(1)(e) GDPR) and posts of a community whose administrator connected a Telegram channel themselves (necessary to carry out their request, Art. 49(1)(b) GDPR). The amount of data is minimised, and the moderator deletes screenshots after review.
14. Message encryption
- Where your private key is stored: on iOS — in the Keychain; on Android — in storage protected by the Android Keystore and in a Google Block Store backup in your Google account (if a screen lock is set on the phone, Google encrypts this backup end-to-end); in the browser — in that browser's IndexedDB. The private key never reaches our server.
- Moving to a new device happens via a QR code or a link between your devices. The key is transferred encrypted for a one-time session that lasts 5 minutes, after which its content is erased.
- What is not end-to-end encrypted: metadata (who, to whom, when, attachment type and size), group chats, communities, stories, listings, profiles, calls (they are encrypted in transit, but not end-to-end). All connections are protected by TLS (HTTPS/WSS).
- Reports: if you report a 1:1 message, the report may include fragments decrypted on your device or a screenshot that you chose to send.
- If the key is lost on all devices and in the backup, we will not be able to restore the history of encrypted chats.
15. Retention periods
| Data | Period |
|---|---|
| Account, profile, libraries, friends, settings | Until you delete them or delete the account |
| Messages and attachments | Until the message or conversation is deleted. After account deletion your messages in 1:1 chats remain with the other person (under the name “Deleted account”) until they delete the conversation or their own account; in groups they are deleted together with the account |
| Stories (photo, caption, views, reactions) | 24 hours of display, then up to 24 hours for final deletion |
| “Happiness Nearby” pins | Shown for up to 12 hours. The exact coordinates are deleted from the database 30 days after the pin ends or is deleted; the rest of the record (venue, tag, time) is kept for venue statistics (“Popular on Друзі”) |
| Posts you deleted (including community posts), “Companies” listings and communities | Disappear for everyone immediately and are permanently erased from the database 30 days after deletion (longer — only while a report about them is under review). Posts imported from a Telegram channel keep a service record so that they are not imported again |
| Comments you deleted | Disappear for everyone immediately. A service copy may remain in the database; to erase it permanently, write to us |
| Call metadata | Within the chat history |
| “What to write?” suggestions | Text — 7 days, service marks — 90 days |
| AI portraits and recommendations | Until the account is deleted. Anthropic keeps input data for a limited period under its policy |
| “Online” status (last activity time) | In Redis — up to 30 days; the moment you were last online — in the profile database until the account is deleted |
| Profile views | Shown for 30 days, kept for 180 days (or until either person's account is deleted, if earlier) |
| Candidates shown to you in “Search” | 12 months (so as not to show the same people again), or until the account is deleted |
| Report screenshots | 30 days in our storage. The copy in the internal moderators' channel — until the moderator deletes it after review |
| Reports and moderation decisions | While the review is ongoing, and afterwards no longer than needed to prevent repeated violations and protect rights |
| Records of account suspensions for violations | While the suspension lasts and afterwards — as a violation history, so that a suspended person cannot return unnoticed |
| In-app notifications | Until you delete them or delete the account |
| Push tokens | Until you sign out, turn off notifications or delete the account |
| Server logs | 14 days (request addresses without parameters) |
| Usage statistics | 14 months or until the account is deleted |
| Purchases | Until the account is deleted. Apple, Google and RevenueCat may keep transaction records longer to meet tax and accounting requirements |
| Invitation device log (device identifier and pseudonymous UID) | While the invitation programme runs, including after account deletion. Only to avoid crediting invitations twice |
| Database backups | Up to 5 weeks (encrypted, overwritten cyclically) |
| Correspondence with support | Up to 3 years after the last request |
16. Account deletion
You can delete your account in the app or on the website: «Налаштування» → «Видалити акаунт» [Settings → Delete account]. For security you need to confirm your sign-in again. If you have no access to the account, write to druzi.support@gmail.com from the address linked to the account. After confirmation we immediately delete:
- the Firebase account, profile, photos, username, libraries and connected services together with their tokens;
- in groups — your messages and membership; message requests and 1:1 chats the other person no longer sees — completely, together with attachments. Other 1:1 chats remain with the other person as read-only — see below;
- stories, views, venue reviews, friends, blocks, hidden people, profile views, notifications, portraits, recommendations, suggestions;
- push tokens and encryption keys on the server;
- records about you in RevenueCat and usage statistics in Google Analytics and Amplitude (we send a deletion request, and the services process it within their own timeframes);
- in other people's notifications your name is replaced with an anonymised entry.
What may remain:
- 1:1 chat history with the other person — as in Telegram or WhatsApp: your messages and attachments (end-to-end encrypted, we cannot read them) are labelled “Deleted account”, without your name, photo and profile. It is no longer possible to write there. The conversation is erased completely when the other person deletes it or deletes their account;
- your posts, comments, likes and votes in communities, replies to events, communities you created and membership in them, “Companies” listings and responses to them, pins and “Going” replies, “Venue closed” reports with coordinates — without the profile, which no longer exists. To remove your content, delete it before deleting the account or write to us and we will permanently erase it on request;
- service records with your identifier but without a profile (reactions, poll votes, read marks, call metadata, a mark that the account was deleted), needed for the integrity of other people's conversations;
- credited invitations in the counter of the person who invited you (anonymised) and the invitation device log;
- records of suspensions for violations and data we are required to keep by law. Reports filed by you or about you are deleted together with the account;
- copies in backups until they are overwritten cyclically (up to 5 weeks).
17. Security
- encryption in transit (TLS) for all connections and end-to-end encryption of 1:1 chats;
- authentication via Firebase with short-lived tokens that the server checks on every request;
- keys and tokens on the device — in the Keychain (iOS) or Android Keystore;
- private attachment storage accessed via temporary signed links;
- encrypted backups, restricted server access, rate limiting;
- separation of age groups, message requests, limits on calls from strangers, a language filter, moderation.
No system can guarantee absolute security. If an incident occurs that creates a risk to your rights, we will notify the competent authority and you within the time limits set by law (for the GDPR — the authority within 72 hours) and tell you what to do. If you suspect your account has been compromised, change your password and write to us.
18. Your rights
Under Article 8 of the Law of Ukraine “On Personal Data Protection”, the GDPR and other applicable law you have the right:
- to know what data about you is processed, where it comes from, why and who receives it;
- to access your data and obtain a copy;
- to rectify inaccurate data (most of it directly in the profile, the date of birth — via support);
- to erasure (“right to be forgotten”) — section 16;
- to restrict processing;
- to data portability: to receive your data in a structured machine-readable format (JSON). You can download a copy of your data directly in the app or on the website: «Налаштування» → «Приватність» → «Завантажити мої дані» [Settings → Privacy → Download my data] (up to three times an hour). The file contains your profile, libraries, posts, comments, communities, friends, notifications, settings and your messages (from 1:1 chats — in encrypted form, as they are stored on the server);
- to object to processing based on legitimate interest;
- to withdraw consent at any time, without affecting the lawfulness of prior processing;
- not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects for you;
- to lodge a complaint with a supervisory authority. In Ukraine this is the Ukrainian Parliament Commissioner for Human Rights (ombudsman.gov.ua). In the EEA — the data protection authority in the country where you live or work; in the United Kingdom — the ICO; in Switzerland — the FDPIC.
How to exercise your rights. You can get a copy of your data and delete your account yourself in settings. For other requests, write to druzi.support@gmail.com from the address linked to the account, with the subject “Personal data request”. We may ask you to confirm that the account belongs to you. We respond free of charge within 30 days. If the request is complex, the period may be extended within the limits permitted by law, and we will let you know.
Residents of California (CCPA/CPRA) and other US states
You have the right to know which categories of data we collect (section 4), as well as the rights to access, correction and deletion and to equal treatment for exercising these rights. We do not sell personal data and do not share it for cross-context behavioural advertising, so a separate opt-out (“Do Not Sell or Share”) is not needed. We do not use sensitive personal data to infer characteristics about you. Send requests with the subject “CCPA Request”.
19. Children and teenagers
- We determine the country at sign-up by IP address (via Cloudflare). If it cannot be determined, the minimum age of 16 applies. If the date of birth entered is below the minimum age, the newly created account is deleted immediately together with its data.
- We do not knowingly collect data of children under 13 (including in view of the US COPPA), and in the EEA, the United Kingdom and Switzerland — under 16. If we learn of such an account, we will delete it together with its data. Parents can write to us at druzi.support@gmail.com.
- Users aged 13–17 see only peers and communicate only with them. “Happiness Nearby”, 18+ content and appearing in the website's guest view are not available to them. Their profile views can be seen only by an Ambassador aged 13–17 whose profile they viewed. Links to listings by underage authors do not show the name.
- For users under 18, AI features (portrait, “Recommendations of the week”, “What to write?” suggestions) are not available, and their data is not sent to Anthropic (section 4.12).
- Users under 18 use the Service with the knowledge and consent of their parents or legal guardian (Terms, section 4).
20. Changes to this Policy
We update the Policy when features, providers or the law change. The current version is always available at druziua.com/privacy-policy and in the app («Налаштування» → «Політика конфіденційності» [Settings → Privacy Policy]), and the update date is shown at the top. We will notify you of significant changes, in particular new purposes of processing or new recipients of data, in the app at least 7 days before they take effect. If a change requires your consent, we will ask for it separately. This English version is a translation; in case of any discrepancy, the Ukrainian version prevails.
21. Contact
- Data questions and exercising rights: druzi.support@gmail.com
- Support in the app: «Налаштування» → «Зв'язатися з підтримкою» [Settings → Contact support]
- Website: druziua.com
We reply in Ukrainian or English.
