GetDone Privacy Policy

Effective date: 28 September 2026 · Version: 1.6

This is the privacy policy for the GetDone mobile app (Android) and its web version. It also serves as the information notice required by Article 10 of Turkey's Personal Data Protection Law No. 6698 (KVKK). The Turkish text at veyronistudios.com/getdone/gizlilik is authoritative; this English text is a translation.

1. Data controller

The controller of your personal data is Berkay Atalay, trading as "Veyroni Studios". No company has been formed yet; the app is published on Google Play under a personal developer account.

• E-mail: veyronistudios@gmail.com
• Postal address for written applications: Ulu Cami Mahallesi, Kemalpaşa Caddesi, Ulus Meydanı Yeraltı Çarşısı No: 1, Antakya/Hatay
• Web: veyronistudios.com

2. What data we process

Most data is entered by you while using the app; some is generated automatically or results from actions of people in your connection or group (approvals, points, votes). Collection is fully automated, through the app and our servers. When you write to us by e-mail, your data is processed partly by automated means, in our mailbox.

Account. Your e-mail address and password. The password is stored only as a hash; we cannot see it. To confirm your address when you create an account, and to reset your password, we e-mail you a one-time 6-digit code. Sign-in with Apple or Google does not exist yet.

Acceptance of the Terms of Use. Which version of the Terms of Use you accepted and when (date and time).

Profile. Username, display name, the app language you chose and your device's time zone.

Connections and groups. Which connection or group you belong to, in which role (task giver / task doer) and for which period; invitation codes you create (stored only as a hash) and acceptance records.

Messages. Messages you write in connection and group chats, plus system lines such as task starts and departures. The departure line contains your display name at the moment you left.

Tasks and reports. Task title, description, schedule and targets; your progress reports and notes; approval or rejection decisions and their notes; outcome texts for missed work; your requests to leave a task and their reasons.

Points and rewards. Point movements and balances; reward definitions and their change history; reward claims, votes on them and notes.

Notifications. Event records in the in-app inbox (type, related connection or group, related task, the person whose action triggered it, limited status values, creation, read and closing times). No names, titles or text are stored. For notifications sent to your phone, see "Phone notifications" below.

Phone notifications (push). If you turn notifications on in the Android app, the record of your phone: the address the notification service gives your phone (push token), a random identifier the app creates for this installation, the platform (Android), the number of the session that registered it, when the record was created, last refreshed and closed, and why it was closed (sign-out, permission turned off, phone registered by another account, token no longer valid). The notification types you turned off on the notification settings screen. For each notification, whether it was sent to your phone, why it was skipped if it was, and the number of attempts. A notification sent to your phone carries only the name of the person who acted (or the nickname you gave them), a general sentence in your app language, the number of unread notifications, and the notification, chat or group and task numbers needed to open the right screen; it carries no task, note or reward text. The web version has no phone notifications.

Nicknames. A private nickname you give to a contact; only you see it.

Blocks and user reports. When you block someone, we record who you blocked, when, and the display name they had at that moment, so your list of blocked people can show it. When you report someone, we record who reported whom, in which connection or group, the reason you chose, your optional note (up to 500 characters) and the time; if you report a specific message, we also record which message it was and keep a copy of its text as it was when you reported it. While a report is reviewed we record the admin who took it on and when it was taken on and handed up to a senior admin; when it is closed we record the decision (no action, content removed from view, a warning, a temporary suspension, a permanent closure, or an account restriction), the reason for it, when it was made and by whom. If content is removed from view because of a report, we keep its original text and the text of the copies the app shows with the report.

Warnings, suspensions and permanent closures. If your account is given a warning, we record its category (for example harassment or spam), the related report if there is one, the admin who gave it, the date, and when you acknowledged it in the app. If your account is suspended or closed permanently, we record the category, when the suspension ends, the related report if there is one, the admin who did it, and the date. The reason the admin wrote is not shown to you; it stays in the admin action log. Every view and action an admin makes about your account in the admin panel is written to that log with your account number (section 4).

