Free tool

How ready are you for KVKK and GDPR?

27 questions in five areas, each with why it matters and what good looks like. Answer yes, partly or no — the score updates as you go. Your answers stay in this browser.

Records and transparency

Do you know what you process, why, and can you show it?

  1. We have a written record of the personal data we process: where it comes from, who gets it and how long we keep it.

    GDPR Art. 30 · KVKK m.16

  2. Every purpose has a named legal basis, decided before the processing started.

    GDPR Art. 6 · KVKK m.5

  3. Our privacy notice (aydınlatma metni) states each purpose, its legal basis, recipients and retention in plain language, and is linked from every page.

    GDPR Art. 13–14 · KVKK m.10

  4. People are told about the processing at the moment we collect their data (forms, chat, calls), not only in a policy page.

    GDPR Art. 13 · KVKK m.10

  5. If we must, we are registered in VERBİS and the entry matches our record of processing.

    KVKK m.16

Security and breaches

Is the data protected, and do you know what to do when it is not?

  1. We can notify the authority within 72 hours of learning about a breach, and we have rehearsed it.

    GDPR Art. 33–34 · KVKK m.12(5)

  2. Personal data is encrypted in transit and at rest, and minimised or pseudonymised where the purpose allows.

    GDPR Art. 32 · KVKK m.12

  3. Access to personal data is limited to the people whose role needs it, and it is reviewed.

    GDPR Art. 32 · KVKK m.12

  4. Everyone with access to customer data signs in with two-factor authentication.

    GDPR Art. 32 · KVKK Teknik Tedbirler Rehberi

  5. Staff who handle personal data are trained and know how to recognise and report an incident.

    GDPR Art. 39 · KVKK m.12

Accountability

Who is responsible, and what do the contracts say?

  1. Every service provider that handles personal data for us is bound by a data processing agreement.

    GDPR Art. 28 · KVKK m.12(2)

  2. A named person answers privacy questions (DPO under GDPR where required, contact person under KVKK).

    GDPR Art. 37 · KVKK VERBİS irtibat kişisi

  3. Transfers of personal data abroad rest on an adequacy decision, standard contracts or another lawful tool.

    KVKK m.9 (2024) · GDPR Ch. V

  4. We know when a data protection impact assessment is needed and have done one where it is.

    GDPR Art. 35

  5. We have retention periods and a destruction policy, and data is deleted or anonymised when they end.

    KVKK m.7 · Silme Yönetmeliği · GDPR Art. 5(1)(e)

Individual rights

Can a person use their rights, and do you answer in time?

  1. A person can ask for a copy of their data and gets it within the deadline (30 days under KVKK, one month under GDPR).

    GDPR Art. 12, 15 · KVKK m.11, 13

  2. Requests to correct, delete or restrict data follow a defined process, and recipients are told.

    GDPR Art. 16–19 · KVKK m.7, 11

  3. A person can object to direct marketing, and the objection stops it everywhere.

    GDPR Art. 21 · KVKK m.11

  4. Data can be given to the person in a structured, machine-readable format.

    GDPR Art. 20

  5. People are told when they talk to an AI, and automated decisions with real effects can be reviewed by a person.

    GDPR Art. 22 · EU AI Act Art. 50

Nothing on this page is legal advice. It shows where to start; apply it to your own situation with counsel where the stakes require it.

Let the data answer for you

In Pexpy's Privacy Center the same check fills itself in from your real records — late requests, consent evidence, website scans, two-factor sign-in, retention rules — next to KVKK / GDPR requests with their legal deadlines and erasure across every module.