Consent
Apps request named scopes. The production consent screen should describe what each scope allows in plain language.
PRIVACY
Access should be visible and revocable.
Lucion Identity is designed so people can understand which apps, organizations, and AI agents can act with their identity.
Data minimization
Applications should receive the minimum identity claims and organization data needed for the feature being used.
Revocation
Users and authorized organization administrators must be able to revoke sessions, app access, and delegated authorization.
AI transparency
Lyra activity should appear in the same audit history as human and application actions rather than being hidden behind an AI layer.
Documentation helper
Questions asked in the public documentation helper are sent server-side to the configured Lucion AI provider, or Gemini 3 Flash while the Lucion provider is unavailable. Do not enter secrets or personal data. The helper returns advisory text only and does not access accounts or perform actions.
Foundation privacy boundary
Verified identifiers, public-key credentials, sessions, organization access, consents, developer credentials, and audit evidence are server-backed; session/API/OAuth secrets are stored only through protected server-side representations where the contract requires it.