Privacy Policy
Privacy policy
Last updated: 11 October 2026
1. Introduction
Duet is an app for two partners, provided by Seyfi Can Zeyrek, an individual developer in Türkiye, who publishes it as Morrowline on Google Play. You pair your phone with your partner's, and you keep a shared space with notes, drawings, photos, places, widgets for your home screen, a shared pet, games and a daily question. This policy explains what personal data Duet handles, why, who receives it and what you can do about it. It covers the Duet app for iPhone and Android, its home-screen and lock-screen widgets and its notifications. The Terms of use are at https://duet.morrowline.app/en/terms/ and apply together with this policy. Users in Türkiye also receive the separate information notice required by the Turkish data protection law (KVKK).
In short:
- Duet creates an anonymous account identifier for you. You add a first name or nickname; there is no email address or phone number to give.
- Anything you add to your shared space is visible to your partner and is stored on servers run by Google (Firebase).
- Your location is used only if you allow it; the version stored for your partner is rounded to about 1 km, and you can stop sharing it in Settings.
- Usage and crash data is shared with Google (Firebase) only if the Settings switch is on; in Europe, the UK, Switzerland and Türkiye it starts off.
- Duet does not show ads and does not use your data for advertising.
- You can delete your account in the app at Settings > Delete account.
2. Who we are
The controller of your personal data is Seyfi Can Zeyrek, an individual developer, Esenyalı Mahallesi, İzmir, Türkiye ("we"). Privacy contact: zeyrekseyfican@gmail.com.
3. Scope
This policy applies to the Duet app, the Duet widgets, Duet notifications and the web pages we host: the invite page for people who open a Duet invite link in a browser, this policy, the Terms of use, the Turkish information notice and the account deletion page. These pages are static: it does not load third-party scripts and does not use cookies; the hosting provider keeps ordinary server logs such as the IP address of the request.
It does not cover the App Store, Google Play, your operating system, your phone maker, the map and search services described below when you deal with them directly, or any site or app of another company. Screens in the app may give extra notices at the moment data is collected, for example before the system asks for location access.
4. Data we collect
We collect only what the features you use need. The labels below are the ones used in the store privacy summaries.
You give us
| Data | What it includes | Why we use it | Who receives it |
|---|---|---|---|
| Name or nickname | The first name or nickname you type, shown to your partner and on widgets | To show who you are to your partner | Your partner, Google (Firebase) |
| Photos (optional) | A profile photo; a photo for a widget, including the original; photos of people on a widget; a cover photo for a place | To show them on your widgets, in the app and to your partner | Your partner, Google (Firebase) |
| Messages and notes | Notes up to 1,000 characters (including a sealed note with an opening date), miss-you pings, nudges, "I love you" pings, reactions and whether a note was seen, answers to the daily question and questions you write yourselves | To deliver them to your partner and show them in the app and on widgets | Your partner, Google (Firebase) |
| Other content you create | Drawings, widget settings (titles, dates, countdowns, names), places (name, address, note, category, coordinates, visit date, favourite), pet name and care, game answers, a short status that lasts up to 24 hours | To run the features, keep them in sync between the two phones and show them on widgets | Your partner, Google (Firebase) |
| Search queries (optional) | The place name or address you type in Our places, and the pin you drop on the map (to about one metre) | To find a place and label it | Google (Firebase) (our search relay), which passes it on to Photon (komoot); on a fallback also Apple (App Store and iOS) or Google (Android and Google Play) |
| Precise location, rounded (optional) | Your device location while the app is open, rounded to two decimal places (about 1.1 km), with the time; you can turn this off with Share my distance in Settings | To show the distance between you and your partner | Your partner's app, Google (Firebase) |
We collect automatically
| Data | What it includes | Why we use it | Who receives it |
|---|---|---|---|
| Account identifier (user ID) | An anonymous identifier created when you open the app; the identifiers of the two people in a pairing, its status, its time zone and the invite code; the version of the Terms you accepted and when | To run your account and your pairing | Google (Firebase), RevenueCat (as your purchase identifier), your partner (pairing status) |
| Device identifiers and push token | The push token and platform (iOS or Android), the Firebase installation identifier, your notification choices | To deliver notifications and widget refreshes and to run Firebase | Google (Firebase), Apple (App Store and iOS), Google (Android and Google Play) |
| App usage and interactions | When you were last active, how many free moments you have used, an activity list of what you and your partner did (kept 90 days), analytics events such as pairing, notes sent and paywall steps (only if usage and crash sharing is on) | To run the features, to show your partner what is new and, if sharing is on, to understand usage in aggregate | Your partner (activity and last active), Google (Firebase) |
| Crash reports and diagnostics | Crash reports and device details attached to them (only if usage and crash sharing is on), app attestation results, a hashed form of the network address used to limit invite-code guessing, server logs | To keep the app stable and secure | Google (Firebase), Apple (App Store and iOS), Google (Android and Google Play) |
| Approximate location of the map | The map area you view in Our places, sent as map tile requests with your IP address | To draw the map | OpenFreeMap |
We receive from others
| Data | What it includes | Why we use it | Who receives it |
|---|---|---|---|
| Purchase and subscription status | Whether Couple Pro is active, its expiry and product, delivered by the store and RevenueCat; we do not see your payment card | To unlock Couple Pro for you and your partner | Google (Firebase), RevenueCat, Apple (App Store and iOS), Google (Android and Google Play) |
Duet stores the version of the Terms you accepted and the time you accepted them. If usage and crash sharing is on, we collect usage analytics and crash diagnostics through Google (Firebase). In the EEA, the UK, Switzerland and Türkiye, and when your device region is unknown, sharing usage and crash data starts off and is switched on only if you turn on Share usage and crash data in Settings; in other regions it starts on and you can turn it off in the same place. The choice follows the region setting of your device, not your location.
How photos are handled
Photos you add (a profile photo, a widget photo, a person photo on a widget or a place photo) are uploaded to Cloud Storage for Firebase, a Google service, and are visible to the person you are paired with; for widget photos both the cropped copy and the original are stored. Camera and location metadata is removed from your pictures on your phone before they are uploaded.
Stays on your device
A copy of widget content (including images) is kept on your phone so your widgets can draw without a connection; on iPhone it sits in an app group shared by the app and the widget. The near-you reminder position, the person cut-out of a photo, an install marker, an image cache and your preferences also stay on the device.
What we do not collect
We do not ask for your contacts, calendar or microphone, we do not read your location in the background, and we do not request an email address or phone number. The app does not read an advertising identifier for advertising.
Sensitive information
Location, the content of your notes and photos of you can be sensitive. Location is collected only after you allow it in the system prompt. Notes, photos and places are visible only to you and your partner in the app, as described in section 9. You decide what you write; do not add details you do not want your partner or our service providers to hold.
Required or optional
A first name and the anonymous identifier are needed to pair and use the app. Location, photos, place search, a status, usage and crash sharing and notifications are optional; without them the matching feature does not work and the rest of the app does.
5. How we collect data
- Directly from you: what you type, choose, draw or upload.
- Automatically: the app, the system and our service providers' software create the identifier, push token, last-active time and attestation results (and usage and crash data if sharing is on), and permissions you grant let the app read your location.
- From others: the stores and RevenueCat tell us whether your subscription is active, and your partner adds content that you can see.
6. How we use data
- To provide and sync the service: pairing, notes, pings, drawings, widgets, places, games, the daily question, the pet, streaks and the "Our year" recap.
- To create and secure your account: the anonymous identifier, app attestation, limits on invite-code guessing and abuse.
- To deliver notifications and refresh your widgets.
- To process purchases and decide whether Couple Pro is active. Subscriptions renew automatically until you cancel in your App Store or Google Play account settings.
- To keep the app working: logs and, if sharing is on, crash reports and aggregate usage events.
- To comply with the law and to defend legal claims.
Duet does not show ads and does not use your data for advertising. We do not sell your personal information and we do not share it for cross-context behavioural advertising. We do not send marketing messages; notifications are about what your partner does and about pairing.
7. Legal bases
| Purpose | Data | Legal basis (GDPR / UK GDPR) | KVKK article 5 |
|---|---|---|---|
| Provide the service you asked for | Name, content, photos, places, account identifier, pairing, push token, last active, activity list | Contract (article 6(1)(b)) | 5/2-c performance of a contract |
| Distance between you and your partner | Rounded location | Contract (article 6(1)(b)); you start it by allowing location access and can end it in your device settings | 5/2-c performance of a contract |
| Place search and map | Search text, rounded map centre, pin, map area | Contract (article 6(1)(b)) | 5/2-c performance of a contract |
| Purchases | Purchase and subscription status | Contract (article 6(1)(b)) | 5/2-c performance of a contract |
| Analytics and stability, where sharing starts off (EEA, UK, Switzerland, Türkiye, unknown region) | Usage events, crash reports | Consent (article 6(1)(a)), given by turning on Share usage and crash data in Settings and withdrawn by turning it off | 5/1 explicit consent, requested in the app separately from this text |
| Analytics and stability, where sharing starts on (other regions) | Usage events, crash reports | Legitimate interests (article 6(1)(f)): keeping the app stable and understanding aggregate usage; you can turn it off in Settings | 5/2-f legitimate interest |
| Security and abuse prevention | App attestation, hashed network address, logs | Legitimate interests (article 6(1)(f)): protecting the service and its users | 5/2-f legitimate interest |
You can object to processing based on legitimate interests by writing to zeyrekseyfican@gmail.com; we then weigh your reasons against ours. Withdrawing consent for usage and crash sharing is as easy as giving it: switch it off in Settings > Your data, and it stops at once without affecting what was shared before.
8. Device permissions
Duet asks for permissions only for the features below. You can refuse any of them, and you can change your mind in the system settings; the core app does not require them.
Location (while the app is open)
Why we ask: To show the distance between you and your partner, to show where you are on the map and to remind you about saved places. On iPhone the string is "Duet uses your location while the app is open to show your partner how far apart you are (they receive a location rounded to about 1 km), to show where you are on the map and to remind you about saved places." On Android the permissions are approximate and precise location. What we do not do: We do not read your location in the background, use it for advertising or sell it. Stored or sent: While the app is open and you have allowed location access, Duet reads your device location to show the distance to your partner and to show where you are on the map; the location stored for your partner is rounded to about 1 km. The near-you reminder compares your position with your saved places on your phone and does not send your position to us. How to turn it off: The Share my distance switch in Settings stops location updates and deletes the position stored for your partner; the stored position is also deleted when you turn off location access for Duet in your device settings. Unpairing or deleting your account deletes it as well. On iPhone: Settings > Privacy & Security > Location Services > Duet. On Android: Settings > Apps > Duet > Permissions > Location. The near-you reminder also has its own switch in Settings > Notifications.
Notifications
Why we ask: To tell you what your partner did (notes, pings, drawings, games, places, a new meetup) and when pairing changes. What we do not do: We do not send marketing or advertising messages, and Duet 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. Notifications are service messages about what your partner does in Duet and about pairing; we do not send marketing notifications. The text shown on your lock screen can include your partner's name and, for places and meetups, the name you or your partner chose. A note's text is never put in a notification. How to turn it off: Settings > Notifications > Duet on your phone, or switch single categories off in Settings > Notifications in the app.
Camera
Why we ask: To take your profile photo. The camera opens only when you choose to take a profile photo, and the person cut-out tool for widget photos runs on your device. What we do not do: We do not record video or take pictures in the background. Stored or sent: A photo you take is handled like one you pick from your library: it is resized on your phone and uploaded as your profile photo. On Android the system camera app takes the picture and Duet asks for no camera permission. How to turn it off: On iPhone: Settings > Privacy & Security > Camera > Duet.
Photos
Why we ask: To let you choose pictures for widgets, places and your profile photo. What we do not do: We do not browse your library; the system picker returns only the pictures you choose, and Android uses its photo picker without a permission. Stored or sent: The pictures you choose are uploaded as described in section 4. On Android, the cut-out model is delivered by Google Play services. How to turn it off: On iPhone: Settings > Privacy & Security > Photos > Duet.
9. What other people can see
Anything you add to a shared space (notes, pings, drawings, photos, widgets, places, answers, your status, when you were last active and the distance between you) is visible to the person you are paired with. Your partner's phone also receives the rounded location stored for you; it shows the distance, not a position. Your partner's game answers are revealed to you after you have given yours. Each of you can delete the notes, drawings and places you added.
Someone who holds your invite code can see your first name or nickname, your avatar, a theme preview of your widget and whether you left a note, before they decide to join. Invite codes expire after a few days.
Home-screen and lock-screen widgets can show your notes, drawings, photos, names, countdowns and distance to anyone who can see your screen. Silent background messages that refresh your widgets carry widget content, such as note drafts, names, question answers and image links, through Google's and Apple's push services.
Shared content is stored on our servers so it can be delivered to the other person; we do not use it for advertising. The people who run the service can technically access stored data and do so only when needed to run and secure the service.
If you unpair, your stored location, game rounds, next meetup and shared streak are cleared, and the notes, drawings, places, pet and photos you added stay with your partner. You can also pause Duet, which only switches nudges off; either of you can resume it. If you pair again later, you start a new space. Duet shows another person's content only after that person has added it, and every phone writes its own location. If you feel unsafe because of how Duet is used, write to zeyrekseyfican@gmail.com.
10. Who receives data
Some data leaves your device: your profile, notes, drawings, photos, places, answers, rounded location and push token are processed by Google (Firebase), and your purchase status by RevenueCat, to run the features you use.
Service providers
| Recipient | What it does for us | Data |
|---|---|---|
| Google (Firebase) | Hosts the backend: authentication, database, file storage, server functions and web hosting; delivers push messages; provides analytics, crash reports and app attestation | Everything in section 4 that is stored on our servers, plus analytics and crash data |
| RevenueCat | Handles subscription purchases and tells us whether Couple Pro is active | Account identifier used as purchase identifier, purchase and subscription status, IP address and device details |
| Google (Gmail) | Receives the mailbox of our support address: the email address and message of people who write to us, which we keep while needed to answer and to handle your request | Your email address and what you write |
| Google (ML Kit) | Android only: supplies the on-device model that cuts a person out of a widget photo; the photo is processed on the phone | None of your content; Google may receive technical and usage details, for example when the model downloads |
Independent services
| Recipient | What it receives |
|---|---|
| Photon (komoot) | The text you type when searching for a place, the rounded map centre and the coordinates of a dropped pin, passed on by our search relay. Photon sees the address of our server, not yours, and is not given your account identifier. If the relay cannot answer, the geocoder of your phone's system is used instead. |
| OpenFreeMap | The visible map area and your IP address, to draw map tiles. |
| Apple (App Store and iOS) | Processes App Store purchases, delivers notifications on iPhone, performs app attestation and, as a fallback, place search. Apple acts under its own privacy policy. |
| Google (Android and Google Play) | Processes Google Play purchases, delivers notifications and attestation on Android and, as a fallback, place search. Google acts under its own privacy policy. |
When you search for a place, the text you type and the rounded map centre are sent to Duet's search relay on Google (Firebase), which forwards them to the Photon geocoding service run by komoot without your IP address or account identifier; when you drop a pin, its coordinates (to about one metre) are sent the same way to look up its label; map tiles come directly from OpenFreeMap, which receives the visible map area and your IP address. The search relay logs how long a request was, but not the text or the coordinates. Photon and OpenFreeMap are independent of us and decide for themselves how they handle the requests; the app tells you in Our places that search is sent through Duet to a public map service.
Other people in the app
Your partner receives what is described in section 9.
Legal and corporate
We disclose data to authorities when the law requires it, to protect rights and safety, and to a successor if the service is transferred; this policy then continues to apply.
Sale and sharing
Duet does not show ads and does not use your data for advertising. We do not sell your personal information and we do not share it for cross-context behavioural advertising.
11. International transfers
Our backend runs on Google's cloud: the database is in the United States multi-region "nam5" and server functions run in "us-central1" in the United States. Uploaded files, analytics, crash reports and app attestation are handled on Google's infrastructure, which can be in the United States and other countries. RevenueCat, Apple and Google process data in the United States and other countries. When data of people in the European Economic Area, the United Kingdom or Türkiye goes to these providers, we rely on standard contractual clauses (with the UK addendum for the United Kingdom) and, for Türkiye, on the safeguards of article 9 of Law no. 6698. The search relay runs in the United States and passes requests to Photon (komoot). Photon (komoot) and OpenFreeMap are independent services whose server locations are not stated in the app; we have no agreement with them, and their requests happen because you search or open the map. For Türkiye we rely on the standard contract of article 9 of Law no. 6698 for processors. You can ask for a copy of the safeguards at zeyrekseyfican@gmail.com.
12. Retention
| Data | How long | What triggers deletion |
|---|---|---|
| Account identifier, name, avatar, status, pairing, last active, free-moment counter, push token and settings | Until you delete your account. A status lasts at most 24 hours. | Deleting your account |
| Notes, pings, drawings, widgets, places, answers, game content, pet and streak data | Until deleted by their author, by you or your partner where the app allows it, or by deleting the account of the only member | Deleting content, unpairing or account deletion; content you added to a shared space stays with your partner after you leave |
| Photos and uploaded images | Until you replace or delete them or delete your account | Account deletion removes your uploads |
| Rounded location | Until you turn off Share my distance, turn off location access, unpair or delete your account | Switching sharing off, revoking permission, unpairing or account deletion |
| Record of the Terms version you accepted and when | Until you delete your account | Account deletion |
| Activity list | 90 days, then deleted automatically | Automatic expiry |
| Invite codes and network-address hashes for rate limiting | A few days up to a month, then deleted automatically | Automatic expiry |
| Place search text and map requests | Our search relay does not keep the text or coordinates; Photon and OpenFreeMap keep requests for the period they set in their own settings | Controlled by those services |
| Analytics, crash, attestation and push data | For the period Google sets in its own retention settings; we have not shortened it | Controlled by the provider; deleting your account asks Analytics on your phone to reset |
| Messages you send to our support address | While needed to answer you and handle your request | When the matter is closed |
| Purchase and subscription records | As long as the stores, RevenueCat and the law require (for example accounting records) | Store policy |
| Widget copies and caches on your phone | Until you remove the app or unpair | Removing the app |
Deleted data can remain in encrypted backups and logs for a limited period until they are overwritten. Content that your partner has already received on their device or widget is controlled by your partner after you leave. Store purchase records stay with Apple or Google under their rules. Your phone's own backup (iCloud or Google backup) can include app data stored on the device.
13. Account and data deletion
The app creates an anonymous account identifier when you first open it; it is not tied to your name unless you add one. To delete it, open Settings > Delete account in the app and confirm. The deletion runs immediately; if a step fails the app tells you and you can try again. You can also use the account deletion page at https://duet.morrowline.app/en/delete-account/ for the same instructions.
Deleting your account removes your profile, your private settings, the invitations you created, the photos and drawings you uploaded, your stored location and your sign-in identity. If you are paired, your partner keeps the shared space, including the notes and answers you wrote. More precisely, deletion also removes your push tokens, your free-moment counter, the links to your uploads on shared widgets, and your name and photos on shared places. If you were the only member of your space, the whole space and its files are removed. The number of free moments you used stays with the seat for the next member.
After the account is deleted, we also ask RevenueCat to delete your customer record, and the app asks Analytics on your phone to reset its identifiers; if the RevenueCat request fails or cannot be made, the record is kept under RevenueCat's own rules. Deleting the app does not delete your account or cancel a subscription; cancel in your App Store or Google Play account settings. Purchase records held by Apple and Google, any RevenueCat record that remains, and analytics, crash and service data already sent to Google are not removed by the deletion in the app and age out under those providers' rules.
On iPhone the sign-in can survive a reinstall in the system keychain, and Android Auto Backup can restore it. A new install that finds an earlier account shows a "Welcome back" screen where you continue or choose "Start fresh", which deletes the earlier account. If you lose your phone without either of these, you lose access to the account.
To ask for deletion without the app, write to zeyrekseyfican@gmail.com and include your support code. Settings shows a support code, which is your account identifier; include it when you write to us so we can find your account. If you can no longer open the app, we may instead ask for details that only the account holder knows, such as your first name, your partner's first name and when you paired, before we act.
14. Your rights and choices
Wherever you live you can ask us what we hold about you, ask for a copy, ask us to correct it, delete it, restrict it or stop using it where the law gives you that right, withdraw a consent you gave, and complain. In the app you can switch notification categories off, change or remove your photos, delete your notes, drawings and places, pause or unpair, and delete your account. To use a right that the app does not offer, write to zeyrekseyfican@gmail.com and include your support code from Settings. We may ask for details linked to your account to check who you are. We answer within one month (45 days for US state laws, 30 days for requests under the Turkish law); we do not treat you differently for using a right. If we refuse a request you can appeal by replying to our message, and we answer within the period the law sets. An authorised agent can write on your behalf with proof of authority. If the data protection law where you live gives you other rights, we honour them: write to us and tell us where you live.
15. Additional information for the EEA and UK
The controller is named in section 2. Under the GDPR and the UK GDPR you have the right of access, rectification, erasure, restriction, data portability and objection (articles 15 to 21), and the right not to be subject to a decision based solely on automated processing with legal or similarly significant effects (article 22). We do not make such decisions. Where processing rests on consent (usage and crash sharing in the regions where it starts off) you can withdraw it at any time with the Share usage and crash data switch in Settings, without affecting earlier processing. You can complain to your local supervisory authority; 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 a first name and the anonymous identifier is needed to use the app; everything else is described as optional in section 4. The legal bases are in section 7 and the recipients in section 10.
16. Additional information for US residents
We extend the rights below to all US residents. 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. We therefore have no opt-out link for sale or sharing, and an opt-out preference signal changes nothing.
| California category | Examples | Source | Disclosed to |
|---|---|---|---|
| Identifiers | Account identifier, name or nickname, push token, installation identifier, IP address | You, your device | Service providers (Google (Firebase), RevenueCat) |
| Commercial information | Subscription status | Stores, RevenueCat | Service providers |
| Internet or other electronic network activity | App usage events, crash reports, search text | Your device | Service providers; Photon (komoot) for search text |
| Geolocation data | Rounded device location, saved places, map area | Your device, you | Service providers; OpenFreeMap; your partner |
| Audio, electronic, visual or similar information | Photos you upload | You | Service providers; your partner |
| Other personal information | Notes, drawings, answers, widgets | You | Service providers; your partner |
| Inferences | Streaks and counters computed from your actions | Our systems | Service providers; your partner |
Sensitive personal information we collect: location rounded to about 1 km (and the coordinates, to about one metre, of a pin you drop for place search) and the content of your notes. We use it only to provide the service you asked for. Rights: to know, delete, correct, and to limit the use of sensitive information (we use it only for the purposes above). Submit a request at zeyrekseyfican@gmail.com, with your support code from Settings; we verify it against details tied to your account. Retention periods are in section 12. This policy was last updated on 11 October 2026.
17. Additional information for Türkiye
For users in Türkiye the data controller is Seyfi Can Zeyrek, an individual data controller in Türkiye. Your personal data is also described in the separate information notice under Law no. 6698 (KVKK) for Duet. That notice is an information text; it does not ask for consent. Under article 11 of the law you may ask whether your data is processed, request information, learn the purpose, learn the recipients in Türkiye or abroad, request correction or deletion, object and claim compensation. Apply in writing at zeyrekseyfican@gmail.com; we answer within thirty days. The Turkish notice is available at https://duet.morrowline.app/en/kvkk/ and from Settings when the app is in Turkish.
18. Children
Duet is not for people under 13, or under the age at which the law of your country lets you use an online service without a parent's agreement, if that is higher. We do not knowingly collect personal data from people under 13. If we learn that we have, we delete it. A parent who believes a child has used Duet can write to zeyrekseyfican@gmail.com.
19. Security
We protect your data with these safeguards. Data travels between the app and our servers over encrypted connections. Access rules on the database and storage limit who can read each record, and your private settings and purchase record are readable only by you and our systems. Our server functions require attestation from the app (Play Integrity on Android, App Attest or DeviceCheck on iPhone) and limit repeated requests. Stored data sits with Google's cloud services, which encrypt it at rest. The anonymous sign-in is kept in the system keychain or app storage of your phone. No system's security is perfect. Lock your phone, keep your invite code to the person you intend, and remove the app from phones you no longer use. We will tell you and the authorities about a breach as the law requires.
20. Changes to this policy
When we change this policy in a material way, for example a new type of data, a new recipient or a new purpose, we tell you in the app and update the date above before the change applies. Earlier versions are available on request. If a change needs your consent, we ask for it again.
21. Contact
Seyfi Can Zeyrek (individual developer; publisher name on Google Play: Morrowline), Esenyalı Mahallesi, İzmir, Türkiye. Email: zeyrekseyfican@gmail.com. We answer within one month. For users in the EEA and UK, the details above are the trader details and you can also contact your local data protection authority. For users in Türkiye, applications under the KVKK are made as described in section 17.
