privacy policy
Explains which of your data we process and why, who can see it, how long we keep it and how you can use your rights.
Last updated: 18 November 2026 · Version: 2026-11-18
on this page
In short
B4Drink is an app for people aged 18 and over that helps them meet in İzmir and plan a first meeting at a venue. This text explains what data we process and why, who can see it, how long we keep it and what you can do.
Our notice under Article 10 of the Turkish Personal Data Protection Law No. 6698 (KVKK) is a separate page: the KVKK Notice.
This text applies to the B4Drink mobile app, the b4drink.app website and the services connected to them (together, the "service").
- We do not sell your data and we do not share it for advertising. The app has no analytics, advertising or crash-reporting tool.
- Our servers and service providers are outside Türkiye. Your data is processed outside Türkiye.
- Explicit consents are taken separately: for your gender and who you want to meet, for transfers abroad, for location, for selfie verification and for notifications. You see them all in Settings > Security and privacy > My consents and can withdraw them there.
- You can verify your profile with a selfie. This is optional and needs a separate consent.
- The profile and chat photos you upload may be checked automatically when you upload them for inappropriate content such as nudity, sexual content and violence. The check is done by Amazon Rekognition from Amazon Web Services (Frankfurt, EU). Details are in "Automated systems and moderation".
- You can delete your account yourself in the app. Most of your data is deleted; the remaining exceptions are listed plainly in "Data retention and deletion".
Who is the data controller?
Data controller: B4 Labs LLC, a Missouri LLC (registry no. LC014786788), 117 S Lexington St Ste 100, Harrisonville, MO 64701, USA. Our company is established in the United States and is not established in Türkiye.
For privacy matters you can reach us at privacy@b4drink.app.
What data do we process?
While you use the app we process the data below. You provide most of it; some of it arises as you use the app.
- Account: your e-mail address, password and app language. Your password is not stored in plain text; Supabase Auth stores it as a bcrypt hash. When you sign up and when you reset your password, a 6-digit code is sent to your e-mail address; it is valid for 10 minutes and works once. Whether you granted location and notification permission (yes or no) is also stored on your account.
- Profile: your first name, date of birth (age), gender, who you want to meet, whether you are open to everyone, what you are looking for (for example friendship, flirting, relationship), drink preferences, favourite drinks, preferred İzmir districts and your photos.
- Verification (optional): if you choose to verify with a selfie, your selfie photo and the record of your verification request. Details are in "Verifying your profile with a selfie" below.
- Interactions: who you liked (including sparks you sent; a spark is a highlighted like, and the record keeps that a like is a spark and when it was sent), passed, matched with, blocked and reported, and your meeting invites and plans with venue and time. If you leave a plan to the other person, this (who left it to whom, and when) is kept in the plan state of the match and is deleted when the match is deleted. When you end a match, only the two user ids and a time are kept so the same two people do not match again; this record does not say who ended it or why.
- Meeting preferences (optional): your vibe (calm or lively), the venue types you like (cafe, bar, outdoors; up to 2), the times you are usually free, and whether your "free tonight" switch is on and when it turns off (at the latest 04:00 the next morning, Istanbul time). You can skip these.
- Favourite venues: up to 3 venues you pick in Profile, in your order.
- Profile details (optional): an "about me" text (up to 160 characters, free text), your link to İzmir, your work field (a broad category such as student, employed or entrepreneur; no workplace or school name is asked), height, zodiac sign, languages you speak, your first-order style, your style on a meetup, smoking (I don't, socially, I do), your signature drink (alcohol-free options only), your interests and your "this or that" answers. You do not have to provide any of them, and you can change or delete them at any time. Phone numbers, links, usernames and e-mail addresses are blocked in the "about me" field. This block is a first line of defence, not a guarantee; do not write personal data in a place others can read.
- Meeting feedback (optional): your answers after a meeting. Whether you met (we met, the other person did not show, I could not make it, no meeting happened), a like or dislike for the venue, and whether you want to meet again.
- Suggestion preferences and log: when you postpone or switch off a meeting suggestion in a chat ("not now" or "turn off in this chat"), the day a suggestion was shown to you and how you answered.
- Chat: the messages you write, photos you send, voice notes (with duration), a location you share (latitude, longitude and place name) and drink cards. A drink card is an invitation indicator; no payment is made.
- Photo check record: when your profile and chat photos are checked automatically (see "Automated systems and moderation" below), a decision record is kept for each photo: the file path, the decision (approved, not approved, under review), the time of the decision, the number of attempts and the names and confidence scores of the labels that led to the decision. The image itself is not in this record.
- Delivered and read information: when a message you sent reached the other person's app (delivered) and when the other person saw it with the chat open (read). It is kept on the server in a separate record tied to the message.
- Settings: hiding from discovery, taking a break, incognito mode, spotlight, read receipts (on by default), your notification preferences, quiet hours and time zone.
- Notification information: if you turn notifications on, your device's notification token, device type (iOS or Android), app version, language and time zone.
- Feedback: the reason you pick when you end a match and, if you write one, a note of up to 300 characters; the reason you pick when you delete your account.
- Support and feedback form: the kind (suggestion, bug, support, other), message, whether you want a reply, app version, platform and language you send from the form in Settings. The e-mail address of your account is not copied into the form; it is read from your account only if you asked for a reply, when we answer.
- Usage events: records kept on our server about meeting plans (for example plan sent, accepted, expired, moved to another time, leaving a plan to the other person and taking that back), the type of meeting feedback, the venue like, favourite venue choices, suggestions postponed or switched off and venue suggestion records. We use no third-party analytics or advertising tool.
- Abuse-limiting counters: counters of how many times you did certain actions, to stop too many actions in a short time.
- Your usage allowances: your daily swipe allowance (likes and passes together; currently 40 a day) and your weekly spark allowance (currently 3 a week) are calculated on the server from the times of your likes and passes; no separate counter is kept for them. The numbers may change over time. If an allowance has been set specially for your account, its type and expiry date are also recorded; right now everyone has the same allowances and no payment or price data is kept.
- Waiting list: if you join the waiting list for a district that has not opened yet, the district and the date.
- Consent record: for each explicit consent, the type of consent, the version of the text, whether it was given or withdrawn, the time and where it was given (app or web). Every grant and withdrawal is also written to a consent history. For selfie verification, the consent version and time are also kept on the verification request.
- Technical logs: our infrastructure provider may keep connection logs (for example your IP address); how long these logs are kept is set by the provider's own retention periods.
- On your phone: your session, unfinished sign-up details, filter and Today screen preferences and the "free tonight" end time stay in the app's own storage and are not sent to us. Your password is not stored on the phone.
Verifying your profile with a selfie (optional)
Selfie verification is entirely optional. If you choose it, you take a selfie to show that the person on your profile is really you, and once verified a "verified profile" badge appears on your profile. You tick a separate explicit consent box for it (Selfie Verification Explicit Consent).
How it works: you are given a random pose and take the selfie with the app's camera (you cannot pick one from your gallery). A person at B4Drink compares your selfie with your profile photos; no software or artificial intelligence is used. We do not use face recognition software, artificial intelligence, face templates or a third-party face recognition service. A face image can still be treated as sensitive, so we make this step depend on a separate consent.
Your selfie is kept in private storage. Other users never see it, and you cannot read it back from the app. Only an authorised person at B4Drink opens it, with a short-lived (10-minute) link.
The selfie file is deleted when a decision is made (approved or rejected), when you cancel the request, when the request is not completed within 14 days, and when you delete your account. Deletion runs through a queue and usually takes a few minutes; if something goes wrong, the system retries.
The record of your verification request (status, requested pose, rejection reason if any, attempt number, times, consent version and time) stays while your account exists and is deleted when you delete your account. The selfie file path is removed from this record when the decision is made.
Other users only see the badge as "verified". If you change your first profile photo the badge is removed and you can verify again. The badge does not mean an ID, background or criminal record check; it only shows that a person compared the selfie with your profile photos.
To withdraw your consent or ask for the badge to be removed, write to privacy@b4drink.app.
Location
Location permission is asked for during sign-up and when you want to share a location in a chat; you do not have to give it. We also take a separate optional explicit consent for looking at your location at sign-up (Location Explicit Consent text). If you give the permission and the consent, your phone's location is checked once during sign-up and the nearest İzmir district is worked out on your phone. This location is not sent to our server and is not stored. On the server we only keep whether you granted location permission. We do not track your location in the background.
If you share a location in a chat, your current latitude, longitude and a place name are sent as a message and the other person in the chat sees them. We show a confirmation screen before sending; nothing goes to the other person until you confirm. Your phone's operating system map service (Apple or Google) may be used to find the place name; this lookup happens before the confirmation screen is shown, so your location may reach that service before you confirm. A shared location is part of the message: it is deleted when the message is deleted, and it can remain in a report copy (see below). If you tap a location message you received, the location opens in the map app on your phone (Apple Maps on iPhone, a map app on Android, or Google Maps in your browser if there is no suitable app). The coordinates then go to that map service, and its own terms apply.
Special category data and explicit consent
Your gender and who you want to meet may be treated as special category personal data (sex life) under KVKK Article 6. What you are looking for (for example flirting, relationship) and whom you like are handled with the same care. That is why we process your gender, who you want to meet and what you are looking for only with your explicit consent.
This consent is collected in a text and a checkbox separate from the terms of use. This consent is required to create an account: if you do not consent, we cannot match you using this information and sign-up cannot be completed; you can then leave sign-up. When you tick the box, we store the version of the consent text and the time as proof in your consent record. We also take separate explicit consents for transfers abroad, location, selfie verification and notifications; the transfer consent is also needed for the account, the others are optional. You see and withdraw your consents in Settings > Security and privacy > My consents. You can withdraw consent at any time; withdrawal does not make earlier processing unlawful.
Your photos may show information about your appearance. We do not use profile photos for face recognition. Please do not upload photos that show other people or contain sensitive information.
Your drink preferences (alcoholic or not) are not processed as health data and are used only for matching and venue suggestions. The app does not encourage anyone to drink alcohol.
Messages, voice notes and photos are free content; a person can write or send anything. Please do not share other people's private information.
Device permissions
To make features work, the app may ask your device for the permissions below. All of them are optional and you can take them back at any time in your phone's settings; if you do not grant one, only the related feature does not work.
- Location: to suggest your nearest district at sign-up and to share a location in chat (see the Location section above).
- Photo library: to add photos to your profile or a chat. We only upload the photos you pick. On Android, photos are chosen with the system's own photo picker; access to your whole library is not requested.
- Camera: to take photos in chat and to verify your profile with a selfie.
- Microphone: to send voice notes. A recording is made only when you start it.
- Notifications: to send notifications such as matches, messages and plans.
- We do not access your contacts.
What do we use your data for?
The full table of our purposes and legal grounds under KVKK is in the KVKK Notice. In short:
- To open your account, let you sign in, show your profile, match you with suitable people, offer chat and meeting plans, and suggest venues.
- We use your gender, who you want to meet and what you are looking for in two places on the server: the matching filter, and the rule for who picks the venue in a meeting plan (in the first plan, if exactly one of the two people is a woman, she picks the venue; the planning can be left to the other person while no plan is open, and once the time of a meeting has passed the turn to plan moves to the other person).
- Taste preferences, availability, "free tonight" and favourite venues: to rank venue suggestions for you and highlight suitable times. You give these voluntarily and can change or delete them at any time.
- Profile details: to complete your profile. They are also used to show you, inside the app, how complete your profile is; this percentage is not shown to other users.
- Selfie verification: only to verify your profile.
- Applying the daily swipe and weekly spark limits and highlighting a spark you send to the person who receives it.
- To send notifications: for events such as a new match, a message or an invite. You can turn notifications off in your phone settings or in the app.
- Reports, blocking and preventing abuse, keeping people safe, and enforcing the 18+ age limit.
- To measure and improve the product with meeting feedback, event records and match-ending feedback.
- To meet a legal obligation, answer requests from competent authorities and protect a right.
- To protect children, prevent child sexual abuse and exploitation (CSAE, CSAM), report such cases to the competent authorities and help with investigations (see "Child safety and legal duties" below).
Automated systems and moderation
Who appears first in discovery and which venues are suggested is worked out on the server by certain rules. These rules look at things such as shared districts, drink preference, what you are looking for and, if you gave them, your taste and availability answers. Venue suggestions are not ranked in return for payment.
These calculations do not make a fully automated decision with legal effect on you or anyone else. For decisions such as suspending or closing an account, our authorised team reviews reports and records.
Photos may be checked automatically by an image check when you upload them. The check exists to stop images with nudity, sexual content, violence or hate symbols from being published on B4Drink. Our team decides when the check is switched on, and once it is on it works as described below. Until it is switched on, your photos are not sent anywhere for this purpose.
Your message text, your about-me text and your name are checked on the server against a short list of banned words; no artificial intelligence is used. When an attempt is refused, the text is not stored; only your user id, the category, the source and the time are kept, for 180 days. We do not scan the content of your voice notes with automated systems. Security checks such as rate limiting look at how often requests are made to prevent abuse.
- Who does it: the Amazon Rekognition service of Amazon Web Services (AWS). AWS acts here as a processor on our behalf. The photo is sent to AWS's region in Germany (Frankfurt, eu-central-1). AWS is a US-based company.
- What is analysed: only your profile photos and the photos you send in chat. The image is analysed only to find content such as nudity, sexual content, violence and hate symbols. We do not do face recognition, we do not identify anyone and we do not compare faces. Your verification selfie, your message text and your voice notes are not sent to this system.
- How AWS may use it: AWS processes the photo only to analyse it on our behalf. By default, AWS's artificial intelligence services may use content to improve their own services; we apply the AI services opt-out policy in our account, which prevents this, and no photo is sent to AWS before that setting is in place.
- What we keep: we do not make a separate copy of your photo for the check. Only a decision record is kept: the file path, the decision, the time, the number of attempts, and the names and confidence scores of the labels that led to the decision. This record stays until you delete your account; records of failed attempts are deleted after 7 days.
- The result: if the photo is acceptable, it appears as normal. If it is not, it is not published, it is deleted and the app tells you. A photo we cannot be sure about is put "under review"; an authorised member of our team looks at it and approves or rejects it, and until then it is not shown to others. If the check service cannot be reached, the photo also waits "under review". If you think a photo was rejected by mistake, write to support@b4drink.app.
- Limit: this check does not catch every inappropriate image and is not designed to reliably detect illegal content (for example child sexual abuse material). It does not replace our reporting system or our team's review.
Who can see it?
Other users see the following in discovery, likes and chat lists: your first name, age, what you are looking for, drink preferences, favourite drinks, districts, photos and, if you have one, the "verified profile" badge. Your e-mail address and password are never shown to other users. Your date of birth is sent to the app to work out your age; only your age is shown on screen. When they open someone's profile page they also see that person's profile details and meeting taste (atmosphere and venue types) and, if you matched, their favourite venues.
Your gender is not shown to other users as an information field, and neither is who you want to meet. However, because the person who picks the venue in the first meeting plan is decided by a rule that depends on gender, the person who sees the plan may be able to work this out indirectly (the plan may have been left to the other person later or the turn may have moved, so this is not certain). The "show my gender on my profile" option in Settings currently only shows a label on your own profile screen; it does not show your gender to any other user.
Likes: you see the people who liked you on the "Likes" screen. If incognito mode is on, only the people you liked can see you on that screen. You always see the person who sent you a spark; the person you send a spark to also always sees you on the Likes screen, and your spark is highlighted in their list.
Only the person you matched with in the chat sees your messages, voice notes, photos and a location you share.
You always see that your message arrived (delivered). You see that it was read (two ticks) only when both of you have "read receipts" on in Settings. If you turn it off, you do not show what you read and you do not see what others read. Messages you read while it was off are never shown to the other side, even if you turn it on later. Your own unread count is visible only to you and is kept even while the setting is off. Your read-receipts setting is stored on your profile record and is used only so the server can apply the rule; other users cannot see this setting directly.
Your availability answers, your "free tonight" status and your meeting feedback are not shown to anyone else. They can only appear when they overlap, in a suggestion or a chat card (for example, if you both picked a calm vibe, "you both like a calm place"). Your atmosphere choice (calm or lively) and the venue types you like, however, are shown as your "meeting taste" to people who can see your profile. If notifications are on and someone you matched with turns on "free tonight" while you also have it on, the person who turned it on first may get a notification.
Your profile details (about-me text, height, zodiac sign, smoking and the others) are shown on your profile page to other users who can see your profile: people who can see you in discovery, people who liked you and people you matched with. Only you can edit them. Authorised members of our team may read your "about me" text while reviewing a report.
Your favourite venues (up to 3) are shown to the person you matched with when a plan is prepared; a venue you both picked is marked "a favourite of both of you".
Your "meet again?" answer is private: it appears only if you both say yes. "The other person did not show" answers are not shown to the other person and trigger no automatic penalty; if at least two different people report this about one person within 60 days, our team may see it for review.
You and a person you blocked cannot see each other. If you turn discovery off or take a break, you do not appear in discovery.
Your profile photos are kept in a storage area that anyone who knows the link can open, because they are shown to other users. File names contain your user id, a time and a random part, so they are hard to guess, and the area cannot be listed; but the link is not secret, and if you give it to someone they can see the photo. Photos and voice notes you send in chat are in private storage: only you and your match in that chat can open them, with signed links that are valid for about one hour. If you send such a link to someone else, they can open it until it expires.
The B4Drink team: authorised members of our team can access the data needed for support, report review, safety, selfie verification and photos that are put "under review" in the photo check. Technically, the team's access covers the whole database. In the admin panel, authorised team members can see account information, reports and evidence copies for support and safety work; access is given by role and every access is logged. Private chats are not open for free browsing.
Service providers
We share your data only with providers needed to run the service. The ones we actually use:
- Supabase: database, authentication, file storage, server functions and scheduled clean-up jobs. Our project runs on AWS in the Frankfurt (EU) region. The provider is a US-based company.
- Amazon Web Services (Amazon Rekognition): while the photo check is in operation, an image analysis service that analyses the profile and chat photos you upload for nudity, sexual content, violence and hate symbols. The photo is sent to the Frankfurt (EU) region; the provider is a US-based company. The AI services opt-out policy is applied so that AWS does not use the content to improve its own services. Until the check is switched on, no photo is sent to AWS.
- Resend: the e-mail service that sends sign-up and password-reset e-mails. Resend receives your e-mail address and the e-mail containing the code; no other profile data is sent. The processing region is Ireland (EU). How long Resend keeps data depends on its own retention periods; we do not set them.
- Expo Push service and Google (FCM): deliver notifications to your device on Android. The notification text (the sender's name, venue and time, and, if on, the first 110 characters of a message preview) passes through these services. You can turn the message preview off in Settings > Notifications; then a fixed text is sent. How long these services keep notification content depends on their own policies; we do not set it. On Android the notification infrastructure may create its own technical identifiers.
- Apple (APNs): will be used for iPhone notifications once the iPhone version is released. It is not active now.
- Your device's operating system map service (Apple or Google): only to find a place name when you choose to share a location in a chat (the lookup happens before the confirmation screen).
- App Store and Google Play: when you download the app, the store keeps its own download and crash data under its own responsibility; we do not process it.
- Competent authorities and child-protection organisations: if there is a legal request, or if we have a legal duty to report child abuse, to the extent the law allows and requires.
Transfers abroad
Because our company is established outside Türkiye and our infrastructure is abroad, all your personal data is processed outside Türkiye: our company in the USA, Supabase servers in Germany (Frankfurt), Resend in Ireland, and the notification services on Expo's and Google's infrastructure. While the photo check is in operation, your photos also go to the Frankfurt region of Amazon Web Services (Rekognition); the provider is a US-based company.
We aim to make these transfers under KVKK Article 9 (as amended by Law No. 7499): first an adequacy decision is looked for; if there is none, one of the appropriate safeguards is used, including the standard contract announced by the Board. When a standard contract is signed it is notified to the Personal Data Protection Authority within the period the Law sets. On top of that, we take your separate explicit consent to this transfer (Transfers Abroad Explicit Consent text); that consent is needed for the account, because our whole infrastructure is abroad.
You can read the details of the transfer in the Transfers Abroad Explicit Consent text as well.
Data retention and deletion
We keep your personal data as long as it is needed for the purpose it is processed for. The table below describes what the app does today. Where it says "automatic" the system deletes it; where it says "manual" our team does.
| Data | How long | Note |
|---|---|---|
| Account, profile and settings | Until you delete your account | When you delete your account your e-mail, profile and settings are deleted. |
| Likes (including sparks), passes, matches, invites, plans and meeting records | Until the match or your account is deleted | If you unmatch or block, the related records are deleted for both sides. Plans that run out are marked "expired" and the record stays until the match is deleted. |
| Ended-match marker | Until you delete your account | Two user ids and a time. It stops the same two people from matching again. |
| Messages, delivered and read times | As long as the match lasts | Deleted automatically for both sides if the match is removed or blocked. If you delete your account, all chats in your matches are deleted, including what the other person wrote. |
| Photos and voice notes sent in chat | With the message | When a match is removed, blocked or the account is deleted, the server deletes these files automatically; this usually takes a few minutes and is retried on error. Exception: files that a report copy (below) points to remain. |
| Profile photo files | Until you remove the photo or delete your account | When you remove a photo the app tries to delete the file. When you delete your account the server deletes all remaining files automatically. |
| Photo check record | Until you delete your account; failed-attempt records 7 days | File path, decision, time, number of attempts, label names and confidence scores. The image is not in the record. A rejected photo file is deleted automatically (usually within a few minutes). Amazon Web Services processes the photo only to analyse it. |
| Selfie file | Until the decision or 14 days | Deleted automatically on decision, cancellation, expiry after 14 days and account deletion. A selfie that was never sent is also deleted when the request closes. |
| Verification request record and badge | Until you delete your account | Not the selfie file itself; status, pose, times and consent version. The badge is removed if your first profile photo changes. |
| Report record | Until the reporter's or the reported person's account is deleted | If either party deletes their account, the report record is deleted as well. Exception: the chat copy saved at the time of a report and a child-safety suspicion (see the rows below). |
| Blocks | Until you delete your account | Deleted in both directions. |
| Chat copy kept after a report or a block | Not deleted automatically; manual deletion target about 180 days | Kept for safety review when a match ends because of a report, a block or inappropriate behaviour; only our team sees it. Deletion is manual and 180 days is a target, not a guarantee. The copy of the last 50 messages saved at the time of a report is kept here too. The copy contains the message text, a shared location and a record of media files; the files stay in storage while the copy exists. Deleting your account does not delete the copy; it only cuts the copy's link to your account, and the content may still identify you. |
| Records kept because of a child-safety suspicion | For as long as a legal retention duty or an investigation requires; we have not set a number of days | If there is a report or a reasonable suspicion of child sexual abuse or exploitation (CSAE, CSAM), the report record, the chat copy, account and profile data and the technical data we can reach may be kept longer than the normal deletion periods. Legal retention duties are reserved even if you delete your account. Copies handed to the competent authorities do not depend on our deletion periods. |
| E-mail hash of a banned account | No time limit set; until an authorised person removes it | A one-way scrambled form (hash) of the e-mail address, not the address itself. Kept so that the same address cannot sign up again. |
| Match-ending feedback | No period set | The reason and your note, if any. When you delete your account your user ids are removed from the record, and the record stays. A note you wrote may identify you. |
| Account deletion reason | No period set | Kept without your identity; it has no link to you. |
| Log of actions our team took | Manual deletion target about 2 years | The action, the account id and a short reason code; no personal text. Deletion is manual and 2 years is a target, not a guarantee. It can remain after you delete your account. |
| Notification token and notification queue | On sign-out or account deletion; queue 30 days | Tokens that become invalid are deleted after 30 days; sent or failed notification records are deleted after 30 days, automatically. |
| Usage events and venue records | Events 180 days, venue suggestion records 60 days, venue feedback signals 120 days | Deleted automatically by a nightly clean-up job. When you delete your account the identity link in events is removed. |
| Suggestion display log | 30 days | Deleted automatically; all of it is deleted when you delete your account. |
| Abuse-limiting counters | 2 days | Deleted automatically. |
| Banned-word filter records | 180 days | For a refused attempt: user id, category, source and time. The text is not stored. Deleted automatically. |
| Taste, availability, favourite venues, waiting list, suggestion preferences | Until you change them or delete your account | "Free tonight" switches off by itself at 04:00 the next morning (Istanbul time). |
| Profile details | Until you change them or delete your account | If you empty a field, that field is deleted. All of it is deleted when you delete your account. It is not copied into a report copy. |
| Meeting feedback | With the meeting record | Deleted if you unmatch or delete your account. A venue like is also kept as a venue signal (see the row above). |
| Consent records and consent history | Until you delete your account | This is the proof of consent. When you delete your account, your current consent records and the history of every grant and withdrawal are deleted. |
| Support and feedback messages | Until handled; 12 months after handling | Messages marked as handled are deleted after 12 months; ones not yet handled stay until handled. When you delete your account, your messages are deleted. |
| Technical server logs | The provider's own retention periods apply | Kept at our infrastructure provider. |
| Backups | The provider's own retention periods apply | Even after you delete your account, data may stay in backups for a while. |
| What stays on your phone | Until you delete the app or sign out | Unfinished sign-up details are deleted after 7 days. When you sign out the session closes; a list of accounts without passwords may remain on the phone, and when you delete your account it is removed from that list. Clearing the app's data removes everything. |
How do you delete your account?
You can delete your account yourself in the app:
- Go to Settings > Delete account.
- If you prefer, you can choose to become invisible in discovery instead of deleting.
- Pick a reason. The reason is not written to your account; it stays anonymous.
- Type your password and confirm. This cannot be undone.
- If you cannot sign in, you can also ask for deletion by e-mail using the steps on b4drink.app/hesap-silme.
What happens and what stays when you delete your account
Deleted: your profile, e-mail address, likes (including sparks), matches, all chats in your matches (including what the other person wrote), invites and plans, taste, availability and favourite venue answers, profile details (including your about-me text), meeting feedback, suggestion preferences and logs, notification tokens and preferences, waiting list records, verification requests, photo check records, consent records and consent history, the usage allowance record set for your account, and the messages you sent through the support and feedback form. The profile photo, chat photo, voice note and selfie files you uploaded are deleted automatically through the server's clean-up queue.
What stays: the account deletion reason and match-ending feedback (with their link to your identity removed), usage events with the identity removed, the log of actions our team took (action, account id, short reason code; deleted manually, target about 2 years), chat copies kept after a report or a block and the files they point to (see the table above), records that may be kept because of a child-safety suspicion under a legal retention duty or an investigation, the e-mail hash of a banned account, and Supabase's own logs and backups.
Unmatching, blocking and reporting
If you unmatch, the chat messages and the files sent are deleted for both sides and you will not match again. The other person does not see who ended it or why.
If you block, you cannot see each other and the match and chat are deleted. When you block, a copy of the chat is kept separately for safety review. When you report, the reason you pick is recorded. A chat copy is also kept when a match ends because of a report or inappropriate behaviour. When you report, a copy of the last 50 messages of that chat (text and file records) is saved as evidence. It may stay even if an account is deleted, as far as a legal duty or an investigation requires; it is used only to review the report and, when required, to give to the competent authorities. How copies are kept is described in the table above.
If an account is banned, a one-way scrambled form (hash) of its e-mail address is kept so that it cannot sign up again; the e-mail address itself is not kept for this purpose.
Notifications and communication
We send you only messages about the service: app notifications such as matches, messages and plans, e-mails about your account and support replies. We take a separate explicit consent for app notifications (Notifications Explicit Consent text); you can turn notifications off in Settings > Security and privacy > My consents, in Settings > Notifications or in your operating system settings.
We do not currently send marketing e-mails or advertising notifications. If we ever do, we will ask for your permission first and give you a way to opt out at any time.
E-mail waitlist on the website
If you join the waitlist on b4drink.app, we store only your e-mail address, the site language you used (Turkish or English), the path of the page that held the form, and the time you signed up. This list is separate from the district waitlist in the app and is not linked to any account. We use your address only to e-mail you when the app is released; we do not use it for anything else and do not share it with anyone. We do not send you an e-mail when you sign up.
The legal basis is your explicit consent, which you give by submitting the form with your e-mail address. We do not store your IP address in clear. To limit abuse we keep an irreversible hash made from the IP address; hashes older than one day are deleted. The records are held with our infrastructure providers Supabase (database) and Vercel (hosting); their servers may be outside Turkey.
The list is deleted within 3 months after the launch announcement e-mail has been sent. To have your address deleted earlier, or to withdraw your consent, write to privacy@b4drink.app from the address you signed up with. We complete deletion requests within 30 days at the latest.
The 18+ age limit
B4Drink is only for people aged 18 and over. We ask for your date of birth when you sign up and do not accept the sign-up if you are under 18. Our server also does not store a date of birth under 18. Still, the date of birth is self-declared; we do not check ID documents.
If we learn that someone under 18 has an account, we close it and carry out the deletion of their data manually. If there is a suspicion of child abuse or exploitation, the records may not be deleted, as described in the next section. You can report such a case to privacy@b4drink.app; the ways to report are in the "Child safety standards" section of the Community Guidelines.
Child safety and legal duties
We have zero tolerance for child sexual abuse and exploitation (CSAE) and child sexual abuse material (CSAM). When there is a report or a reasonable suspicion, we process the following data to protect children and prevent crime, based on our legal obligations and our legitimate interest: the reported content and the report record, the chat copy (message text, shared location, a record of media files), account and profile data (e-mail, name, date of birth, photos) and the technical data we can reach.
We may keep this data longer than the normal deletion periods, and even if you delete your account, for as long as a legal retention duty or an investigation by the competent authorities requires. Legal retention duties are reserved. We do not give a number of days; the period is as long as the law and the investigation require.
We share this data only as far as needed and as far as the applicable laws require, with the competent law-enforcement and judicial authorities (in Türkiye, the public prosecutor) and with child-protection organisations; we do not share it with other users or third parties. Our team looks at this content only for review and legal duties.
Our automated systems are not designed for this purpose: the word filter catches only some expressions, and photo moderation (if it is switched on) is not designed to detect child abuse material. That is why we rely on reports.
Security
We apply the following measures to protect your data. No system is entirely free of risk.
- Connections between the app and the server are encrypted with TLS.
- Row-level security (RLS) is on for database tables. Other users' profiles cannot be read directly; they are seen only through server functions that return limited fields.
- The feedback, support feedback, consent and consent history, report, report copy, event, meeting feedback, verification request and profile details tables cannot be read directly from the app. You write your profile details only through server functions that work on your own row. Other people's profile details and meeting taste are read only through the profile-page function, for people allowed by the match, like or discover rules, and only as a limited set of fields.
- Passwords are stored by Supabase Auth with bcrypt. The app contains no admin key.
- Chat photos, voice notes and selfie files are kept in private storage. Chat files are opened only through short-lived signed links; only our team can open a selfie. Profile photos are reachable through public links (see above).
- The 18+ check on the date of birth is also made on the server.
How do you use your rights?
Under KVKK Article 11 you have rights such as learning whether your data is processed, asking for information, correction, deletion or destruction, objecting and asking for compensation. The full list of your rights and how to apply are in the KVKK Notice. You can write to privacy@b4drink.app.
The easiest way to delete your data is Settings > Delete account.
Changes
We may update this text. We will tell you in the app about important changes. The current version and date are at the top of this page.
If the English and Turkish versions differ, the Turkish version applies.
Contact
Privacy and KVKK requests: privacy@b4drink.app. Support: support@b4drink.app. Legal matters: legal@b4drink.app.
Company: B4 Labs LLC, a Missouri LLC (registry no. LC014786788), 117 S Lexington St Ste 100, Harrisonville, MO 64701, USA.

