Terms of Service

Version 2026-09-27 · Effective September 27, 2026

These Terms of Service (the “Terms”) govern your access to and use of the Nescio ID verification API and related dashboards and documentation (the “Service”), operated by Nescio (“we”, “us”). By creating a game, generating an API key, or otherwise using the Service, you (the “Customer”) agree to these Terms. If you are agreeing on behalf of an organization, you represent that you are authorized to bind that organization.

1. The Service

Nescio ID confirms that an end user is a real, unique human and, only where the Customer configures a minimum age for a game (13, 16, 18 or 21), that the end user meets it. Games have no minimum age unless the Customer sets one. The identity proof is performed on the end user’s device by a third-party passport app, such as Self or ZKPassport, each of which operates under its own terms. For each verified end user, the Service returns to your application only:

• an opaque subject identifier that is specific to your game (subjectId);
• verified_human, confirming a real, unique human;
• age_proven, the highest minimum age the end user has proven, or null where no minimum age was requested;
• over_18, 1 where a minimum age of 18 or more has been proven, otherwise null; and
• issuing_country, the end user’s nationality as disclosed by the document (an ISO 3166 three-letter code).

Nescio does not receive, request, or store end-user personally identifiable information.

2. Environments: sandbox and live

API keys are issued per environment. Test (sandbox) keys verify simulated passports on a test network rather than real documents, are intended for development and evaluation, and are subject to daily usage limits. Live keys verify real documents and are granted only after review and approval by us. You must not use sandbox verification results as evidence of a real person, and you must not attempt to use a live key before it has been approved.

3. Acceptable use

You agree not to: (a) use the Service to unlawfully discriminate against, surveil, or harm any person; (b) attempt to re-identify, de-anonymize, or correlate end users across services using subject identifiers; (c) probe, scan, or circumvent the Service’s rate limits, quotas, or access controls; (d) resell or sublicense the Service except as expressly permitted; or (e) use the Service to build a competing identity product. You are responsible for your end users’ experience and for complying with all laws applicable to your application.

4. API keys and security

API keys authenticate your backend and must be kept confidential and stored server-side only — never embedded in client applications or public repositories. You are responsible for all activity under your keys. Notify us promptly of any suspected compromise; we may rotate, suspend, or revoke keys to protect the Service.

5. Data and privacy

The Service is designed so that no end-user PII — no name, date of birth, document number, or photograph — is transmitted to or stored by you or by us. What you receive is limited to the per-game subject identifier and the claims described in Section 1. Nescio retains only a one-way pseudonym per verified person, those claims, and aggregate, non-identifying operational data. Proofs are generated on the end user’s device by third-party passport apps such as Self and ZKPassport, which operate under their own terms and privacy policies. Any business-contact information you provide during onboarding is processed to administer your account.

6. Player data and erasure

End users (“players”) never create a Nescio account. For each verified player, Nescio holds only a one-way pseudonym derived from the proof (one for each passport app the player verified with), the claims listed in Section 1, and the per-game subject identifiers that connect that pseudonym to the games the player has verified in. Nescio cannot recover a name, date of birth, document number or photograph from that record. Data a player keeps in a third-party passport app, such as Self or ZKPassport, is governed by that app’s own terms.

Players may exercise the rights available to them under applicable data-protection law, including the right to have their record erased. A player can ask the studio that runs the game, which identifies the record by its subjectId, or write to us directly at the privacy contact in Section 12. Because we hold nothing that identifies a player by name, we may need the game and its subjectId to locate the record. Nescio operators carry out erasure; it removes the pseudonym, its claims and every per-game subject identifier linked to it. There is no self-serve player portal.

Customers must pass erasure requests they receive to us without undue delay, and remain responsible for any personal data they hold themselves, such as their own account records, which Nescio never receives.

7. Quotas and availability

Sandbox keys are rate-limited per day; exceeding a limit returns an HTTP 429 response. We aim to keep the Service available but provide it without any uptime guarantee unless a separate written agreement states otherwise. We may modify, suspend, or discontinue features with reasonable notice.

8. Disclaimers

The Service is provided “as is” and “as available,” without warranties of any kind, whether express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that a verification result is free from error or fraud, and you remain responsible for your own risk, compliance, and moderation decisions.

9. Limitation of liability

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits or data, arising out of or relating to these Terms or the Service. Our aggregate liability will not exceed the amounts you paid us for the Service in the twelve months before the event giving rise to the claim.

10. Suspension and termination

You may stop using the Service at any time. We may suspend or terminate access for violation of these Terms, for security or legal reasons, or if required by our providers. Provisions that by their nature should survive termination will survive.

11. Changes to these Terms

We may update these Terms; the version identifier and effective date above will change accordingly, and continued use after an update constitutes acceptance. Your acceptance is recorded with the version in effect at onboarding.

12. Contact

Questions about these Terms: hello@nescio.dev.

Privacy and erasure requests: hello@nescio.dev, with “Privacy request” in the subject line.