privacyportal
Back to Compass
Path consoleIdentity & Accountsmedium risk

Verify without oversharing

Prove you are a real person or meet eligibility rules without uploading government IDs to every app.

20–40 minutesCommunity members and app users facing sybil checks or eligibility gates 1 starting tool

Target outcome

You can pass sybil checks without repeating document uploads to every service

Do this first · quick win

If you only do one thing today: install BrightID, make three trusted connections, and check whether your target app accepts it.

Setup queue

Start with verified tools

Compare the fit, keep the ones you want in My Stack, then open the verified setup guidance.

BrightID

applications

Choose BrightID when apps need proof-of-personhood without centralized KYC for every login.

applicationsEvidence pending
Visit project
More compatible tools (2)

Self Protocol

applications

Choose Self when you need reusable credential proofs with selective disclosure in Web3 apps.

applicationsOpen source
Visit project

Iden3

infrastructure

Choose iden3 when you operate apps that issue or verify programmable credentials.

infrastructureOpen source
Visit project

Understand · act · verify

Your path

Nothing is detected automatically. You decide when a step is done or needs another review.

  1. 1

    Install BrightID and create your profile on a device you control.

    Step 1 · Not started

    • BrightID installed: BrightID opens and shows your profile with a shareable QR or link.
  2. 2

    Connect with trusted people — join a connection party or scan nearby contacts until you reach the connection threshold.

    Step 2 · Not started

    • Connection threshold met: BrightID shows enough active connections for the verification level you need.
  3. 3

    Review which apps request verification and what each level actually proves before accepting prompts.

    Step 3 · Not started

  4. 4

    Link BrightID only to services that need sybil resistance — skip optional KYC uploads when BrightID suffices.

    Step 4 · Not started

    • First app verified: At least one target app accepted BrightID without uploading a government ID.
  5. 5

    Keep recovery and backup contacts separate from your public social graph.

    Step 5 · Not started

  6. 6

    Re-check connection health monthly — inactive graphs can expire and break verification.

    Step 6 · Not started

How you know it worked

  • You can pass sybil checks without repeating document uploads to every service
  • You understand what each verification level proves before sharing it
  • Your BrightID graph stays maintained for ongoing eligibility

Watch out

Verification graphs can be gamed — treat BrightID as sybil resistance, not proof of good intent.

Linking BrightID to a public social account can deanonymize your graph.

Some jurisdictions treat identity proofs as personal data — know your retention obligations.

Key terms
Sybil attack
Creating many fake identities to game votes, airdrops, or access controls — verification aims to raise the cost.
Connection party
A BrightID meetup (in person or online) where participants vouch for each other to build a trust graph.
Selective disclosure
Proving one fact (e.g. uniqueness) without revealing your full legal identity.