What information must a personal data breach notice contain in Türkiye?
A personal data breach notice in Türkiye should contain more than a statement that 'some of your data may have been affected'. Under Turkish Data Protection Board Decision 2019/271, a controller's notice to an affected person must be written in clear and plain language and include at least when the breach occurred, the personal-data categories affected with a distinction for special-category data, the likely consequences, measures taken or recommended to reduce adverse effects and a contact route for further information. Those details allow a person to choose an appropriate response for passwords, banking, identity or a mobile line. It may be impossible to establish every technical fact in the first notice, but uncertainty should be stated and material updates supplied as the scope changes. The statutory duty to notify the Board belongs to the controller. Decision 2019/10 requires notification without delay and no later than 72 hours after the controller learns of the breach, followed by notice to identified affected people within the shortest reasonable time. That 72-hour rule is not the user's deadline for changing a password or filing a complaint. A notice should distinguish the date of the incident, its detection and notification. It should also state whether an attacker merely accessed data, extracted a copy or whether that point remains unknown. A person receiving an incomplete notice may request detail through the controller's verified application channel and begin risk-reduction measures without waiting for the investigation to finish. This article provides general legal information. The incident, data categories, continuing risk and rules in force on the relevant date can change the assessment.
The contract and responsibility
1. Verify the notice and request missing detail through an official channel Attackers may use a real breach to launch a second phishing wave, or invent a breach as a pretext. A familiar sender name, logo or some correct personal details do not prove authenticity. Instead of opening the message link, type the organisation's address, use its official application or call the number printed on the card or contract. Compare its public announcement and any breach announcement published by the Turkish Data Protection Authority. A genuine notice should explain the incident date, affected data categories, likely consequences, measures taken or recommended and a contact route in plain language. If it merely says that 'some of your data may be affected', ask in writing which account and period are involved and whether password, identity, contact, location, health or payment data is included. Do not answer a suspicious address by sending a fresh identity document. Use the controller application channel verified on the organisation's official website. 2. Separate the incident, detection and notification dates The date on which the breach occurred may differ from the date on which the controller learned of it. The Board's 72-hour measure concerns the controller's notification to the Board after awareness; it is not a user deadline automatically running from the beginning of the attack. A notice to the affected person should distinguish the incident period and detection date where known and provide an intelligible timeline instead of saying only 'recently'. Information unavailable in the first investigation may be identified as unknown and supplied progressively. That flexibility does not justify withholding a known material risk or postponing updates indefinitely. The recipient should preserve the first notice and later scope updates together. The date of notification to the Board may differ from the date on which the person was contacted. Once affected individuals are identified, they must be reached by an appropriate method within the shortest reasonable time. 3. Specify affected data categories and connect them to likely consequences A notice should move beyond a broad term such as 'account information' and identify affected categories such as name, email, password hash, national identity number, card data, location or health information. Risk changes depending on whether a password was stored in plain text or protected by a particular hash and whether payment exposure covers only a card number or also an authentication element. Special-category personal data should be distinguished. The controller should separate confirmed viewing, extraction or publication from a point that remains unverified. Likely consequences should then be connected to the data: email and telephone can support targeted phishing, identity data fraudulent applications, password reuse account takeover and financial data unauthorised transactions. A bare statement that no adverse effect is expected provides little useful risk information unless the finding on which it rests is explained.
Claims and evidence
4. Require practical measures taken and recommended The notice should distinguish measures taken by the organisation, such as terminating system access, rotating keys, ending sessions or beginning forensic review, from steps expected of the user. Advice to change a password should identify which accounts, the official page to use and the risk to other services where the password was reused. If card data was affected, the notice should point to the bank's official route; where identity and telephone data were combined, it should address SIM-change and targeted-phishing risk. Multi-factor authentication and review of sessions and recovery settings may be useful, but a notice should never ask for a one-time code, e-government password or a fresh identity copy. The contact point should provide a functioning route such as a complete web address, call centre or responsible unit rather than an unattended generic mailbox. Recommendations must be specific and accessible enough to reduce the person's actual risk. 5. Preserve evidence and make a breach-specific controller application Keep the notice email with its header, the text with sender and time visible, the application alert and the public announcement with dates. Record the time of password changes and any case number, not the password itself. Ask the controller which of your data was affected, whether the attacker only accessed or also extracted it, when the incident and detection occurred, which recipients had the data, what remediation was taken and what risk-reduction step applies to you. Use the rights in Article 11 to obtain information, correct inaccurate data and, where the conditions are met, request erasure or destruction. An erasure request does not mean every record must disappear instantly; statutory retention, evidence for a dispute and security logs may require separate assessment. Submit through the controller's current declared application route and preserve proof of delivery. If the scope changes, keep the original notice and every later update together so that the sequence remains clear. 6. Separate a Board complaint from fraud reports and compensation claims If the controller rejects the application, gives an inadequate answer or does not respond within the current statutory period, a complaint to the Board may be considered. The Authority's official Right to Complain page requires a controller application first and explains deadlines tied to learning of the response and to the original application date. Recheck those official rules on the filing date. The controller's 72-hour notification to the Board is not a complaint filed on behalf of the user. Nor does the user take over the controller's duty by completing a breach form. If there is an unauthorised transfer, identity misuse, threat or another sign of crime, bank measures and a police or prosecutor report are separate from the data-protection process. A personality-right or financial-loss claim also requires assessment of actual harm, causation and the competent court. Receipt of a breach notice does not by itself create automatic compensation. Official sources: https://www.kvkk.gov.tr/Icerik/5362/Veri-Ihlali-Bildirimi, https://www.kvkk.gov.tr/Icerik/5547/2019-271, https://www.kvkk.gov.tr/Icerik/2063/Sikayet-Hakki and https://dsy.usom.gov.tr/usom/23/07/230704143127_Kurumsal%20Siber%20Gu%CC%88venlik%20O%CC%88nlemleri.pdf.