How is a data controller different from a data processor?
A data controller decides the purposes and means of processing personal data; a data processor processes it on the controller's behalf. Those are the definitions in Article 4(7) and 4(8) of GDPR, and the ICO uses the same words for UK GDPR.
| Controller | Processor | Joint controllers | |
|---|---|---|---|
| Who decides why data is used | Yes | No | Both, together |
| Acts on someone else's instructions | No | Yes | No |
| Main responsibility for compliance | Yes | More limited duties | Shared, by agreement |
| Example on a dating service | The brand or platform that decides what member data is collected and why | A hosting, email or ID check supplier | Two businesses that jointly decide how a shared member base is used |
The ICO puts it simply: controllers make decisions about processing activities, and if you are a controller you are responsible for complying with UK GDPR. A processor has more limited compliance responsibilities and should only process personal data in line with the controller's instructions.
Why does it matter who is the data controller on a dating site or app?
It decides who answers to the regulator, who handles members' requests, and who is liable if something goes wrong. On a white label platform the roles are not always obvious. The brand owner chooses the brand and brings members, while the platform runs the software, the shared member network, moderation and support. Depending on the contract, the platform may be the controller, a processor for the brand, or a joint controller with it.
Dating data makes the question more pressing, because profiles can include special category data such as sexual orientation. The controller must have an Article 9 condition for that data, usually explicit consent.
Where one party acts as a processor for another, Article 28 requires a binding contract, known as a data processing agreement, setting out what the processor may do.
What should you ask a provider about the data controller role?
Ask the provider to state in writing who is the controller for each kind of member data, and why. Then ask:
- Whose name is on the privacy policy members see?
- Who handles access and deletion requests, and who reports breaches?
- If roles are shared, is there a joint controller arrangement?
- What happens to member data, and your role, when the contract ends?
Our guides to who owns the members and GDPR for dating sites cover the commercial and legal sides together. This page is general information, not legal advice.
Also known as: controller, data processor, joint controller
Related terms
- GDPRGDPR (the General Data Protection Regulation) is the EU law on personal data that has applied since 25 May 2018.
- Data processing agreementA data processing agreement (DPA) is the contract a data controller must have with any processor that handles personal data for it.
- Special category dataSpecial category data is personal data that GDPR and UK GDPR protect more strictly, including data about sex life, sexual orientation, religion, ethnic origin, health and biometrics used for identification.
- White label datingWhite label dating is running a dating site or app under your own brand on another company's platform.
Questions
Can a company be a controller and a processor at the same time?
Yes, for different processing. A platform can process member data on a brand's behalf for one purpose and decide for itself how to use data for another, such as fraud prevention across its whole network. The contract should say which is which.
Who answers members' data requests on a white label site?
The controller is responsible for answering them. A processor must help, which GDPR Article 28 requires the contract to say, but the controller carries the duty.
Does being the controller mean I own the members?
Not in a commercial sense. Controller status is about legal responsibility for data. Who may market to members, export their data or keep them when a contract ends is set by your contract, so read it alongside the data terms.
Sources
- ICO: What are controllers and processors?, checked 21 November 2026
- Regulation (EU) 2016/679 (GDPR), Article 4, EUR-Lex, checked 21 November 2026
- UK GDPR Article 28 (legislation.gov.uk), checked 21 November 2026
What changed
- : First published.