Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A controller decides why and how personal data is processed; a processor acts only on the controller’s documented instructions. The distinction sets who is accountable and what the contract must say.

What Is the Difference Between Controller and Processor?
Two organisations handle the same personal data. One decides why it is being processed and broadly how; the other does what it is told. The first is a controller, the second a processor, and almost every obligation in data protection law hangs off that split. Getting it wrong is not a labelling error, it is a misallocation of legal accountability that becomes visible exactly when something has gone wrong.
Under UK GDPR, a controller determines the purposes and means of processing. A processor processes personal data on behalf of the controller. The ICO’s guidance is clear that the label in the agreement does not settle the question: what matters is who actually decides. A supplier that chooses what data to collect, decides how long to keep it, or reuses the data for its own analytics is making controller decisions whatever the contract calls it.
Some technical latitude is expected of a processor. Choosing which database engine to run, how to shard storage, or which monitoring tool to deploy are means of implementation rather than essential means. The essential questions, which data, about whom, for what purpose, for how long, and who receives it, belong to the controller.
Where two organisations jointly determine purposes and means, they are joint controllers under Article 26 and must set out their respective responsibilities in a transparent arrangement. The CJEU’s decision in Fashion ID in 2019 made the point sharply: embedding a social plugin made a website operator a joint controller for the collection and transmission of visitor data, even though it never saw the data itself.
Turkish Personal Data Protection Law No. 6698 uses equivalent concepts, translated as data controller and data processor, with a similar instruction-based test. The architecture around them differs in ways that catch UK groups out.
The most visible is registration. Controllers must enrol in VERBIS, the national data controllers’ registry, and publish a processing inventory covering purposes, categories, recipients, retention, and transfers. Exemptions exist for smaller organisations based on employee numbers and balance sheet size, and for those whose main activity does not involve special category data. There is no UK analogue beyond the ICO’s data protection fee, and nothing comparable is published. Processors do not register, which makes the controller determination a filing obligation as well as a legal one.
A foreign controller processing personal data in Turkey must appoint a representative established in Turkey and register through that representative. The UK dropped its equivalent requirement for foreign controllers at a different point in its history, so this is a genuine extra step for a British company that sells directly into Turkey without a local entity.
Breach notification runs on a comparable clock. The Turkish authority expects notification as soon as possible and within 72 hours of the controller becoming aware, with affected individuals informed as well; a processor tells its controller. Transfers abroad were overhauled by Law No. 7499, with the new regime applying from 1 June 2024, introducing adequacy decisions, standard contractual clauses that must be notified to the authority within a short deadline, and binding corporate rules. That replaced an older arrangement in which almost every transfer waited on a specific authority approval, and it moves Turkish practice closer to the residency and transfer mechanics a UK privacy team already understands, without making the two regimes interchangeable.
Map the role per processing activity rather than per supplier. The same cloud provider can be your processor for the hosting service and a controller for the account and billing relationship. Record the reasoning, not just the conclusion, because the question you will be asked after an incident is why you decided as you did.
Audit instruction drift. Processors that start producing benchmarks, training models on customer data, or enriching records have quietly crossed the line, and the first the controller usually hears of it is a marketing announcement. Build the question into supplier reviews alongside your UK GDPR obligations. At Privia Security, we assess processing arrangements and the technical controls behind them through our regulation and compliance services.
Usually yes for the hosting service itself, where the customer decides what data goes in and why. The same provider is commonly a controller for account administration, billing, abuse prevention, and service improvement using its own telemetry. Read the data processing addendum carefully: most large providers now state explicitly which activities they perform as processor and which as controller.
VERBIS is Turkey’s registry of data controllers, in which controllers publish a processing inventory covering purposes, data categories, recipients, retention periods, and international transfers. Registration is required for controllers above defined employee and balance sheet thresholds, and for those whose main activity involves special category data. Processors do not register. A foreign controller must appoint a Turkish representative and register through them.
The controller reports to the supervisory authority: the ICO in the UK within 72 hours where the breach is likely to risk individuals’ rights, and the Turkish authority on a comparable timetable under KVKK. A processor’s duty is to notify its controller without undue delay so that the controller can meet its own deadline. Contracts should set a processor notification time measured in hours.
It becomes a controller for that processing and takes on the full set of controller obligations and liability for it, including lawful basis and transparency. The most common examples are reusing customer data for product analytics, training models on it, or sharing it with a sub-processor without authorisation. Supplier reviews should ask directly about new uses rather than assume the contract is being followed.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.