// what the tool compares
Category names
The diagnostic literally compares categories declared in the certificate with categories presented by the request. It receives no name, address or attribute value.
11
digital identity
Check the request before sharing
The registry and certificate should make the requester verifiable. The wallet must warn about categories requested beyond the declaration and retain the transaction’s minimum evidence.
Reference checked on 2026-08-29. Do not enter a name, identifier or personal attribute value.
- public model
- v1.0.0
- pre-sharing checks
- 3
- receipt fields
- 6
// LOCAL REQUEST AUDIT
Who asks for what from your identity?
Compare the categories declared in the certificate with those requested by the transaction, then inspect the receipt left by the wallet.
Educational examples
The examples describe no real service. They only demonstrate the comparison logic.
Method, sources and limitations
Comparison is literal after typographic normalisation. Synonyms may be incorrectly flagged as different. The “stop” status is this tool’s precautionary rule, not a decision imposed on every wallet. The tool does not validate legal basis, necessity or a service’s real identity. Enter category names only, never personal values.
- Public registry of wallet-relying parties primary source
- Request-to-certificate comparison and overasking warning primary source
- Minimum transaction-log fields primary source
- Dashboard, erasure and reporting primary source
Reference checked on 2026-08-29 · model v1.0.0
// what it cannot decide
Lawfulness and necessity
A match does not prove that collection is necessary or lawful. A difference may also reflect synonymous labels. The certificate, legal basis and context still need review.