Trust
Security & trust
Repairo needs repo access to open PRs. Here is exactly what we touch, store, and never do.
GitHub access
Repairo uses a GitHub OAuth App (not a GitHub App installation with org-wide defaults). Scopes:
- repo — read OpenAPI + consumer files; create branches and pull requests you request
- read:user — account identity for your Repairo profile
You can revoke access anytime in GitHub → Settings → Applications. We never merge PRs for you.
What we store
- GitHub user id, login, avatar, display name
- Encrypted GitHub access token (AES-256-GCM at rest)
- Workspace, members, integration configs, webhook secrets
- Repair run history (status, summary, PR URL, errors)
- Optional Stripe customer / subscription ids when billing is enabled
Spec and consumer file contents are fetched for a repair, processed in memory for that job, and are not sold or used to train third-party models. See also Privacy.
Architecture
- UI on Vercel; API + SQLite on Railway (persistent volume)
- /api/* proxied to the backend — sessions set on the app domain
- GitHub and Stripe webhooks verified with HMAC signatures
- SESSION_SECRET / TOKEN_ENCRYPTION_KEY required in production
Compliance roadmap
Early access focuses on least-privilege OAuth, encrypted tokens, and audit events for workspace actions. Formal SOC 2 / ISO programs are on the roadmap for enterprise buyers — talk to us via Contact if you need a security questionnaire filled today.
Responsible disclosure
Found a vulnerability? Email or message via Contact with steps to reproduce. Do not open public issues for sensitive reports.