Permanently closed accounts. If we close an account permanently for breaking the Terms of Use, we keep, to stop a new account being opened with the same e-mail address, not the address itself but only a hash of it computed with a secret key (HMAC-SHA256), together with the account number and the date. The address cannot be read from the hash; the hash is compared only when someone tries to sign up again with the same address or to change an account's address to it, and when an authorised member of our team checks an address someone gives us, for example in an appeal, to find the closed account it belonged to. Upper and lower case and spaces before or after the address are ignored in the comparison. No such record is kept for a temporary suspension.

Photo and video evidence. This feature is currently switched off. Once enabled, the photo or video you attach to a progress report (including the sound track of a video) is processed together with its size, type, resolution, duration, a fingerprint (SHA-256) of the original file and any processing error code. Source metadata such as location is stripped on the server; the original file is deleted from the server once processing ends.

Technical records. The authentication component (Supabase Auth) writes, for session security, your IP address and device/browser information to the session record each time you sign in, and writes your sign-up, e-mail confirmation, sign-in, sign-out and password events together with your e-mail address and IP address to an authentication event log. These records live in the database of our Supabase project; they are not shown in the app and only the database operator can access them. The session record is deleted when you sign out or the session expires; the authentication event log is kept until your account is deleted (see section 7). Supabase's server access logs also keep your IP address for the provider's log retention period; we read them only for troubleshooting and security review. The same rule applies to the access logs of the media processing server and the web version once they are live. The app contains no advertising, analytics, crash reporting, location or contacts access.

Please do not write special categories of personal data (health, religion, political opinion and the like) into chats, notes or evidence; the app is not designed for them.

3. Purposes and legal bases

No processing relies on your explicit consent. Your data is used only for these purposes, never for marketing, profiling or advertising.

4. Who sees what inside the app

