Skip to main content
Privacy Track
Category: Consent Requirements

Presented Distinguishable From Other Matters

Also known as: Clearly Distinguishable Consent Request, Distinguishable Presentation of Consent
Simply put

This is a requirement about how an organisation asks for a person's consent to use their personal data. Where a consent request appears alongside other content, such as general terms and conditions, it must be set apart so the person can clearly see it and understand what they are agreeing to. The aim is to prevent consent from being buried or hidden within unrelated text.

Formal definition

A condition for valid consent under the UK GDPR (as reflected in Article 7, per the ICO guidance and the GDPR text) requiring that, where a data subject's consent is sought within a written declaration that also concerns other matters, the request for consent be presented in a manner clearly distinguishable from those other matters, in an intelligible and easily accessible form, using clear and plain language. In practice this generally means separating the consent request from documents such as standard terms and conditions rather than bundling them together. The precise application is context-dependent and should be assessed against the current official text and applicable regulatory guidance; this entry addresses only the presentation requirement and does not, on its own, establish the other elements of valid consent (for example that it be freely given, specific, informed, and unambiguous).

Why it matters

The presentation of a consent request directly affects whether that consent can be relied upon as a valid lawful basis under Article 6 (with an additional condition under Article 9 for special category data). Where consent is sought within a written declaration that also concerns other matters, such as general terms and conditions, burying the request within unrelated text undermines the data subject's ability to understand what they are agreeing to. If the presentation requirement is not met, the consent may be challenged, and an organisation relying on it could find that it has no valid legal basis for the relevant processing.

This requirement matters most where consent is bundled into onboarding flows, sign-up forms, or acceptance of standard terms, which are common points at which organisations gather agreement. Separating the consent request so that it is clearly distinguishable, intelligible, and easily accessible reduces the risk that a regulator or court later treats the consent as invalid. It also supports the broader documentation and accountability expectations that surround consent, though this particular requirement addresses only how the request is presented, not whether all other elements of valid consent are satisfied.

Because the precise application is context-dependent and can be affected by regulatory guidance, organisations should assess their consent presentation against the current official text and applicable guidance, such as that published by the ICO for the UK GDPR. This entry does not, on its own, establish that consent is freely given, specific, informed, or unambiguous; those remain separate requirements that must be met for consent to be valid.

Who it's relevant to

Data Protection Officers and Compliance Leads
Those responsible for consent management should review sign-up flows, onboarding processes, and any documents that combine a consent request with other matters, to confirm the request is clearly distinguishable, intelligible, and easily accessible. They should assess presentation against the current official text and applicable guidance, such as the ICO's, recognising that this requirement is only one of several conditions for valid consent.
Product Designers and Engineers
Teams building consent interfaces should ensure the consent request is visually and structurally separated from unrelated content such as terms and conditions, and expressed in clear and plain language. Design choices that bury or bundle consent within other matters can undermine reliance on that consent as a lawful basis.
Lawyers Advising on Consent Documentation
Legal advisers drafting or reviewing consent language should confirm that, where consent is sought alongside other matters, it is presented distinguishably and in an intelligible, accessible form. They should note that this presentation requirement does not on its own establish that consent is freely given, specific, informed, and unambiguous, and that application is context-dependent.
Organisations Relying on Consent as a Lawful Basis
Businesses that use consent under Article 6, and any additional condition under Article 9 for special category data, should ensure their request presentation meets this requirement to reduce the risk that the consent is later treated as invalid. Where practices span the UK and EU, they should account for possible divergence in guidance and national implementing law.

Inside Presented Distinguishable From Other Matters

Requirement of Distinguishability
The principle, derived from Article 7(2) GDPR, that where consent is sought within a written declaration that also concerns other matters, the consent request must be presented in a manner clearly distinguishable from those other matters. It addresses the form and presentation of a consent request rather than the substantive validity conditions of consent itself.
Written Declaration Concerning Other Matters
The typical scenario in which this requirement applies, for example a set of terms and conditions, a contract, or a combined notice that bundles a consent request together with unrelated provisions. The requirement is engaged when consent is not the sole subject of the document.
Intelligible and Easily Accessible Form
Article 7(2) also requires that the relevant part be presented using clear and plain language and in an intelligible and easily accessible form, reinforcing broader transparency expectations. This is closely related to, but analytically distinct from, the distinguishability element.
Consequence of Non-Compliance
Article 7(2) provides that any part of a declaration which infringes the Regulation is generally not binding. The precise scope and effect of this consequence can depend on the circumstances and on national implementing law, so its application should be assessed case by case.
Relationship to Valid Consent Conditions
Distinguishability is a presentation requirement that operates alongside the substantive conditions for valid consent (such as being freely given, specific, informed, and unambiguous under Article 4(11) and Article 7). Satisfying distinguishability does not by itself establish that consent is valid.

Common questions

