Learn/Foundation of TrustIdentity

Digital ID on Your Device: Logging In With a Key That Never Leaves the Chip

MATA's digital ID is a DID whose private key is made and kept in your phone or laptop's secure chip. You log in with Touch ID, Face ID or Windows Hello, and nothing is typed.

Signed by M·
A brass house key lying on the dark glass of a smartphone on a walnut desk
How does a digital ID on your device replace a password?

Instead of a secret you type, MATA gives you a decentralized identifier whose private key is generated inside your device's secure chip. When a site asks who you are, you approve with Touch ID, Face ID or Windows Hello, the chip signs a challenge, and the site checks the signature without ever receiving the key.

Think about how many places hold a copy of your login. Every site with a password field keeps a record of it, every password reset sends a link to an inbox, and every text-message code can be redirected by someone who talks a phone shop into moving your number. The identity is "yours" only in the sense that you are allowed to use it.

MATA's digital ID works the other way round. It is a decentralized identifier, a DID in the sense of the W3C DID specification, whose private key is generated inside your device's secure chip and never leaves it. A digital ID on your device unlocks with Touch ID, Face ID or Windows Hello. When a site wants to know it is you, the chip signs a challenge and the site checks the signature. There is no secret to type, so there is nothing for a phishing page to collect and no password file for a breach to leak.

This is the login half of Wallet & Identity; the other half is a private screen for your bank accounts. How the wallet, the DID and the human signature fit together is in Wallet, DID and IAMHUMAN.

Why a Typed Secret Is the Weak Point

A password can be typed into the wrong box, reused on a site that gets breached, or reset by whoever controls your email. The NIST digital identity guidelines describe a better model, in which a verifier confirms a claim without holding a copy of the secret. A device-bound DID is that model built into hardware: the site receives a signature, never the key.

Security agencies have been pushing in the same direction. CISA's guidance on phishing-resistant MFA singles out authenticators that bind a cryptographic key to the device as the form attackers cannot simply trick you out of. The FTC's identity theft resources exist largely because the old model leaks.

In MATA's terms, this sits in Era 1, the Foundation of Trust. Trust is a key that stayed on the phone. Security is the absence of a password database. Incentive is a login that takes a glance rather than a phrase you have to remember.

What Happens When You Sign In

You unlock the device once, the identifier signs, and the site gets a proof. Nothing travels so that a server can "remember" you.

The Key Is Made Inside the Chip

Apple calls it the Secure Enclave, Android calls it StrongBox, and Windows uses a TPM. The names differ but the rule is the same: the identity key is generated within that boundary and used there. Copying it out so a cloud service could restore it "for convenience" would undo the whole point. The same principle covers the rest of the vault, as described in hardware you hold.

The Prompt Is the Interface

There is no extra password for your identity and no code sent by text. The biometric or PIN prompt you already use is the entire user interface, which is why this is faster than juggling a password manager: the password was always the workaround. The EFF has written about how account recovery flows and "sign in with" buttons become tracking points. A prompt that is answered by the local chip does not need to ask a directory who you are.

Phishing Has Nothing to Take

A lookalike page can capture what you type. It cannot get your chip to answer a challenge on behalf of a different site, because the signature is bound to the real one. Credential stuffing, where attackers try leaked passwords on other services, fails for the simplest reason: there is no reused password. A digital ID on your device removes the thing those attacks depend on.

Where You Use It

It is not a photo of your licence handed to a vendor, and not a face scan a platform can revoke. It is a key in hardware, used only when you approve.

Signing In to Other Sites

Sign in with Sovereign ID is a button a site places on its own login page. The visitor approves on their device; the site verifies the signature locally, with no OAuth provider and no key-set download. MATA is not part of that exchange, which is exactly what you want from a key that never left the chip.

Proving a Person Wrote It

IAMHUMAN is a signature that shows a real person stood behind a post or message, without giving a platform the power to switch that person off. It uses the same device-bound key, so login, money and "a human sent this" are three uses of one identity rather than three accounts. The details are in prove you are human.

Turning It On

Your digital ID on your device arrives as part of Wallet & Identity. The Freedom Guide walks you through enabling the vault and enrolling a passkey first, so you have at least two devices before you rely on it. The memory-safe code underneath is part of Remade with Rust. If you want the reasoning behind keeping keys on devices more broadly, read hardware you hold next.

FAQ

Short answers already in this article.

What do I actually see when I log in?

The same prompt you use to unlock the device: Touch ID, Face ID or Windows Hello. There is no second password for the identity and no SMS code, so a swapped SIM card has nothing to intercept.

Can a cloud backup restore my identity key?

No, by design. The key is generated and used inside the Secure Enclave, StrongBox or TPM and is never exported to a cloud vault. If a device is lost you enroll a new one from another device you hold, or through Friends backup.

What does a website learn when I sign in this way?

It receives a signed proof that the holder of your identifier approved this login, and it verifies that proof locally. There is no OAuth provider in the middle, no key-set fetch, and MATA does not see the handshake.

Is this the same thing as uploading a photo of my driving licence?

No. Many services verify identity by collecting an ID photo or a face scan and keeping it. A device-bound identifier proves control of a key instead. Nothing about your face or your documents is sent, and no platform can switch the identity off.

What else uses the same key?

IAMHUMAN signatures, which show a real person stood behind a post, use the same device-bound key, as does the login side of Wallet and Identity. One key covers money, sign-in and proof of humanity, rather than three accounts at three vendors.