Digital rights are not a luxury set against convenience: they are the conditions that allow technology to be used with dignity, safety and a response when a decision harms a person.

The false choice#

Presenting digital rights as a luxury opposed to convenience creates a misleading choice. A platform can offer a useful function while having a duty to explain which data it uses, limit what is unnecessary and allow a complaint. Easy access does not remove the duty to protect people who use the service.

Presenting digital rights as a luxury opposed to convenience creates a misleading choice.

Keeping the date, a full screenshot and a brief description helps make a precise request. Recording an incident does not dramatise it; it preserves context and supports a concrete response.

Power and design#

Digital decisions do not occur between parties with equal power. Those who create an app know its architecture, set initial settings and can steer behaviour through notices, recommendations or time-on-service features. A family or teenager often decides with limited information and under time pressure.

Privacy does not compete with security. Limiting data, protecting accounts and offering clear controls reduces exposure and makes a response easier when something goes wrong. These measures should be designed to support one another.

Data and consequences#

Data are not merely private details. Age, location, an image or activity history can influence advertising, recommendations, visibility or access to content. It is therefore important to ask why data are collected, how long they are kept and who receives them.

Data protection and digital-services rules exist because individual negotiation is not enough. They recognise duties of information, minimisation, security and complaint handling, and help identify who is responsible.

Accepting a pop-up does not prove understanding. Meaningful consent requires a clear purpose, a real possibility of refusing secondary uses and no unfair penalty for someone who limits data. Design should explain consequences rather than hide alternatives.

Individual responsibility matters, but it exists alongside duties of transparency, safety and proportionality for companies, schools and public bodies. Asking every person to identify every risk turns a design obligation into an impossible task.

Protection for children#

Children and teenagers are not miniature adult users. Their experience, reliance on educational spaces and need to belong mean a confusing notice or public setting can carry greater weight. Protection should anticipate harm.

A calm review can ask about purpose, necessity, recipients, duration and route to remedy. These questions do not require technical expertise; they organise a decision that is often presented in a hurry.

Institutional duties#

Presenting digital rights as a luxury opposed to convenience creates a misleading choice. A platform can offer a useful function while having a duty to explain which data it uses, limit what is unnecessary and allow a complaint. Easy access does not remove the duty to protect people who use the service.

Keeping the date, a full screenshot and a brief description helps make a precise request. Recording an incident does not dramatise it; it preserves context and supports a concrete response.

The right to understand#

Digital decisions do not occur between parties with equal power. Those who create an app know its architecture, set initial settings and can steer behaviour through notices, recommendations or time-on-service features. A family or teenager often decides with limited information and under time pressure.

Privacy does not compete with security. Limiting data, protecting accounts and offering clear controls reduces exposure and makes a response easier when something goes wrong. These measures should be designed to support one another.

Correction and remedy#

Data are not merely private details. Age, location, an image or activity history can influence advertising, recommendations, visibility or access to content. It is therefore important to ask why data are collected, how long they are kept and who receives them.

Data protection and digital-services rules exist because individual negotiation is not enough. They recognise duties of information, minimisation, security and complaint handling, and help identify who is responsible.

Not placing everything on families#

Accepting a pop-up does not prove understanding. Meaningful consent requires a clear purpose, a real possibility of refusing secondary uses and no unfair penalty for someone who limits data. Design should explain consequences rather than hide alternatives.

Individual responsibility matters, but it exists alongside duties of transparency, safety and proportionality for companies, schools and public bodies. Asking every person to identify every risk turns a design obligation into an impossible task.

Speaking without panic#

Children and teenagers are not miniature adult users. Their experience, reliance on educational spaces and need to belong mean a confusing notice or public setting can carry greater weight. Protection should anticipate harm.

A calm review can ask about purpose, necessity, recipients, duration and route to remedy. These questions do not require technical expertise; they organise a decision that is often presented in a hurry.

Practical criteria#

Presenting digital rights as a luxury opposed to convenience creates a misleading choice. A platform can offer a useful function while having a duty to explain which data it uses, limit what is unnecessary and allow a complaint. Easy access does not remove the duty to protect people who use the service.

Keeping the date, a full screenshot and a brief description helps make a precise request. Recording an incident does not dramatise it; it preserves context and supports a concrete response.

Security and privacy#

Digital decisions do not occur between parties with equal power. Those who create an app know its architecture, set initial settings and can steer behaviour through notices, recommendations or time-on-service features. A family or teenager often decides with limited information and under time pressure.

Privacy does not compete with security. Limiting data, protecting accounts and offering clear controls reduces exposure and makes a response easier when something goes wrong. These measures should be designed to support one another.

The role of rules#

Data are not merely private details. Age, location, an image or activity history can influence advertising, recommendations, visibility or access to content. It is therefore important to ask why data are collected, how long they are kept and who receives them.

Data protection and digital-services rules exist because individual negotiation is not enough. They recognise duties of information, minimisation, security and complaint handling, and help identify who is responsible.

A culture of care#

Accepting a pop-up does not prove understanding. Meaningful consent requires a clear purpose, a real possibility of refusing secondary uses and no unfair penalty for someone who limits data. Design should explain consequences rather than hide alternatives.

Individual responsibility matters, but it exists alongside duties of transparency, safety and proportionality for companies, schools and public bodies. Asking every person to identify every risk turns a design obligation into an impossible task.

Youth participation#

Children and teenagers are not miniature adult users. Their experience, reliance on educational spaces and need to belong mean a confusing notice or public setting can carry greater weight. Protection should anticipate harm.

A calm review can ask about purpose, necessity, recipients, duration and route to remedy. These questions do not require technical expertise; they organise a decision that is often presented in a hurry.

Shared responsibility#

Presenting digital rights as a luxury opposed to convenience creates a misleading choice. A platform can offer a useful function while having a duty to explain which data it uses, limit what is unnecessary and allow a complaint. Easy access does not remove the duty to protect people who use the service.

Keeping the date, a full screenshot and a brief description helps make a precise request. Recording an incident does not dramatise it; it preserves context and supports a concrete response.

A reasonable expectation#

The central question is not whether a person can live without an application, but under what conditions its use is requested. A tool that concentrates communication, school, leisure or essential services can affect real opportunities. It should therefore justify its decisions, provide protective settings and offer a contact able to review a specific problem. Utility does not authorise collecting every kind of data or closing an account without an explanation.

This perspective avoids two extremes: banning through fear or accepting through habit. It allows each function to be assessed for need, risk and safeguards. When an answer does not explain who decides, which data are involved or how an error is corrected, more information is still needed for a responsible decision.

A reasonable expectation#

The central question is not whether a person can live without an application, but under what conditions its use is requested. A tool that concentrates communication, school, leisure or essential services can affect real opportunities. It should therefore justify its decisions, provide protective settings and offer a contact able to review a specific problem. Utility does not authorise collecting every kind of data or closing an account without an explanation.

This perspective avoids two extremes: banning through fear or accepting through habit. It allows each function to be assessed for need, risk and safeguards. When an answer does not explain who decides, which data are involved or how an error is corrected, more information is still needed for a responsible decision.