• Members of the same connection or group see your username, display name, messages and task details; they do not see messages or tasks from before they joined. Your point balances and point movements are visible only to you and to the task giver who awarded them; group point balances are visible to all task givers of the group. Other doers do not see your balance. Your progress reports, notes and (once enabled) evidence are visible only to the responsible people of that task, not to other doers in a group. If a task giver switched on the shared scoreboard for a task, the other people assigned to that task see only your approved total progress; your report texts and notes stay private. Group reward proposals and votes are visible only to that group's task givers.
• When you leave a group or connection, the messages, reports and evidence you sent stay visible in the remaining members' history; you can no longer see them. Tasks removed when you leave a group as a task giver are the exception (see section 7).
• Blocks are visible only to the person who made them; the blocked person is not notified. Blocking someone ends any one-to-one chat you share with them, wherever you block them from, and the other person sees that you left. In a group, neither of you sees the other's messages or appears in the other's member list, and other members are not told; the other person may still notice that your messages are gone. Shared tasks, points and rewards stay visible to both. User reports are visible only to Veyroni Studios' authorised staff (according to the roles below) and the database operator (including the contracted developer, section 5). The reported person is never told who reported them; if a report leads to a warning, a suspension or a permanent closure, the person sees that and its category in the app, and a warning also says that a report was reviewed. You cannot view a report after sending it, and you are not told its outcome.
• Admin panel and staff roles. Only people authorised by Veyroni Studios sign in to the admin panel, with admin accounts separate from app accounts, a password and two-step verification; an admin account cannot reach the app's data the way a user does. Every admin has one of three roles: the Super Admin and the Moderator review and decide reports; Support sees only the record details of reports and users, cannot open content and cannot take action. The panel's dashboard shows only totals (numbers of users, groups, tasks, reports and sanctions).
• Reviewing reports. All three roles see the report list and the report page: the display name and username of the person who reported and of the reported person, the report's reason, type, status and dates, the reported person's account status, the other reports about them (date, reason and status) and the number of warnings they received. Only the Super Admin and the Moderator see the reporter's note and the reported content. Content opens only from a report's page, each time by choosing an access reason (report review, safety review or a request from an authority) and writing a justification. For a message report, only the copy of the reported message as it was at report time opens. For a report about a person, only one kind of the reported person's own content in that connection or group opens: task texts, progress and outcome notes, review notes and rejection reasons, notes on requests to leave a task and on reward claims, rewards, group reward proposals, or the name of a group they created; notes open only as far as the person who reported could read them in the app. Chat messages never open this way; photo and video evidence cannot be viewed in the panel.
• Sanctions. In an open report, the Super Admin and the Moderator can remove from the members' view a single item that report can open; "Removed by GetDone" then shows in its place for everyone, and an item removed by mistake can be put back from the same report. These two roles can, as the outcome of a report or from the user page, give an account a warning shown in the app, and suspend an account for 1 to 365 days or lift the suspension; closing an account permanently and lifting the closure are for the Super Admin alone. Every action needs a reason; the person is shown only the category (for example harassment or spam), never the admin's reason. A suspended or closed account cannot read or write any data in the app, but can still delete itself.
• User search and user page. All three roles can look a person up by account number, by exact e-mail address (exact match only; the result never shows the e-mail address) or by the beginning of the username; an account that was closed permanently and then deleted by its owner is found through the e-mail hash described in section 2. The user page shows the display name, username, joining date, account status, the number of open connections and groups, the numbers of reports about the person and made by them, the latest reports about them, warnings and the moderation history; Support does not see the admins' reasons. The user page has no e-mail address, chats or content.
• Admin action log. Every opening of the report list, a report or a user page in the panel, every content opening (with its access reason and justification), every search (without the searched text) and every action is written to the audit log, which is never deleted, with the admin, their role, the time, the IP address and browser information. The system does not write the text of opened or removed content to this log. Only the Super Admin sees the whole audit log.
• Database operator. The controller, as the person operating the database, can access the database directly for technical maintenance, troubleshooting, security review, suspected abuse and lawful requests; such access is made only for these purposes. The same access applies to the contracted developer described in section 5. When the admin panel is not available, the database operator can review and close a report directly in the database: this review reads the report and its message copy, not the rest of the chat, and, when a report about a person describes a task text, a note, a reward or a group name, only that item. The operator can remove a single item from the members' view (the copy kept with a report stays with the report) and restrict the account; on this path a warning is sent by e-mail. The closure is written to the same audit log with the operator's name and reason.

5. Processors and transfers abroad

We do not sell your data or share it for marketing. These service providers process your data on our behalf and under our instructions:

The contracted developer who builds and technically operates the app may access the database as a processor, only on our instructions and for maintenance and troubleshooting; the "database operator" in sections 2 and 4 is whoever holds that role. A written confidentiality and data-processing agreement covers this access.

