For users

Keep your identity on your device

Set up Checkify once, approve requests when you choose, and share only what is needed.

Checkify is designed so your identity stays in your hands. You can prove things like “I’m human” or “I’m over 18” without handing over more personal data than necessary.

Get started See setup steps

Why use Checkify

A simpler way to prove what matters without losing control of your personal data.

You stay in control

Every request is shown to you clearly before anything is shared.

Less repetition

Set up once, then reuse your verified proofs across different websites, apps, and QR flows.

Less data sharing

Often you can share a simple proof instead of full identity details.

How it works

A simple setup flow that turns verification into reusable proof.

Secure your device

Protect your Checkify identity with your device security, PIN, and biometrics.

Complete verification

Prove you are human and optionally add government ID verification for stronger assurance.

Approve requests

Review each request and share only the proof or data you choose to share.

User setup steps

From first setup to approving a live request.

Step 1

Protect your device

Secure your Checkify identity with a PIN and Face ID or Touch ID. Your identity stays device-bound and protected by your biometrics.

Outcome: Device secured

Step 2

Prove you’re human

Complete liveness and face confirmation. Checkify converts this into reusable verified signals without sharing raw biometric data by default.

Outcome: Human verified

Step 3

Add optional government ID

Verify a passport, ID card, or driving licence on-device to strengthen your assurance level. You confirm extracted details before they are stored locally.

Outcome: Identity strengthened

Step 4

Scan a verification request

A business can generate a QR request for specific proofs such as “Age over 18”. You scan it to see exactly what is being requested.

Outcome: Request received

Step 5

Review and approve

You approve the request. Checkify shares only what is needed and blocks personal data unless you explicitly consent to share it.

Outcome: Signed response shared

Result

Clear confirmation

Both sides get a clear record of what was verified, when, and for whom, without exposing unnecessary personal data.

Outcome: Verification completed