Trust & Security

Technical security model for beta users: auth flow, permission boundaries, stored data, revocation steps, and incident path.

Landing Sign in Security docs

Why OAuth + GitHub App

Release Trace separates identity from repository access. User identity is handled by Clerk via GitHub OAuth. Repository data is read through a GitHub App installation token scoped to repositories selected during app installation. Current beta is GitHub-only (GitLab is not available yet).

System	Purpose	Requested access
Clerk + GitHub OAuth	Authenticate the user identity for Release Trace session.	GitHub account identity and basic profile needed for sign-in.
GitHub App installation token	Read release sources for selected repository and compare range.	Read-only code, metadata, and pull requests for installed repositories.

Data boundaries

Stored

- Workspace and product configuration.
- Repository mapping (owner/repo + installation id).
- Release run artifacts, bullets, source references, and review edits.
- Operational analytics events used for onboarding and beta funnel diagnostics.

Not stored

- GitHub account password.
- Personal access tokens from users.
- GitHub repository write credentials.
- Raw payment card data (handled by Paddle).

How to revoke access

1. Revoke GitHub OAuth authorization for Release Trace in GitHub Settings → Applications → Authorized OAuth Apps.
2. Uninstall or restrict repository access for the GitHub App in GitHub Settings → Applications → Installed GitHub Apps.
3. In Release Trace, remove products/workspaces that should no longer be connected.

Incident contact path

For suspicious auth activity or data-access concerns, contact support@release-trace.com with:

- account email used for sign-in,
- approximate time window,
- repository/installation affected,
- relevant request ids or screenshots if available.

Last updated: 2026-03-31 (UTC).