Preventing Abuse of Digital Credentials

W3C Draft TAG Finding

More details about this document
This version:
https://www.w3.org/2001/tag/doc/draft-finding-web-no-papers-20250807/
Latest published version:
https://www.w3.org/2001/tag/doc/web-no-papers/
Latest editor's draft:
https://w3ctag.github.io/web-no-papers/
History:
Commit history
Editors:
Daniel Appelquist (Samsung Electronics)
Martin Thomson (Mozilla)
Feedback:
GitHub w3ctag/web-no-papers (pull requests, new issue, open issues)
www-tag@w3.org with subject line [web-no-papers] … message topic … (archives)

Abstract

The use of digital identity for web users presents many opportunities for abuse. This risk is heightened when legal names or identities are involved. This document explores some of these risks, with a focus on the presentation of government-issued digital credentials. Misuse of these systems risks doing irreparable harm to individual autonomy online.

Status of This Document

This is a preview

Do not attempt to implement this version of the specification. Do not reference this version as authoritative in any way. Instead, see https://w3ctag.github.io/web-no-papers/ for the Editor's draft.

This is a draft TAG finding and does not yet represent TAG consensus.

1. Background

APIs that facilitate access to verifiable claims about identity, such as the proposed Digital Credentials API, are starting to be developed and deployed. A large number of jurisdictions are starting to create digital identity systems for their citizens. The Federated Identity Working Group includes an API for accessing these systems as a chartered deliverable.

Digital identity APIs provide a convenient way for websites to access proof of legal identity. This convenience leads to a range of implications for privacy, as noted in a recent objection to the formation of the Federated Identity Working Group [OBJECTION].

The TAG believes that the addition of government-issued digital credentials to the web has great potential to cause the harms listed in the objection:

The report produced by the W3C Council [COUNCIL-REPORT] also acknowledged these problems and recommended that these concerns be addressed in the work of the Working Group.

2. Finding Summary

The TAG believes that the addition of government-issued digital credentials to the web has great potential for harm.

The benefits of digital credentials must be aligned with the web user's needs. Following our established principles for privacy, this includes providing people the tools to understand and control how their personal information is collected and used. A browser — or user agent — plays an essential role in mediating these types of requests and ensuring that people have agency.

The web should not become a platform that demands your government-issued identity documents, in the course of its normal operation. Use of such credentials should be exceptional, only when required, and always on a person's own terms.

The TAG therefore encourages contributors to pay special attention to the societal impact of digital credentials.

3. Uses for Identity Information

There are multiple reasons that a site might seek to ask for proof of legal identity. Often, there are multiple reasons that a site seeks to identify a visitor.

Motivations that tend to produce user-beneficial outcomes include:

These uses are not necessarily directly felt by people who are required to present credentials, but they can provide a societal benefit that outweighs the costs to individuals. Each of these still carries the potential for abuse.

There are also motivations for which requesting identification is not justified and those that are outright harmful to end user interests:

That is, while at least some of these goals are beneficial, the use of identity documents is not appropriate. Any benefits are not justified by the cost that people pay in terms of losing their ability to control the identity they present [PRIVACY-PRINCIPLES]. Other goals are inherently objectionable.

5. Overuse of Identity

A streamlined process for providing verifiable identity reduces the cost of requesting and providing that information. In turn, this will make sites that would otherwise not ask for information choose to take advantage of reduced friction to make a request.

Though increasing friction might not be worthwhile, other mechanisms might be used to disincentivise requests for legal identity. A method that might alter the costs for site operators is described in 7.1 Authorizing Sites.

Normalizing the practice of providing identity credentials to websites risks serious harm. Providing any form of external identity information needs to be an exceptional process.

For example, it is entirely inappropriate to use government-issued credentials as a login credential, even if credentials are used during account creation.

5.1 Case Study: Aadhaar

That digital credentials might be used to track people is not a fancy of science fiction, it is the lived experience of a very large number of people.

