Identity verification

A structured path from submission to review.

Tuvybe identity verification uses authenticated document and selfie submission with explicit review status, resubmission, validity and revocation controls.

Identity verification

Submit

The verification request requires a full name, an allowed identity-document type, the document file and a selfie image.

  • File type and size validation.
  • Authenticated submission.
  • Private verification workflow.

Review

A request can carry review notes, requirements and status reasons while the platform evaluates the evidence.

  • Pending and review states.
  • Resubmission can be requested.
  • Review metadata remains separate from the public profile.

Maintain status

Approved verification can have validity and expiry information, and verification can later be revoked where required.

  • Verification level and status.
  • Approval timestamp.
  • Expiry and revocation support.
Role-sensitive trust

Verification can be a prerequisite for higher-trust roles.

Tuvybe keeps normal account verification and approved commercial roles connected but distinct. Host and Guardian records carry their own verification state in addition to the user account.

  • Host approval requires the relevant verification requirements.
  • Guardian approval also uses role-specific verification state.
  • Verification status can change independently of public profile presentation.
Verification is not a guarantee

An approved identity check confirms that the platform accepted the submitted verification evidence under its process. It should not be treated as a guarantee of a person’s intentions or conduct.