EU Digital Services Act Puts Non-Personalised Feeds at the Center of User Control

The EU Digital Services Act is bringing user choice over personalised feeds into sharper focus, with consequences for platform design and governance.

EU Digital Services Act Puts Non-Personalised Feeds at the Center of User Control
EU DSA and Non-Personalised Feeds: What Changes

The European Union's Digital Services Act (DSA) is putting a clearer user-choice question in front of online platforms: should people be able to view feeds that are not personalised? EU messaging on the regulation says users can now choose non-personalised feeds, positioning greater control over recommendations as a practical outcome of the DSA.

That matters because feeds are central to how many digital services present information, content and commercial messages. A non-personalised option gives users an alternative to a feed shaped around information associated with them. For platforms, the issue is not simply whether a setting exists. It is whether the choice is intelligible, accessible and supported by accountable product and governance decisions.

What non-personalised feed choice means

A feed is the stream of material presented to a user in an app or online service. The distinction highlighted by the EU is between a personalised feed and a non-personalised feed. The supplied material does not set out the detailed implementation requirements for individual services, but it makes the policy direction clear: users should have more control over whether personalisation shapes what they see.

This is particularly relevant for services that use automated systems to organise and recommend content. Personalisation can make a service feel more relevant, but it can also make the basis of content selection difficult for users to understand. A visible alternative gives users a direct way to exercise a preference rather than treating recommendation design as an opaque default.

For product teams, that reframes feed design as a governance matter as well as a user-experience decision. Teams should be able to explain what the available choices are, how users reach them and how those choices are reflected in the experience.

Three practical areas come into focus:

  • User controls: People need a clear way to select a non-personalised experience.
  • Product clarity: The distinction between available feed options should be understandable in the interface and related communications.
  • Internal accountability: Platform, product, legal and governance teams need shared ownership of how feed choices are designed and maintained.

The DSA discussion is therefore broader than a single settings menu. It concerns the relationship between automated curation, user agency and the operational decisions behind a platform's recommendation experience.

Why this matters for platform governance

The announcement is a reminder that recommendation and feed design have consequences beyond engagement metrics. When a platform offers personalised experiences, it also needs to consider how it communicates that approach and how it gives users meaningful control. This is especially important where automated systems are involved in determining what content is surfaced.

Developers and product managers can use the non-personalised-feed question as a practical design review. Is the relevant choice easy to find? Does the service describe the choice in plain language? Do internal teams understand which systems and settings affect the resulting feed? These are useful questions even where the technical implementation differs between products.

For compliance and governance functions, the value is in connecting policy expectations to operational evidence. A team responsible for an AI-enabled or algorithmically curated service may need a clear record of who owns feed behaviour, how user controls are represented and how product changes are evaluated. The supplied material does not provide a compliance checklist or enforcement timeline, so businesses should avoid treating a high-level public message as a complete implementation guide.

For businesses that operate AI-enabled experiences, a feed-choice message is also a governance signal: teams need a clear view of how personalisation is designed, explained and controlled. Scalevise helps organizations translate emerging AI and platform requirements into practical governance, accountability and implementation priorities. A focused AI governance consultation can identify the decisions, ownership and evidence your team should address before product or policy changes create avoidable risk. Request a consultation.

Frequently Asked Questions

What does the EU Digital Services Act say about non-personalised feeds?

EU messaging supplied for this article says that, thanks to the Digital Services Act, users can choose to see non-personalised feeds.

What is a non-personalised feed?

It is a feed option presented as an alternative to a personalised feed. The supplied material frames it as a way for users to have more control over what they see.

Why are non-personalised feeds important for platforms?

They make user choice over feed personalisation a product and governance issue. Platforms need to consider how the option is presented, explained and supported internally.

Does the supplied material provide an enforcement timeline or detailed technical requirements?

No. It identifies the user-choice outcome but does not provide a detailed enforcement schedule, technical specification or service-by-service implementation guidance.


Conclusion

The DSA's focus on non-personalised feed choice brings a concrete form of user control into the design of digital services. For platforms, the important task is to connect that choice to clear product experiences and accountable governance, rather than treating personalisation as a purely technical feature.