Does closing an account also erase personal data?
Someone who closes an account on a shopping website may assume that their telephone number, address and purchase history have also been removed from the system. However, closing an account and erasing personal data are separate processes. The company may be legally required to retain certain records. It cannot, however, retain information it no longer needs indefinitely simply because it might use it in the future. Closing the account to the user does not, by itself, establish what has happened to the underlying records.
The Turkish Personal Data Protection Law No. 6698 (KVKK) gives individuals the right to request information about their personal data. They may also request erasure where the relevant conditions are met. This right is not limited to online accounts. Records held by a former employer, gym, hotel or other service provider may also fall within its scope. If an individual does not know what information is held, they may ask for this to be explained in their application.
The Law protects information relating to natural persons. Information relating solely to a legal entity, such as a company's registered business name, falls outside its scope. However, a company representative's name, personal telephone number and other identifying information may constitute personal data. Companies must also assess applications from employees and customers concerning their own data. The exceptions under the Law and any special provisions must also be taken into account.
Must a company accept every erasure request?
The right to erasure does not mean that all records must be removed unconditionally whenever an individual requests it. Under Article 7 of the Law, an obligation to dispose of personal data (imha) arises when the reasons requiring its processing cease to exist. Each item of data and each purpose of use must be assessed separately. There may be a legal requirement to retain a particular record, while the grounds for retaining other information about the same individual may have ended.
For example, legislation may require certain transaction documents to be retained even after the customer relationship has ended. Records necessary to protect a right in an existing dispute may also be retained. However, the company must explain what information it retains and the legal grounds for doing so. A general need to maintain an archive or an unspecified possibility of litigation does not, by itself, justify retaining an entire customer file indefinitely.
Withdrawing explicit consent does not necessarily require all data to be erased. Uses based on consent may cease while mandatory retention based on another legal ground continues. However, a ground for retention does not authorise the use of the data for other purposes. The right to retain a transaction document does not automatically make it lawful to use the telephone number in that document for advertising. Each use must have its own legal basis.
To whom should an erasure request be sent, and how?
The application must be sent to the data controller, which determines the purposes and means of processing the data. This will usually be the company or organisation providing the service. The website's privacy notice, the contract and invoice details can help identify the correct recipient. The brand name may differ from the company's registered name. Simply messaging the brand's social media account may not establish that a valid application has been made.
The Communiqué on the Procedures and Principles for Applications to Data Controllers provides for several application methods. Applications may be made in signed written form, by registered electronic mail (kayıtlı elektronik posta, KEP), or using a secure electronic signature or mobile signature. Individuals may also apply from an email address previously provided to the data controller and registered in its system. Software or applications developed for this purpose may also be used. The application must be made in Turkish.
For written applications, the application date is the date on which the document is served on the data controller or its representative. For other methods, the relevant date is likewise the date the application reaches the data controller. Delivery and transaction records should therefore be retained, along with a copy of the application itself. Proof of dispatch alone does not always establish what request was submitted. These documents help determine the deadlines for responding and lodging a complaint.
What information and requests should the application contain?
The application must include the applicant's first name, surname, residential or business address for service and the subject of the request. A written application must be signed. Turkish citizens must provide their identity number. Foreign nationals must state their nationality and passport number or, if available, their identity number. An email address, telephone number and fax number for notifications should also be included, where available. Relevant information and documents must be attached.
The scope of the request should be clear. A membership number, the telephone number used or a transaction date can help identify the records concerned. If the individual does not know what data is held, they may ask what it is and for what purposes it is processed. They may request erasure or destruction of data where the grounds for processing have ended. For records that will continue to be retained, they may ask for an explanation of the legal basis and retention period.
If data has been transferred to others, the application may also cover those records. The individual may request that third parties to whom the data was transferred be notified of any erasure or rectification. If information is inaccurate, the request for rectification should be set out separately. The application should do more than express dissatisfaction. On reading it, the data controller should be able to identify the information concerned and the action requested.
How long does the company have to respond?
The data controller must resolve the application as soon as possible, depending on the nature of the request, and no later than thirty days. If the request is accepted, the necessary action must be taken. Where all grounds permitting processing have ceased to exist, merely acknowledging receipt is insufficient. The data controller must erase, destroy or anonymise the data covered by the request. It must also inform the individual of the outcome.
The data controller must communicate its final response in writing or electronically. According to the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu), a telephone conversation cannot replace this response. The company may call the individual to clarify the request. However, it must separately explain which requests it has accepted and which it has rejected, giving reasons for any rejection. This allows both the scope of the action taken and the date on which the response became known to be established.
The company's own periodic disposal schedule does not extend the thirty-day deadline for responding to an individual's application. A data subject's request and the company's disposal process carried out on its own initiative are governed by separate rules. If data whose processing grounds have ended has been transferred to third parties, the data controller must also inform those parties. It must ensure that they take the necessary action under the Regulation.
Are erasure, destruction and anonymisation the same?
These operations have different effects. Erasure makes the data inaccessible and unusable by the relevant users. Destruction makes the data inaccessible, irretrievable and unusable by anyone. Anonymisation irreversibly breaks the link between the data and the individual. If the individual can be identified again by matching the data with other information, it has not been genuinely anonymised.
The fact that an account no longer appears on screen does not, by itself, prove that any of these operations has been performed. The company must also take the technical and organisational measures required by its chosen method. Under the Regulation, the data controller may select the appropriate disposal method unless the Personal Data Protection Board decides otherwise. When selecting a method in response to a data subject's request, it must explain its reasons. A request for destruction does not mean that this particular method must be used in every case.
The Council of State (Danıştay) judgment dated 19.12.2024, case no. 2023/1921 and decision no. 2024/3448, concerned a regulation on camera recordings in private educational institutions. The panel upheld the dismissal of the action challenging the regulation. The reasoning upheld in the judgment stated that the periods set out in the general disposal regulation would apply even if the specific regulation did not prescribe a retention or erasure period. The judgment assessed the lawfulness of the regulation concerning camera recordings, rather than an individual erasure application.
What can be done if the request is rejected or no response is received?
Before lodging a complaint with the Personal Data Protection Board, the individual must first exhaust the application procedure before the data controller. A right to complain arises if the request is rejected, the response is considered inadequate or no response is given within thirty days. An individual who receives an early rejection need not wait until the thirty days have elapsed. A complaint sent directly to the Board without first applying to the data controller does not satisfy this prerequisite.
Article 14 of the Law provides a complaint period of thirty days from the date on which the individual learns of the response. An overall limit of sixty days from the initial application also applies in every case. If the company responds within the prescribed period, the individual must complain within thirty days of learning of the response. They must not let this period expire on the assumption that they can wait until the sixtieth day. If no response is received, the complaint must be lodged after the thirty-day response period but before the overall sixty-day limit expires. A late response does not restart that overall period.
The complaint should include the application, delivery or dispatch records and any response received. It should explain specifically which request has not been met. The Authority's electronic complaint channel may be used. If the initial application only asked about the source of the data, requesting erasure for the first time in the complaint may create a procedural issue. The requests submitted to the data controller should therefore be compared with the scope of the complaint brought before the Board.
Can the Board order erasure and award damages?
If the Board finds a breach, it may order the unlawful situation to be remedied. Depending on the circumstances, this may include disposal of the data. However, lodging a complaint does not guarantee that every record the individual wants removed will be erased. The Board also assesses the legal basis for processing, any obligation to retain the data and the scope of the request. Special provisions governing areas such as health records and judicial records must be examined separately.
The Board is not a court empowered to award an individual damages for pecuniary or non-pecuniary loss. An individual whose personality rights (kişilik hakkı) have been infringed retains the right to seek damages under the general provisions of law. Such a claim requires an assessment of the infringement, the loss and the causal link between them. Rejection of an erasure request does not, by itself, establish an entitlement to damages. The nature of the dispute also affects the appropriate judicial route.
The requirement to apply to the data controller first applies to complaints to the Board. The same prerequisite cannot be assumed to apply in every case involving recourse to the courts. The conditions and time limits governing the Board procedure and judicial claims must be assessed separately. Application documents, company responses and records showing continued use of the data should be retained. These documents may establish both the scope of the request and what happened after the application.
Frequently Asked Questions
Must an application for erasure of personal data be made through a notary?
No. In addition to a signed written application, the electronic methods specified in the Communiqué may be used. The chosen method should allow the content of the application and the date it reached the data controller to be documented.
Does cancelling an account require all purchase records to be erased?
No. Records subject to a legal retention obligation may be kept after the account is closed. Retention of other data must also have a valid ground for processing. Closing an account does not give the company a right to retain all data indefinitely.
Is withdrawing explicit consent the same as requesting erasure?
No. Withdrawing consent affects uses of data based on consent. An erasure request is assessed against all legal grounds requiring the data to be processed. Where necessary, both requests may be expressly included in the same application.
Is it sufficient for the company to say over the telephone that the data has been erased?
A telephone conversation cannot replace the final written or electronic response required by the legislation. The data controller must communicate the outcome of the application by one of those methods. The notification should clearly explain the extent to which the request has been met.