Releap installs as a GitHub App, and the exact permissions it requests are shown on the GitHub consent screen before you install. The baseline installation covers indexing and retrieval.

Some features request additional permissions, and only when a workspace administrator explicitly enables them: pull_requests: write for GitHub PR Comments (Growth and above), and contents: write for ticket-to-draft-PR workflows — limited to auto-generated Releap branches or user-designated non-default branches. Nothing beyond the baseline is part of the standard installation. See the GitHub permissions detail at the top of this page for the complete permissions model.

Only for features a workspace administrator explicitly enables, and only within the permissions shown on the GitHub consent screen. When the GitHub PR Comments feature is enabled (Growth and above), Releap posts comments on GitHub’s Pull Requests collaboration surface, never the underlying code. When the ticket-to-draft-PR workflow is enabled, Releap works on auto-generated or user-designated non-default branches — it never targets the repository default branch, never merges pull requests, and never modifies repository settings. Workspaces that don’t enable these features are unaffected.

Releap stores vector embeddings (mathematical representations of code chunks) and the original text of indexed chunks in our database for retrieval purposes. We do not store your full repository. Chunks are deleted when you remove a repo from your workspace or delete your workspace. We do not use your code to train any model.

Access to customer data requires explicit authorization and is logged in our audit system. Releap staff do not access customer workspace data in the normal course of operations. Support access requires a documented reason and is logged.

Without BYO LLM configured, query context (relevant code chunks) is sent to Anthropic or OpenAI for answer generation. We use zero-data-retention API agreements with these providers where available. On Growth and above with BYO LLM, query context goes to your own endpoint — it never leaves your network.

Without a BYO embedder configured, text chunks are sent to OpenAI’s embedding API for indexing. On Growth and above with BYO embedder, embeddings are generated by your own endpoint — your code never leaves your network at any stage of the pipeline.

All data is encrypted in transit via TLS. Integration credentials (GitHub tokens, OAuth tokens, API keys) are encrypted at rest using AES-256-GCM with keys managed in a secure secrets store. Your source code chunks and query history are encrypted at rest at the infrastructure level via Google Cloud SQL’s managed encryption.

SOC 2 isn’t a certification — no one issues a SOC 2 certificate. Here’s where we stand: Proga Digital has completed its SOC 2® Type 1 examination for the Security, Confidentiality and Availability Trust Services Criteria, performed by Prescient Assurance. Type 2 observation period underway · report expected Q1 2027. Alongside this, we’ve documented our security posture in depth — covering our GitHub App permission model, encryption approach, audit log surface, multi-tenant isolation controls, and known gaps with remediation timelines. Enterprise customers can request this documentation package ahead of any procurement conversation.

For Enterprise plan customers, we’re happy to work through your organization’s security evaluation process directly. Contact us at security@releap.app or through the Enterprise inquiry form and we’ll set up a conversation with the right level of detail for your team’s needs.

Yes, on Enterprise plans. Contact us to request our standard Data Processing Agreement. Custom DPA negotiation is available; allow 2–4 weeks for legal review on both sides.

Releap uses the following subprocessors: Google Cloud Platform (infrastructure — Cloud Run, Cloud SQL, Secret Manager), Anthropic (LLM completions unless BYO LLM is configured), OpenAI (embeddings and optional completions unless BYO is configured), Stripe (payment processing), Postmark (transactional email), GitHub (source code access), Atlassian (Confluence and Jira integration), Aha! (Aha! integration), Linear (ticket export), VS Code Marketplace (extension distribution), and Slack (Slack bot integration). Customers on Growth and above with BYO LLM and BYO embedder replace Anthropic and OpenAI with their own providers.

SAML/OIDC SSO is available on Team and above and integrates with Okta, Azure AD, Google Workspace, and any standard SAML 2.0 or OIDC-compliant identity provider. Solo plans support magic link (passwordless), Google OAuth, and TOTP (authenticator app) authentication.

All plans: magic link (passwordless email), Google OAuth 2.0, and TOTP (authenticator app with single-use recovery codes). Team and above: SAML/OIDC SSO. Programmatic access: workspace-scoped API keys (SHA-256 hashed, never stored in plaintext) and OAuth 2.1 with PKCE for MCP clients.

Every piece of data in Releap — every chunk, query, ticket, and audit row — is scoped by workspace ID at the database level. The vector retrieval index applies the same workspace filter on every query. It is not possible to retrieve data across workspace boundaries even if the application layer were bypassed. Repo visibility is enforced via a default-deny join table — turning off a repo makes it structurally invisible to retrieval, not just hidden in the UI.

We maintain an incident response process and will notify affected customers within 72 hours of confirming a breach that affects their data. Enterprise customers receive direct notification via their dedicated account manager. Our security contact is security@releap.app.

Yes. Enterprise prospects can request our security posture package — GitHub App permissions manifest, encryption model documentation, audit log surface description, subprocessor list, and current gap inventory with remediation timeline. Contact us via the Enterprise inquiry form or email security@releap.app.