Design intent · Pre-launch · Last updated 2 November 2026
Versidian is pre-launch. This page describes the commitments the service is being built against, the standard we intend to be measured by. It is not an operative privacy policy: the service's full privacy notice will be published when the service launches, and we expect it to be read side-by-side with this page. Our website's own data handling is covered separately, in the website privacy notice.
Our charter. Versidian Inc is a Delaware public benefit corporation. The specific public benefit in our certificate of incorporation is: "to reduce the collection, retention, and exposure of individuals' personal data in digital interactions by advancing technologies that enable people to prove facts about themselves without revealing the underlying information."
The principles below are how we intend to deliver on it.
Versidian is designed so that your documents are checked one time, by AI running where the data is, and Versidian's own copies are then destroyed within seconds: not archived, not kept "for quality," destroyed. What you keep is the only copy, on your own device, and the ability to prove what a site needs: that you're old enough, for example. We are building so that we keep no copies of you.
We are building a verification service, not a data business. The design goal is simple to state and hard to retrofit: no user database. Identities and activity records that are never accumulated can't leak, can't be sold, and can't be quietly repurposed later, by us or by anyone who comes after us. Versidian is built so that it retains no identity documents, no identities, and no record of where or when anyone verifies.
A platform asking about age, for example, is owed an answer about age, nothing more. Versidian is designed so the platform receives a yes/no and a signed compliance receipt, with no personal data, designed to evidence the check for its regulators: no name, no birthdate, no document. And no thread that ties you together across sites: two platforms should not be able to tell they ever met the same person.
By default, Versidian is designed so that it does not hand a site a way to recognize you when you come back: each visit is fresh, and unlinkable, everywhere. Where the law allows, a site may ask you to carry a persistent handle for that site only, for example to keep banned accounts out. It is visible to you, it works at that site alone, and it is not the default. In either case, Versidian is committed to giving no two sites a way to tell they ever met the same person.
Proofs are designed to come from your own device, built on cryptographic proofs, mathematics that can demonstrate a fact about you without revealing what sits behind it. The question gets answered; you don't get exposed.
A protection that exists only in a policy can vanish with the next edit of that policy. Wherever possible, we are building protections that hold because of how the system is constructed, not because of what a document says on a given day. This page is the promise; the architecture is the point.
Holding us to it. When the service launches, we will publish its full, operative privacy notice, and this page is the standard we expect that notice, and the shipped product, to be measured against. If we ever fall short of these principles, we would rather be told loudly: Inquiries@Versidian.com.