How should a controller choose among the seven bases?
Start with the purpose, the controller's relationship with the person, and the legal or practical reason the processing is needed. Contract applies only where processing is objectively necessary to perform a contract with the person or take requested pre-contract steps. Legal obligation needs a duty imposed by UK law. Vital interests is narrow and protects a person's life. Public task requires a task in the public interest or official authority laid down by law.
Use consent only when the person has a genuine choice and can withdraw without detriment. Use ordinary only after the purpose, necessity, and balancing tests. Use only when every requirement of a specific Annex 1 condition is met; unlike ordinary legitimate interests, it does not require a separate balancing test.
- Describe each purpose precisely. One system may need different bases for account delivery, fraud prevention, analytics, and marketing.
- Test necessity: if a less intrusive reasonable method achieves the purpose, a necessity-based basis may not fit.
- Do not treat contract terms or a privacy notice as proof that processing is necessary for a contract or legal obligation.
- Tell people the and purpose in the privacy information, subject to any applicable exception.
Explains when each Article 6 basis may apply, the need to choose before processing, necessity, documentation, and privacy information.
Sets out the binding Article 6 lawful bases and the restriction on public authorities using Article 6(1)(ea) or (f) when performing their tasks.
Explains the five Annex 1 conditions, necessity test, limits for public authorities, and difference from ordinary legitimate interests.
Brought section 70 and the new Article 6(1)(ea) lawful basis into force on 5 February 2026.