Privacy by design

Ask for the proof you need, not the identity data you do not.

One of the important design goals of the EUDI Wallet ecosystem is selective disclosure: enabling a user to present the required information without automatically exposing every attribute held in a credential.

Adminyra EUDI
Your software
Adminyra API + verifier
EUDI Wallet
Attribute minimisationPurpose bindingPolicy controlReduced data footprint
01

From document collection to attribute verification

Traditional onboarding often collects an entire document even when the service only needs one fact. A wallet-based workflow can be designed around narrower attribute requests, depending on the credential and use case.

Examples include proving an age threshold, retrieving specific identity fields for a regulated onboarding process, or verifying a driving entitlement without treating the complete document image as the primary artefact.

02

Policies should match declared intended use

The European Digital Identity Regulation requires relying parties to declare their intended wallet use and the data they plan to request. It also states that relying parties shall not request data beyond what they indicated during registration.

Adminyra models requested attributes as verification policies so the application can use an approved policy instead of assembling arbitrary attribute requests at runtime.

03

Less stored data, smaller breach impact

Data minimisation is not only a privacy principle. Reducing collected and retained identity data also reduces the amount of sensitive information a service must protect, govern and delete.

The Adminyra control plane therefore stores operational metadata separately and is explicitly designed not to persist wallet presentation payloads or identity claims in its normal transaction records.

FAQ

Questions teams ask before integrating EUDI Wallets

What is selective disclosure?

It is the ability to disclose only the specific attributes or proofs required for a transaction rather than presenting an entire identity document or credential dataset.

Can I request any wallet attribute I want?

No. Requests must fit the relying party's legitimate and registered intended use, applicable law and the credential types available in the ecosystem.

Does Adminyra store the disclosed claims?

The control-plane architecture is designed to avoid persistent storage of wallet claims. Any production handling of presentation content will be transient and bounded by the verifier workflow.

Primary sources

Official material behind this guidance

Build before the rush

Start with a real use case in the sandbox.

Model the relying party, define the minimum data request and integrate the application flow before production trust infrastructure is required.