vibedoo
Vibedoo Privacy Policy
Effective from 20 October 2026. It explains what data we collect in Vibedoo, why, how long we keep it and what your rights are. This is an English translation; if it differs from the Polish version, the Polish version prevails.
1. Controller
The controller of your data is Dev IT Adam Woźny, ul. Zwardońska 30A, 43-316 Bielsko-Biała, Poland, tax ID (NIP) 9372601350, REGON 384722342. For privacy matters, write to contact@vibedoo.com.
2. What data, why, and on what legal basis
| Data | Why | Legal basis (GDPR) |
|---|---|---|
| Phone number, or your Google account ID with the name and e-mail from Google (for accounts created earlier: e-mail or Apple account ID) | Creating your account and signing in, sending the sign-in code by SMS | Art. 6(1)(b) (contract) |
| First name, date of birth, photos, bio, city, interests, height and the “At a glance” details you choose to add: eye and hair color, smoking, drinking, kids, pets, education, job, languages and zodiac sign (worked out from your date of birth, shown only if you turn it on) | Your profile shown to others; checking that you're 18+ | Art. 6(1)(b) |
| Your gender and who you're looking for (may reveal your sexual orientation); values such as spirituality (may reveal beliefs) | Matching you with people looking for someone like you | Art. 9(2)(a) (explicit consent) |
| Your phone's precise location, updated while you use the app | Showing people nearby and distances (others only see the distance in km) | Art. 6(1)(b) |
| Fixed location (Premium): the place you pick and its coordinates. While it's on, we keep your phone's current location separately and show it to no one | Showing you people from the chosen place and showing your profile to people there, with that place and the distance from it | Art. 6(1)(b) |
| Likes and passes, matches, messages and reactions, filters (distance, age) | Running the app: matches and chat | Art. 6(1)(b) |
| Voice messages: the recording of your voice, its length and loudness graph (waveform), and whether the other person has listened to it | Sending and playing voice messages in the chat with a match | Art. 6(1)(b) |
| Photos and videos sent in the chat: the file (the photo resized, the video compressed), its thumbnail, dimensions, video length, caption, the disappearing setting (view once or a time after opening), whether the other person has opened a disappearing one, and the result of the automatic check for possible nudity | Sending and showing photos and videos in the chat with a match; covering those that may contain nudity until the recipient chooses to see them; handling reports | Art. 6(1)(b) and Art. 6(1)(f) (legitimate interest: user safety) |
| Profile voice intro, if you record one: the recording of your voice (with the silence at its start and end cut off), its length and loudness graph, a text record of what you say (transcript), and the result of the check | Showing the recording on your profile to other users; automatically checking that it doesn't break the Terms (e.g. swearing, sexual content, contact details); handling reports | Art. 6(1)(b) and (f) (legitimate interest: safety and compliance with the Terms) |
| Your phone's notification token and app language, if you allow notifications | Notifications about new matches and messages, in your language | Art. 6(1)(b) |
| Blocks and reports, including the copy of the profile and chat attached to a report | User safety, moderation, obligations under the Digital Services Act (DSA) | Art. 6(1)(c) (legal obligation) and (f) (legitimate interest) |
| Your phone's system (iOS or Android) that you use the app on | Adapting the app to your system, technical support, internal statistics (e.g. how many people use Android) | Art. 6(1)(f) (legitimate interest: developing and maintaining the app) |
| Moderation decisions about your account: account ID, type of decision (dismissing reports, banning, unbanning or deleting the account), its reason, the message to you, the moderator's internal note, the date and whether we notified you by SMS or email | Enforcing the Terms, notifying you of the decision and its reasons, handling appeals, obligations under the Digital Services Act (DSA) | Art. 6(1)(c) (legal obligation) and (f) (legitimate interest: user safety) |
| A hash (SHA-256) of the phone number of an account we deleted for breaking the Terms, and the reason for the deletion; we don't keep the number itself | Preventing a new account being created with the same number (Terms, §3(2)): before sending a sign-in SMS code we compare the hash of the number entered with it | Art. 6(1)(f) (legitimate interest: user safety) |
| Messages sent with the “Idea or problem?” form in Settings: kind (idea, problem, other), the message, your phone's system, app version, account ID and profile name at the time of sending | Answering reported problems and ideas, improving the app; at most 5 messages a day, so the form can't be used to flood us | Art. 6(1)(f) (legitimate interest: user support and developing the app) |
| An anonymous record of an account deletion (without the account ID, name, phone number or email): who deleted the account (you in Settings, us for breaking the Terms, or automatically after 90 days of inactivity), the reason chosen in the app and an optional comment (up to 500 characters), phone system, gender, age, how long the account existed and whether Premium was active | Statistics and improving the app, e.g. understanding why people leave | Art. 6(1)(f) (legitimate interest: developing the app) |
| Date you accepted the Terms and gave consent | Proving we obtained your consent | Art. 6(1)(c) |
| Photos you add, the result of their automatic analysis (whether they show nudity or sexual content, whether a face is visible) and a cropped face thumbnail | Protecting users from adult content, making sure the main photo shows a person, the round avatar in the app | Art. 6(1)(b) and (f) (legitimate interest: safety and compliance with the Terms) |
| Profile verification, if you choose it: a selfie taken in the app with a random gesture, the result of comparing the face on the selfie with your profile photos (a similarity score), the result of checking the gesture and whether the selfie is a photo of a screen or a print, the decision and the date of your consent | Confirming that the photos on your profile show you, and showing others the blue “Verified profile” badge; protection against fake profiles | Art. 9(2)(a) (explicit consent, given before you take the selfie; you can withdraw it by writing to us or deleting your account) |
| Error data: account ID, phone model, system and app version, error trace | Detecting and fixing crashes | Art. 6(1)(f) |
| Data on the Premium subscription and message packs bought: your account ID, the plan or pack bought, dates of purchase, renewals and expiry, country and currency and the store's purchase ID (we don't receive your card or payment account details) | Selling and running Premium and message packs: unlocking features, adding the messages bought to the account, renewals, restoring purchases on a new account, handling complaints and refunds | Art. 6(1)(b) |
Giving your profile data is voluntary, but you can't use the app without it. Without consent to the data in the third row we can't match you, which is why it's required to create a profile.
We don't analyse voice messages automatically or transcribe them. We transcribe the profile voice intro only to check that it doesn't break the Terms; other users never see the transcript. We don't use any recordings to recognise your voice or to create a biometric template. Photos and videos sent in the chat are checked automatically by AWS Rekognition (for a video: a few of its frames) so that those which may contain nudity are covered for the recipient; we don't reject them or assess them in any other way.
The app's appearance is stored only on your phone. We don't use your data for advertising and we don't sell it.
3. Who sees your data
Other users see your profile: first name, age, photos, voice intro (if you record one), bio, city, interests, values, the “At a glance” details you add, and distance. They don't see your date of birth, phone number, e-mail address or exact location. If you turn on a fixed location (Premium), they see the place you picked instead of your profile's city, and the distance is measured from it; we don't mark it as a chosen location or show where you really are. They also see whether you use the app: “Recently active” on your profile (within the last day), and your matches also see “Online” in the chat; never the exact time. You can turn this off in Settings (Activity status); then you don't see others' status either. Only your match sees your messages, photos and videos and hears your voice messages. A disappearing photo or video can be opened by your match only once, for the chosen time; meanwhile the app blocks screenshots and screen recording, but it can't stop someone photographing the screen with another device. If you verify your profile, others see a “Verified profile” badge by your name; nobody sees the selfie itself except the person on our side who checks the verification.
When handling reports and moderating, an authorised person on our side sees your profile, the chats covered by a report, your account's phone number or email address and the history of moderation decisions. They can ban or delete an account that breaks the Terms (Terms, §7).
We entrust data to companies that help us run the app and act on our instructions:
| Provider | What it does | Where the data is |
|---|---|---|
| Supabase Inc. | Database, sign-in, real-time chat | EU (Ireland) |
| Cloudflare, Inc. | Storage of photos, profile voice intros, voice messages and photos and videos sent in the chat and their fast delivery and playback through its CDN; the vibedoo.com domain | Europe; cached copies of photos and recordings on servers worldwide |
| Functional Software Inc. (Sentry) | App error reports | EU (Germany) |
| Fly.io, Inc. | Application server (API) | EU (Germany) |
| Amazon Web Services EMEA SARL (AWS Rekognition, AWS Transcribe, Amazon Bedrock) | Automatic photo analysis: detecting nudity and faces, also in photos and videos sent in the chat; transcribing the profile voice intro and having a language model (Anthropic's Claude, run in AWS) assess the text, to check it; profile verification: comparing the face on the selfie with the profile photos (Rekognition) and checking the gesture on it (Claude) | EU (Germany) |
| LINK Mobility Poland sp. z o.o. (SMSAPI) | Sending SMS messages with the sign-in code and notices that an account was banned or deleted (phone number and the text of the SMS) | EU (Poland) |
| 650 Industries, Inc. (Expo) | Passing notifications on to Apple and Google, who deliver them to your phone (notification token, the other person's name and photo, message text) | USA |
| RevenueCat, Inc. | Running the Premium subscription and message packs: checking purchases with the store and the subscription status (account ID, purchase data) | USA |
| Google Cloud (Google Ireland Ltd.) | Passing Google Play notifications about subscription changes to RevenueCat (purchase IDs) | EU and USA |
Places are suggested from our own list, based on GeoNames data (CC BY 4.0 license). The text you type and your location don’t go to anyone but us.
Google and Apple process data as separate controllers when you sign in with their accounts, under their own privacy policies. Notifications are delivered to your phone by Apple (iOS) and Google (Android). We may also share data with public authorities where the law requires it.
Payment for Premium is handled by the store you buy it in (Google Play or the App Store) as a separate controller, under its own privacy policy. We have no access to your card details.
4. Transfers outside the EEA
We store your data on servers in the European Union. The exceptions are notifications, which pass through Expo's servers in the USA, and Apple and Google may deliver them through their servers outside the EEA, and photos and recordings (profile voice intros and voice messages), which Cloudflare's network caches on the servers closest to whoever views or plays them, also outside the EEA. Supabase, Cloudflare, Sentry, Fly.io and Amazon Web Services (parent company Amazon.com, Inc.) are based in the USA, so in exceptional cases, e.g. technical support, data may be accessed from the USA. This happens on the basis of the European Commission's adequacy decision (EU-US Data Privacy Framework) or standard contractual clauses; you can get a copy by writing to us. Premium subscription data is stored by RevenueCat in the USA, under standard contractual clauses.
5. How long we keep data
- Account (with your phone number), profile, photos, location, likes, notification tokens: until you delete your account. Deleting in the app erases them immediately. We also record when you last used the app: after 30 days without it we stop showing your profile to new people, and after 90 days (a year while your profile is paused) we delete the account (Terms, §14), unless a paid Premium period is running or you have direct messages you bought and haven't used. An account whose profile was never finished is deleted, with its photos, 30 days after the last sign-in.
- Fixed location: until you turn it off, Premium ends or you delete your account. We then go back to your phone's current location and don't keep the chosen place.
- Messages: until the match is removed, i.e. one of you deletes their account or blocks the other. When you delete a message, we erase its text immediately.
- Voice messages: we delete the recording automatically 90 days after it was sent, or sooner when you delete that message or your account. When a match is removed or blocked, the message disappears from the chat right away and the recording is deleted at the latest 90 days after it was sent. A copy in Cloudflare's cache may remain for a short while, no longer than a month, reachable only at a random address known only to your match. If a conversation is reported, a moderator may listen to the reported person's recordings while the file exists.
- Photos and videos sent in the chat: we delete the files automatically 90 days after they were sent, or sooner when you delete that message (or that photo from an album) or your account. A disappearing photo or video is deleted when its time after opening runs out or when the recipient closes it (view once), at the latest 5 minutes after it was opened; until then it is only available through a one-time, short-lived link. A copy in Cloudflare's cache may remain for a short time, no longer than a month.
- Profile voice intro: until you remove it, record a new one in its place or delete your account. A recording that fails the check is deleted right away. Transcripts and check results (of rejected recordings too) are kept until you delete your account, so we can handle reports and repeated violations. A copy in Cloudflare's cache may remain for a short while, no longer than a month. AWS processes the recording only at the moment of the check, on our instructions.
- Notification token: also until you sign out on that phone.
- Reports (with the copy of the profile and chat, including copies of the reported person's photos and videos from that chat, also disappearing ones not opened yet): 3 years from the report, also after account deletion, in case of a dispute, an appeal or proceedings by authorities.
- Banned account: the data stays as it is until the account is unbanned or deleted.
- Moderation decisions: 3 years from the decision, also after account deletion, for the same reasons as reports.
- Hash of the phone number of an account deleted for breaking the Terms: indefinitely, as long as it serves user safety. If you think the block on the number is unjustified, you can appeal (Terms, §7) or object (section 6); if we accept it, we delete the hash.
- Messages from the “Idea or problem?” form: until you delete your account.
- Anonymous record of an account deletion: 3 years from the deletion. It contains no data that easily identifies you, but if you write something about yourself in the comment, we use it only for statistics and improving the app and don't combine it with other data.
- Acceptance and consent dates: until you delete your account.
- Photo analysis results and face thumbnails: as long as the photo, at most until the account is deleted. AWS analyses a photo only when it's added, on our instructions.
- Profile verification: the selfie is deleted as soon as it is decided - right away when verification passes automatically or a new selfie is needed, and after the decision when a person checks it (usually within 24 hours). The selfie of a verification left unfinished is deleted after a day. The result (face similarity, gesture check, decision) is kept until the account is deleted. AWS processes the selfie only when it is checked, on our instructions, and doesn't store a template of your face.
- Error reports: 90 days.
- Database backups: up to 7 days, then overwritten.
- Data on the Premium subscription and message packs (with us and at RevenueCat): until the account is deleted. After the account is deleted, we keep only the store's purchase ID of a pack, not linked to any account, so the same purchase doesn't add messages twice when the Google account's purchases are restored on a new account (our legitimate interest, Art. 6(1)(f)). The store you buy Premium in keeps purchase data under its own rules.
6. Your rights
You have the right to:
- access your data and get a copy;
- rectify your data (you can change most of it yourself in your profile);
- erasure (Settings → Delete account, or without the app);
- restrict processing;
- data portability in a machine-readable format;
- object to processing based on legitimate interest;
- withdraw consent at any time by deleting your account. Withdrawal doesn't affect the lawfulness of earlier processing;
- lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office (Prezes UODO), ul. Stawki 2, 00-193 Warsaw, or the authority in your country.
Send requests to contact@vibedoo.com and give your account's phone number (for a Google account: write from its e-mail address). So that nobody can pretend to be you, we may ask you to confirm the account is yours, e.g. with a code we send by SMS to that number. We reply within one month.
7. Automated decisions
The app automatically chooses who to show you: based on distance, age, gender and who you're both looking for (details: Terms, §2). An automatic filter also blocks posting forbidden words, links and contact details (Terms, §7). We don't make decisions about you with legal effects solely by automated means. Photos are checked automatically by AWS Rekognition: a photo with nudity or sexual content won't be added, and the main photo has to show a face. The analysis only detects that there is a face in the photo: it doesn't recognise who you are, doesn't compare you with other people and doesn't create a biometric template. If you think a photo was rejected by mistake, write to us and a person will review it. Photos and videos sent in the chat are never rejected: those that may contain nudity are shown covered, and the recipient decides whether to see them. The profile voice intro is transcribed automatically by AWS Transcribe, the text is checked with the same filter as the profile bio, and then the Claude language model (in Amazon Bedrock, on AWS servers in the EU) assesses whether what it says breaks the Terms: a recording with forbidden words, sexual content, contact details, insults, or talk of money or advertising, shorter than 5 seconds or with no speech won't be added, and the app tells you why. If you think it was rejected by mistake, write to us. Decisions to remove content already published, and to ban or delete accounts, are made by a person. Profile verification is optional: AWS Rekognition compares the face on the selfie with your profile photos, and the Claude model checks that you show the asked gesture and that the selfie isn't a photo of a screen. When the result is clear, you get the badge right away. When the gesture or your face isn't visible, we ask for a new selfie. In every other case a person decides: the automatic check never rejects a verification on its own.
8. Phone permissions
- Location (only while you use the app): showing people nearby. The app doesn't work without it.
- Notifications (optional): new matches and messages. On Android you can mute matches and messages separately.
- Photos and videos: adding photos to your profile and sending photos and videos in the chat; the app shows you your gallery, but we only upload what you choose. You can also give access to selected photos only.
- Microphone (optional): recording voice messages, only while you hold the record button or record with the lock, and the profile voice intro, from tapping “Record” to “Done”. We don't listen in the background. We only upload recordings you send or save, and the ones you delete are erased from your phone.
- Camera (optional): the front camera on the profile verification screen, to take the selfie, and the camera in the chat when you take a photo or record a video to send (a video also records sound, so the microphone is needed then). We send only what you confirm.
You can revoke permissions at any time in your phone's settings.
9. Minors
Vibedoo is only for people aged 18 or over. If we learn that an account belongs to a minor, we delete it.
10. Security
Connections are encrypted (HTTPS), sign-in codes sent by SMS are single-use, and only authorised people have access to the data.
11. Changes to this policy
We'll tell you about significant changes in the app, by SMS or by e-mail before they take effect.
12. The vibedoo.com website
The website counts visits with Umami: no cookies, no stored IP addresses and no tracking across websites. We only see totals, e.g. how many people opened a page and from which country.
The vibedoo.com/app link (in the QR code and in our social media profiles) takes you to the app store. We only count how many times it was opened on a given day, from which source (e.g. TikTok, Instagram), from which system (Android, iOS, computer) and as part of which campaign, with no cookies, no IP address and no device identifier. We pass the source and campaign on to Google Play to see where installs come from.