One real human per account. No smurfs, no throwaway accounts, no dodging a ban with a new email.

Nescio ID confirms each player is a real, unique person and gives your game one stable, anonymous ID for them. Only a zero-knowledge proof leaves the phone: a unique nullifier and the facts your game asks for, like a minimum age. We turn it into a one-way pseudonym. No name, birthdate, document number or photo.

Get a free sandbox key → Try to beat it

Self-serve, with mock passports. Live keys are switched on after a quick review.

What Nescio knows about this playerexample player

Name: nescio
Date of birth: nescio
Passport number: nescio
Face photo: nescio
Email address: nescio
verified_human: true
over_18: true *
issuing_country: "ESP"
subjectId: "a91f…"

Nescio is Latin for “I do not know.” That's how the system works: the fields above are never collected, so there is nothing identifying to leak.* Only if your game sets a minimum age of 18+; otherwise null. Age is optional, per game: none, 13, 16, 18 or 21.

Verify the human, not the paperwork.

Three steps. Only the first one involves the player, and it happens on their phone.

The player scans their passport
In a passport app, Self or ZKPassport, they hold their passport's chip to the phone. The app creates a zero-knowledge proof: math that confirms facts like “real and unique” without revealing the data behind them.
Nescio checks the proof
We verify it and derive a one-way pseudonym from its nullifier. We keep that pseudonym and a few claims: human, nationality, and the minimum age proven if your game asked for one. No name, birthdate, document number or face image is ever stored.
Your game gets a player ID
Your backend receives a stable subjectId, can look up claims such as verified_human, and gates whatever it wants on them.

What players need

A passport app: Self, on iOS and Android, reads the passport and generates the proof on the device. ZKPassport works the same way, adds a face check against the chip photo, and is available in sandbox today.
A passport with an NFC chip: Look for the chip symbol on the cover. Passports without a chip can't be verified today.
One identity per passport: Uniqueness is per document, within each app. A player with two chipped passports, such as a dual national, could verify twice, and so could one passport used in both apps if your game offers both. Renewing a passport can also create a new identity, depending on the app, which would clear a ban.

Gate the stakes, not the sign-up. Ask for verification at ranked play, rewards or early access, so players who can't verify can still play everything else.

New login, same player.

Bans attach to the subjectId, not the login. A new email, device or IP with the same passport maps back to the same subjectId, so a second account needs a different valid passport. A renewed or second passport can count as a new player.

Nothing identifying to breach.

No passport data or ID scans to store, secure or explain to a regulator. Nationality, and age when your game asks for it, arrive as simple claims.

Unlinkable across games.

Each game gets its own ID for the same person, so players can't be tracked from one studio to the next. That comes from how the IDs are derived, not from a policy.

Try to beat it.

You get one passport. Swap your email, device, IP or name and try to sneak a second account in. Then take the same person to a second game and see if anyone can link them.

Start the challenge →

Runs in your browser: no signup, no passport, nothing sent. About 60 seconds.

Example run

In this example run there were 5 attempts: 1 got in and 4 were blocked. A new email, a new device, a new IP and a new name all failed. One passport, one account.

Three working apps. Three problems solved.

Each one is an ordinary customer of the public API, built the way any studio would build it. They run in sandbox, so you can open one, verify with a mock passport and see exactly what the app gets back.

arena.nescio.dev

🔒 Ranked · lockedSandbox

Signed in as guest_4821

Scan with the Self app on your phone

Waiting for the Self app…

✓ Ranked · unlockedSandbox

✓

Ranked unlocked.

✓ Real human✓ 18+Nationality: ESP

guest_4821player ID7c4e19a2b0…85d31

⊘ Ranked · bannedSandbox

Banned from ranked.

guest_7305 is a brand-new account, but the same person as banned guest_4821.

guest_4821Bannedplayer ID7c4e19a2b0…85d31

guest_7305New accountplayer ID7c4e19a2b0…85d31

⛓ Same player ID: same person

Ranked play

Arena

A ban a new account can't shake.

Nescio tells it: A per-game player ID, and whether this person already plays here.
It keeps: That ID and its ban list. No name, no email.

Open Arena

LLumina Live

Join the queue

One place per real person. No sign-up, no email.

Open in the Self app

or scan from another phone

LLumina Live● Gate open

You're in the queue.

Main stageWaiting

