Account & data

GitHub account privacy

A plain-language record of what Cerberus receives, what it keeps, and what signing out changes.

Identity data

When you sign in with GitHub, Cerberus stores your GitHub user ID, username, verified primary email address, and the time your account was updated. These records identify your Cerberus account. Your public GitHub profile email is not used as proof of a verified email address.

OAuth credentials

Account records are stored in the deployment operator's Cloudflare D1 database and remain after logout. Cerberus uses your GitHub access token on the server to retrieve your identity and email. It does not save that token or send it to the browser.

Sessions

A secure, HttpOnly cookie keeps you signed in for seven days. The database stores a hash of this session identifier. Signing out invalidates the current session. Expired sessions and temporary ten-minute sign-in records are removed by a daily cleanup job.

Repository access

Account sign-in does not grant repository access. You separately choose repositories when installing the Cerberus GitHub App. Cerberus stores the installation ID and basic repository metadata, then creates short-lived, repository-scoped installation tokens only when it needs to read files or create an approved draft pull request. You can remove this access from GitHub at any time.

Public scans continue to use GitHub's public API. If you manually enter a personal access token for scanning, it is stored separately in this browser tab's session storage until removed or the tab is closed, and is sent directly to GitHub.

Agent conversations and proposed changes

For repository-aware agent sessions, Cerberus stores the scan report, your conversation messages, model responses, the pinned commit, and proposed file changes. Prompts and the repository files the agent reads are sent to the configured Pollinations model so it can reason about the request. Proposed changes remain reviewable in Cerberus. The app creates a branch and draft pull request only after you separately approve the complete change set.

Account deletion

Contact the operator of the Cerberus deployment you use to request account deletion. Operators can delete the account and its sessions using the documented account maintenance procedure.

Return to Cerberus Agent