This notice explains in plain language who processes your personal data in the Foodbudy mobile app, for what purpose, by what method and on what legal ground, to whom it may be transferred, and what rights you have. It is a disclosure notice, not a consent form. (Weight and measurement data, public sharing on Explore and sending photos in chat each have a separate explicit-consent text: Explicit consent for weight and measurements, Explicit consent for Explore sharing, Explicit consent for chat photos.) For visitors to the website see “Website visitors” in the Privacy Policy.
The Turkish text is the primary draft; which language prevails is for the lawyer to decide.
1. Data controller
| Brand | Foodbudy is a venture of Codeativ. |
|---|---|
| Legal name | [ŞİRKET UNVANI — TAM TÜZEL KİŞİLİK ADI] |
| Trade registry (MERSİS) no. | [MERSİS NO] |
| Address | [ADRES] |
| Registered e-mail (KEP) | [KEP ADRESİ] |
| info@codeativ.com |
- Brand
- Foodbudy is a venture of Codeativ.
- Legal name
- [ŞİRKET UNVANI — TAM TÜZEL KİŞİLİK ADI]
- Trade registry (MERSİS) no.
- [MERSİS NO]
- Address
- [ADRES]
- Registered e-mail (KEP)
- [KEP ADRESİ]
- info@codeativ.com
2. Which personal data do we process?
| Category | Data | How collected | Purpose | Legal ground (suggested) |
|---|---|---|---|---|
| Account | E-mail, account ID, sign-in method (e-mail / Google / Apple) | You enter it, or it comes from the sign-in provider | Creating the account, authentication | Performance of a contract (Art. 5/2-c) |
| Profile | Display name (we do not ask for a surname), optional profile photo, goal, diet style, language, time zone, birth year, gender, matching preferences (age range, gender preference) | You enter it during onboarding | Buddy suggestions, enforcing the 18+ rule, app language and day calculation | Performance of a contract (Art. 5/2-c); age check: [lawyer to decide: legitimate interest / legal obligation] |
| Meal content | Meal photo (location/EXIF data is removed on the server), meal type, optional short note, reactions, comments | You share it | Shared feed and shared streak with your buddy | Performance of a contract (Art. 5/2-c) |
| Explore post (optional, public) | The photo of the meal you choose to share on Explore (a copy with location/EXIF data removed), meal type, an optional short note (up to 140 characters), your display name and avatar | Only if you choose “Also share on Explore”; no meal reaches Explore without your separate explicit consent | Showing the meal you shared to all Foodbudy users; automatic screening of the photo for inappropriate content before publication; reviewing reports | Explicit consent (Art. 5/1), separate text: Explore sharing consent; legitimate interest (Art. 5/2-f) for the automatic screening [AVUKAT ONAYI BEKLENİYOR: a single legal basis must be chosen for the screening (explicit consent or legitimate interest); because the Vision transfer is systematic, the Art. 9 basis (standard contract + notification to the Authority) is to be determined] |
| Dietary preferences (allergies/diet restrictions; may be special category) | The allergens you select (the 14 EU allergens), lactose intolerance and vegetarian/vegan preferences | Stored only on this device; NOT sent to our servers, third parties, your buddies, logs or crash reports. Not part of your account profile or device backups. Deleted from the device when you sign out, when your session ends and when you delete your account; if you switch devices you enter it again | Letting the app on your device show, locally, which items in general diet programmes overlap with your preferences and “if you don't have this, eat this” alternatives | Foodbudy does not process or collect this information (only the app on your device uses it locally), so no separate processing ground arises [AVUKAT ONAYI BEKLENİYOR: whether data that stays on the device counts as “processing”; whether this row should be removed from the table and moved into the “Data we do not process” paragraph] |
| Messaging | The message text you exchange with your buddy, sent and read times (“seen” status) | You write it | One-to-one messaging with your matched buddy; reviewing messages that are reported | Performance of a contract (Art. 5/2-c); legitimate interest for report review (Art. 5/2-f) [lawyer to confirm] |
| Chat photo (optional) | The photo you send in chat (a re-encoded copy with location/EXIF metadata removed), sent time; screening result (accepted/rejected) | Only if you send one; no photo can be sent without your separate explicit consent (text chat is unaffected) | Delivering it to your match; screening it with Google Cloud Vision (SafeSearch) before delivery against unlawful or abusive content; reviewing reports. A rejected photo is not delivered; if 3 photos are rejected within 24 hours, sending is paused for up to 24 hours | Delivering it to your match: performance of a contract (Art. 5/2-c). Reviewing reports: legitimate interest (Art. 5/2-f) [lawyer to confirm]. Screening with Google Cloud Vision and the cross-border transfer: explicit consent (Art. 5/1), separate text: chat photo consent; legal ground and Art. 9 basis for the screening [AVUKAT ONAYI BEKLENİYOR: same assessment as the Explore screening; because the transfer is systematic, under Art. 9 explicit consent can be a basis only for incidental transfers, so a standard contract + notification to the Authority is to be determined; if the transfer is to rest on consent, the “Consent” sentence in the consent text must also cover the transfer and its risks (requires a chat_media_scanning version bump)]; rejected photo record (user ID and time) and 24-hour pause count: legitimate interest in preventing abuse (Art. 5/2-f) [lawyer to confirm] |
| Session and real-time connection | Session record (valid 90 days), connection metadata (time, session, IP address); re-authentication record on account deletion; a pseudonymised deletion record for every account deletion (and verification for deletion by e-mail) | Automatic / you initiate it | Keeping you signed in and chat real-time, account security, deletion by e-mail for suspended accounts | Performance of a contract (Art. 5/2-c); legitimate interest for security (Art. 5/2-f). The real-time connection adds no new data category |
| Matching and safety | Invite codes, match records (who, status, dates), block and report records | Generated by using the app | Providing the service, preventing abuse, community safety | Legitimate interest (Art. 5/2-f); legal obligation where required (Art. 5/2-ç) |
| Health (special category) | Weight and body-measurement entries (waist, hips, chest), date, visibility choice | Only if you record them; nothing is recorded without your separate explicit consent | Personal progress chart; sharing with your buddy only if you choose | Explicit consent (Art. 6/2) — separate text: weight/measurements consent [AVUKAT ONAYI BEKLENİYOR: after the 2024 amendment, whether the explicit-consent basis for special-category data should be cited as Art. 6/3-a] |
| Consent records | Which text, which version, when you accepted / withdrew | Created when you consent | Being able to prove what you consented to | Legal obligation / legitimate interest [lawyer to confirm] |
| Notifications | Push token, platform; your notification preferences and evening reminder time | If you grant notification permission | “Buddy posted”, “new comment”, “new message” and reminder notifications. Message notifications never contain the message text (you only get a text-free notice such as “… sent you a message”) | Performance of a contract; your permission and preferences |
| Technical and crash | Crash reports, device model and OS version | Automatic; you can turn crash reports off inside the app (on by default) | Monitoring stability and fixing bugs | Legitimate interest (Art. 5/2-f) |
| Membership (only if paid membership is launched) | Subscription status | Via the store purchase system | Providing membership benefits | Performance of a contract |
- Category
- Account
- Data
- E-mail, account ID, sign-in method (e-mail / Google / Apple)
- How collected
- You enter it, or it comes from the sign-in provider
- Purpose
- Creating the account, authentication
- Legal ground (suggested)
- Performance of a contract (Art. 5/2-c)
- Category
- Profile
- Data
- Display name (we do not ask for a surname), optional profile photo, goal, diet style, language, time zone, birth year, gender, matching preferences (age range, gender preference)
- How collected
- You enter it during onboarding
- Purpose
- Buddy suggestions, enforcing the 18+ rule, app language and day calculation
- Legal ground (suggested)
- Performance of a contract (Art. 5/2-c); age check: [lawyer to decide: legitimate interest / legal obligation]
- Category
- Meal content
- Data
- Meal photo (location/EXIF data is removed on the server), meal type, optional short note, reactions, comments
- How collected
- You share it
- Purpose
- Shared feed and shared streak with your buddy
- Legal ground (suggested)
- Performance of a contract (Art. 5/2-c)
- Category
- Explore post (optional, public)
- Data
- The photo of the meal you choose to share on Explore (a copy with location/EXIF data removed), meal type, an optional short note (up to 140 characters), your display name and avatar
- How collected
- Only if you choose “Also share on Explore”; no meal reaches Explore without your separate explicit consent
- Purpose
- Showing the meal you shared to all Foodbudy users; automatic screening of the photo for inappropriate content before publication; reviewing reports
- Legal ground (suggested)
- Explicit consent (Art. 5/1), separate text: Explore sharing consent; legitimate interest (Art. 5/2-f) for the automatic screening [AVUKAT ONAYI BEKLENİYOR: a single legal basis must be chosen for the screening (explicit consent or legitimate interest); because the Vision transfer is systematic, the Art. 9 basis (standard contract + notification to the Authority) is to be determined]
- Category
- Dietary preferences (allergies/diet restrictions; may be special category)
- Data
- The allergens you select (the 14 EU allergens), lactose intolerance and vegetarian/vegan preferences
- How collected
- Stored only on this device; NOT sent to our servers, third parties, your buddies, logs or crash reports. Not part of your account profile or device backups. Deleted from the device when you sign out, when your session ends and when you delete your account; if you switch devices you enter it again
- Purpose
- Letting the app on your device show, locally, which items in general diet programmes overlap with your preferences and “if you don't have this, eat this” alternatives
- Legal ground (suggested)
- Foodbudy does not process or collect this information (only the app on your device uses it locally), so no separate processing ground arises [AVUKAT ONAYI BEKLENİYOR: whether data that stays on the device counts as “processing”; whether this row should be removed from the table and moved into the “Data we do not process” paragraph]
- Category
- Messaging
- Data
- The message text you exchange with your buddy, sent and read times (“seen” status)
- How collected
- You write it
- Purpose
- One-to-one messaging with your matched buddy; reviewing messages that are reported
- Legal ground (suggested)
- Performance of a contract (Art. 5/2-c); legitimate interest for report review (Art. 5/2-f) [lawyer to confirm]
- Category
- Chat photo (optional)
- Data
- The photo you send in chat (a re-encoded copy with location/EXIF metadata removed), sent time; screening result (accepted/rejected)
- How collected
- Only if you send one; no photo can be sent without your separate explicit consent (text chat is unaffected)
- Purpose
- Delivering it to your match; screening it with Google Cloud Vision (SafeSearch) before delivery against unlawful or abusive content; reviewing reports. A rejected photo is not delivered; if 3 photos are rejected within 24 hours, sending is paused for up to 24 hours
- Legal ground (suggested)
- Delivering it to your match: performance of a contract (Art. 5/2-c). Reviewing reports: legitimate interest (Art. 5/2-f) [lawyer to confirm]. Screening with Google Cloud Vision and the cross-border transfer: explicit consent (Art. 5/1), separate text: chat photo consent; legal ground and Art. 9 basis for the screening [AVUKAT ONAYI BEKLENİYOR: same assessment as the Explore screening; because the transfer is systematic, under Art. 9 explicit consent can be a basis only for incidental transfers, so a standard contract + notification to the Authority is to be determined; if the transfer is to rest on consent, the “Consent” sentence in the consent text must also cover the transfer and its risks (requires a chat_media_scanning version bump)]; rejected photo record (user ID and time) and 24-hour pause count: legitimate interest in preventing abuse (Art. 5/2-f) [lawyer to confirm]
- Category
- Session and real-time connection
- Data
- Session record (valid 90 days), connection metadata (time, session, IP address); re-authentication record on account deletion; a pseudonymised deletion record for every account deletion (and verification for deletion by e-mail)
- How collected
- Automatic / you initiate it
- Purpose
- Keeping you signed in and chat real-time, account security, deletion by e-mail for suspended accounts
- Legal ground (suggested)
- Performance of a contract (Art. 5/2-c); legitimate interest for security (Art. 5/2-f). The real-time connection adds no new data category
- Category
- Matching and safety
- Data
- Invite codes, match records (who, status, dates), block and report records
- How collected
- Generated by using the app
- Purpose
- Providing the service, preventing abuse, community safety
- Legal ground (suggested)
- Legitimate interest (Art. 5/2-f); legal obligation where required (Art. 5/2-ç)
- Category
- Health (special category)
- Data
- Weight and body-measurement entries (waist, hips, chest), date, visibility choice
- How collected
- Only if you record them; nothing is recorded without your separate explicit consent
- Purpose
- Personal progress chart; sharing with your buddy only if you choose
- Legal ground (suggested)
- Explicit consent (Art. 6/2) — separate text: weight/measurements consent [AVUKAT ONAYI BEKLENİYOR: after the 2024 amendment, whether the explicit-consent basis for special-category data should be cited as Art. 6/3-a]
- Category
- Consent records
- Data
- Which text, which version, when you accepted / withdrew
- How collected
- Created when you consent
- Purpose
- Being able to prove what you consented to
- Legal ground (suggested)
- Legal obligation / legitimate interest [lawyer to confirm]
- Category
- Notifications
- Data
- Push token, platform; your notification preferences and evening reminder time
- How collected
- If you grant notification permission
- Purpose
- “Buddy posted”, “new comment”, “new message” and reminder notifications. Message notifications never contain the message text (you only get a text-free notice such as “… sent you a message”)
- Legal ground (suggested)
- Performance of a contract; your permission and preferences
- Category
- Technical and crash
- Data
- Crash reports, device model and OS version
- How collected
- Automatic; you can turn crash reports off inside the app (on by default)
- Purpose
- Monitoring stability and fixing bugs
- Legal ground (suggested)
- Legitimate interest (Art. 5/2-f)
- Category
- Membership (only if paid membership is launched)
- Data
- Subscription status
- How collected
- Via the store purchase system
- Purpose
- Providing membership benefits
- Legal ground (suggested)
- Performance of a contract
Data we do not process: phone number, location, contacts, advertising ID, energy or nutrition values; your allergies and dietary preferences are not processed on our servers either (they stay on your device). We do not ask you for a surname; only if you sign in with Google or Apple, the name the provider shares may be stored when your account is created. Your personal data is not used for advertising and is not processed for tracking.
Diet programmes and alternatives: these are general meal templates prepared by Codeativ, the same for everyone; they are not a personal diet list. Your allergy/dietary preferences are not sent to the server when the content is downloaded; the fit information is computed on your device. A “No overlapping items found” result is not a guarantee of suitability. For general information only; not medical advice.
3. Purposes (summary)
Managing your account; matching you with suitable adults (18+); providing meal sharing, shared feed, reactions, comments, messaging with your buddy and shared streak; letting you share meals publicly on Explore if you choose and screening shared photos for inappropriate content; showing your personal progress if you choose; sending notifications; handling reports and blocks to keep the community safe; keeping the app stable; meeting legal obligations.
4. To whom may data be transferred?
| Recipient group | Purpose | Outside Türkiye? |
|---|---|---|
| Your matched buddy | Core function: your name, avatar, goal, diet style, language, time zone, and the meals, reactions and comments you share. Your weight/measurement entries are visible only if you set an entry to “buddies can see” and your consent is active. Messages and chat photos are visible only to the two sides of the match (while it is active); no third user can see them. | — |
| All Foodbudy users (only if you choose to share on Explore) | The photo, note, display name and (if it passed screening) avatar of that meal. Your surname, email, birth year, gender, time zone and location are not shown; people who blocked you or whom you blocked do not see the post. You can withdraw a post at any time. | — |
| Google (Cloud Vision) — screening your photo (and avatar) for inappropriate content (SafeSearch) BEFORE it is shared on Explore | The image is sent to Google only for this screening (with location data removed); Google's EU endpoint is used [official confirmation that data does not leave the EU is pending; “stays in the EU” will not be claimed without it]. If the scan cannot be done, the post is not published. Transfer under KVKK Art. 9 (lawyer approval pending) [AVUKAT ONAYI BEKLENİYOR: after the 2024 amendment to Art. 9, explicit consent alone may not be sufficient; the basis for the systematic Vision transfer (standard contract + notification to the Authority) and a single legal basis for the screening (explicit consent or legitimate interest) are to be determined]. | Yes (may be outside Türkiye) |
| Google (Cloud Vision) — screening a photo BEFORE it is sent in chat for unlawful or abusive content (SafeSearch); only if you gave the chat photo consent | Only the re-encoded image, with location/EXIF metadata removed, is sent to Google; Google's EU endpoint is used where configured [official confirmation that the data does not leave the EU is to be obtained]. Retention at Google is governed by Google's terms. If the screening cannot be done, the photo is not delivered. Screening serves only to block unlawful or abusive content. This transfer falls under KVKK Art. 9 [AVUKAT ONAYI BEKLENİYOR: same basis and safeguards as the Explore screening]. | Yes (may be outside Türkiye) |
| The Foodbudy team (moderation) | If you report a message (or a meal/comment/Explore post), the content concerned — including the message text — may be viewed manually by our team so that the report can be reviewed. Every new report also triggers an automatic notification e-mail to the info@codeativ.com mailbox; that e-mail contains NO identity or name of you or the other person and none of the reported content (only the report number, type, reason and the deadline for action). Reports are acted on within 24 hours. Reports and blocks are not disclosed to the other person. [Who reviews, in which roles, and the access rules are to be defined by the business.] | — |
| Infrastructure providers (data processors): Railway (server and database hosting), Cloudflare R2 (file storage) and [E-POSTA SAĞLAYICISI] (verification and password-reset codes sent by e-mail, and report notifications that contain no identity) | Hosting the service, storing files and sending e-mails | Region: [VERİ BÖLGESİ] — a transfer abroad if outside Türkiye |
| Google (Firebase) — push notifications (FCM) and crash reports (Crashlytics); Sign in with Google | Notification delivery, error monitoring, sign-in | Yes |
| Apple — push notifications (APNs), Sign in with Apple | Notification delivery, sign-in | Yes |
| RevenueCat — only if paid membership is launched | Subscription management | Yes [to be confirmed before launch] |
| Competent authorities | Obligations under legislation | — |
- Recipient group
- Your matched buddy
- Purpose
- Core function: your name, avatar, goal, diet style, language, time zone, and the meals, reactions and comments you share. Your weight/measurement entries are visible only if you set an entry to “buddies can see” and your consent is active. Messages and chat photos are visible only to the two sides of the match (while it is active); no third user can see them.
- Outside Türkiye?
- —
- Recipient group
- All Foodbudy users (only if you choose to share on Explore)
- Purpose
- The photo, note, display name and (if it passed screening) avatar of that meal. Your surname, email, birth year, gender, time zone and location are not shown; people who blocked you or whom you blocked do not see the post. You can withdraw a post at any time.
- Outside Türkiye?
- —
- Recipient group
- Google (Cloud Vision) — screening your photo (and avatar) for inappropriate content (SafeSearch) BEFORE it is shared on Explore
- Purpose
- The image is sent to Google only for this screening (with location data removed); Google's EU endpoint is used [official confirmation that data does not leave the EU is pending; “stays in the EU” will not be claimed without it]. If the scan cannot be done, the post is not published. Transfer under KVKK Art. 9 (lawyer approval pending) [AVUKAT ONAYI BEKLENİYOR: after the 2024 amendment to Art. 9, explicit consent alone may not be sufficient; the basis for the systematic Vision transfer (standard contract + notification to the Authority) and a single legal basis for the screening (explicit consent or legitimate interest) are to be determined].
- Outside Türkiye?
- Yes (may be outside Türkiye)
- Recipient group
- Google (Cloud Vision) — screening a photo BEFORE it is sent in chat for unlawful or abusive content (SafeSearch); only if you gave the chat photo consent
- Purpose
- Only the re-encoded image, with location/EXIF metadata removed, is sent to Google; Google's EU endpoint is used where configured [official confirmation that the data does not leave the EU is to be obtained]. Retention at Google is governed by Google's terms. If the screening cannot be done, the photo is not delivered. Screening serves only to block unlawful or abusive content. This transfer falls under KVKK Art. 9 [AVUKAT ONAYI BEKLENİYOR: same basis and safeguards as the Explore screening].
- Outside Türkiye?
- Yes (may be outside Türkiye)
- Recipient group
- The Foodbudy team (moderation)
- Purpose
- If you report a message (or a meal/comment/Explore post), the content concerned — including the message text — may be viewed manually by our team so that the report can be reviewed. Every new report also triggers an automatic notification e-mail to the info@codeativ.com mailbox; that e-mail contains NO identity or name of you or the other person and none of the reported content (only the report number, type, reason and the deadline for action). Reports are acted on within 24 hours. Reports and blocks are not disclosed to the other person. [Who reviews, in which roles, and the access rules are to be defined by the business.]
- Outside Türkiye?
- —
- Recipient group
- Infrastructure providers (data processors): Railway (server and database hosting), Cloudflare R2 (file storage) and [E-POSTA SAĞLAYICISI] (verification and password-reset codes sent by e-mail, and report notifications that contain no identity)
- Purpose
- Hosting the service, storing files and sending e-mails
- Outside Türkiye?
- Region: [VERİ BÖLGESİ] — a transfer abroad if outside Türkiye
- Recipient group
- Google (Firebase) — push notifications (FCM) and crash reports (Crashlytics); Sign in with Google
- Purpose
- Notification delivery, error monitoring, sign-in
- Outside Türkiye?
- Yes
- Recipient group
- Apple — push notifications (APNs), Sign in with Apple
- Purpose
- Notification delivery, sign-in
- Outside Türkiye?
- Yes
- Recipient group
- RevenueCat — only if paid membership is launched
- Purpose
- Subscription management
- Outside Türkiye?
- Yes [to be confirmed before launch]
- Recipient group
- Competent authorities
- Purpose
- Obligations under legislation
- Outside Türkiye?
- —
Transfers abroad (KVKK Art. 9): the basis for transfers to the recipients above is [compliance/lawyer to determine: adequacy decision / appropriate safeguards (e.g. standard contract with notification to the Authority) / explicit consent only for incidental transfers]. For the systematic image transfer to Google Cloud Vision, the chat photo explicit consent (Art. 5/1) is envisaged as the basis [AVUKAT ONAYI BEKLENİYOR: explicit consent can be a basis only for incidental transfers; because the transfer is systematic, a standard contract + notification to the Authority is to be determined]. The version of Art. 9 amended in 2024 and current Board decisions must be checked by a lawyer. We do not sell your personal data.
5. Retention
| Data | Period |
|---|---|
| Account, profile, meal content, matches, progress entries | While your account is open. When you choose “Delete account” in the app, your account and related data (including photos you uploaded) are deleted. |
| Backups | Database backups are encrypted and kept for 35 days in a separate storage bucket; deleted data disappears from backups within that time. If a backup is restored, accounts deleted earlier are deleted again. [FILE BACKUP — whether Cloudflare R2 keeps a separate backup of photos, and for how long, to be verified; the 35 days above apply to database backups only] |
| Account deletion record | User ID, time and source of the deletion and a keyed hash of the e-mail (no plain e-mail, no content); kept for 40 days so the deletion can be re-applied if a backup is restored, then deleted. |
| Session | At most 90 days (it also lapses after 30 days of non-use); it ends earlier on sign-out, account deletion or termination for security reasons. |
| Chat photos | Kept while the match is active; deleted together with the messages 30 days after the match ends (unless they are or were the subject of a report, open or closed; those are kept while the report is reviewed and for a limited period afterwards: [ŞİKAYETLİ İÇERİK SAKLAMA SÜRESİ — lawyer/product decision]). Deleted immediately when you delete your account or an administrator removes the content. Retention of the screening copy at Google is governed by Google's terms. |
| Rejected photo record | Only the user ID and the time are kept (no photo or content); it is used for the 24-hour pause count and deleted after 2 days. Deleted immediately when you delete your account. |
| Explore posts | Public until you withdraw the post or your consent, or delete the meal or your account. When withdrawn, the photo copy and note are deleted; a short record of which post was removed, when and why may be kept for [RIZA/ŞİKAYET KAYITLARI SAKLAMA, lawyer to decide]. Images already saved to other people's devices and screenshots cannot be recalled. |
| Messages | Kept while the match is active. When a match ends (one side ends it or blocks), the messages become invisible to both sides; they are kept on the server for 30 days and then deleted (including chat photos). Messages that are the subject of an open or past report are not deleted in that window; they are kept while the report is reviewed and for a limited period afterwards: [ŞİKAYETLİ İÇERİK SAKLAMA SÜRESİ — lawyer/product decision]. When you delete your account, your messages are deleted too. |
| Consent and report records | [RIZA/ŞİKAYET KAYITLARI SAKLAMA — lawyer to decide whether they are kept after account deletion for evidence/safety, and for how long] |
| Crash reports | [Crashlytics retention to be verified] You can turn them off inside the app (on by default). |
- Data
- Account, profile, meal content, matches, progress entries
- Period
- While your account is open. When you choose “Delete account” in the app, your account and related data (including photos you uploaded) are deleted.
- Data
- Backups
- Period
- Database backups are encrypted and kept for 35 days in a separate storage bucket; deleted data disappears from backups within that time. If a backup is restored, accounts deleted earlier are deleted again. [FILE BACKUP — whether Cloudflare R2 keeps a separate backup of photos, and for how long, to be verified; the 35 days above apply to database backups only]
- Data
- Account deletion record
- Period
- User ID, time and source of the deletion and a keyed hash of the e-mail (no plain e-mail, no content); kept for 40 days so the deletion can be re-applied if a backup is restored, then deleted.
- Data
- Session
- Period
- At most 90 days (it also lapses after 30 days of non-use); it ends earlier on sign-out, account deletion or termination for security reasons.
- Data
- Chat photos
- Period
- Kept while the match is active; deleted together with the messages 30 days after the match ends (unless they are or were the subject of a report, open or closed; those are kept while the report is reviewed and for a limited period afterwards: [ŞİKAYETLİ İÇERİK SAKLAMA SÜRESİ — lawyer/product decision]). Deleted immediately when you delete your account or an administrator removes the content. Retention of the screening copy at Google is governed by Google's terms.
- Data
- Rejected photo record
- Period
- Only the user ID and the time are kept (no photo or content); it is used for the 24-hour pause count and deleted after 2 days. Deleted immediately when you delete your account.
- Data
- Explore posts
- Period
- Public until you withdraw the post or your consent, or delete the meal or your account. When withdrawn, the photo copy and note are deleted; a short record of which post was removed, when and why may be kept for [RIZA/ŞİKAYET KAYITLARI SAKLAMA, lawyer to decide]. Images already saved to other people's devices and screenshots cannot be recalled.
- Data
- Messages
- Period
- Kept while the match is active. When a match ends (one side ends it or blocks), the messages become invisible to both sides; they are kept on the server for 30 days and then deleted (including chat photos). Messages that are the subject of an open or past report are not deleted in that window; they are kept while the report is reviewed and for a limited period afterwards: [ŞİKAYETLİ İÇERİK SAKLAMA SÜRESİ — lawyer/product decision]. When you delete your account, your messages are deleted too.
- Data
- Consent and report records
- Period
- [RIZA/ŞİKAYET KAYITLARI SAKLAMA — lawyer to decide whether they are kept after account deletion for evidence/safety, and for how long]
- Data
- Crash reports
- Period
- [Crashlytics retention to be verified] You can turn them off inside the app (on by default).
6. Your rights (KVKK Art. 11)
By applying to the data controller you may: learn whether your data is processed; request information about it; learn the purpose and whether it is used accordingly; know the third parties in Türkiye or abroad to whom it is transferred; request correction of incomplete or inaccurate data; request erasure or destruction under Art. 7 and that this be notified to recipients; object to a result against you arising solely from automated analysis; and claim compensation for damage caused by unlawful processing.
How to apply: e-mail info@codeativ.com or write to the address above [additional channels to be defined by the lawyer]. We respond within 30 days. You can also withdraw your weight/measurement consent, your Explore sharing consent and your chat photo consent at any time inside the app (Profile > Privacy and legal; for chat photos: “Chat photo scanning” card > “Manage” > “Withdraw my consent”) and delete your entries and posts.
7. Updates
If this notice changes, the new version is published with a new date and, where needed, your consent/acceptance is requested again.