Google Play only distributes the app; the app sends no user data to Google Play (how phone notifications pass through Google's notification service is in the next paragraph). When you install or update the app from Google Play, the data Google itself collects (your Google account, device information) is processed by Google as an independent controller under its own privacy policy; it is not passed to us.

Phone notifications. When you turn notifications on, your phone's push token is obtained from Google's notification service (Firebase Cloud Messaging) and registered with our server. When a notification is due for your phone, our server sends the token and the short content described in section 2 to Expo's notification service; Expo passes it to Google, and Google delivers it to your phone. Expo and Google process this data to deliver it and keep it for their own retention periods.

Once photo and video evidence is enabled, files pass through a processing server we will operate on Railway (in the Netherlands) into Supabase's private storage; a file stays on that server only while it is processed.

Because Supabase's and Resend's servers are in Ireland, Railway's servers are in the Netherlands and Railway Corporation is based in the USA, this is a transfer abroad under KVKK Article 9. The safeguard relied on under Article 9/4 for transfers to these providers is the standard contract published by the Turkish Personal Data Protection Board. Phone notifications sent through Expo (USA) and Google (global infrastructure) are a transfer abroad too. Where the law requires it, your data may also be disclosed to competent public authorities.

6. Data on your device and permissions

• Session data is kept in the operating system's secure store on Android and in browser storage on the web; it is removed when you sign out.
• Your chosen language and unsent message drafts are stored on the device; drafts are removed once sent, when you leave the chat or when you sign out. The language choice stays on the device after sign-out.
• Because photo and video evidence is off, the app package does not declare the camera, microphone or storage permissions at all; they do not appear in your phone's permission list either. When the feature is turned on those permissions are added to the package and are requested only when you tap the button to add evidence; this policy is updated before that release. No location, contacts or advertising ID permission is requested.
• Phone notifications need the notification permission on Android 13 and later. The app does not ask for it when you first open it: it first shows its own explanation card and opens the system window only when you tap "Turn on notifications". If you do not allow it, the app works just the same; notifications wait in the app's inbox. You can take the permission back in your phone's settings at any time; your phone record is then closed. For notifications the app keeps a random installation identifier and your answer to the permission question on the device. When you sign out, the notifications on the phone are cleared and the phone record is closed.
• The time zone is read from your device's date/time setting; your calendar entries are not accessed. The device language is not read; the app opens in English until you choose a language.
• An invitation code is copied or shared only when you ask; the clipboard is never read. In the web version the shared invitation link contains the code.

7. Retention and deletion

• The basic rule: your data is kept until your account is deleted. This applies to your account, profile, messages, tasks, reports, approvals, points, rewards, notifications and membership history; records with their own period or rule below are the exception. The last item of this section explains what is deleted when your account is deleted and what stays in the other members' history, no longer linked to your name.
• The record of your acceptance of the Terms of Use is kept until your account is deleted; accepting a new version replaces it.
• The authentication event log (sign-up, e-mail confirmation, sign-in, sign-out and password reset events, with e-mail and IP address) is not deleted after a set period; it is kept until your account is deleted. When you delete your account, every entry in it that names you by your user number or your e-mail address is deleted.
• When you leave a group, your point movements in that group (points you earned and, if you are a task giver, points you awarded in your own point currency) are deleted immediately with no copy kept. If you leave as a task giver, your pending and active tasks in that group are marked "removed" and can no longer be seen by anyone, the personal rewards you defined become invisible, and pending reward claims and proposals are closed; those task, report, evidence and reward records are not deleted, only made inaccessible, and can be read only in a complaint or security review (the 90-day period in the next item applies to the evidence files). Your messages stay. Leaving a one-to-one connection deletes nothing.
• Photo and video evidence has two periods of its own: uploads never attached to a progress report are deleted 7 days after upload, and evidence files of removed tasks, which no one can see any more, are deleted 90 days after the task was removed. Because the feature is currently switched off, no such file can be uploaded; both periods apply once the feature is enabled. Other evidence files follow the basic rule.
• A nickname you gave to a contact is deleted as soon as you remove it.
• Your phone record (including the push token) is kept while the phone stays registered. When you sign out, turn off the notification permission, the phone is registered by another account or the token stops being valid, the record is closed and is deleted 30 days after closing. The record of whether a notification was sent to your phone is deleted 30 days after sending finished, and Expo's delivery ticket numbers after 2 days. Your notification settings are kept until your account is deleted.
• An account-restriction record (a suspension or a permanent closure: user id, category or reason, duration, the related report if there is one, and the admin who made it) is not deleted automatically when the restriction ends; it is deleted when the restriction is lifted or the account is deleted. A new suspension replaces the earlier one; the details of a replaced or lifted restriction stay in the admin action log.
• A warning record (section 2) is kept until your account is deleted; when the related report is deleted, the warning stays and only its link to the report goes.
• The e-mail address hash of a permanently closed account (section 2) is kept until the ban is lifted; deleting the account does not delete it. When the ban is lifted the hash is deleted at once and the address can be used again.
• A block is kept until you remove it (unblock) or either account is deleted.
• A user report (with its take-on, hand-up and closing details) is kept while it is open and for one year after it is closed, and is then deleted automatically. The kept original text of content removed from view because of a report is deleted with the report; if the removal is undone, it is deleted at once. Reports are not deleted when either account is deleted: the account is anonymised as described below, but the report, including the message copy and the original text of removed content, stays until that period ends.
• The admin action log permanently records the report and account actions taken in the admin panel and the database operator's report closures (opening a report, a user page or content, removing content from view and putting it back, warnings, suspensions, permanent closures and lifting them, taking on, handing up and closing a report: the report number, the account number concerned, the connection or group, the content type, the reason code and access reason, the decision, the restriction before and after, the admin or operator who acted and their reason), without any content or message text. It is not deleted when your account is deleted; your account number stays, no longer linked to your name.
• Admin panel login-attempt records (e-mail hash, IP address and browser information of whoever attempts) are deleted automatically after 30 days. Admin session records (including IP address and browser information) and the admin action log, which also records failed admin logins, are never deleted.
• Account deletion. In the app, Profile → Delete account deletes your account immediately and irreversibly. Deletion removes your e-mail address, password hash, sessions, authentication event log, settings, nicknames, blocks, notifications, phone records and notification settings, warning and account-restriction records and your Terms of Use acceptance record; your profile is anonymised (your name and username are removed); you leave every chat and group you are in (the rules for leaving a group apply: the pending and active tasks you created are marked "removed" as described above, and your point movements in those groups are deleted). Your messages remaining in other members' chats, the reports and evidence you submitted, and the points other members earned are not deleted (the 7-day and 90-day periods for photo and video evidence above still apply); "Deleted member" (in the app's language) appears in place of your name and cannot be linked to your account. Reports you made and reports about you are kept for the period above. The deletion date and the (anonymous) account number are kept in the operations log. If your account was closed permanently, the hash of your e-mail address is not deleted and stays until the ban is lifted, as described above; your right to delete your account is not affected. If you cannot access the app, write "Delete my account" to veyronistudios@gmail.com from the e-mail address registered in your account; your request is completed the same way within 30 days at the latest.