In India, the Aadhaar national identity scheme was introduced as a way to enable access to government services, like health, welfare, and food assistance. Though the legislation originally included the option for Aadhaar to be used by non-government actors, that provision (Section 57) was ruled unconstitutional by the Supreme Court in 2018.

In 2025, the Indian government has enabled wide use of Aadhar for any entity, expanding the set of recognized reasons to include "promoting ease of living for residents". As a result, the roughly 1 billion Indian participants in the Aadhaar program are potentially subject to surveillance through the use of their unique 12 digit identifier, which links fingerprints and iris scans to name and other personal details.

Despite Aadhar use being optional in law, even prior to this change, refusals to do business were widespread in employment and other non-government interactions. This further highlights the need for accountability, but also demonstrates that there are strong incentives that motivate the use of legal identity where it is available. Privacy therefore depends on having an equivalently strong countervailing force.

6. Exclusion

Online services that have real-name policies are justifiably controversial. The use of legal identity provides very different social dynamics when compared with pseudonymous or anonymous systems.

Insistence on use of legal identity inevitably excludes certain people, which can be for a range of reasons:

In some cases, such as Aadhaar (5.1 Case Study: Aadhaar), the law recognizes the risk that people might not be able to produce evidence that they hold a credential and forbids discrimination against those who do not authenticate. However, what matters is whether refusal is respected in practice.

Even if laws only permit the use of digital credentials as a convenience, there is a risk that no alternative means of access to services are provided. This leads to exclusion.

It should not be possible to refuse service to a person based on their refusal or inability to provide a digital credential. This is aligned with such principles as not revealing when assistive technologies are in use or non-retaliation.

6.1 Centralization of Trust

Any website that requests legal identifiers needs to decide which legal identities it accepts. The easiest way to do this is to trust the issuers of credentials that are most-used among visitors and distrust the rest. Another way might be to choose government-issued credentials from jurisdictions in which the site has a legal presence. This risks centralization of trust in the most-used credentials and makes it hard for any new authority to become trusted.

This centralization can lead to a fragmented web, where access depends on which authorities a site or user is willing, or able, to work with.

This also risks marginalizing people who are unable to obtain accepted credentials for any reason. The choice of jurisdiction is not often something that a user can choose, but instead one dictated by factors outside of their control. This could undermine the global and open nature of the web.

For example, a visitor, migrant, or refugee may not be able to, or may not feel safe to, use credentials from their country of origin. Especially where major platforms only recognize a narrow set of issuers, or only recognize issuers tied to a specific jurisdiction.

6.2 Centralization of Control

The implementation of identity verification is complex. Sites might choose to delegate to external services to manage the process.

It is possible that a limited number of service providers will be capable of implementing the technical and legal process of gathering and validating credentials. This is presently the case for payments infrastructure, which has high degrees of consolidation.

Centralized control provides opportunities to use — or, depending on perspective, abuse — the power it confers to advance political goals. For instance, centralized control over access to payments infrastructure has been used to refuse business from sex work, legal drugs, and video games.

Open standards and implementations can help reduce this risk of capture. Designing systems and standards to minimize any structural bias that might lead to market consolidation is better.

7. Use Cases and Technical Options

A better understanding of why sites seek to obtain and use identity is necessary. While the universality of a generic solution is appealing, each use case could depend on providing different sorts of information, as discussed in 3. Uses for Identity Information.

Each use case might require a different type of solution. Different solutions can have dramatically different privacy characteristics.

The properties of different approaches need to be understood and matched to needs. A possible data minimization approach might choose to use selective disclosure, so that people can choose what is disclosed to sites. Such a system can accept the linkability risks on the basis of the need for identifying information. Such a system might instead avoid identifying information, but rely on linkability as an essential feature, because it might be used to trace bad actors when necessary. These are very different reasons to use the same technique, with dramatically different privacy and control characteristics.

A system that seeks to authorize based on certain traits — such as a system to authorize access to online gambling, something that might be restricted by age or past history of susceptibility — might be best suited to a zero-knowledge system that provides strong unlinkability.

