TERMS / IDENTITY BROKER
USE THE
CONTRACT.
Triad lets a provider-authenticated person approve narrow identity claims for a registered application. These terms describe the boundaries of that service.
01 / SERVICE
WHAT TRIAD DOES
Triad provides provider sign-in, account-scoped identity values, consent screens, and OAuth-compatible authorization flows. Device approval can authorize a Triad session or a registered OAuth client. An application receives only the scopes and resource permissions you approve, subject to the protocol response and the application’s own terms.
Triad's application records do not retain request IP addresses, authentication paths, or browser user-agent strings. Session records keep only the data needed to authenticate the session. Rate-limit records keep an opaque keyed bucket, a request count, and a timestamp.
02 / RESPONSIBILITIES
KEEP ACCESS UNDER CONTROL
Use an upstream provider account you are authorized to use. Match every device code exactly. Review the Client ID, token result, requested scopes, Protected Resource, Wallet Namespace, Wallet Profile, Account Index, resolved Derivation Path, applicable Chain ID, and Signing Envelope before approval. Keep your provider, Passkeys, and browser access secure, and report a suspected unauthorized connection through the project’s source repository.
03 / CONNECTIONS
APPLICATIONS STAND APART
A downstream application is responsible for its own service, security, availability, and use of the claims it receives. Triad does not endorse an application merely because it appears in an authorization request. Removing consent affects stored approval; a token that has already been issued may remain valid until it expires.
04 / BOUNDARIES
NO MISUSE
Do not probe, overload, bypass safeguards, impersonate another person, submit misleading provider data, or use Triad to violate law or another service’s terms. Triad may suspend or change a flow when necessary to protect the service, its users, or an upstream provider.
05 / CHANGES
THE SERVICE ITERATES
Triad is an evolving project. The service, supported providers, protocol behavior, and these terms may change as the implementation changes. Continued use after a published update means you accept the current version. If you do not accept a change, stop using the service and delete the account.