01 · SCOPE OF SUPPORT
What does this procedure involve?
Customer lists, personnel files, CCTV footage, applicants’ CVs and website enquiries involve different processing activities. Their purposes, legal bases, access permissions and retention needs may differ. A single generic document may not explain those differences.
Compliance work begins with how the business actually operates. An unused policy or a retention period that the business does not apply shows only that a document has been produced. The objective is a clear arrangement that management, human resources, customer relations and technical staff can implement.
Legal assessment of current practices
Needs are identified by examining data collection channels, systems in use, and employee and customer processes.
Privacy notices and contracts
Notices, processing conditions and data-sharing relationships are reviewed against the business’s actual activities.
VERBİS assessment
Registration duties or exemptions are examined, together with consistency between the data inventory and the registry declaration.
Requests and ongoing updates
Responsibilities are allocated for data subject requests, correspondence with the Authority and changes to processing activities.
02 · THE PROCEDURE
From preparation to follow-up, step by step
Identify business processes
Map which department collects each category of data and with whom it shares it.
Prepare the data inventory
Connect purposes, legal bases, groups of individuals, data categories, transfers and retention information.
Adapt the legal documents
Prepare privacy notices, explicit consent documents where necessary, employee arrangements and supplier provisions.
Registration and internal implementation
Where VERBİS registration is required, prepare the appropriate declaration information and inform the people responsible within the business.
Monitor changes
Plan updates to documents and procedures whenever new software, services or data-sharing relationships are introduced.
03 · DOCUMENT PREPARATION
Documents and preparation checklist
0 / 7 document categories prepared
Use this as a preparation checklist. The authority or your circumstances may require additional documents. Selections are cleared when you leave the page.

Providing information is different from obtaining explicit consent
Informing people about how their data is processed and obtaining their explicit consent for a particular operation serve different purposes. Relying solely on consent documents for every activity is not the correct approach. The applicable processing condition must be identified from the specific process.
Instead of copying the same wording for employees, customers, visitors and website users, the explanation should address the activity concerned. The data collected and the purposes described in the notice must be consistent.
VERBİS registration and exemptions
Assessing the registration obligation requires consideration of current Board decisions, business activities and applicable criteria. Instead of relying on outdated thresholds found online, the position should be assessed using current information about the business.
Registration in VERBİS does not show that every KVKK obligation has been met. An exemption from registration does not necessarily remove duties concerning transparency, lawful processing or data security.
Cloud services, employee data and international transfers
Email, file storage or customer management systems using servers abroad should be assessed for data transfer implications. A security clause in a contract does not, on its own, establish that every condition for a transfer has been satisfied.
Legal assessment relies on accurate information about the systems provided by the technical team. A document prepared by a lawyer does not itself implement access permissions, backups or technical configuration. Responsibility for legal and technical work must therefore be allocated together.
POINTS TO WATCH
Common mistakes and important distinctions
Using copied notices
Systems, recipient groups or purposes mentioned in another business’s documents may misrepresent your own activities.
Making registration the only objective
Completing a VERBİS declaration without addressing actual data flows leaves the compliance work incomplete.
Keeping data indefinitely
Instead of retaining everything because it may be useful later, identify a retention justification and an applicable period.
Trying to solve technical tasks with documents
Creating a legal policy does not establish that the necessary technical measures have actually been implemented.
PLANNING THE WORK
Legal fees, expenses and timing
How are fees and expenses determined?
Fees depend on the number of departments, business activities, data collection channels, employee and supplier arrangements, and depth of the review. Assessing one privacy notice is different from a full inventory and compliance project. Legal services, technical consultancy, software development and training are separated at the outset. Urgent work on a request or breach may require its own scope. Where regular updates are required, the changes covered by the ongoing service are specified in writing. Official sanctions or the costs of future disputes are not assumed to be included in the consultancy fee. The scope of the real processes matters more than the number of documents.
What can affect the timetable?
The time required depends on access to accurate information within the business. Even when forms and contracts are ready, the assessment cannot be completed without explaining the software used and the data-sharing relationships. If there is a data subject request or a letter from the Authority, its legal timetable is addressed separately from the general compliance project. Priority gaps are identified first, and the inventory, notices, registration and implementation stages are ordered accordingly. Updates remain necessary when new activities begin.
HYPOTHETICAL EXAMPLE
Example scenario: A growing service business
Suppose an Istanbul service company receives customer enquiries through a website form, keeps personnel files in the office and stores its customer list in a cloud application abroad. Management may initially want only a notice added to the website. The assessment first identifies the information collected by the form, who can access it and how the cloud application is used. Employee records and customer enquiries are considered separately according to their purposes and retention needs. The privacy notice is prepared to reflect these actual arrangements, while transfers are assessed in their own right. Technical changes and the internal procedures to be implemented by management are identified. This hypothetical example explains why the same document package will not be sufficient for every business; it does not conclude that any particular business is compliant.
QUESTIONS AND ANSWERS
Frequently asked questions
If I am registered in VERBİS, does that make all my processing compliant?
Registration is only one part of compliance. Processing conditions, transparency, transfers, retention and implementation require separate assessment.
Are small businesses exempt from all KVKK duties?
Exemption from the registry and the other obligations under the Law are different issues. The business’s activities and processing operations must be assessed.
Will a standard notice be enough?
The document must explain how the business actually operates. It should not describe systems that are not used or transfers that do not occur.
Does the lawyer carry out the technical changes?
Legal assessment is a legal service. System and software changes are implemented by the relevant technical specialist.
Can we obtain help only with employee records?
Yes. A limited scope can be agreed for human resources, job applications or a particular data collection channel.
READ THE ORIGINAL SOURCES
Official sources and application information
- Personal Data Protection Authority — Obligation to Inform ↗
The content and legal framework of information provided to individuals.
- Personal Data Protection Authority — Information on the Data Controllers Registry ↗
Authority resources on the registry, data inventories and registration obligations.
This English edition was prepared on 10 November 2026 from the Turkish guide dated 9 November 2026, retaining its official sources. Editorial dates are not legislation commencement dates or a record of individual lawyer approval. Some sources are in Turkish. Current authority requirements and the circumstances of your matter must be considered together. Editorial policy (Turkish)