EUTechRegResearch
MenuClose menu
Digital Omnibus legislative tracker
Texts to 22 Oct 2026

Article 7a

Only Parliament amendments would change this article. Parliament committees have tabled 1 amendment to this article.

Latest text22 October 2026ST 14756/26

Contains no amendment to this article.

What each text does

  1. 19 Nov 2025 Commission proposalCOM(2025) 837 No amendment to this article.
  2. 21 May 2026 Council textST 9547/26 No amendment to this article.ST 9547/26 reproduces only some of the proposal’s changes, so this comparison applies only those it shows or visibly drops. It says nothing about the others.
  3. 10 Jun 2026 Council textST 10426/26 No amendment to this article.
  4. 18 Jun 2026 Council textST 10677/26 No amendment to this article.
  5. 27 Jul 2026 ITRE–LIBE amendments 777–1052 to the draft reportCJ72-AM-791072 1 amendment to this article. Amendments in this document
  6. 3 Sep 2026 Council textST 12535/26 No amendment to this article.
  7. 2 Oct 2026 Council textST 13886/26 No amendment to this article.Page 126 prints “(9a)” without an instruction or target, so no change can be assigned to that marker.
  8. 22 Oct 2026 Council textST 14756/26 No amendment to this article.

Parliament amendments

1 amendment to this article

1 would add wording.

By political group; co-sponsored amendments count for each group
TypeECRPfE
+ Addition11

By political group

  • + Addition ECR 1 PfE 1
  1. 1017 Addition Julie Rechagneux +8ECR, PfE · ITRE–LIBE “Article 7a Consent interfaces 1. Any interface used to request, give, refuse or withdraw consent under this Regulation, including for the storing of…”

    2g. The following Article 7a is inserted

    Article 7a

    Consent interfaces

    1.Any interface used to request, give, refuse or withdraw consent under this Regulation, including for the storing of, or access to, information in terminal equipment, shall be fair, neutral, intelligible and easily accessible.

    2.Consent shall be freely given, specific, informed and unambiguous. It shall be requested separately for each purpose and require a statement or clear affirmative action. Silence, inactivity, pre-ticked boxes or the mere continued use of a service shall not constitute consent. Fresh consent shall be required for any other purpose.

    3.Consent shall not be freely given where the data subject has no genuine choice, cannot refuse or withdraw consent without detriment, including in the presence of a clear imbalance between the data subject and the controller, or where access to a service, its functionalities or an equivalent version thereof is made conditional on consent to processing, storing or access that is not necessary for that service.

    4.Before consent is given, the data subject shall receive, in clear and plain language, information on the controller, any joint controllers, recipients or categories of recipients relying on the consent, the purposes pursued, the categories of data concerned, the right to withdraw consent, and, where relevant, automated decision-making under Article 22 or transfers to a third country without an adequacy decision or appropriate safeguards. Consent requests shall be clearly distinguishable from other matters and shall not be concealed within general terms and conditions.

    5.Consent interfaces shall not deceive, coerce or manipulate the data subject, give greater prominence to acceptance than to refusal, make refusal, withdrawal or non-consent options less easy, less accessible or more time-consuming than acceptance, or repeat requests in a manner liable to pressure the data subject. Where an option to accept is presented, an equivalent option to refuse shall be presented at the same level of the interface.

    6.Refusing or withdrawing consent shall be as easy as giving consent and shall not entail any cost, disadvantage or degradation of the service. Where consent was given through an electronic interface, withdrawal shall be possible through the same interface. Following withdrawal, the controller shall cease the processing concerned and, in the absence of another lawful basis, erase the data concerned.

    7.Where consent is withdrawn or found to be invalid, the controller shall not retroactively rely on another legal basis under Article 6 to justify the same processing.

    8.The controller shall be able to demonstrate that valid consent was given. The information retained for that purpose shall be limited to what is necessary.

    9.Where this Regulation requires explicit consent, consent shall be given by an express statement.

    Justification

    Codifies the EDPB Guidelines 05/2020 on consent and 03/2022 on deceptive design patterns. Consent must be freely given, specific, informed and unambiguous; the interface must be fair and neutral and must not give visual or other prominence to acceptance over refusal, whether through size, colour, positioning or wording; refusal must be as easy to exercise, and as prominent, as acceptance; consent must be capable of being withdrawn as easily as it was given; and the controller may not retroactively rely on another legal basis where consent is withdrawn or found invalid. Consent obtained through a manipulated interface is not consent.

    Tabled by
    Julie Rechagneux, Mélanie Disdier, Aleksandar Nikolic, Pierre-Romain Thionnet, Alexandre Varaut, Fabrice Leggeri, Marion Maréchal, António Tânger Corrêa, Christophe Bay
    Group
    ECR, PfE
    Targets
    GDPR Article 7a (new)
    Document
    ITRE–LIBE amendments 777–1052 to the draft report
    Printed header
    Article 3 – paragraph 1 – point 2 g (new) / Regulation (EU) 2016/679 / Article 7a (new)