Identity & Consent
How identity verification, consent scopes, protected lookups, and audited access work across the platform.
Each section is linked and available for Docs AI citations.
Keys stay tied to an app, a purpose, an approved consent scope, and a clear billing lane.
Galactus unlocks after one verified completed commitment in the last 30 days. Create your account first, then finish one verified commitment to open Docs AI.
Identity verification
Funding, payout access, and higher-trust proof flows require verified identity. The account holder submits legal identity details, then completes Stripe Identity capture for government ID and any required selfie checks.
Identity state moves through not started, pending, verified, or failed. Funding stays locked until the account is verified.
Consent scopes
Protected reliability access is consent-gated. There is no open legal-name lookup, no unrestricted public reliability search, and no broad scraping access for protected records.
When a user grants the identity scope, an approved enterprise integration can match the protected reliability record to that user's legal identity for the declared purpose. Every consent grant is scoped, logged, and attributable to an app, an account, a purpose, and a timestamp. Users can review granted scopes and revoke them where applicable.
Consent does not add artificial points to a score. It makes a verified record portable to approved organizations that need to review real reliability history for real decisions such as approvals, underwriting, hiring, partner review, or trust-sensitive access.