IDENTITY
Supabase Auth receives identity information from Google or GitHub so HARIKOS can authenticate you and associate projects with your account.
This notice explains the product data HARIKOS needs to provide a shared project brain. It does not claim certifications or retention guarantees beyond the implemented service.
EFFECTIVE / AUGUST 24, 2026Supabase Auth receives identity information from Google or GitHub so HARIKOS can authenticate you and associate projects with your account.
The HARIKOS GitHub App can read only repositories you authorize, within its configured read-only Contents and Metadata permissions.
HARIKOS stores project records, scans, evidence-backed claims, memories, Context Packs, agent connections, sessions, and outcomes needed to provide the service.
OAuth, database, GitHub App, billing, and agent-token secrets are handled through server-side boundaries. Existing agent token plaintext is not displayed again after creation.
You can revoke repository access in GitHub, revoke agent connections in HARIKOS, and sign out to end the active session.