8. Security

Data travels between device and server encrypted with TLS. Row-level security rules in the database show each record only to the members entitled to it. Evidence files are kept in a private bucket and opened only through signed links valid for 60 seconds. Passwords and invitation codes are stored only as hashes. A permanent ban keeps only a hash of the e-mail address, not the address itself; the key for that hash sits in the database's encrypted secret store (Vault) and is used only by the server's matching and lookup functions. Push tokens are kept in tables the app cannot read and only the server can reach. The admin panel requires two-step verification (TOTP), and every admin action is written to a chained, tamper-evident audit log that is never deleted. In the panel the permission for every action is checked in the database against the admin's role; reported content opens only through the report record, with an access reason and a justification. The panel's server holds no secret key with full access to the database. If we learn of a data breach, we inform you and the Personal Data Protection Board as soon as possible, as KVKK Article 12 requires.

9. Your rights (KVKK Art. 11)

By applying to us you may:

• learn whether your personal data is processed,
• request information if it has been processed,
• learn the purpose of processing and whether the data is used accordingly,
• know the third parties to whom it is transferred in Turkey or abroad,
• request correction of incomplete or inaccurate data,
• request deletion or destruction under KVKK Article 7,
• request that corrections, deletions and destruction be notified to third parties who received the data,
• object to a result against you produced exclusively by automated analysis,
• claim compensation for damage caused by unlawful processing.

