Skip to main content

KVKK checklist for online stores in Türkiye

What KVKK asks of an online store in Türkiye, a 12-point checklist, what the regulator actually inspects, the common mistakes and the penalties.

Enes Özkan, Founder and CEO9 min read

12 points

TL;DR. If your shop collects customer data, KVKK applies: publish a privacy notice, ask for consent only where you rely on it, answer data requests, and keep data safe and only as long as you need it. Most small shops, with fewer than 50 employees and a balance sheet under 100 million TL, don't have to register with VERBİS, and transfers abroad follow new rules since 1 June 2024.

Note: General information, not legal advice, and not a statement that FaStart or any shop is compliant. Thresholds and official guidance change, so check them with the Kişisel Verileri Koruma Kurumu and a qualified lawyer before you rely on this list.

KVKK (Kişisel Verilerin Korunması Kanunu) has been in force since 2016, and its Board publishes decisions and guidance. Fines depend on the case, so use this list to find your gaps, not to predict a penalty.

What KVKK requires (the short version)

KVKK regulates "personal data", anything that identifies a person directly or indirectly. For an e-commerce site this means name, address, email, phone, IP address, billing details, browsing history, and order data. The law gives data subjects rights set out in Article 11. The exact scope and procedure should be checked against the current Turkish text and the applicable application rules rather than inferred from a translated checklist.

Your obligations as a "Data Controller" (Veri Sorumlusu):

  • Publish a privacy policy and cookie policy that are specific to your business, not template boilerplate.
  • Collect personal data only for explicit, lawful purposes and only as much as you actually need.
  • For each processing purpose, document the applicable legal ground; obtain separate, specific consent only where consent is the appropriate ground (marketing is not the same purpose as fulfilling an order).
  • Check whether VERBİS registration applies under the current Board decisions and any available exemption; customer count alone is not a safe registration test.
  • Maintain a documented data-processing register.
  • Notify the Board without delay and, under the Board's current interpretation of the statutory rule, no later than 72 hours after becoming aware of a qualifying breach; notify affected people as soon as reasonably possible after they are identified where required.
  • Apply technical and organizational security measures appropriate to the risk.

The 12-point operational checklist

A footer link leading to a Turkish-language privacy notice that names, for the actual business: what data you collect, the applicable legal grounds, retention periods, third-party recipients or processors, data-subject rights, and a contact route for KVKK requests. A cookie inventory and preference mechanism should reflect the technologies actually deployed.

2. VERBİS registration

VERBİS (Veri Sorumluları Sicil Bilgi Sistemi) is the national registry of data controllers. Under the Board's decisions, a data controller with fewer than 50 employees a year and an annual balance-sheet total under 100 million TL, whose main activity is not processing special-category data, is exempt from registering (2018/87 and 2023/1154). Since 4 September 2025 a controller whose main activity is special-category data is also exempt with fewer than 10 employees and a total under 10 million TL (2025/1572); read the Authority's notice before deciding.

3. Documented data-processing register

A spreadsheet or document listing every kind of data you collect, every system that stores it, every third party that touches it, the purpose and legal ground, and the retention decision. The format and level of detail should match the actual role, processing, and current obligations; keep it as evidence rather than treating a template as a safe harbour.

Do not rely on pre-checked boxes or a bundled “accept everything” action to evidence specific consent. Separate each purpose and use another legal ground where appropriate; fulfilling an order is a different purpose from marketing, so marketing should not be hidden in the checkout acceptance.

Keep the distance-sales contract acknowledgement separate from privacy consent. Marketing email and SMS need a separate, purpose-specific legal analysis and choice. Profiling or recommendation use also needs its own purpose and legal-ground analysis; do not call every privacy notice acknowledgement consent.

6. Working delete-my-data path

Provide an account or contact route for data-subject requests that reaches a responsible person. The law asks you to conclude a request as soon as possible and within thirty days at the latest (article 13); check fees and details against the official guidance. A deletion request may be limited by lawful retention, so the workflow must record the decision rather than promise that every record is erased.

7. Retention periods written down

You cannot keep data without a purpose. Set a documented period or review trigger for each category from the purpose, legal ground, statutory or contractual retention, security risk, and the current operation; the examples below are deliberately not fixed legal periods:

DataRetention decision
Order recordsConfirm the applicable commercial, tax, consumer, and sector rules.
Customer accountsKeep while needed for the account purpose, then review or delete subject to lawful retention.
Marketing recordsRecord the source, purpose, status, withdrawal, suppression, and any lawful retention.
Cart or browsing dataUse the shortest period that serves the documented purpose and actual product.
IP and security logsSet from security, abuse, operational, and legal needs; document access and deletion.