This highlights that there is no single approach that will work in all cases. For a web API, like digital credentials, this is challenging, because such APIs need to serve a range of purposes. However, this highlights that it is unlikely to be clear to the people who need to authorize use of their credentials whether the system they are participating in has adequate safeguards for the situation.

Developing a better understanding of what is appropriate for a given situation will take time. Developing the necessary understanding of different uses of new technology — and then evolving norms to handle those situations — is not something that can be rushed. Deployment is.

7.1 Authorizing Sites

The architecture specified in the European Union’s digital identity eIDAS regulation envisions not only the issuance of digital credentials to individuals, but also the explicit authorization of businesses and service providers that will request those credentials.

These business or government entities (known as "relying parties") must be registered and approved by identity issuers, before they are granted permission to access the system. Relying parties can then request only the information they received approval for. This design is intended to ensure that businesses and agencies cannot request arbitrary personal data, and that their ability to do so is constrained, transparent, and subject to oversight.

This depends on having a system for transparency:

relying parties should provide information regarding the data that they will request, if any, in order to provide their services and the reason for the request.

Transparency contributes to accountability by making it possible for users to understand who is asking for what, and under what legal authority. This safeguard mitigates against some of the risks associated with digital credentials. However, it does not eliminate the need for scrutiny, particularly with regard to proportionality of use, user control, and the risk of such mechanisms becoming normalized across the web. Nevertheless, we recommend that the specification authors look to such mechanisms as a guide for mitigating potential harms in this area.

7.2 Multiple National Credentials

Individuals with more than one nationality, when traveling across international borders, have the choice of which credential (passport) to assert. For example, a person is generally required to present a passport for the country they entering if they are a citizen of that country, even if they hold other passports. When entering a country in which they do not hold citizenship, individuals with multiple nationalities have the choice of asserting whichever nationality is more convenient.

The systems that support digital passport credentials — and therefore enable these assertions to move to the digital domain — should not behave any differently. It's vital that national authorities are not able to query or enumerate what credentials may exist and equally important that end users remain in control of what information is provided.

7.3 Avoiding Dependence

Any credential system needs to carefully consider what might happen if someone is unable to authenticate or they refuse to.

A protection that might protect people who cannot provide a credential, for any reason, might be to artificially induce a non-trivial failure rate even where credentials are available and valid. This might ensure that sites do not come to assume that all users are equally able to produce a credential and so build systems to handle failures.

Any choice to induce such failures needs to be balanced against the potential for fallback mechanisms to be considerably less private.

8. Call to Action

The TAG supports the work on digital credentials. And we also encourage the groups working in this space to consider all the risks associated with these technologies with open eyes, and to develop mitigations where possible. We encourage threat modelling to understand how these technologies can be misused and potentially lead to unintended and negative societal consequences.

In the Ethical Web Principles, we called for putting "internationally recognized human rights at the core of the web platform". We can think of no area of current work where this is more important.

A. References

A.1 Informative references

[COUNCIL-REPORT]
W3C Council Report on the Formal Objection Against Federated Identity Working Group Charter — Adding Digital Credentials API. 2025-02-20. URL: https://www.w3.org/2025/02/council-report-fedid-dig-cred.html
[ETHICAL-WEB-PRINCIPLES]
Ethical Web Principles. Daniel Appelquist; Hadley Beeman; Amy Guy. W3C. 12 December 2024. STMT. URL: https://www.w3.org/TR/ethical-web-principles/
[OBJECTION]
[/wg/fedid] Formal Objection (charter review). W3C. 2024-09-12. URL: https://lists.w3.org/Archives/Public/public-review-comments/2024Sep/0017.html
[PRIVACY-PRINCIPLES]
Privacy Principles. Robin Berjon; Jeffrey Yasskin. W3C. 15 May 2025. STMT. URL: https://www.w3.org/TR/privacy-principles/