Home / Guides / What Is a Data Controller?

GDPR Basics

What Is a Data Controller?

Controller definition, legal duties, and practical examples for websites.

Author

GDPRChecker Editorial Team

Reviewed by

Privacy & Compliance Research Team

Last updated

June 2026

Reading time

2 min read

Educational guidance for compliance readiness — not legal advice. Requirements vary by jurisdiction and your specific processing activities.

Introduction

Determine when your company acts as a controller and what accountability duties come with deciding the purposes of processing. Use this for role mapping in contracts and operations.

What it means

A controller determines why and how personal data is processed.

Controllers are responsible for lawful basis selection, transparency, and rights handling.

Joint controllership can exist when two parties jointly decide purposes and means.

Controller responsibilities remain even when processing is outsourced to vendors.

Why it matters

Regulators, customers, and automated scanners increasingly treat published policies and live site behavior as one system. Gaps between what you say and what your site does create enforcement and commercial risk.

Fixing issues early is cheaper than retrofitting consent, tag managers, and legal pages after a complaint or failed enterprise security review.

Common mistakes

  • Calling yourself a processor while setting campaign targeting and retention rules.
  • Using vague vendor contracts that do not reflect actual roles.
  • Failing to document controller decisions for high-risk processing.
  • Assuming processors handle all DSAR and breach obligations.
  • Not assigning internal ownership for controller duties.

Practical checklist

  1. Map which party decides purpose and essential means per workflow.
  2. Document controller or joint-controller role per processing activity.
  3. Align privacy notice and lawful basis with controller decisions.
  4. Maintain records of processing and risk assessments.
  5. Define DSAR ownership and escalation paths internally.
  6. Review vendor agreements for role consistency.

How GDPRChecker helps

GDPRChecker helps teams turn legal theory into testable controls. Its scanner identifies trackers, third-party calls, and policy mismatches so you can prioritize the highest-risk gaps first.

After changes ship, GDPRChecker runtime monitoring can confirm consent and tag behavior remains aligned over time. That makes compliance less of a one-off audit and more of an operational process.

FAQ

Can a startup be both controller and processor?
Yes, depending on the service and activity. Role is context-specific.
Who is liable in controller-processor setups?
Each party has direct obligations; controllers carry primary accountability for purpose decisions.
Do controllers need a DPO?
Only in specific high-risk or public-authority scenarios, not automatically for every controller.

GDPRChecker guides are educational resources and do not constitute legal advice. Use them to understand technical and operational privacy requirements, and consult qualified counsel for legal interpretation.

Check Your Website in Under 60 Seconds

  • No signup required
  • GDPR-focused checks
  • Cookie banner detection
  • Privacy policy verification