1The service
GrayPass supplies human-authority evidence at the moment of a consequential action. Your backend registers protected actions and asks GrayPass to authorize one; GrayPass returns a decision with reason codes and, on an allow in enforce mode, a short-lived Proof of Agency your relying party verifies.
GrayPass is additive. It is not a login, not identity verification, and not a replacement for your existing authentication, MFA, or fraud controls. It proves continuity with whoever enrolled, not who that person is. The limitation is documented in the enrollment limitation and you are expected to have read it.
2Environments
- Sandbox: the integration environment, with 1-day retention by default. Proofs are signed with a sandbox key and cannot verify as production. No availability commitment is published.
- Live: the server blocks behavioral enforcement until an approved real-human validation and calibration release exists. Configuration alone is not production approval.
Browser integrations use short-lived, subject-bound ct_*
credentials minted by your authenticated backend. A publishable
pk_* key is not accepted by the API. Secret
sk_* keys must never reach a browser; you are responsible
for activity under your credentials.
3Commercial terms
There is no self-serve subscription or published price. The service counts assured actions and active Brainprint months for contract evaluation; those counts do not invoice a customer or establish a commercial agreement on their own.
Metering never affects a decision. If a meter write fails, the decision still happens and the usage is reconciled afterwards. There is no circumstance in which a billing state changes an authorization outcome.
4Your obligations
- Tell your users, in your own privacy disclosure, that behavioral evidence is collected for authorization at consequential actions. Silent deployment is prohibited.
- Obtain any consent your jurisdiction requires for behavioral or biometric processing.
- Declare enrollment anchors honestly. The anchor is what you told us; we repeat it back without embellishment.
- Enforce decisions on your own side. GrayPass cannot stop you executing an action it denied, and outcome reporting makes that visible.
- Verify proofs properly: audience, action, action hash, environment, and expiry.
- Comply with prohibited uses. Employee surveillance, cross-site tracking, trait inference, and automated adverse decisions without human review are grounds for immediate termination.
5What we do not promise
We publish no availability target, no recovery objective, and no latency figure, because none has been measured by an independent monitor. The status page says so rather than inventing a number. We publish no accuracy figure for the continuous engine, because no evaluation on recorded humans exists yet. Every claim we do make is registered with its source in the claim registry.
The service is provided as is. GrayPass is one signal among several and must not be your only control for an action where being wrong is unacceptable.
6Data, deletion, and export
You may revoke, delete, or export a subject at any time through the API or the console. Deletion removes the template, ends live sessions, clears subject metadata, and revokes outstanding proofs in the application database and session store. Deletion from backups and scheduled retention on the hosted service are operational procedures that run outside this application path.
7Earlier API paths
The /v1 and /v2 paths remain available only
to integrators who already use them. They carry
Deprecation and Sunset headers, receive no
new capabilities, and will be withdrawn with notice based on measured
usage. New integrations use /api/v1, which is the only
surface these terms describe.
8Changes
Material changes to these terms are announced to customers before
they take effect. Breaking API changes require a new dated version;
the current version is returned by GET /api/v1/meta.
9Contact
Questions about these terms, vulnerability reports, and reports of misuse go to founders@graypass.org.