Document these, implement them, and test that the live systems match the notice and register.

8. KVKK clauses in supplier contracts

For every third party that touches customer data (email, SMS, CRM, analytics, payment, hosting), document the parties' roles, purposes, safeguards, retention, and transfer mechanism. A contract template does not by itself establish compliance; the right terms depend on the actual controller/processor relationship and current law.

9. Breach notification protocol

A documented plan for what happens when a breach is detected. The Board's current guidance addresses notification without delay and the applicable statutory timing after awareness of a qualifying incident; check the current official breach guidance and document awareness, assessment, escalation, notifications, and remedial action.

10. Security baseline

Security measures should be proportionate to the risk and actual systems. A practical baseline may include HTTPS, modern password hashing, protected backups, role-based access, no shared administrator credentials, MFA, monitoring, and an incident plan; the right controls and review cadence depend on the processing and threat model, not this checklist.

11. Employee training

Train and authorize staff who access personal data in a way that matches their role and risk. Record the scope, date, attendees, confidentiality expectations, and follow-up; the law and current guidance, not a fixed annual or 30-minute rule in this article, determine what is sufficient.

12. Annual audit and update

Review the register, retention, data-subject responses, supplier contracts, vendors, training, security, and deployed scripts at a cadence appropriate to change and risk. External advice may help, but its need and fee depend on the operation; obtain a current scope rather than relying on a benchmark.

What regulators actually inspect

Public decisions and guidance make it prudent to be ready to evidence the actual inventory, legal grounds, notices, consent choices, retention decisions, supplier terms, security measures, breach response, and rights-request handling. The twelve items are governance controls, not a guarantee of an enforcement outcome. Keep evidence that the controls match the actual processing and update them when the business or law changes.

Common mistakes

  • Translating the GDPR template directly. KVKK and GDPR are distinct frameworks; map the actual Turkish and EU obligations instead of assuming equivalence.
  • One catch-all consent box. "I accept all terms" is not a reliable record of purpose-specific consent or contract acknowledgement.
  • Treating cross-border transfers as a one-line consent problem. Since 1 June 2024 a transfer abroad rests first on an adequacy decision, otherwise on an appropriate safeguard such as the Board's standard contract, which is notified to the Authority within five business days of signing (article 9 as amended by Law 7499). Explicit consent is now only an exception for occasional transfers; identify each recipient abroad, its role, the purpose and the mechanism, and see the KVKK transfer page.
  • Treating cookies as functional-only. Analytics and marketing technologies may process personal data and may require consent or other controls depending on the technology, purpose, jurisdiction, and deployment. Inventory the actual scripts and do not load optional tools before the required choice.
  • Assuming a title solves governance. Whether a DPO, representative, privacy lead, or adviser is required or useful depends on the actual role, processing, jurisdiction, and current law; document responsibility and escalation.

Penalties and enforcement

Do not publish or rely on a static fine table: Turkish administrative fine amounts are amended and adjusted, and the applicable range depends on the offence, date, facts, and current official tariff. Check the KVKK's current publications and decisions and obtain professional advice for a live matter.

FAQ

Does a small shop have to register with VERBİS? Not if it has fewer than 50 employees a year, an annual balance-sheet total under 100 million TL, and processing special-category data is not its main activity; the Board exempts it. These limits change by Board decision, so check the Authority's notice before deciding.

Do I need a Data Protection Officer? Not in the GDPR sense: KVKK has no DPO duty, though a shop registered with VERBİS names a contact person there. If you also sell to the EU, check separately whether GDPR asks you for an EU representative.

Are cookie banners legally required? For optional cookies, in effect yes: analytics and ad tools shouldn't run until the shopper chooses, while cart and session cookies can work without asking. Keep a list of what you use and let shoppers change their choice at any time.

What if my store sells to EU customers? Then check GDPR on its own: it can apply when you target or track EU shoppers, and it may require an EU representative. KVKK and GDPR overlap, but neither stands in for the other.

Can I send data to a service abroad (analytics, email, cloud)? Yes, but since 1 June 2024 the route is set: an adequacy decision, otherwise an appropriate safeguard such as the Board's standard contract, which you notify to the Authority within five business days of signing. Explicit consent is an exception for occasional transfers, not the basis for a regular one.

Can I get a one-time KVKK template package? You can start from one, but a template can't know your purposes, providers or retention periods. Adapt it to your shop and have it reviewed.


FaStart publishes its own KVKK notice, and the product page shows its privacy tools for merchants' stores. Neither makes a store compliant on its own.

Spend your time on the shop, not the admin

FaStart is the online store platform with AI agents built in. Open your store this afternoon and hand Ally the routine work.