How to apply. Write to veyronistudios@gmail.com from the e-mail address registered in your account; send an application signed with a secure electronic signature or mobile signature to the same e-mail address; or deliver a hand-signed written application to the address in section 1, in person or through a notary. Include your name and surname (and your signature if the application is in writing), your Turkish ID number (for foreigners: nationality, passport number or ID number if any), your residence or business address for notifications, an e-mail address and telephone number for notifications if you have them, and the subject of your request. Applications are concluded free of charge within 30 days at the latest; where the operation involves a separate cost, the fee in the Board's tariff may be charged. Formal applications are made in Turkish; we also answer questions in other languages. If your application is rejected, the answer is insufficient or no answer is given within 30 days, you may complain to the Personal Data Protection Board within 30 days of learning the answer and in any case within 60 days of applying. You must apply to us first before complaining to the Board.

10. Children

GetDone may be used by people aged 16 or older; it is not directed to anyone under 16. If you are under 18, use GetDone with the knowledge of a parent or guardian (Terms of Use section 3). If we learn that a person under 16 has created an account, we close it, delete it as described in section 7 and remove the messages it sent from the other members' view. You can report such a case to veyronistudios@gmail.com.

11. Changes

When we change this policy, we publish the new Turkish version at veyronistudios.com/getdone/gizlilik and this translation at veyronistudios.com/getdone/privacy, and update the version number and effective date on both. Every version is also published at its own address, which carries the version number (for example veyronistudios.com/getdone/privacy/1.6). We announce significant changes inside the app. Before processing your data for a new purpose, we inform you separately.

12. About this document

• Version 1.6, effective 28 September 2026 (phone notifications (push), Expo and Google Firebase Cloud Messaging: sections 2, 3, 5, 6, 7 and 8; versioned publication address: sections 11 and 12; added before publication on 28 September 2026: the e-mail address hash of a permanently closed account: sections 2, 3, 7 and 8; added before publication on 1 October 2026: report review and moderation in the admin panel (staff roles and what each sees, content opening only through a report, removal from view, warnings, suspensions and permanent closures, the admin action log and retention periods) and hosting the admin panel's server on Railway, with the transfer abroad: sections 2, 3, 4, 5, 7 and 8). Earlier versions were updated before publication: 1.5 (26 September 2026; age limit raised from 13 to 16: section 10; retention rules, keeping the authentication event log until the account is deleted, and the 7-day and 90-day periods for photo and video evidence: sections 2 and 7; on account deletion a task giver's pending and active tasks are marked "removed", not deleted: section 7; in the Turkish interface the in-app link opens the Turkish original: section 12), 1.4 (24 September 2026; sign-up confirmation code and Terms of Use acceptance record: sections 2, 3, 5 and 7; removing single items from view and reading the item a report describes: section 4; accounts of children under 13: section 10; link to the Terms of Use), 1.3 (24 September 2026; blocking and user reports: sections 2, 3, 4 and 7), 1.2 (22 September 2026; section 6: with evidence off, the package no longer declares those permissions), 1.1 (in-app account deletion) and 1.0 (22 September 2026).
• App: GetDone. Developer: Berkay Atalay (Veyroni Studios).
• This translation is published at veyronistudios.com/getdone/privacy, and this version also at veyronistudios.com/getdone/privacy/1.6; the authoritative Turkish text is at veyronistudios.com/getdone/gizlilik (and veyronistudios.com/getdone/gizlilik/1.6). Both are reachable from the Google Play listing and from the "Privacy Policy" link on the app's sign-in and sign-up screen, the "Updated Terms" screen and the profile sheet. In the app, the link opens the Turkish original in the Turkish interface and this translation in every other language.
• Terms of Use: veyronistudios.com/getdone/terms (the authoritative Turkish text is at veyronistudios.com/getdone/kosullar).
• The Turkish text is authoritative; in case of conflict it prevails over this translation.
• Earlier versions and their change dates are available on request.