Skip to main content

Security — Qably

What the product does today

Security

What Qably protects, how it protects it, and which data reaches third parties. This page describes only what the product does today.

Encrypted secrets

Webhook secrets, repository access tokens, and Slack and Discord webhook URLs are encrypted with AES-256-GCM before they are stored.

Human review

New cases proposed by the AI wait in a review inbox and enter the catalog only when a person approves them.

Project-scoped API keys

Each key belongs to one project, is shown only once, and is stored only as a SHA-256 hash. An owner or an admin can revoke it.

1. Access and roles

Each organization has three roles: owner, admin, and member. Only owners and admins can create and revoke API keys, manage repository connections, and configure notification webhooks. An API key identifies one project: the results it sends are recorded in that project. A revoked key is no longer accepted.

2. Connections and webhooks

Communication with the application and the API uses HTTPS, and in production session cookies are issued with the Secure attribute. Events that GitHub sends through a webhook are accepted only when their HMAC-SHA256 signature matches the connection's secret. That secret can be rotated from the application.

3. Test files and the AI provider

Qably does not clone repositories. To document a test file, it reads that file from the connected GitHub repository and sends its content to Google Gemini, up to a character limit that depends on the plan. Conversations with Aeris send the same provider the message, the history, the project context and, when a case is consulted, fragments of its test file. For each proposal, Qably stores the file path and a short quote of its code as evidence.

4. Review decisions and API keys

Each review decision, whether an approval or a rejection, records who made it, when, and the comment, if there is one. For each API key, Qably stores the creation date, the last-use date and, if it is revoked, the revocation date.

5. Contact

To report a security issue, write to [email protected].