Online Interface Design and Organization

Legal Framework

The Digital Services Act establishes a layered set of obligations governing how providers of online platforms must design, organise, and operate their interfaces. The primary provision is Article 25 DSA, which prohibits providers from designing or operating online interfaces in ways that deceive, manipulate, or otherwise materially distort the autonomy and decision-making of recipients. This prohibition is further contextualised by Recital 67, which describes the dark patterns it targets, and by Recital 74, which addresses the interface obligations specifically applicable to platforms allowing consumers to conclude distance contracts with traders.

Article 25(2) carves out practices already covered by Directive 2005/29/EC (the Unfair Commercial Practices Directive) or the GDPR, meaning that the DSA's dark patterns prohibition operates as a complementary layer rather than a replacement of existing consumer protection and data protection regimes.

For marketplace-style platforms, Article 30 DSA imposes traceability obligations that directly shape interface design: platforms must collect and verify specified trader information before allowing the trader to use the service. Recital 74 reinforces this by stating that platforms should design their interfaces to enable trader compliance with Union law and should not allow products or services to be offered until required information is complete.

"Providers of online platforms allowing consumers to conclude distance contracts with traders should design and organise their online interface in a way that enables traders to comply with their obligations under relevant Union law"
— DSA Recital 74

Key Developments

No case law or enforcement decisions under the DSA's interface design provisions have yet been reported, as the regulation's application to online platforms began only on 17 February 2024. The practical thresholds are therefore drawn from the statutory text and recitals.

Recital 67 provides the most granular catalogue of prohibited practices, identifying specific design patterns that the Commission and national authorities are likely to scrutinise:

"presenting choices in a non-neutral manner, such as giving more prominence to certain choices through visual, auditory, or other components, when asking the recipient of the service for a decision"
— DSA Recital 67

Article 25(3) further signals that the Commission may issue guidelines on three specific practices: non-neutral prominence of choices, repeated requests after a choice has been made, and asymmetric friction between subscribing and terminating a service. These enumerated examples give platforms a concrete compliance checklist even before formal guidance is adopted.

Status of the Debate

This topic is developing. No dominant doctrinal pattern has emerged, and no enforcement decisions or court rulings interpreting Article 25 have been published. The provision's relationship with the UCPD and GDPR under paragraph 2 remains untested — particularly whether a given dark pattern falls under the DSA, the UCPD, or both simultaneously. The Commission's anticipated guidelines under Article 25(3) will be the first authoritative interpretive instrument and will likely define the practical boundaries between the regimes. Until then, platforms must self-assess against the recital's descriptive examples and the statutory prohibition.

Practical Guidance

• Audit interface choice architecture for neutrality. Article 25(1) prohibits materially distorting recipients' free and informed decisions. Review all decision points — consent flows, subscription upgrades, cancellation paths — to ensure choices are presented with equal visual and functional prominence.

• Eliminate asymmetric friction in sign-up versus termination. Recital 67 and Article 25(3)(c) both flag making cancellation more cumbersome than subscription as a prohibited practice. Map the steps required for each and eliminate unjustified disparities.

• Stop repeated choice prompts after a user decision is recorded. Article 25(3)(b) specifically targets pop-ups that re-surface a choice already made. Implement technical logic that suppresses repeated prompts once a user has acted.

• For marketplace platforms, gate trader onboarding on information completeness. Article 30 requires verification of trader identity and compliance information before platform use. Recital 74 adds that products should not be offered until trader information is complete. Design the onboarding interface to block listing creation until all Article 30(1) fields are submitted and assessed.

• Document design rationale and DPO involvement. The data protection by design principles reflected in GDPR Article 25 and the DSA's interface obligations overlap significantly. Involve the DPO early in interface redesign projects and maintain records of design decisions and their compliance rationale to demonstrate good-faith implementation.