1. Account and sign-in information
When you create a Coff account, we process your first name, last name, email, phone number (optional; only if you give it), a secure hash of your password, your account role, email verification status, account status and account creation date. For sign-in, email verification and password reset, we may keep temporary verification records and token hashes.
2. Profile and preference information
When you complete your profile, we may store profile details such as your date of birth, age, city, district, gender, bio, education, university, work status, industry, social coffee intention, interests, availability, coffee preferences and favorite coffee spot. Coff does not filter discovery by gender, and it does not collect sexual orientation or draw conclusions about it.
Coff is not for anyone under 18 and does not knowingly collect data from people under 18. You declare your date of birth when you sign up; it cannot be changed in the app later, and the age requirement is applied based on it. You can report a user as Under 18; accounts found to belong to someone under 18 are closed and their data is cleared under the account deletion rules.
3. Profile photos and verification
If you upload a profile photo, we process the photo, its link, storage key, provider details, crop settings, upload time, moderation status and, if any, the moderation reason. Uploaded photos may go through an automatic pre-screening before they are published; for this, the photo is sent to a content safety service provider. This screening alone never leads to a rejection; it can only send the photo to review. Photos may also be reviewed by an authorized team member for inappropriate content, fake profiles or safety reasons. Photos that are not approved may not be visible to other users.
4. Location, coffee spots and check-ins
When you give location permission, Coff may use your location to show coffee spots nearby, create coffee check-ins and let you discover coffee activity near you. For check-ins at a café, the chosen spot's name, address, source, city, district and coordinates may be saved. For home, office or other types of coffee logs, an approximated device location may be used instead of your exact location. When you log a coffee, we may store the coffee type, note, time, the visibility you chose and the limited usage information needed to calculate popular coffees around you. For coffee logs you share with “Everyone”, the coffee type, the time of day and, for café check-ins, the spot and its approximate area may also be used to calculate compatibility scores and decide who is shown first in Discover. Logs set to “Only me” or “My connections”, your notes, and the location of home, office or other logs are never used for this, and the spot history used this way is not shown to other users.
Your connections see only the coffee type and the day of the coffee logs you share with “My connections” or “Everyone”, on the app’s Today screen (the place, location and time are not shown there); an invite link shows the inviter’s first name, and nothing else, to anyone who opens it. If you chose your university on your profile, the weekly campus number on the Today screen counts the people of the same university who logged a coffee this week, whatever the coffee’s sharing setting; it is only ever shown as a total of at least 10 people, and nobody is shown individually.
5. Messages and connections
The Coff team does not review your private messages under normal circumstances. If a user reports someone for safety, abuse or inappropriate content, an authorized team member may review limited message evidence related to that report.
The Coff team does not routinely browse live chats or read private messages for general monitoring. Message content, sender, connection, creation time and read status are stored to run the chat feature and are kept encrypted in the database. What may be reviewed after a report is a frozen slice of evidence limited to that safety request. Information such as compatibility score, candidate actions like liking or passing, connection status and the last-message preview may also be processed to run the product.
When you remove a connection, the message content and preview of that chat are deleted automatically 30 days after the removal date; the connection itself (who was connected with whom) may be kept separately for safety and abuse tracking. Messages in an active (not ended) chat are not subject to this automatic deletion.
6. Notifications and device information
If you turn on notifications, your device notification token, platform, app package details, active status and last-seen time may be stored to send notifications such as connections, messages, photo approval or reminders. This token is linked to your account and is used only to provide the notification service.
7. Reports, blocking and moderation
When you report or block a user, the action may be stored together with the report reason, description, the users involved, the time of the action, the report status, notes by the authorized team and the limited evidence needed for a safety review. Authorized administrators can review reports and take actions on content or accounts such as a warning, a review, a suspension or closing the account.
8. Service providers
Coff uses third-party infrastructure providers for sending email, notifications, verifying subscription and purchase status, map and place search, photo storage, automatic photo pre-screening, server hosting and content delivery. Your notification token is sent to the notification provider for this purpose, and your subscription status is sent to the subscription provider only to verify purchases. These providers process only the technical data needed to provide the service. Our current main providers:
- Railway (US company; servers in the European Union, the Netherlands): app server, database and backup job.
- Cloudflare (US): domain, secure content delivery, storage of profile photos and encrypted database backups.
- Resend (US): verification and password reset emails.
- Sentry (US company; data in its European Union region): error and performance records.
- RevenueCat (US): verifying subscription status.
- OpenAI (US): automatic pre-screening of profile photos; photos are not used to train the provider's models.
- Google (US): Android notifications (Firebase Cloud Messaging), maps and place search.
- Apple (US): iPhone notifications and maps.
- GitHub (US): the automated job that takes a second copy of the database backup, and the weekly restore test from backup.
For purchases through the App Store and Google Play, your payment details are processed by Apple or Google under their own privacy policies; Coff does not receive payment card details. Because these providers' systems are outside Turkey, your personal data is transferred abroad; the legal framework for this transfer is explained in section 6 of the KVKK Privacy Notice. We currently do not add external tracking or advertising analytics to this public website.
9. Analytics, logs and error records
Product analytics are processed from the moment you sign in to your account, without a separate consent request. This is not tracking for advertising or marketing; it is processing based on legitimate interest that is needed to run and improve the service itself. You can read how these records are separated from direct identity information when you delete your account in section 10 below, and how to use your right to object in the data subject rights in the KVKK Privacy Notice.
Coff processes limited product usage information to understand how the connection and discovery flow works, detect empty results and problems users run into, measure the subscription flow and improve the service. This may include events such as a screen or state being shown, the position of a discovery card, the search area being widened and the steps in the subscription flow, with a limited, predefined context for each. The extra fields of product analytics events do not store information that directly identifies other users.
Product analytics records may be linked to Coff's internal user number. When an account is deleted, direct identity and contact details such as name, email and phone are removed from the account record tied to that internal number; limited analytics events may stay linked to the same internal number so we can evaluate user journeys, the connection funnel and why people leave the service. These records are not fully anonymous; they are not used to rebuild the deleted profile or to contact the user, and they are evaluated only through authorized access for product and service analysis.
When you sign up, the app stores with your account a short label showing which channel the install came from (for example an Instagram link, a printed QR code or an Apple Ads campaign number). The label is read from Google Play’s install record or Apple’s ad attribution service; it contains no advertising ID, device ID or location, and is not used for ad targeting or cross-app tracking. It is evaluated only in aggregate, to understand which channels bring people who actually use the app.
Coff may also process limited technical data such as IP address, request time, app or device version, errors, crashes and performance information for security, abuse prevention, troubleshooting and keeping the service stable. Crash/performance and subscription infrastructure providers may be used for these purposes. We do not use this data for ad targeting, cross-app tracking or selling data.
Because Coff hosts the profiles, photos and messages its users share, it is a hosting provider under Turkey's Law No. 5651 on the Regulation of Internet Broadcasts. Under this law, we keep traffic data showing which account used the service from which IP address, on which day and in which time range, for 1 year. These records are kept for this period even if the account is deleted, are used only for proper requests from the competent authorities and for safety reviews, and are deleted when the period ends.
10. Account deletion and data retention
Account and profile data are kept while your account is active and as long as they are needed to provide Coff's services. When you delete your account, it is closed; the real values of direct contact and identity details such as name, email and phone are removed from the system, and your old password becomes invalid. Profile content such as date of birth, city, bio, interests and discovery distance is cleared; your profile photo, its storage and processing details, coffee preferences, favorite spots, personal check-ins and device notification tokens are deleted. The content of messages you sent is replaced in the chat record with a deleted-message notice, and the last-message previews and sender details in chat lists are cleared.
Some limited records may be kept after an account is deleted. These may include block and report records kept to protect users and prevent abuse, limited evidence frozen at the time of a report, relationship records needed to keep other users' connection and chat history intact, limited candidate action and product analytics records kept to evaluate product and connection performance, invalidated session records until they expire, and records needed to verify legal, financial or subscription transactions. These records may stay linked to an internal record number stripped of direct contact details; for this reason we do not describe them as fully anonymous.
These records are kept only as long as needed for their purpose. The period is set per data category, taking into account the nature of the data, the risk to safety and of abuse, how long the technical record stays valid, possible legal claims and applicable legal obligations. When the purpose ends and no other reason to keep it remains, the record is deleted or made impossible to link to a person. The periods set so far:
- Message content of an ended connection: deleted 30 days after it ends.
- Message evidence frozen at the time of a report: deleted 60 days after the report is reviewed; the report itself (who reported whom, for what reason) stays as a safety record.
- The email hash of a deleted account: 7 days.
- Traffic data under Law No. 5651: 1 year.
- Database backups: at most 30 days, encrypted where they are stored. A deleted account's data may remain in backups until this period ends; backups are used only to restore the system.
When an account is deleted, its email address is removed from the account. To prevent the same address from immediately opening and closing new accounts, we keep only an irreversible hash of the address, produced with a secret server-side key, in a separate record for 7 days, not the address itself. This hash cannot be turned back into the email address, is not used for notifications or contact, and the record is deleted completely when the period ends. If someone tries to sign up with the same address during this period, they are told how long they need to wait.
11. Deleting your account
You can delete your account inside the app. From the menu on the profile screen, go to Account security and choose Delete account. If you need help, follow the steps on the Account Deletion page or write to the support team.
12. Contact
For privacy requests and questions, reach us at destek@coffcircle.com. For requests under the KVKK, use kvkk@coffcircle.com and the methods in the KVKK Privacy Notice.
This English version is a translation for your convenience. If it differs from the Turkish version, the Turkish version applies.