Ticket#3736 ahead

112 in the queue · 36 admitted

✓ Real person

No account, no email. Nothing identifying stored.

LLumina Live● Gate open

Welcome back. Still you.

Main stageWaiting

Ticket#3711 ahead

131 in the queue · 61 admitted

Same person, same ticket. Never a second one.

Fair queue

Lumina Live

One place in line per real person, with no sign-up.

Nescio tells it: A per-event fan ID: the same person always gets the same one.
It keeps: A ticket number against that ID. No email, no contact details.

Open Lumina Live

ashveil.nescio.dev

Ashveil18Blood · Intense violence · Dark themes

You must be 18 or older

Ashveil learns you're 18 or older, and nothing else.

Wave 2Score 205 x1.75Burst

Leaderboard212 wardens

#1Cinderwake4,870
#2Mara Vey3,925
#3Lantern Keeper you3,410
#4ashfall_92,760

One row per verified human. A second account plays on the same row.

Age gate · 18+

Ashveil

An adults-only game that learns “18 or older” and nothing else.

Nescio tells it: “18 or older: yes”, and a per-game player ID.
It keeps: A signed 18+ cookie and one leaderboard row per verified human.

Open Ashveil

All three are sandbox demos: use a mock passport, not a real one. Make one in the Self app or the ZKPassport app.

Three calls. One opaque ID.

Your backend holds the API key and talks to a small REST API over plain HTTP, in any language. The key never reaches the browser.

Start a verification session and show the returned QR to the player.
Poll the session; on success you receive a stable subjectId.
Look up a subjectId any time to read its claims.
Key your records on subjectId, and ban, gate or reward the identity, not the account.

Full API reference and samples → docs.nescio.dev

# 1 · start a verification (server-side key)
curl -X POST \
  https://api.nescio.dev/v1/game/verify/sessions \
  -H "authorization: Bearer $NESCIO_API_KEY"
# → { "sessionId": "…", "minAge": null, "client": { …QR… } }
#   show `client` as a QR for the player; minAge is
#   your game's setting: null, 13, 16, 18 or 21

# 2 · poll until verified
curl \
  https://api.nescio.dev/v1/game/verify/sessions/$SESSION_ID \
  -H "authorization: Bearer $NESCIO_API_KEY"
# → { "status": "verified", "subjectId": "…",
#     "duplicate": false, "mode": "sandbox", … }
# same passport → same subjectId, in this game only.
#   "duplicate": true = this passport already has a
#   player in YOUR game. Never a cross-game signal.

# 3 · look up a player any time
curl \
  https://api.nescio.dev/v1/game/players/$SUBJECT_ID \
  -H "authorization: Bearer $NESCIO_API_KEY"
# → { "subjectId": "…", "claims": [ { "verified_human": 1, … } ] }

// gate ranked play on a verified, unique human
const r = await fetch(
  `${API}/v1/game/verify/sessions/${sessionId}`,
  { headers: { authorization: `Bearer ${apiKey}` } },
);
const { status, subjectId } = await r.json();

if (status === "verified") {
  if (bans.has(subjectId)) return deny("banned");
  if (seats.has(subjectId)) return deny("already has an account");
  seats.add(subjectId);  // one passport, one seat
}

// subjectId is stable for this player, in THIS game only.

Your studio sees outcomes, never identities.

Your backend gets one small object per player. The dashboard shows verified players and blocked duplicate accounts in aggregate.

What a player lookup returns

// GET /v1/game/players/a91f…  (game min. age 18)
{
  "subjectId": "a91f…",
  "claims": [{
    "method": "document_nfc",
    "assurance_level": "substantial",
    "verified_human": 1,
    "age_proven": 18,  // or null: no age set
    "over_18": 1,     // 1 or null, never 0
    "issuing_country": "ESP", // nationality
    "verified_at": "2026-09-27T18:04:11Z"
  }]
}

Studio dashboard with counts of verified players and blocked duplicate accounts, and a growth chart. No player names or personal data. — A fictional demo studio. Nescio ID is pre-production and has no customer numbers to show yet.

Keep the smurfs out. Keep the data out.

Nescio ID is pre-production. The sandbox is free and self-serve; live keys are switched on after a quick review by our team.

Founding studios get a direct line to the people building it and a say in what we ship next. Write to hello@nescio.dev.

Get a free sandbox key → Read the docs