What is a digital identity service?

A digital identity service is any service that helps establish, hold, or rely on digital information about who a person is. The category is broad on purpose: it covers the app on your phone, the verification performed when you open an account, and the trust infrastructure that lets unrelated services share confidence in a result.

Almost every digital identity service does one or more of four jobs, and naming the job is the fastest way to understand the product.

• Prove. Verification and proofing services establish that an identity claim is genuine and issue a result — the subject of digital identity verification.
• Hold. Wallets store credentials, keys and consent records so the person controls presentation. See what a digital identity wallet is.
• Decide. Policy layers translate risk into required assurance: which tier, which proof, for which action.
• Attest. Registries and trust frameworks publish what has been approved — which issuers, which verifier versions — so a relying service knows what it is checking against.

Two services can perform identical checks and have opposite risk profiles, decided entirely by what happens to the evidence. The conventional model retains document images and selfies, which turns every verification into a small archive — and archives of identity evidence are attacked precisely because they exist. That is the honeypot problem, and it is structural rather than a matter of operator care.

The alternative produces results and discards or encrypts the evidence: services receive tiers, pass/fail answers and proofs, while raw material never enters circulation. When evaluating any identity service — including this one — the useful question is not “how good are your checks?” but “what exists in your databases about me today?”

• Minimisation. Does the service receive less than the question requires, or the maximum by default? Threshold answers exist for most yes/no questions.
• Retention, stated in numbers. What is kept, for how long, and what happens at the end of it — “promptly” is not a retention policy.
• Consent you can see and revoke. Structured, purposed, time-limited grants with an auditable history, as described in consent as infrastructure.
• Openness. Can the method be inspected? An identity system that cannot be examined asks for trust it has not earned — see how security claims are evidenced here.
• Honest claims. Accreditation, availability and capabilities stated precisely, with limits named. Overclaiming identity infrastructure is itself a warning sign.

This site documents one particular service: the Identity Wallet — a free, open-source digital identity wallet and the verification layer behind it, stewarded by DETIO FOUNDATION LTD, an Australian not-for-profit. It is independent of the Australian Government and claims no accreditation; it states plainly what it is as it rolls out with the VirtEngine network.

For organisations, the verifier-facing side starts at for services — whether the become a verifier path or the integration overview fits depends on where you are in the decision. For everyone else, the get-started guide is the front door.