Answers to the questions practitioners most commonly ask about Presented Distinguishable From Other Matters.

Does the requirement to present a consent request 'distinguishable from other matters' mean consent must always be a separate standalone document?
No. The requirement, which derives from Article 7(2) GDPR where consent is given in the context of a written declaration that also concerns other matters, does not generally mandate a wholly separate document. It requires that the part of the declaration seeking consent be clearly distinguishable in its presentation from the other matters, using clear and plain language. A consent request can appear within a broader document provided it is set apart in an intelligible and clearly separated way. The key is distinguishability and clarity, not physical separation into a distinct instrument.
Does satisfying the 'distinguishable' presentation requirement mean the consent itself is valid?
Not on its own. Distinguishable presentation under Article 7(2) addresses how the request is presented, but it is only one element. For consent to be a valid legal basis under Article 6(1)(a), it must also generally be freely given, specific, informed, and unambiguous, as defined in Article 4(11), and it must be as easy to withdraw as to give under Article 7(3). A request can be perfectly distinguishable in presentation yet still fail on other grounds, such as bundling or lack of genuine choice. Distinguishability supports validity but does not guarantee it, and the overall assessment is context dependent.
How can a consent request be made distinguishable when it appears within longer terms and conditions?
In most cases this is achieved by visually and textually separating the consent element from surrounding contractual or informational content, for example through a dedicated section, distinct headings, or spacing, and by using clear and plain language rather than embedding it in dense legal text. The aim is that a data subject can readily identify what they are being asked to consent to and distinguish it from other obligations they are agreeing to. Specific formatting expectations can vary, and organisations should verify current regulatory guidance, as supervisory authorities may express differing views on presentation.
Should consent for different processing purposes be presented separately?
Generally, yes, where distinct purposes are involved. Because consent typically needs to be specific, presenting separate, distinguishable consent options for each purpose helps demonstrate that the data subject can choose per purpose rather than being required to accept everything together. This granularity interacts with the distinguishability requirement but is conceptually a separate expectation. The appropriate level of granularity is subject to assessment and depends on the processing activities in question.
How can an organisation demonstrate compliance with the distinguishable presentation requirement?
Compliance is typically supported by retaining evidence of how the consent request was presented, such as records or screenshots of the interface or document version shown to the data subject, alongside the accountability records generally expected for consent. Keeping versioned copies helps show that, at the relevant time, the consent element was clearly distinguishable and expressed in clear and plain language. What constitutes sufficient evidence is context dependent, and organisations should align their approach with current supervisory guidance.
Does the distinguishable presentation requirement apply where processing relies on a legal basis other than consent?
The Article 7(2) presentation requirement is specific to consent given within a written declaration concerning other matters. Where processing relies on a different Article 6 basis, such as contract, legal obligation, or legitimate interests, this particular requirement does not apply in the same way, although separate transparency obligations under Articles 13 and 14 still apply to how information is communicated. Care should be taken not to seek consent unnecessarily where another basis is more appropriate, and the correct basis should be determined before presentation questions arise.

Common misconceptions

Meeting the distinguishable-presentation requirement means the consent is valid.
Distinguishability under Article 7(2) concerns only how a consent request is presented within a broader document. Consent must still, in most cases, satisfy the separate substantive conditions of being freely given, specific, informed, and unambiguous. Presentation and validity are distinct questions.
Consent is always the required legal basis, so this presentation rule applies to every processing activity.
Consent is only one of the Article 6 legal bases (alongside contract, legal obligation, vital interests, public task, and legitimate interests). The Article 7(2) distinguishability requirement is relevant where consent is actually relied upon and is bundled with other matters; it does not apply where a different lawful basis is used.
A non-compliant consent clause invalidates the entire document.
Article 7(2) generally provides that the infringing part is not binding, which typically points to the offending portion rather than automatically voiding the whole declaration. The precise effect can vary and may be influenced by national implementing law, so it should be assessed against the current official text and relevant guidance.

Best practices

Separate any consent request from surrounding terms and conditions or contractual provisions, for example using a distinct section, heading, or clearly delineated checkbox, so the consent element is not buried within unrelated matters.
Draft the consent portion in clear and plain language and ensure it is intelligible and easily accessible, consistent with the requirements of Article 7(2).
Confirm before relying on this requirement that consent is genuinely the appropriate Article 6 legal basis, rather than defaulting to consent where another basis may be more suitable.
Where special category data under Article 9 is involved, recognise that an additional Article 9 condition is required beyond the Article 6 basis, and reflect that in how consent is framed and presented.
Maintain records of how the consent request was presented and worded, so the distinguishability and clarity of the request can be demonstrated if challenged.
Verify the applicable position against the current official GDPR text, the UK GDPR where relevant, and any national implementing law or regulatory guidance, since the effect of non-binding clauses and related requirements can vary by jurisdiction.