A Trust Certificate provides evidence that a trust validation occurred, under defined authority, for a specific purpose and at a specific point in time. It does not contain the underlying personal information behind the validation — it certifies that the validation happened, and on what terms.
What it can validate
Trust Certificates may be used to confirm identity, number ownership, consent, authority, contactability, SIM status, or other trust attributes — any specific, bounded question a Trust Authority is positioned to answer.
How a certificate is produced
A Trust Certificate is assembled once a validation request has passed through governance: the requester's authority to ask the question is checked, a lawful basis for the query is confirmed, the request is sent to the relevant Trust Authority containing only the minimum needed to ask the question, and the Trust Authority responds with an outcome — not raw data. That outcome is then assembled into a signed certificate carrying its type, issuance timestamp, expiry window, and the purpose it was issued for, and delivered to the Trust Consumer. The consumer applies its own risk policy on top — the certificate informs the decision, it does not make it.
Why this differs from a data export
A Trust Certificate is evidence, not information. It is governed, auditable, time-bound and revocable, in the same way a certificate of any kind should be — rather than a static copy of a record that, once shared, is out of the issuer's control.