Verity ID
Privacy policy.
How Verity ID handles account sign-in, public handles and optional verification.
Request account deletion without installing or signing in to the app.
Who operates Verity ID
Kevin Koh operates Verity ID. For support, privacy questions, or an account-data request, contact admin@verity.id.
Google sign-in and account data
Google sign-in lets you create or recover a Verity ID account. Verity processes Google’s signed identity token on its server to check the issuer, account identifier, audience, expiry and sign-in nonce. We store the Google account connection and verified email with the Verity account. We do not use your email as a public profile identifier. Google sign-in alone does not prove personhood, possession of a device key, or employment. The sign-in flow does not request access to Gmail, contacts or Google Drive.
Sign in with Apple
The iOS app also offers Sign in with Apple for account creation and recovery. Verity checks Apple’s signed identity and sign-in nonce and stores the verified provider identifier and an email address when supplied, which may be a private relay address. An Apple account is separate from a Google account; matching emails do not link them. Server-only Apple grant material is retained in protected account storage, or temporarily during registration, so authorization can be revoked when the account is deleted. It is not part of your public profile or verification credential.
Where sign-in information is kept
Identity tokens are processed in memory for sign-in or proof generation. Verity does not store a Google refresh token in its account database or app-managed account storage. The native Google SDK can hold its own authentication state in the operating system’s protected storage during sign-in; the app clears local SDK state when the sign-in finishes or is cancelled. Browser session storage holds a short-lived Verity registration token, private continuation material and the operation needed to recover an interrupted claim. These are separate from a Google grant.
Your account and public handle
Verity stores account connections, device bindings, verification credentials and account preferences needed for the features you use. Reservation and sign-in records have expiry times. A handle becomes public only when you explicitly choose Claim and publish after reviewing the signed-in account and handle. The store app shows and shares your own handle as plain text. The separate web profile can show the handle and user-entered social links; it does not publish your private verifications, sign-in email or internal account identifier. Ordinary handle changes reserve the previous name while the account remains. Fulfilled account deletion removes its active and retired handle records, so those names may be claimed again.
Optional verification and organization proofs
Passport, device, liveness and organization verification are separate from Google account sign-in. Depending on the feature, Verity processes device attestations, credential results, account-scoped identifiers and disclosure settings. The organization proof uses Google Workspace identity claims and a separate proof policy; supported custom domains can issue an account credential without onchain registration. In a browser proof flow the Google token is used by the browser prover; in a native proof flow it is used by the phone prover. Proofs, organization-policy bindings, transaction records and pseudonyms submitted to a public chain can remain public permanently. Verity cannot erase public-chain history.
Service providers and retention
The features you use can involve Google and Apple for sign-in, AWS for application hosting and storage, Telegram for organization-request delivery, and the relevant public network for proof transactions. Optional identity verification can also involve our configured verification providers and TEE gateway. We keep durable account records to operate and recover your account; expiring authorization and reservation records are checked for expiry by the application and removed through the storage lifecycle. Logging and backups have separate storage lifecycles. A privacy request must distinguish removable account data from records subject to a documented retention requirement and public-chain history.
Your choices and privacy requests
You can sign out of Verity, manage a connected Google account where that control is available, and remove Verity access in your Google Account’s third-party connections settings. Removing a Google grant does not itself delete a Verity account, revoke every Verity session, or erase a public handle or chain record. Local logout, app reset and uninstall are not whole-account deletion. Use Request account deletion in the app, including during authenticated account setup, to submit a verified request. Deletion is fulfilled manually after ownership and data checks; submitting a request does not immediately disable the account. You can also request account deletion without the app at /account-data or email admin@verity.id for access, correction or deletion. We will verify control of the affected account and explain the records that can be removed and any records that must be retained. Do not send passwords, Google tokens, private continuation codes, passport scans or biometric images by email.