Effective date: 18 September 2026 · Previous version: 7 September 2026
You may delete your account at any time, without giving a reason and without paying a fee. This page sets out the two routes to deletion, which data is erased, and which data is retained — on what legal ground and for how long.
Data controller. In this document, "we" and "Traknock" mean the service provider established in Türkiye that acts as the data controller within the meaning of Art. 3/1-(ı) of Turkish Law No. 6698 on the Protection of Personal Data ("KVKK"), and as the controller within the meaning of Art. 4(7) GDPR. As of today the controller is a natural person — Fahri Selçuk, trading under the name Traknock; KVKK Art. 3/1-(ı) expressly provides that a data controller may be a natural person. The obligations set out in this document are in force today, independently of the incorporation of a company, and bind the controller as of today.
Telephone: +90 533 598 34 09. The full postal address for service of notice will be entered in this section, and the trade name will be added once incorporation is completed; this document will be updated on the same day. Until then, the absence of those details does not extinguish the controller's obligations under the KVKK or the GDPR: you may submit your request through the channels listed on this page, and if you receive no answer you may use the complaint routes in section 14.
Undertaking. The app will not be released on any app store, and in-app purchases will not be enabled, before those identity details are published. This sentence is not a description; it is a binding term of this document.
Contact for requests: privacy@traknock.com · info@traknock.com
This document serves two functions at once:
The full inventory of personal data processed by the app, the purposes of processing and the legal grounds are set out in the Privacy Policy. This page does not replace it; it expands on it as regards deletion. In the event of any conflict between the two documents, the provision more favourable to the data subject applies.
The grounds for a deletion request and for the undertakings given in this document:
The Turkish Regulation defines these three operations separately (Art. 4) and requires the data subject to be told which one has been applied. In Traknock, deletion and destruction are applied today; anonymisation is provided for but is not yet applied (see section 9).
| Operation | Definition | Where it applies in Traknock |
|---|---|---|
| Deletion (silme) | Rendering the data inaccessible and unusable in any way for the relevant users (Regulation Art. 4, Art. 8). | Removal of the profile record and its sub-records from the cloud database; removal of photographs from the file store. |
| Destruction (yok etme) | Rendering the data inaccessible, irretrievable and unusable in any way by anyone (Regulation Art. 4, Art. 9). | Removal of the local records and photograph files held on your device; closure of the authentication account. |
| Anonymisation (anonim hâle getirme) | Rendering the data incapable of being associated with an identified or identifiable natural person, even when matched with other data (Regulation Art. 4, Art. 10). | Provided for in respect of messages posted in general and street chat: the message text is to remain part of the shared conversation while the link to the account is severed. This operation is not applied today; the undertaking and the present position are set out in section 9. |
Anonymisation is not destruction. Data that have been properly anonymised no longer meet the definition of personal data in KVKK Art. 3/1-(d) and therefore fall outside the scope of that Law; under GDPR Recital 26 they likewise fall outside the scope of the GDPR. The content itself, however, does not disappear. We do not conceal this: section 7 states which data are deleted, section 8 which are retained, and section 9 which records today remain linked to your account.
This route takes effect immediately and requires no further approval:
The records listed in section 7 are deleted the moment you confirm. The operation is free of charge and you do not have to give a reason.
Possibility of partial failure — stated openly. Deletion is carried out separately on a number of records. If one of those operations fails because of a network interruption or a technical fault, the process does not stop: the remaining records continue to be deleted and the failed record may remain undeleted. Likewise, if closure of the authentication account fails, your profile and content records are nevertheless deleted. In either case you may submit a request in respect of the remaining record through the channel in section 5; that request is concluded within the period stated in section 5.3 and free of charge.
If you cannot access the app, or if you want the deletion to be documented, you may send your request directly to the data controller.
If you are outside Türkiye — including in the European Union, the United Kingdom and the United States — an email to privacy@traknock.com stating your in-app username is sufficient. No particular form is required.
If you are in Türkiye and wish your application to take the statutory form, Art. 5 of the Communiqué on the Procedures and Principles of Application to the Data Controller provides that an application may be made in writing, or by registered electronic mail (KEP), secure electronic signature, mobile signature, or by using an email address previously notified by the data subject to the controller and registered in the controller's system, or through software or an application developed for the purpose of the application.
A Traknock-specific point, stated openly: the app does not collect email addresses. For that reason the "email address registered in the controller's system" route cannot in practice be used today. The postal address for written applications will be published on this page together with the identity details. This gap does not result in your request being refused: deletion requests sent to privacy@traknock.com are processed and concluded as if they were applications made in the statutory form.
Applications made in Türkiye must contain the elements listed in Art. 5(2) of the Communiqué: name, surname and, where the application is in writing, signature; Turkish identity number for citizens of the Republic of Türkiye, or nationality, passport number and identity number if any for foreign nationals; residential or business address for service of notice; email address, telephone and fax number if any; and the subject matter of the request.
In addition, and whatever your country of residence, you must state your in-app username so that we can verify that the account is yours. Because sign-in is anonymous, we have no means of matching an account to any information other than the username. This is requested solely for identity verification and in accordance with the principle of proportionality; we ask for no other document.
We conclude your request as soon as possible according to its nature, and in any event within thirty days, free of charge (KVKK Art. 13/2; Regulation Art. 12(1)(a)). This period is shorter than the one month allowed by GDPR Art. 12(3) and than the forty-five days allowed by Cal. Civ. Code § 1798.130(a)(2), and we apply it to every data subject regardless of residence. Where an operation entails an additional cost, the fee set out in the tariff determined by the Turkish Personal Data Protection Board may be charged; we undertake to charge no fee for account deletion requests.
Where all of the conditions for processing personal data have ceased to exist, the data in question are deleted, destroyed or anonymised. Where those conditions have not all ceased to exist, the request may be refused with reasons stated, and the refusal is notified within thirty days at the latest, in writing or electronically (Regulation Art. 12(1)(c); KVKK Art. 13/3). Where the data have been transferred to third parties, those parties are also notified (Regulation Art. 12(1)(b)). The table in section 8 shows in advance in which cases and on which ground such a refusal may arise.
Cancel your subscription before deleting your account.
A Prime subscription is administered through Google Play. Deleting your account, uninstalling the app or changing your device does not cancel that subscription; it continues to renew on its own and your Google Play account continues to be charged.
How to cancel: Google Play → Menu → Subscriptions → Traknock → Cancel subscription.
We give this warning by way of prior information and for the protection of the consumer. Because collection and refund of the subscription price are operated through Google Play, the fastest route for a refund request is Google Play's own refund process. That does not prevent you from coming to us: you may also send your request to the address in section 11, and we will consider it and tell you the outcome with reasons. Nothing in this notice limits the rights you have under consumer protection legislation.
The following records are removed the moment you confirm deletion of your account:
| Data | Where it is held | Operation |
|---|---|---|
| Your entire profile record: display name, username, about text, location, heading and speed, vehicle details and licence plate, driver status, list of users you have blocked, friend list, reputation score, violation counters, Prime status and the server-side copy of your token balance | Cloud database | Deletion |
| Your username reservation | Cloud database | Deletion |
| The private record holding the address of your profile photograph | Cloud database | Deletion |
| The record of who viewed your profile | Cloud database | Deletion |
| Your device's notification address (push notification tokens) and your undelivered gift box | Cloud database | Deletion |
| Profile and vehicle photographs you uploaded — both the device copy and the server copy | File store and device | Deletion and destruction |
| Photographs you sent in conversations | File store | Deletion |
| Your account identifier within the per-device account limit record (for the rest of that record, see section 8) | Cloud database | Deletion |
| Your authentication account | Authentication service | Destruction |
| Your session record, account archive and local photograph files on your device | Device | Destruction |
KVKK Art. 7 does not confer an absolute right to erasure; where the grounds requiring processing persist, the data are retained. GDPR Art. 17(3) provides for exceptions to the same effect. The records below are retained after your account is deleted. Each row states the legal ground and the retention period.
| Data retained | Legal ground | Retention period |
|---|---|---|
| Messages you posted in general and street chat. The message text is part of a shared conversation; removing one party's records afterwards would corrupt the content other users have read. | As regards retention of the message text: KVKK Art. 5/2-(f) — the legitimate interest of other users in the integrity of the conversation; GDPR Art. 6(1)(f). No such ground exists for the account identifier and the display name attached to the message; their removal from the record is undertaken in section 9. | The text, indefinitely. Severing the link to the account (anonymisation within the meaning of Regulation Art. 10) is not applied today — see section 9. |
| Your messages in one-to-one conversations. The other party to the conversation holds a separate interest in the record of the message sent to them. | KVKK Art. 5/2-(f) — the legitimate interest of the other party; GDPR Art. 6(1)(f) and, as regards the protection of claims, Art. 17(3)(e). | Until the conversation is deleted by the other party. Photographs sent to you by the other party fall within the same scope. |
| Road reports you submitted. These are not deleted at the moment your account is deleted; they are deleted automatically by the server once the lifetime set for their type expires. | KVKK Art. 5/2-(f) — the road safety interest of the other drivers who see the report. | Depending on type, at least 30 minutes and at most 24 hours: traffic 30 minutes, help request 1 hour, road cleared 1 hour, crash 2 hours, ice 6 hours, warning 12 hours, information 24 hours. The clean-up job runs every 30 minutes. |
| Confirmation and abuse votes you cast on other users' reports. The list of voting accounts is held on the report itself. | KVKK Art. 5/2-(f) — preventing multiple votes on the same report and preserving the reliability of reports. | Limited to the lifetime of the report; deleted together with it. |
| Moderation records. The original text of a message blocked by automated content review (up to 500 characters), its category and your account identifier. | KVKK Art. 5/2-(e) — necessary for the establishment, exercise or protection of a right: so that an automatically imposed ban remains auditable afterwards and defensible in the event of an objection. Also the hosting provider obligations under Art. 5 of Law No. 5651. | 1 year maximum. On expiry the records are destroyed. As to the applicable period: for a controller that is obliged to prepare a personal data retention and destruction policy, Regulation Art. 11(2) requires the periodic destruction interval not to exceed six months; a controller under no such obligation must, under Art. 11(3), carry out destruction within three months of the date on which the obligation arises. The controller currently falls into the second group, so the binding period is three months. Technical implementation of the destruction job will be completed before the app is released on any app store. |
| Abuse reports. The reporting and reported accounts, the reason given and, where applicable, the text of the content removed. | KVKK Art. 5/2-(e) — establishment, exercise or protection of a right; the evidential interest of both the reporting user and the user reported. GDPR Art. 17(3)(e). | 1 year maximum. Subject to the same destruction regime as moderation records. |
| Administrator action log. By whom, when and on what grounds a sanction was applied to you. | KVKK Art. 12/1 — the obligation to ensure data security and the traceability of operations; Art. 5/2-(e). | 1 year maximum. Subject to the same destruction regime as moderation records. |
| Purchase records. Your account identifier, the product identifier, the Google Play order number and the purchase token. | KVKK Art. 5/2-(ç) — compliance with a legal obligation of the controller; and Art. 5/2-(f) — preventing a reward from being claimed twice on the same receipt. Because this record is used as an idempotency key, its deletion is not technically possible. | For the periods prescribed by tax and commercial legislation: 5 years under Art. 253 of Tax Procedure Law No. 213; and, after incorporation, 10 years for commercial books and records under Art. 82 of Turkish Commercial Code No. 6102. The longer of the two applies. |
| Per-device account limit record. Your account identifier is removed from this record (see section 7), but the record itself is not deleted. The record consists solely of an irreversible hash of the device identifier, salted with an app-specific salt; the raw device identifier is never transmitted or stored. | KVKK Art. 5/2-(f) — preventing abuse and the re-creation of a banned account. Once your account identifier has been removed, the record contains no data pointing to you. | Indefinitely (contains no data attributable to you) |
| Hosting provider traffic data. Access logs that must be kept under Law No. 5651. | KVKK Art. 5/2-(a) — expressly provided for by law; Art. 5 of Law No. 5651. | The period prescribed by that law: not less than one year and not more than two years. Stated openly: this obligation arises when the app is released. Because the app is not published on any app store today, we hold no access logs of this kind; this row will be updated once such logs begin to be kept. |
| Error and crash logs. Your account identifier may appear in technical logs. | KVKK Art. 5/2-(f) — ensuring the stability of the app and fixing faults. | 90 days, according to the service provider's own statement. |
This section is a declaration of a shortcoming in the present technical scope of the account deletion flow, and it is made deliberately. There is no legal ground requiring the retention of the records below; the sole reason they are not deleted is that the deletion flow does not yet cover them.
Our undertaking in respect of this shortcoming:
Data are held on Google Cloud infrastructure in the European Union
multi-region (eur3), and server-side operations run in the
europe-west1 region. This constitutes a transfer abroad
within the meaning of KVKK Art. 9; the ground for that transfer is
explained in the Privacy Policy. For data
subjects in the European Union, this means the data remain within the EU
while the controller is established in Türkiye.
The effect of deletion on third parties:
Under KVKK Art. 11/1-(f) and GDPR Art. 19 you may request that the deletion be notified to the third parties to whom the data have been transferred. On such a request we will make that notification, save where it proves impossible or would involve disproportionate effort, and we will inform you of the outcome.
Deletion cannot be undone. You may open a new account with the same username, but the old account's balance, conversations and reputation score do not come back.
Where you delete your account of your own volition, any unused token balance and the remaining term of your subscription become unusable in practice. That is the technical consequence of the operation. Because it is you who initiates the operation producing that result, we give this warning before you confirm deletion.
We do not raise this as a bar to a refund. Deletion of an account is not of itself treated by us as a ground for a refund; but this sentence does not limit, and may not be read as limiting, any mandatory refund or termination rights arising under consumer legislation. In particular: if you deleted your account without first cancelling your subscription, you may send us a claim in respect of the period that was paid for but that you were never able to use. We will consider it alongside Google Play's refund process and tell you the outcome with reasons. The warning in section 6 is given precisely so that this situation does not arise.
Rights reserved. This provision does not extinguish the rights you have under Turkish Law No. 6502 on Consumer Protection, nor, where applicable, any mandatory consumer rights under the law of your country of residence. If you consider that performance was defective, that an undertaking was not performed at all, or that a charge was taken without cause, you may send your claim to info@traknock.com and may also apply to the Turkish Consumer Arbitration Committee or the Consumer Court. For further detail: Purchase Terms.
What we recommend you do before deleting: cancel your subscription through Google Play (see section 6), use up any remaining token balance, and, if you wish, request a copy of your data (see section 12).
You have the right to request a copy of your data before deleting your account:
Scope and format. On request, all of the records listed in section 7, together with those records listed in section 8 that belong to you, are prepared and sent in JSON format; photographs you uploaded are attached in their original file formats. Records that would by their nature contain the data of other users (for example the text of messages written by the other party) are excluded in order to protect the rights and freedoms of others (GDPR Art. 20(4)).
Stated openly: there is no automated export tool today; the request is fulfilled manually. This does not affect the deadline — the request is still concluded within thirty days at the latest. To make a request: privacy@traknock.com.
Minors. Deletion of a child's account may be requested by the child or by the legal representative holding custody. Applications made by a legal representative require a document evidencing the authority to represent. Such requests are handled as a priority.
Third parties. If you are not a Traknock user but believe that a user's post contains your personal data (your photograph, your licence plate, your name), you may request removal of the content and erasure of the data. Send your application to privacy@traknock.com, describing where the content is located. Applications concerning infringement of personality rights under Law No. 5651 are also made to this address, and content found to be unlawful is removed from publication without delay.
Deceased users. Requests concerning the account of a deceased user are considered on production of a certificate of inheritance.
Türkiye. Where an application is refused, where the response given is found insufficient, or where no response is given within the time limit, you may lodge a complaint with the Turkish Personal Data Protection Board within thirty days of learning the controller's response and in any event within sixty days of the date of the application (KVKK Art. 14/1). A complaint to the Board may be made only after an application has first been made to the data controller (KVKK Art. 14/2). This does not extinguish your right to claim damages or to bring an action under the general provisions (KVKK Art. 14/3).
European Union. If you are in the EU, you retain the right to lodge a complaint with the supervisory authority of the Member State of your habitual residence, place of work or of the place of the alleged infringement (GDPR Art. 77) and the right to an effective judicial remedy (GDPR Art. 79).
California. If you are a California resident, you have the right to request deletion of your personal information (Cal. Civ. Code § 1798.105), to know what is collected (§ 1798.110), to have it corrected (§ 1798.106), and not to be discriminated against for exercising those rights (§ 1798.125). Requests are made to privacy@traknock.com and are answered within thirty days, which is within the forty-five-day period allowed by § 1798.130(a)(2). We do not sell personal information. The advertising identifier used to serve ads may nevertheless fall within the statutory definition of "sharing" for cross-context behavioural advertising; you can turn off ad personalisation or reset that identifier in your device settings, and Prime subscribers are shown no ads at all. Complaints may be addressed to the California Privacy Protection Agency or to the California Attorney General.
This document entered into force on 18 September 2026 and replaces the previous version dated 7 September 2026. It applies from the moment it enters into force; in respect of applications made earlier and not yet concluded, the version more favourable to the data subject applies.
This document is updated in the event of a change in legislation, a decision of the Turkish Personal Data Protection Board, a change in the operation of the app, or the remedying of the shortcomings set out in section 9. Updates are published on this page and the effective date at the top of the page is amended. Material changes are additionally notified inside the app.
The following matters appear in this version as undertakings and this document will be updated once they are fulfilled: entry of the trade name and full address on this page (see "Effective date and controller identity"); implementation of the destruction job for moderation, abuse report and administrator action records (section 8); and the addition of the records listed in section 9 to the account deletion flow — including severing the account link on general and street chat messages, and making the deletion call to the notification provider (section 10).
The Turkish version of this document is available at traknock.com/hesap-silme. The two versions are intended to have the same legal content; in the event of any discrepancy, the Turkish version prevails as between the parties, save where the English version is more favourable to the data subject.