Your identity is yours.

hashID combines three roles in one app: wallet (keep and present credentials), issuer (issue credentials) and verifier (check them). It also includes hIDcom, an end-to-end encrypted messenger, and hIDvault, a vault that keeps your data and treasures safe. From 5 November 2026.

A wallet is like your purse, only for credentials: ID, proof of age, membership card, employee badge. Instead of sending a copy of your ID, you show only what is asked for. At the cinema: over 18, yes or no. At the club: member, yes. With hashID you don't even see the wallet, it works in the background.

hashID is EUDI-compatible and OpenID-conformant. The app uses the same open standards as the European identity wallets: OpenID4VCI, OpenID4VP and HAIP, with SD-JWT VC and mdoc under ISO/IEC 18013-5. As soon as the official EU certification for EUDI wallets is in place, we will go for it, with the aim of getting hashID onto the official list.

Under eIDAS 2.0, every EU member state has to offer its citizens a digital identity wallet by the end of 2026. hashID is built for exactly this ecosystem: receiving, presenting and verifying credentials to EU standards.

The other side asks, for example: over 18? hashID answers only yes or no. It is based on the signature in your ID chip, not on an estimate by camera or AI. This is called deterministic: mathematically sound, the signature is either valid or it is not. Any estimate that can be wrong is called probabilistic.

Your credentials stay on your phone, protected by its secure hardware. When you present them, only you decide what goes out, and nothing goes out beyond what is asked for.

With hIDback you get everything back: new phone, put hashID on it, fetch your backup, show two of your three keys, done. Without a backup there is nothing to get back, because your data only lived on the old phone. So it is best to set up hIDback on day one. And whoever finds your phone has only one key, which means nothing.

Everything that would otherwise be lost with your phone: your contacts, your chats, your hIDvault, your settings, your hashID account and the list of your credentials, meaning what you had from whom. You can add your media if you like. The credentials themselves are bound to the phone and get reissued. And whatever was meant to delete itself stays deleted.

No, you tap instead of run. hIDback shows you the list: what you had from whom. First you scan your ID card again, then you collect one entry after another, usually with a single tap. Only where an issuer wants to see you in person does the list say where to go. And the issuer can revoke your old credentials while you are at it.

Wherever you like: on a USB stick, on your laptop or NAS at home, with someone you trust, or in your own cloud. The backup is encrypted, and without two of your keys it is worthless. That is why the backup may live anywhere, but the keys may not. Ideally keep it in two places.

No, and that is on purpose. There is never a backup on the hashID server, and hashID has no master key, not even for emergencies. Your backup is wherever you put it, just like in real life. And only you can unlock it, with two of your three keys. So print your emergency kit and keep it somewhere safe, not next to your phone.

Three by default: your phone, your emergency kit on paper and a secret only you know. You can add someone you trust, or a retired phone that stays offline in a drawer. More keys, more ways back. If you want it stricter, require three keys instead of two.

Your hIDvault holds … let it surprise you. You're going to love it.

hIDcom encrypts messages, voice and video calls end to end, with forward secrecy. CypherLock takes it further: protection levels from Normal to Journalist, your own keys per chat if you want, decoy traffic and random delays against traffic analysis, and an invisible watermark in your files that only you can read. Messages are deleted from the server once delivered. The servers are in Germany and cannot read the content.