Skip to content

Privacy ​

Tamga's basic rule: a verifierThe party that checks a presented credential: signature, issuer in the trust list, status and policy. Also called relying party. sees only what it needs, and nobody can track a person across sites. Four tools make this work.

Selective disclosure ​

Every field of a credential can be withheld on its own (selective disclosureShowing only the fields a verifier asks for from a credential, and nothing else.). In a job application only "graduated" and "degree" are shown; the grade average and the student number stay hidden. The verifier sees only the salted hashA hash computed over a value together with a random salt, so the value cannot be guessed from the hash; SD-JWT hides fields this way. values of the hidden fields.

One copy per verifier ​

The wallet holds several copies of each credential and shows a different copy to each verifier — and always the same one to the same verifier. Two verifiers cannot match a person by comparing signatures or key values. When copies run low, the wallet renews them in the background.

A pseudonym per site ​

"Sign in with Tamga" sends the website neither an identity number nor a digest of a credential. The wallet derives a separate, stable pseudonymA stable account identifier the wallet derives separately for each website; two sites cannot link the same person. for each site: the site recognises you at every sign-in, but two sites cannot match the same person. When you change phones and verify your identity again, the same pseudonyms come back. One account per person per site is the default.

Age with a zero-knowledge proof ​

The proof "I am over 18" is produced without showing the credential itself (ZK (Zero-Knowledge proof)A proof that a statement is true without revealing the underlying data, for example "over 18" without the birth date.): the verifier sees neither the date of birth nor the credential, and two presentations cannot be linked. The proof system is Longfellow ZKAn open zero-knowledge proof system for mdoc credentials; Tamga uses it to prove facts such as age over 18 without revealing the birth date.; the verifier side is ready in the @tamga-network/verifier/zk subpath and the wallet side (on-device prover) in the @tamga-network/zk package; the prover runs on Android today, the iOS library has not been built yet (there the wallet presents the usual way). Because the proof does not disclose the position in the status list, revocation cannot be checked in the presentation; instead a ZK presentation is made only with short-lived copies of the identity credential (valid for at most 24 hours, refreshed by the wallet on its own) (ADR-0044). The copies of a revoked credential are not refreshed; because the proof binds the copy's type, the verifier sees that it is short-lived. A ZK presentation made without such a copy (unmarked) is accepted only when the verifier's policy explicitly sets accept_unrevocable_zk.

What a verifier must do ​

  • Never log claim values or the status index; log field names only.
  • Do not ask for fields outside the scope of your registration.
  • A person can send you an erasure request from the wallet; keep your registered contact channel up to date.

Details ​