Privacy Policy
1. Data Controller
This Privacy Policy describes the data processing carried out by the Yanvo mobile app (“Yanvo”, the “App”, “we”).
- Data controller: Sergen Baş
- E-mail: privacy@yanvo.app
2. What This Policy Covers
Yanvo matches users for short voice conversations without them sharing identifying information. By design:
- The App does not collect a real name, a profile photo, or direct contact details (e-mail, phone).
- A user is represented only by a unique username.
- Calls are never recorded — audio is relayed between participants in real time.
3. Data We Collect
3.1 When an account is created
The first time you open the App, a random user identifier (UID) specific to your device is created through the Firebase Authentication mechanism called anonymous authentication. That is a sign-in method requiring no name, e-mail or password. The name of the mechanism does not mean your data is “anonymous data” under GDPR or the Turkish KVKK: the profile information listed in Section 3.2 (username, age, gender, province and so on) is stored against that identifier and represents your account in a pseudonymous but uniquely consistent way.
3.2 Profile information (entered by you)
| Data | Description | Required? |
|---|---|---|
| Username | Unique, changeable pseudonym | Yes |
| Date of birth | Used only to verify that you are 18 or older and to show your age (in whole years) to a match candidate | Yes |
| Gender | Self-declared option (Female / Male / Non-binary / Prefer not to say) | Yes |
| Province | One of the 81 provinces of Türkiye — your precise or GPS location is never collected or processed | Yes |
| Conversation language | Turkish or English | Yes |
| Interests | Topics chosen from a fixed list | No |
| Bio | Optional short free-text introduction | No |
There is no field in the App for a profile photo or a real name.
Free text you write (the bio) is checked against our content policy — profanity, sexual content, hate speech, threats, fraud promotion, and contact details such as phone numbers, e-mail addresses, links and social media handles are rejected. The check runs both in the app and on the server.
3.3 Matching and call data
- While you are actively searching for a match, your province, username, age, interests and language are held in a temporary “match queue” record.
- When you are shown a match candidate, the other side sees only your username, age, province, shared interests and language. Yanvo Plus mark: if you have an active Yanvo Plus right (subscription, gift or wheel prize), the people you match, talk and chat with see only a “Plus” mark next to your name; no payment, subscription period or billing detail is shown. The mark disappears when the right ends. Admin role mark (live on Android; on iOS with the next release): if Yanvo has given your account an admin role (Super Admin, Moderator, Safety or Support), other users see only the role name and color next to your name; the mark disappears when the role is removed.
- In-app notices (live on Android; on iOS with the next release): when you are gifted Yanvo Plus or given an admin role, the app shows you a private notice (the gift days and end date, or the role name). Only you see it; the time you dismiss it is stored. Your notices are deleted when you delete your account.
- Inviting friends (live on Android; on iOS with the next release): your invite code and invite statistics (how many people you invited, how many rewards you earned, the day of your last reward) are stored. If you sign up with an invite code, your invite link (the inviting account), your server-verified total call time and the id and counted length of each counted call are stored; the person who invited you only sees the progress and the outcome, not your username or your calls. To prevent abuse (self-invites, re-made accounts on the same device, repeated rewards), the fact that an invite code was used on your device and the ids of the last 20 accounts used on it are stored against an irreversibly hashed device id, for 365 days after the device was last seen; your IP address is not used for this. When you delete your account, your code, statistics and your own invite record are deleted; the device records stay until the end of their retention period to prevent abuse.
- Date of birth and age declaration (live on Android; on iOS with the next release): your date of birth is a declaration; Yanvo does not verify your age with an ID or any other method and never shows it as a "verified age". Once saved, the date of birth can't be changed in the app (contact Support if it's wrong). If a date of birth under 18 is confirmed, that declaration is stored with its date and time on your account and against your hashed device id, and is applied to new accounts made on the same device, so the age limit can't be passed by changing the date.
- A call starts only if both sides explicitly accept.
- Call duration (start and end timestamps) is kept in order to compute daily free or Plus minute usage.
- The voice call itself (the audio) is never recorded or stored on our servers. Audio is relayed between participants in real time over WebRTC; a TURN/STUN relay service is used to establish the connection (see Section 5).
- There is currently no AI or automated voice analysis running in the App — your voice is not analysed and no transcript is produced.
3.3a Text messaging
- You can exchange text messages only with people for whom you both left a “Leave a Trace” after a real voice call. This creates a messaging connection record between the two of you; the connection stays open until either side chooses “Remove connection”, for as long as a block or an account restriction lasts, or until an account is deleted. Messaging is free for every account; either side can start the conversation and both can reply (in the app with the next Android release). These conditions are verified on our servers.
- Data stored: the message text (text only — photos, files or audio cannot be sent), the sender’s user ID and the time it was sent; on the conversation record, both sides’ usernames, a preview of the last message, unread counts and read/delete times.
- Messages can be seen only by the two participants of the conversation. Yanvo administrators cannot access conversations directly; when a message is reported, only a copy of the reported message and at most the 5 messages immediately before it are attached to the report for review by authorised moderation roles.
- Sent messages pass through an automatic text filter for content that breaks the community guidelines (profanity, insults, threats, harassment, hate speech, sexual content, scams, sharing contact details such as a phone number or e-mail — in every written message, messages to the Admin included, for every account); a message that breaks them is not sent. Messages are not used for advertising or profiling.
- New-message notifications do not show the message text; they only say “You have a new message.”
- Message to the Admin: every account can write to the Yanvo Admin (no mutual trace needed): you send one message first, and once the Admin replies the conversation opens both ways. Replies appear in Messages. Only you and the Yanvo Admin account can see this conversation; it goes through the same content filter and 90-day retention rule as other messages, and “Delete chat” hides it for you. The fact that you sent your first message and that the Admin replied (the dates and the conversation ID) is kept for as long as your account exists, so that deleting the chat does not change it; it is deleted together with the conversation when you delete your account.
- Retention: each message is deleted automatically 90 days after it was sent, and an inactive conversation 90 days after its last message.
- Deleting a chat: “Delete chat” hides the conversation and its messages up to that point for you. If both sides delete it, the conversation and all its messages are permanently deleted.
- Messages and announcements from the Yanvo Admin: the Yanvo Admin account can write to you in your Admin conversation, one to one or as a bulk announcement to all eligible accounts (deleted, restricted, under-review and incomplete accounts excluded); you can reply in the same conversation. A notification is sent only if your device’s notification permission and the notification setting in the app are on, and it never contains the message text (“The Admin sent you a message.”); whether and when it is shown depends on your operating system and connection — instant delivery is not guaranteed. For bulk announcements we keep, per recipient, your user ID, your username at the time of sending, whether the message reached your Messages inbox and whether a notification was sent.
- Read information:
- When it is created: only when you actually see a message from the Yanvo Admin or (with the new Android version) from the person you chat with, on that chat screen while the app is in the foreground. A notification reaching your phone, opening the Messages list, the chat staying open in the background or the sender looking at the conversation does not count as read. Only you can create it (by seeing the message); it is never changed or undone afterwards.
- What we keep: on an Admin message and on a message between users, the time you saw it (server time, once); on a conversation between users, the time you first used an app version that sends read information in that conversation (once); for a bulk announcement, a “read” flag and time on your recipient record, and whether your app could send read information when the announcement reached you; on your account, the time you first used an app version that sends read information (recorded once). In every conversation we also keep your unread count and last-read time for the unread badge (this already existed for all conversations).
- Purpose: to let the Yanvo Admin know whether support messages and announcements were seen, to let the person you chat with know whether their messages were seen, and to show the unread badge correctly. “Sent” means the message was stored on Yanvo’s server, not that it reached the other person’s device. Older app versions do not send read information, so those users are shown as “no read information”, never as “not read”. Read information is not used for advertising or profiling.
- Who can see it: read information for Admin messages and announcements is visible only to the Yanvo Admin account — not to other users or other administrator roles. The time you first used a version that sends read information is part of your profile record, visible to you and authorised Yanvo administrators. In conversations between users, the time you saw a message (“Read · time”) is shown only to the person who sent that message; other users cannot see it. The unread count and last-read time are part of the conversation record and therefore technically accessible to both participants, but the app does not show them.
- Retention and deletion: the read time on a message is deleted with the message, 90 days after it was sent. Recipient records of bulk announcements (read information included) are deleted automatically after 90 days. “Delete chat” hides the Admin conversation only for you; its messages and read information remain on the Admin’s side until the 90 days pass. The unread count and last-read time are deleted with the conversation. When you delete your account, your Admin conversation, read information, recipient records and the marker on your account are deleted immediately; the announcement’s totals, which contain no personal data, remain.
- Deleting your account: when you delete your account, all conversations you took part in (including your conversation with the Admin and the record of your one message), their messages (read receipts included), your recipient records for bulk announcements and your messaging connections are permanently deleted for both sides. Account deletion does not delete or change report records, message copies attached to reports, or moderation history (including warning/restriction counters). Message copies attached to reports follow the same retention rule as report/moderation records (see Section 6).
3.3b Call ratings, public summary and Plus extras (live on Android; on iOS with the next release)
- Call rating: After a call that really connected you can optionally give the other person 1–5 stars. Stored: the call id, the rating and rated user ids, the stars and the time. One rating per call; your latest rating of the same person is what counts in their summary. Raw rating records are deleted after 180 days; each rater's latest rating is kept for the summary. Nobody is shown who gave which rating, and a low rating alone never restricts an account.
- Public summary: In a match offer and on the call screen the other person sees your average rating and number of raters (only once at least 5 different people rated you), the month and year you joined Yanvo (from your account's creation time) and a mask gift you chose. With Yanvo Plus a ranking score derived from this summary orders eligible candidates (with fewer than 5 ratings everyone has the same average value).
- Mask gift (Plus): Sender, recipient, mask type, sent and end time are stored; a mask shows for 24 hours from delivery and the record is deleted 7 days after that. The recipient can hide masks.
- Chat theme and pinning (Plus): The chosen theme is stored on the conversation (visible to both sides) together with who chose it; your list of pinned chats belongs to you alone.
- Account deletion: Your public summary, ratings you received, your masks, pins and the mask records you sent are deleted, and ratings you gave are removed from other people's summaries.
3.4 Safety, report and block data
- If you report someone after a call, we record the report category, the optional short note you write (up to 500 characters), the related call identifier, the timestamp, and a 24-hour review deadline.
- The list of users you have blocked is stored against your account (visible only to you).
- Repeated or confirmed reports can change your account’s moderation state (warning, temporary restriction, permanent restriction). A permanent restriction is always decided by a human administrator, never automatically.
3.5 Usage and gamification data
Daily talk-time usage, Leave a Trace (reconnect) usage, and Weekly Wheel participation and rewards are stored against your account.
3.6 Subscription (Yanvo Plus) data
Yanvo Plus purchases are handled through RevenueCat, Inc., with payment processed by the app store billing system. Yanvo’s own database never sees or stores your card details. RevenueCat processes the random user identifier (UID) assigned to your device and your subscription state (active, cancelled, renewal date) — see Section 5 and RevenueCat’s own privacy policy.
3.7 Technical data collected automatically
- Every network request to the Firebase, Xirsys and Cloudflare infrastructure can, by the nature of those services, see your IP address. Yanvo’s own code does not separately log or store it.
- Your in-app interface language is stored locally on your device only and is not sent to our servers.
- If you grant notification permission, a device-specific push notification token (Expo push token) is stored against your account — used only to send in-app notifications (see Section 5). It is permanently deleted when you sign out (for that device) or delete your account (for every device it was registered on).
3.7a Operational measurements (live on Android; on iOS with the next release)
To monitor the service, the app records these events without any message or audio content: app opens (platform, app version and build number), how a match search ended and the waiting time, steps on the Plus purchase screen (view, start, cancel, pending, error) and the result of a store review request. Activity by hour and province is kept only as aggregate counts; groups of fewer than 5 people are not shown. Raw events are deleted after 90 days. No payment token or receipt is stored. For admin accounts, a device id is stored hashed together with the user id for new-device security alerts.
3.8 Data we do not collect
For clarity: Yanvo currently does not use advertising identifiers for tracking, analytics or usage tracking (Firebase Analytics is configured but not actively used in the code), crash reporting, location (GPS), your contact list, or camera/gallery access. The App may show optional rewarded ads through Google AdMob in exchange for extra talk time (see Section 5).
4. Why We Process Your Data
- Checking the 18+ requirement against the birth date you declare, and legal compliance (no identity or age-document verification)
- Operating the matching algorithm (province, language, interests)
- Operating the voice call infrastructure (WebRTC/TURN)
- Safety: running the report and block system and moderation decisions
- Providing and validating the Yanvo Plus subscription
- Enforcing daily usage limits and running gamification features (Weekly Wheel, Leave a Trace, rewarded ads)
5. Third Parties We Share Data With
Limited data is shared with the following service providers, solely to deliver the relevant service:
| Service provider | Purpose | Data shared |
|---|---|---|
| Google Firebase (Google LLC / Google Ireland Ltd.) | Authentication and database (Cloud Firestore) infrastructure | Random user identifier (UID) and all profile/app data listed in Section 3 |
| Xirsys | TURN/STUN relay server for voice calls | Network/IP information during connection (audio is relayed, never stored on Xirsys servers) |
| Cloudflare, Inc. | Hosting the intermediary Worker that delivers Xirsys credentials securely | Authentication token (Firebase ID token), IP information |
| RevenueCat, Inc. | Subscription and purchase management | Random user identifier (UID), purchase/subscription state |
| App store billing | Payment processing | Payment information tied to your store account (Yanvo never sees it) |
| Google AdMob | Optional rewarded ads (in exchange for extra talk time) | Technical/device information needed to show an ad — only if you choose to watch one |
| Expo (650 Industries, Inc.) | Relays the push notification token to Apple and Google notification services (APNs/FCM) | Push notification token — created only if you grant notification permission |
Your data is never shared with or sold to any third party for advertising purposes.
5.1 International transfers
The servers of the providers above may be located outside Türkiye (primarily the US and the EU). Your data may therefore be transferred abroad within the meaning of Article 9 of the Turkish KVKK.
6. Retention
- Your profile data is retained for as long as your account is active.
- Report and moderation records may be retained for a reasonable period after account deletion, for safety and legal compliance.
- Temporary match queue and candidate records are deleted as soon as a match completes, or shortly afterwards.
- Text messages are deleted automatically 90 days after they were sent, and inactive conversations 90 days after the last message; earlier if both sides delete the chat or you delete your account (see 3.3a).
7. Your Rights (KVKK Art. 11)
Under Article 11 of the Turkish KVKK you have the right to: learn whether your personal data is processed; request information if it is; learn the purpose of processing and whether it is used accordingly; know the third parties to whom it is transferred domestically or abroad; request correction if it is incomplete or inaccurate; request erasure or destruction; request that these actions be notified to the parties it was transferred to; object to an outcome against you arising from analysis solely by automated systems; and claim compensation for damage caused by unlawful processing.
To exercise these rights, contact us at privacy@yanvo.app.
From inside the App: use Delete My Account in Settings (the You tab) to permanently delete your account, username and profile. This cannot be undone.
8. Children’s Privacy
Yanvo is intended only for users who are 18 or older; the limit is enforced based on the date of birth declared at registration (a declaration; there is no ID verification). We do not knowingly collect data from users under 18. For our zero tolerance toward child sexual abuse and exploitation (CSAE), our reporting routes and the related processes, see the Safety and Community Guidelines.
9. Data Security
Your data is protected by access control enforced on the server side (Firestore security rules) — each user can reach only their own data, and the limited, pseudonymous information (username and profile details) of the person they matched with. Voice traffic is relayed encrypted.
10. Policy Changes
We may update this policy. The current version is always published on this page, with the “Last updated” date at the top.
11. Contact
- Privacy and data requests: privacy@yanvo.app
- Safety, harassment and abuse reports: safety@yanvo.app
- General support: destek@yanvo.app