Help

VouchMesh is a product of Quavolve. The current service helps you share selected affiliation claims after checking access to an organization email address.

Create and share a proof

  1. Open Verify, choose an affiliation and enter your organization email. Enter the code sent to that address.
  2. Keep the resulting credential in your browser wallet. Use the same browser and device to return to it. Clearing browser storage can remove it.
  3. Open Share, select the claims to disclose and create a proof link. Review what you are sharing before sending the link. A recipient may forward it.
  4. Use the link controls to revoke a link you no longer want to share. Revocation cannot erase information a recipient already saw or copied.

An optional camera check may be offered during verification. It assesses liveness; it does not establish your legal identity. Read about camera and biometric processing before choosing it.

Combine identities and create a limited proof

Open the identity center. Successful email verifications in the same browser join your private master identity as separate child sources. Existing wallet credentials can be imported after proving possession of the browser key.

Select any non-empty combination of sources, choose a disclosure level and fields for each, then generate a token or URL. Both use the same counter: one successful verification by default, or a limit you choose. Opening the URL does not consume it; clicking Verify does. A spent proof shows “Already used” without claims. Invalid or revoked proofs show “Verification failed”.

Anonymous disclosure is the default. Organization domains and full email addresses require encrypted retention during verification and an explicit permission for the specific source. The master policy sets an additional ceiling. Saving an address, selecting all sources or merging identities never automatically authorizes these fields.

To merge browsers, copy the target master ID, generate a merge code from the source browser, then accept it in the target browser. Codes expire after ten minutes, work once and only for the named destination. Source access and earlier proofs become invalid; source restrictions remain in force.

Sign in with Google and restore your identity

Open Google login from your profile or identity center. If you are already signed in, this links Google to that account. Otherwise, it signs you in to the account identified by Google's stable account identifier. Matching email addresses do not automatically join separate accounts.

Google sign-in restores the account's private master identity and adds a Google account child source. To combine a different current identity with that master, explicitly check the merge option before continuing. Without consent, a nonempty current identity is kept and the merge is rejected. Independently anchored accounts cannot be merged. Google sign-in restores server identity sources; browser wallet credentials still require their original browser key.

The Google source defaults to anonymous disclosure and remains valid for 30 days after authentication. Sign in again to refresh it. Refreshing does not enable a source you turned off. To disclose an email or signed Workspace domain, allow that field for the concrete Google source, your master policy and the proof you create. Google login does not prove employment, organization authority or unique personhood. Only basic authentication and email are requested; the service does not read Gmail or Drive.

Signing out removes both account and master-identity access from the current browser. Your sources and other signed-in devices remain available. Use account deletion for the linked Google data described in the Privacy Policy.

What does a proof establish?

Email verification establishes access to an address at the time of the check. Roles such as student or employee are self-asserted. A proof does not confirm current enrollment, employment or authority to represent an organization.

Selective disclosure conceals unselected credential claims from a verifier. The service still processes email addresses, domains and other records. See the Privacy Policy for details and the limits of account deletion.

AI-agent identity

An AI agent can register as a verification client without a browser session. Submit the agent's name and an authorized mailbox at POST /v1/agents/register, then read the six-digit code through the agent's own mail connector and confirm at POST /v1/agents/register/confirm. Store the one-time API-key secret in the agent's secret store. Use that key with /v1/agents/me, key rotation and revocation. A regular developer key is rejected by these lifecycle endpoints. Do not automatically retry code confirmation or key rotation.

This registration only proves mailbox control for a verification client. It does not assert owner identity, affiliation, personhood, registry endorsement or delegated authority. Ownership binding and delegated permissions remain future framework work. Public identity tokens can be checked at POST /v1/identity/verify; invalid and spent tokens disclose no claims.

Developers and support

See the developer overview and plans and limits. Startup and Growth checkout is available in Stripe TEST mode for evaluation; use a Stripe test card and do not enter a real card number. Test keys are not metered and test mode does not create real charges. For live keys, cryptographically valid presentations count toward usage even when a requested claim assertion does not match.

For help, contact [email protected]. Describe the page and error you encountered, but do not include an API key, login link, verification code or recording. Visit your profile for account controls and Changelog for public updates.