Privacy Policy
Last updated: 3 November 2026
1. Introduction
Hold My Fork is a diet pact for two friends on iOS and Android (30 days by default, or a length from 7 to 90 days that you choose), with home-screen widgets and notifications. This privacy policy explains which personal data the app handles, why, who receives it and what choices you have. It applies together with our Terms of use at https://holdmyfork.morrowline.app/en/terms/. Users in Türkiye also receive a separate information notice under Law no. 6698 at https://holdmyfork.morrowline.app/en/kvkk/.
In short:
- You must be at least 18 years old. You confirm this when you continue past the age step; where an app store age law applies, your app store confirms it instead. We do not ask for your birth date.
- Your check-ins, cravings, plate photos and optional weight entries are health data. We ask for your explicit consent before we save them, and you can withdraw it in Settings.
- The friend in your pact sees what you add to the pact. Your weight stays private unless you and your friend both choose to share it.
- Usage analytics are off until you switch them on. We do not show ads and we do not sell personal information.
- You can download a copy of your data under Settings > Privacy & data > Download my data, and delete your account under Settings > Delete account.
2. Who we are
The controller of your personal data is Seyfi Can Zeyrek, an individual trading under the brand Morrowline Apps, established in Türkiye, Esenyali Mahallesi 52/75 Sk. Izmir/Türkiye ("we", "us"). You can reach us about privacy at zeyrekseyfican@gmail.com.
We have not appointed a data protection officer. Send privacy questions and requests to zeyrekseyfican@gmail.com.
We have not appointed a representative in the European Union or the United Kingdom under article 27 of the GDPR or the UK GDPR. If you live in the EU or the UK, contact us directly at zeyrekseyfican@gmail.com; you can also contact your local data protection authority.
3. Scope
This policy covers the Hold My Fork app, its widgets and notifications, and the invite page at https://holdmyfork.morrowline.app/i that we host with Firebase Hosting. The invite page runs entirely in your browser: it shows the invite code and copies it when you tap Copy, and it loads no analytics and no external resources.
It does not cover the App Store, Google Play, the share targets you choose in the system share sheet, or the websites and services of others. Screens in the app can give you extra information at the moment a choice is asked.
4. Data we collect
Providing the data marked optional is your choice. Without a name, your age check and your check-ins the pact cannot work; without photos, weight or notifications, the rest of the app still does.
You give us
| Data | What it includes | Why we use it | Who receives it |
|---|---|---|---|
| Name or nickname | The name you type for your friend to see (up to 40 characters) | To show who you are in the pact and in notifications | Google (Firebase); your friend |
| 18+ confirmation | You confirm once that you are 18 or older. Where an app store age law applies (for example in Texas, Utah or Louisiana), the app instead asks your app store whether you are 18 or older (Apple Declared Age Range, Google Play Age Signals) and you choose whether to share. We store only that you confirmed and whether you or your app store did (no birth date, age or age range) | To keep the service to adults and to comply with app store age laws | Google (Firebase); Apple or Google answer the age request on your device |
| Health information: diet behaviour | Daily check-ins (Held or Dropped the Fork), confessions, your friend's Forgive or Grab a Fork answer, Rest days and pauses, Hold My Fork requests with the craving type you pick (sweet, salty, fast food, other), whether you made it or had it, and counters computed from them | To run the pact, the streak and the Hold My Fork flow | Google (Firebase); your friend |
| Health information: weight (optional) | Weight entries in kilograms, the percentage change since your first entry in the pact, the sharing level you and your friend chose, and a flag that shows you a care card if your weight changed quickly over two weeks | To chart your weight and, only if you both choose, to share it | Google (Firebase); your friend only at the shared level |
| Photos (optional) | Plate photos you take or pick, pact cover photos for the first and the last day, and your own photos for the stamp and heart spots on the Pact tab board (board photos) | To reveal plates to your friend, to build your pact cards and board, and to show on your widgets (board photos never appear on widgets or share cards) | Google (Firebase); your friend |
| Profile photo (optional) | One photo of you that you take or pick. The app resizes it on your device (long edge at most 600 px, JPEG of at most 2 MB) and saves it as a new image without embedded metadata such as location. We store it as avatars/ followed by your user ID in Cloud Storage for Firebase, and keep a note of its version number in your profile and in the pact | To show your friend who you are next to your name | Google (Firebase); your friend in your active pact |
| Messages and notes you send | Notes of up to 80 characters or a ready reply in answer to a Hold My Fork request; plate captions of up to 40 characters | To let you support each other | Google (Firebase); your friend |
| Other content you create | Your fork rules (one to five, up to 80 characters each), the pact reward (up to 60 characters), morning pledges, cheers, nudges, plate reactions and, if you ask your friend to cover Premium, that you asked and when | To make and run the pact | Google (Firebase); your friend |
| Film and share approvals (optional) | When you ask your friend to add their plates to your Pact film, or to approve a share card: which film or card, who asked, your friend's answer and the times. This record holds no video or image | To let your friend decide and to apply the answer | Google (Firebase); your friend |
| Reports you send | The reason, optional details of up to 200 characters, and a copy of the reported text or plate photo as evidence | To review reports and keep people safe | Google (Firebase) |
| Settings and choices | Time zone, reminder time, quiet hours, notification choices, people you blocked, and records of your consents (type, answer, text version, time), including your acceptance of the Terms of use and Privacy policy on the welcome screen and your crash-report choice | To time your day, deliver notifications as you chose and show we asked for consent | Google (Firebase) |
We collect automatically
| Data | What it includes | Why we use it | Who receives it |
|---|---|---|---|
| Account identifier (user ID) | A random identifier created after you pass the age check, also used as your user ID at our subscription provider | To keep your pact and settings with your account | Google (Firebase); RevenueCat; your friend's app receives it inside shared pact data |
| Device identifiers and push token | A push token (if you allow notifications), a random device ID created by the app, platform, app version, language and time zone, refreshed about once a day while you use the app; a Firebase installation identifier | To deliver notifications to your device and keep sessions working | Google (Firebase); Apple for iOS delivery |
| Purchase and subscription status | Whether Premium is active, the product, the store, the expiry date and status | To switch Premium on or off for you and your friend | RevenueCat; Google (Firebase); your friend sees that Premium is on and who pays |
| Pact count | How many pacts you have been paired in, and a marker on the pact when it is your first | To keep the Plates widget free during your first pact | Google (Firebase); your friend's app receives the marker inside shared pact data |
| App usage and interactions (analytics), only if you switch it on | Screens and taps, app version, device model, operating system, approximate country and an app instance identifier created by Firebase Analytics. We do not send weight, craving types or note text as event values | To understand how the app is used and keep it stable | Google (Firebase) |
| Approximate location (analytics), only if you switch analytics on | Country and region that Firebase Analytics derives from your IP address; the app never reads your GPS position | To understand in which regions the app is used | Google (Firebase) |
| Crash reports (optional) | Crash traces, device model, operating system version and app state at the time of a crash. In the production app they start after you pass the age check and you can turn them off under Settings > Privacy & data (Share crash reports) | To fix crashes | Google (Firebase) |
| Other diagnostics | App Check attestation results from App Attest or Play Integrity, the IP address in server logs, and a hashed form of the IP address in short-lived rate-limit counters | To block abuse and keep the service secure | Google (Firebase); Apple; Google (Google Play) |
| Notification content | Names, short message text and a small snapshot of the day state that travels with each push so widgets can update | To tell you what happened in your pact | Google (Firebase); Apple for iOS delivery |
We receive from others
| Data | What it includes | Why we use it | Who receives it |
|---|---|---|---|
| Invite code from Google Play | On Android, the invite code in the Google Play install referrer, read once to prefill the invite screen | To open the invite you were sent | Stays in the app |
The app creates an anonymous account identifier once you pass the age check, and you add your name. There is no sign-in and no email address: the account lives only on your device and cannot be recovered if you delete the app or lose your phone. On iOS the age-check result is kept in the Keychain and on Android in the Keystore-backed secure storage; a failed check locks the gate on that device.
Stays on your device
The widget snapshot (names, counts, day states, reward, your pact cover photo and small plate photos) in the iOS App Group or Android app storage, check-ins waiting for a connection, the age-check result, share card images that you create until you share or discard them, a Pact film while you share it (section 9), and a cached copy of your own profile photo and of your friend's profile photo so they load quickly (older cached versions are removed when a photo changes). If you pick a profile photo without a connection, it waits on your device and is uploaded when you are back online.
What we do not collect
Apart from the approximate location that Firebase Analytics derives from your IP address when analytics is on, we do not collect your device location (GPS), your contacts or microphone audio, and the app has no calorie, food-logging or goal-weight feature. The app does not contain advertising or attribution SDKs.
5. How we collect data
Directly from you: typing a name, rule, reward, caption or note, tapping check-ins and requests, choosing or taking photos (plates, covers, board photos and your profile photo), entering weight, answering consent questions and filing reports.
Automatically: your device and the app create the account identifier, push token, device ID, time zone and app version; Firebase services create installation and diagnostic identifiers; our servers compute days, streaks and counters from the check-ins.
From others: the app stores and our subscription provider for purchase status, Google Play for the invite code, and your friend when they add content to the shared pact.
6. How we use data
- To provide the pact: create your account, run days, streaks and counters on our servers, reveal plates, deliver Hold My Fork requests and replies, and show your friend what you chose to share.
- To keep you informed with service notifications and widgets.
- To process Premium: switch it on or off for both friends based on the subscription status.
- To keep the service secure and stable: attest the app, limit abuse, review reports and fix crashes.
- To understand usage, only after you switch usage analytics on.
- To meet legal duties and defend legal claims.
We collect usage analytics and crash diagnostics through Google (Firebase): usage analytics only after you turn them on, and crash diagnostics after you pass the age check unless you turn them off in Settings.
We do not show ads, we do not use your data for advertising and we do not build profiles beyond the pact features described here. We do not send marketing messages.
7. Legal bases
| Purpose | Data | Legal basis (GDPR / UK GDPR) | KVKK article 5/6 |
|---|---|---|---|
| Run your account and the pact, deliver content to your friend, notifications, widgets | Name, account identifier, device and push data, pact content, film and share approvals, settings | We need this to provide the service you asked for (art. 6(1)(b)) | 5/2-c: performance of a contract |
| Diet behaviour and weight data | Check-ins, confessions, cravings, plate photos, weight | Contract (art. 6(1)(b)) and, for health data, your explicit consent (art. 9(2)(a)), which you can withdraw at any time under Settings > Privacy & data > Data choices without affecting earlier processing | Article 6: explicit consent for special-category data |
| 18+ check | Your 18+ confirmation, or your app store's answer where an app store age law applies | Our legitimate interests (art. 6(1)(f)) in keeping an adults-only service adults-only; you can object. Where an app store age law applies, our legal obligation under that law | 5/2-f: legitimate interest |
| Premium and billing status | Purchase and subscription status | Contract (art. 6(1)(b)) | 5/2-c |
| Usage analytics | App usage, device and analytics identifiers | Your consent (art. 6(1)(a)); analytics stay off until you switch them on and you can switch them off under Settings > Privacy & data > Data choices | 5/1: explicit consent, requested separately in the app |
| Crash reports, app attestation, abuse prevention, reports and blocks | Crash data, attestation results, IP address, reports, block list | Our legitimate interests (art. 6(1)(f)) in keeping the app stable and secure, preventing abuse and defending legal claims; you can object, and you can turn crash reports off under Settings > Privacy & data | 5/2-f |
| Records of your consents | Consent log | Legal obligation (art. 6(1)(c)), including our duty to show that consent was given | 5/2-ç |
Where a rule requires consent before an app reads identifiers on your device for analytics, we rely on your consent as shown above.
8. Device permissions
You can refuse or revoke every permission below in your system settings. The app keeps working without them, except the feature named.
Camera (iOS)
Why we ask: To take a photo of a plate, a pact cover, a board photo or your profile photo when you tap Take a photo. What we do not do: record video or take pictures in the background; the camera opens only after you tap. Stored or sent: the photo is uploaded to Google (Firebase) only when you post it or save it as your profile photo. How to turn it off: iOS Settings > Hold My Fork > Camera.
Photos (iOS)
Why we ask: To let you pick one photo of a plate, a pact cover, a board photo or your profile from your library. What we do not do: browse your library or read photos you did not pick. Stored or sent: the photo you pick is uploaded only when you post it or save it as your profile photo. How to turn it off: iOS Settings > Hold My Fork > Photos.
Add to Photos (iOS)
Why we ask: To save a Pact film to your photo library when you pick Save Video in the share sheet; iOS asks you the first time. What we do not do: read, browse or change your photos; this add-only permission lets a video be added and nothing else. Stored or sent: the video is saved in your photo library on your phone and stays there until you delete it; it is not sent to us. How to turn it off: iOS Settings > Hold My Fork > Photos.
On Android the app uses the system camera and photo picker and does not ask for camera or media permissions. It asks for no permission for a Pact film either: the app you pick in the share sheet saves or sends it.
Notifications (iOS and Android)
Why we ask: To tell you about your pact, including time-sensitive Hold My Fork requests on iOS. What we do not do: send marketing or promotional messages; the core app works without notifications. Stored or sent: if you allow notifications, a push token identifies your device to the push service so we can reach you. We send service notifications about your pact, such as invites, check-in reminders, Hold My Fork requests and replies, drops and responses, milestones and sharing changes; we send no marketing or promotional notifications and notifications never contain your weight. How to turn it off: iOS Settings > Hold My Fork > Notifications, Android Settings > Apps > Hold My Fork > Notifications, or the notification switches and quiet hours in the app under Settings. Hide details in notifications is on by default for Hold My Fork requests and drops, so the lock screen shows only who.
9. What other people can see
Anything you add to a pact (your name, profile photo, check-ins, plate photos and captions, cover photos, Hold My Fork requests and notes, reactions, pledges and, if you both choose to share it, your weight) is visible to the friend you are in the pact with. A pact has two people. Your friend also sees the pact's fork rules and reward, and sees that Premium is on and who pays for it. The person you invite sees your name and the pact preview before joining, and you confirm within 24 hours that the person who joined is the friend you meant. If you turn that person away, what they added to the pact is removed from it.
Shared content is stored on our servers so it can be delivered to your friend; we do not use it for advertising. Authorised staff can technically access stored data to run and secure the service and only do so when needed for that purpose.
Photos you add are uploaded to Cloud Storage for Firebase and your friend sees them: a blurred copy of a plate photo first and the plate photo itself once both of you have posted or the day has closed, and a cover photo as soon as you add it. Plate photos, cover photos and board photos are rewritten on our servers without embedded metadata such as location before your friend can open them. Board photos are your own photos for the stamp and heart spots on the Pact tab board: your friend sees them in the pact, only you can replace or delete them, and they never appear on widgets or share cards.
A profile photo is optional: it is uploaded to Cloud Storage for Firebase and only you and the friend in your active pact can see it. If you end the pact or are blocked, your former friend can no longer open it. Your friend can hide it on their phone and report it, and you can remove it at any time in Settings. Profile photos are resized and re-encoded on your device before upload, which removes embedded metadata such as location; we do not rewrite them on our servers. Your profile photo is not health data, and it never appears in notifications, widgets or share cards. The photo stays in storage after a pact ends, so that a new pact can show it, until you remove it or delete your account. A share card that contains your friend's photo is created only after your friend says OK for that card; share cards are made on your device and go where you send them with the system share sheet.
Your weight is private unless you and your friend both choose to share it; the more private of your two choices applies, and weight never appears in notifications, widgets or share cards.
Widgets can show names, streak and held-day counts, check-in status, the pact reward, your pact cover photo and small plate photos to anyone who can see your screen; they never show weight.
You can hide a plate photo or your friend's profile photo, report a plate photo, a profile photo or your friend, and block your friend, which ends the pact. Blocking also hides what your friend shared and stops invites in both directions. We aim to reply to reports within 24 hours. A report of a profile photo sends us a copy of the photo as evidence. Names, fork rules, rewards, notes and plate captions pass an automatic word filter on our servers that blocks slurs, threats and sexual harassment.
If you delete your account, your photos, notes, cravings and weight are removed from your friend's view as well; your friend keeps their own data and the anonymous pact counters, and you appear as Former member. If you end a pact, plate photos are deleted automatically 90 days later and the other pact records stay in both friends' history until an account is deleted.
If you feel unsafe because of how someone uses the app, write to zeyrekseyfican@gmail.com.
The Pact film
You can make a Pact film, a short, silent, vertical video of your pact, once a pact longer than 7 days reaches day 7 and again once a pact has ended with an outcome. It is not offered in a blocked pact or during your own live Hold My Fork request.
Made on your phone. A Pact film is made on your phone and we do not upload it. The app cuts it from a template, with no AI model and no server involved, and the video never reaches our servers. To build it, the app reads plate photos from your device or downloads them from Cloud Storage for Firebase, as it does when you view them.
What is in it. Both friends' names, the pact's length, the state of each day, counts (such as days held, forks held, forks dropped, rest days and plates shown), the reward if there is one, and revealed plate photos, leaving out plates you have hidden. The names, the day pattern and the totals for the two of you are in the film whether or not your friend has said OK; the plates-shown count covers only the plates in that film. On the free plan the film also carries a small HOLD MY FORK strip and a closing scene. A Pact film never contains weight. The film has no field for it, whatever sharing level you and your friend chose.
Your friend's plates. Your friend's plates go into your film only with your friend's OK. When you ask, the request goes through our servers, your friend gets a notification and can watch the film before answering, and we store the approval record on our backend: who asked, which film, the answer and the times. The video is not part of that record. Without an OK the film uses only your own plates. An OK covers that one person's first-week or final film of that pact; it covers no other pact and not your friend's own film. The OK is a choice between the two of you, not a consent we rely on to process data. The friend who gave an OK can take it back under Share cards on the Pact tab, with Take my plates out. One action covers every film of that pact they said OK to: the record changes to declined, their plates stay out of later cuts, and you would have to ask again. This option shows only while the pact is on the Pact tab: a running or paused pact, or a completed pact during the 72 hours after it completes. It is gone as soon as the pact is ended, blocked or renewed, and once those 72 hours are over. From then on no screen in the app leads to a new film of that pact. To have an OK removed from the record after that, write to zeyrekseyfican@gmail.com and give us what you know about the account, such as the names in the pact; an anonymous account has no email address, so we may not be able to match your request to it. A video already shared cannot be recalled. Blocking your friend ends the pact, and the film is no longer offered in it. The approval record is not in the Download my data file, and you can ask us for it at zeyrekseyfican@gmail.com. Section 13 says how long it is kept.
Temporary file. When you tap Share film, the app writes the video as an MP4 file to its temporary folder, opens the system share sheet and deletes the file when the sheet closes. On Android the system share step keeps its own copy in the app's private cache until the next film screen opens or the system clears that cache. If the app stops before the delete step, the file stays in the temporary folder until the next film screen opens or the system clears the folder. The app keeps no other copy of the film.
Where it goes. The film goes only where you pick in the share sheet. Whatever you pick (a messaging app, a social app, Save Video) handles it under that service's own terms and privacy policy. A film shows part of your diet record and your friend's name, so choose with care: we do not receive it, and we cannot recall or delete a copy that has left your phone.
10. Health and wellness data
Hold My Fork treats your check-ins, confessions, cravings, plate photos and weight as health data (your profile photo is not part of it) and stores them in Cloud Firestore and Cloud Storage for Firebase, configured for the Google Cloud europe-west1 region (Belgium).
The app is a wellness tool, not a medical device. It does not diagnose, treat or prevent any condition.
We ask for your explicit consent before we save diet data and again, separately, before your first weight entry, and you can withdraw each consent under Settings > Privacy & data > Data choices. Withdrawing the diet-data consent stops new check-ins and the app offers to delete your account and data; if you keep your account, what is already stored stays until you delete it, or, for plate photos, until the retention period ends. Withdrawing the weight consent stops new weight entries and the app offers to delete the entries you have.
We do not use your health data for advertising and we do not sell it. Only you, your friend at the level you both chose, our service providers named in section 11 and authorised staff for running and securing the service can access it. A Pact film you choose to send carries day states, counts and plate photos to whoever you send it to (section 9).
If your weight changes by more than 1% of your body weight per week for two weeks in a row, the app computes this automatically, shows a care card with a link to support resources and hides trend arrows. No decision with legal or similarly significant effect is made by automated means. The app also links to eating-disorder support in Settings and during onboarding.
Consumer health data
For residents of Washington, Nevada and other US states with consumer health data rules, this section is our consumer health data privacy policy. Categories collected: diet behaviour records (check-ins, confessions, Forgive or Grab a Fork answers, cravings and outcomes), weight entries and a rapid-change flag, and plate photos. Purposes: to run the pact and the features you use. Sources: you. Shared with: Google (Firebase) as our service provider, and the friend in your pact at the level you choose. We collect this data only with your consent and do not sell it. You can withdraw consent under Settings > Privacy & data > Data choices, delete your account in the app and ask us for access or deletion at zeyrekseyfican@gmail.com; you can ask for the list of third parties that received your consumer health data, which is the list in this paragraph. We will notify you and regulators of a breach of health data as the law requires.
11. Who receives data
Some data leaves your device: your name, check-ins, cravings, notes, photos (including your optional profile photo), weight entries and identifiers are processed by Google (Firebase) to run the pact, and your purchase status is processed by RevenueCat to manage Premium.
Service providers
| Recipient | What it does for us | Data |
|---|---|---|
| Google (Firebase) | Authentication, database, file storage, server functions, push delivery, usage analytics after consent, crash reports and app attestation | The data in section 4 except purchase records held by RevenueCat |
| RevenueCat | Subscription management, store receipts, restore purchases and the entitlement webhook | Account identifier, purchase and subscription status |
Independent services
| Recipient | What it does | Data |
|---|---|---|
| Apple | App Store purchases, Apple Push Notification service, App Attest | Purchases and push delivery for iOS, attestation results |
| Google (Google Play) | Google Play purchases and install referrer, Play Integrity attestation | Purchases on Android, attestation results |
These services decide for themselves how they use data under their own privacy policies. The system share sheet sends a card, Pact film or invite only to the app you pick, under that app's own terms and privacy policy.
Other people in the app
See section 9.
Legal and corporate
We disclose data to public authorities when the law requires it, when we need to protect the rights, safety or property of people or the service, and to a successor if we are part of a merger, acquisition or sale, in which case this policy continues to apply until you are told otherwise.
We do not sell personal information and we do not share it for cross-context behavioural advertising. We have no actual knowledge of selling or sharing the personal information of anyone under 16.
12. International transfers
Cloud Firestore, Cloud Storage and Cloud Functions are configured for europe-west1 (Belgium). Firebase Authentication, push delivery, Analytics, Crashlytics and App Check run on Google's global infrastructure, including the United States. RevenueCat processes data in the United States. Apple and Google operate in the United States and other countries.
When data from the EEA, the United Kingdom or Türkiye reaches a recipient outside those regions, we rely on standard contractual clauses with that recipient, the UK addendum for UK data and, for Türkiye, the safeguards in article 9 of Law no. 6698 as amended. You can ask for a copy of the safeguards at zeyrekseyfican@gmail.com.
13. Retention
| Data | How long | What triggers deletion |
|---|---|---|
| Name, account identifier, check-ins, cravings, notes, reactions, fork rules, reward, weight entries, consent records, settings, block list, invite records, requests to cover Premium and pact count | Until you delete your account | Account deletion; you can also delete weight entries in Settings |
| Plate photos and plate captions | 90 days after the pact ends or completes, then deleted automatically | End of the pact, or you delete a plate |
| Pact cover photos and board photos | Until you delete your account | Account deletion; only the person who uploaded a cover or board photo can delete it |
| Profile photo | Until you remove it or delete your account; it stays after a pact ends so that a new pact can show it, but your former friend can no longer open it | You remove it in Settings; account deletion |
| Film and share approvals | Until the person who asked deletes their account; the record of an answer in the answering friend's own activity stays until that friend deletes their account | Account deletion |
| Reports and their evidence copies (including the copy of a reported plate or profile photo) | 30 days | Automatic deletion |
| Push tokens and device records | Until you delete your account | A token is removed when the push service reports it invalid; device records not used for 12 months are removed |
| Inactive anonymous accounts | An anonymous account with no activity for 12 months (judged by its newest device record, or by its creation date if it has none) is deleted automatically unless it is in a pact that is still active | Automatic deletion |
| Purchase and subscription status | Until you delete your account; technical billing event identifiers are kept for 90 days | Account deletion; the subscriber record at RevenueCat is deleted when your account is deleted |
| Usage analytics and crash reports | For the period Google sets in its own retention settings; we have not shortened it | Provider setting |
| Rate-limit counters | A few hours | Automatic expiry |
| Data stored only on your device (including cached profile photos) | Until you remove the app; the age-check result can remain in the iOS Keychain after you remove the app | Removing the app |
Deleted data can remain in backups and logs for a limited time until they are overwritten. Content that your friend has already seen is controlled by your friend. Purchase records held by Apple or Google stay with them under their rules.
14. Account and data deletion
Open Settings, tap Delete account and confirm. Before you confirm, you can download a copy of your data from the same screen. The app tells you that deleting does not cancel your subscription and links to subscription management. Your friend is told the pact ended. Your data leaves the app at once and is erased from our systems within 30 days.
Deleting your account removes your profile and profile photo, check-ins, cravings and notes, plate photos, cover photos you uploaded, weight entries, consents, device records and account identifier, and your subscriber record at our subscription provider RevenueCat. The board photos you added go with your cover photos.
It keeps: your friend's own data and the pact's anonymous counters, with you shown as Former member; reports filed about you for 30 days as safety evidence; purchase records held by Apple or Google; and short-lived backups and vendor logs until they age out. We finish deletion at once or, if a step fails, retry until it is done, always within 30 days.
If you delete your account, your photos, notes, cravings and weight are removed from your friend's view as well; your friend keeps their own data and the anonymous pact counters, and you appear as Former member.
Removing the app from your phone does not delete your server data and does not cancel a subscription; cancel in your App Store or Google Play account settings. Because the account lives only on your device, nobody can open it again after the app is removed or the phone is lost; what was stored is deleted automatically after 12 months without activity unless the pact is still active (section 13), and your friend keeps their own data. If you cannot open the app, follow the steps at https://holdmyfork.morrowline.app/en/delete-account/ or write to zeyrekseyfican@gmail.com and give us whatever you know about the account, such as the name you used and your friend's name. An anonymous account has no email address, so we may not be able to match your request to it.
15. Your rights and choices
You can ask us to tell you what we hold about you, give you a copy, correct it, delete it, restrict or stop our use of it where the law gives you that right, and move it to another service. You can withdraw a consent at any time and opt out of marketing (we send none). For a copy you do not need to write to us: Settings > Privacy & data > Download my data gives you, right away, a machine-readable file (JSON) with your profile, settings, consent records, check-ins, notes, cravings, weight entries, reports you sent, subscription status and pact count, together with the photos you uploaded. It does not contain your friend's content.
In the app: Settings > Privacy & data > Data choices switches diet data, weight and usage stats, and Settings > Privacy & data has a switch for crash reports; Settings > Notifications controls notifications; you can add, change or remove your profile photo in Settings, hide or report a plate or your friend's profile photo, report or block your friend, download a copy of your data (Settings > Privacy & data > Download my data) and delete your account (Settings > Delete account).
To make a request, write to zeyrekseyfican@gmail.com. We may ask you to confirm who you are using details linked to your account. We answer within one month (45 days for US state law requests, 30 days for requests under Law no. 6698), and extend the period only where the law allows and after telling you. We do not treat you differently for using your rights. You may use an authorised agent. If we refuse a request you can appeal by replying to our message and we answer within the period the law sets. If the data protection law where you live gives you other rights, we honour them.
16. Additional information for the EEA and UK
The GDPR (EEA) and the UK GDPR with the Data Protection Act 2018 apply to our processing for you. Our controller details, and the fact that we have no data protection officer or art. 27 representative, are in section 2.
You have the rights of access, rectification, erasure, restriction, data portability and objection (GDPR art. 15-22), the right to object at any time to processing based on legitimate interests, and the right to withdraw consent at any time. Withdrawal is as easy as giving consent: use Settings > Privacy & data > Data choices. Erasure and portability apply where the law gives you those rights.
You may complain to a supervisory authority, for example in the country where you live or work; in the United Kingdom this is the Information Commissioner's Office. UK users can also complain to us first at zeyrekseyfican@gmail.com; we acknowledge a complaint within 30 days and investigate without undue delay.
Providing your name, your age check and your check-ins is necessary for the pact; without them we cannot provide it. Photos, weight, notifications and analytics are optional. The legal bases are in section 7, recipients in section 11, transfers in section 12 and retention in section 13. We do not make decisions that have legal or similarly significant effects on you by solely automated means.
17. Additional information for US residents
This section applies to residents of California and the other US states with privacy laws, and we honour these rights for everyone in the United States. We collected the following categories in the last 12 months:
| Category (California) | Examples in the app | Sources | Purposes | Disclosed to service providers |
|---|---|---|---|---|
| Identifiers | Name, account identifier, device identifiers, push token | You; your device | Run the service, notifications, security | Google (Firebase); RevenueCat |
| Personal information in Civil Code 1798.80(e) | Name | You | Run the service | Google (Firebase) |
| Commercial information | Purchase and subscription status | App stores; RevenueCat | Premium | RevenueCat; Google (Firebase) |
| Geolocation data | Approximate country and region derived from your IP address by analytics, only if you switch it on | Your device | Understand where the app is used | Google (Firebase) |
| Internet or other electronic network activity | Usage analytics if you switch them on; crash reports | Your device | Understand use, fix crashes | Google (Firebase) |
| Audio, electronic, visual or similar information | Plate, cover, board and profile photos | You | Run the pact | Google (Firebase) |
| Medical or health information (sensitive personal information) | Check-ins, confessions, cravings, weight entries | You | Run the pact and features you chose | Google (Firebase) |
| Other personal information | Notes, captions, fork rules, reward, pledges, film and share approvals | You | Run the pact | Google (Firebase) |
| Inferences | Held-day counts, streaks, a rapid weight change flag | Computed by us | Show progress, show a care card | Google (Firebase) |
We do not sell personal information and we do not share it for cross-context behavioural advertising. We use sensitive personal information (health information) only to provide the pact you asked for and do not use it to infer characteristics about you for any other purpose, so there is nothing to limit. Retention is in section 13.
You can ask to know, delete or correct personal information and to opt out of sale or sharing (there is none). To submit a request write to zeyrekseyfican@gmail.com; because we operate online, e-mail is our request method. We verify your identity by matching details linked to your account. An authorised agent can write to us for you with your permission. Appeals: see section 15. We honour opt-out preference signals. There is a link to this policy in the app under Settings > Legal. Consumer health data rights for Washington and Nevada residents are in section 10.
18. Additional information for Türkiye
The data controller is Seyfi Can Zeyrek, an individual trading under the brand Morrowline Apps (Esenyali Mahallesi 52/75 Sk. Izmir/Türkiye). The separate information notice under article 10 of Law no. 6698 is at https://holdmyfork.morrowline.app/en/kvkk/ and describes the data, purposes, legal reasons, recipients and your rights in Turkish. It is an information notice and asks for no consent. Consent for health data and for usage analytics is requested separately in the app. Under article 11 you can ask whether we process your data, request information, ask for correction or deletion and object to results of purely automated analysis; apply at zeyrekseyfican@gmail.com.
19. Children
You must be at least 18 years old to use Hold My Fork. The app is not directed to children. Your age is self-declared: before it creates your account identifier, the app asks you to confirm that you are 18 or older. Where an app store age law applies (for example in Texas, Utah or Louisiana), the app asks your app store instead, through Apple's Declared Age Range or Google Play Age Signals; your app store asks you whether to share your age range and tells the app only whether you are 18 or older. The app does not ask for your birth date or verify your identity, and it does not keep your age range. If you say you are under 18, or your app store says so, the app creates nothing and the gate stays locked on that device. If an app store age law applies and you do not share your age range, you cannot continue until you do. We do not knowingly collect data from anyone under 18; if we learn that we have, we delete it. Parents and guardians who think a child uses the app can write to zeyrekseyfican@gmail.com.
20. Security
Data moves between the app and our servers over encrypted connections. Access rules let only you, and your friend in the pact where sharing applies, read each record; weight is shared only through a separate derived record at the level you both chose; plate originals are not delivered to your friend before the reveal. Google encrypts stored data at rest on its infrastructure. Invite codes are single-use and valid for 7 days, the invite record on our servers stores them hashed (your own private record keeps the code so you can share it again), and the inviter confirms who joined. App Check attestation and rate limits protect our servers against abuse.
No system is completely secure. Keep your device locked and your invite codes to yourself. If a breach affects your personal data we will notify you and the authorities as the law requires.
21. Changes to this policy
When we change this policy in a material way we announce it in the app and update the date above. Material changes are changes to what we collect, why, who receives it or your choices. Earlier versions are available on request. If a change means we process data for a new purpose that needs your consent, we ask you again.
22. Contact
Privacy questions and requests: zeyrekseyfican@gmail.com
Seyfi Can Zeyrek (trading as Morrowline Apps), Esenyali Mahallesi 52/75 Sk. Izmir/Türkiye.
We have not appointed a data protection officer or a representative in the European Union or the United Kingdom; send privacy questions and requests to zeyrekseyfican@gmail.com.
Trader identification for EU consumers: Seyfi Can Zeyrek, an individual trading under the brand Morrowline Apps, Esenyali Mahallesi 52/75 Sk. Izmir/Türkiye, e-mail zeyrekseyfican@gmail.com. We aim to answer privacy messages within the periods in section 15. Turkish residents can apply as described in section 18 and in the notice at https://holdmyfork.morrowline.app/en/kvkk/. For complaints you can also contact your local data protection authority.