A gendered title at checkout or an outdated detail in an official register can seem like a small administrative matter. But recent European court rulings show how data protection law can give LGBTIQ people practical ways to challenge unnecessary or inaccurate personal data. The wider question is how well these protections will work as digital systems and EU rules evolve.

Essential Takeaways

  • Less data, where possible: In the Mousse case, the Court of Justice said a rail operator couldn’t require customers to choose a gendered title when buying tickets if that information wasn’t necessary for the service.
  • A route to correct records: In Deldits, the Court said inaccurate gender-identity data held in an asylum register must be rectified.
  • The GDPR offers several tools: Its principles include data minimisation and accuracy, while Article 16 provides a right to rectification.
  • Reform brings questions: The European Commission’s Digital Omnibus aims to simplify data rules, but commentators have raised concerns about possible effects on people’s ability to identify and challenge harmful processing.

Everyday data rules can have real consequences

A title dropdown may look harmless, until you’re asked to choose between options that don’t reflect who you are. In the Mousse case, the Court of Justice of the European Union considered whether SNCF Connect could require online rail customers to select “Monsieur” or “Madame”. The Court found that a customer’s title wasn’t objectively indispensable to providing rail transport, and noted that generic, inclusive language could be used instead, according to the Court’s press release. [2]

That reasoning brings a practical GDPR principle into sharp focus: personal data should be limited to what’s needed for its stated purpose. The Court also said that a company relying on legitimate interests must show that processing is strictly necessary, inform customers and weigh its interests against their rights. The risk of discrimination linked to gender identity matters in that assessment. [2][4]

When an official record doesn’t reflect someone’s identity

The Deldits case took the issue from a retail checkout to a public register. VP, a transgender refugee in Hungary, sought to correct gender information in the national asylum register, which did not reflect VP’s gender identity. The Court considered the request under the GDPR’s accuracy principle and right to rectification, set out in Article 16. [3][4]

The judgment says authorities responsible for a public register must rectify gender-identity data when it is inaccurate. It also addresses the evidence an authority may ask for and the relevance of national procedures for legal gender recognition. That makes data protection a possible route to correcting official records, including where domestic procedures offer no straightforward way to do so. [3]

More than privacy: data protection and cross-border recognition

These cases sit within a wider debate about what data protection can do for LGBTIQ rights. The GDPR’s principles of accuracy and data minimisation, its right to rectification and its protections for certain sensitive information can all matter when public bodies or companies collect and use personal data. But the law’s application depends on the purpose and circumstances of each instance of processing. [4]

Cross-border recognition offers another strand of context. In Mirin, the Court considered whether Romania could refuse to recognise a change of first name and gender identity that had been acquired in another state while the person exercised EU free-movement rights. The Court ruled that EU citizenship and free movement precluded refusal in the circumstances of the case. Mirin was not a GDPR judgment, but it shows how other parts of EU law can also constrain the way authorities handle a person’s legally established identity. [5]

Digital reform raises a difficult question

The European Commission’s Digital Omnibus is presented as an effort to simplify and modernise data-related rules, reduce compliance burdens and make data easier to use. Its communication sets out those aims; it isn’t a final law, nor does it establish that proposed changes will necessarily weaken rights. [6]

Still, the practical concern is worth watching. If people can’t discover that data about them has been used in a harmful way, or struggle to prove what happened, a right to challenge the processing may be difficult to use in practice. The wider digital landscape also includes the Digital Services Act, which sets rules for online intermediary services, including obligations involving transparency and systemic risks for certain large services. It isn’t a dedicated LGBTIQ-rights law, and what it delivers depends on how its duties are applied and enforced. [7]

The law’s promise depends on how it’s used

Together, Mousse and Deldits show that data protection isn’t only about keeping information private. It can also question why information is collected in the first place, and provide a way to challenge records that are inaccurate. For LGBTIQ people, those everyday details can carry consequences well beyond the form or database where they appear. [2][3][4]

But a legal right is most useful when people and organisations can understand how to use it. Clear guidance for advocates, practitioners and public bodies could help turn principles such as accuracy and data minimisation into practical steps, while careful scrutiny of future reforms will matter too. [4][6]

A small data field can have a large impact, so it’s worth asking whether it needs to be there at all.

Source Reference Map

Story idea inspired by: [1]

Sources by paragraph: