# Trust Center

How Cactus protects your code and data, and where to report a security problem.

Cactus is built on least privilege.

## In place today

- People log in with Google or GitHub, and Cactus never asks for a password and stores none.
- The GitHub App can read code and list repositories and nothing more, so it cannot push a commit, open a pull request or change a setting.
- Only a team's Owners can invite or remove people, change someone's role, add a custom domain, or create, rebuild from scratch or delete a product, and the server checks the role on each of those requests.
- Every address under heycactus.ai answers only over HTTPS, with TLS 1.2 or newer, and sends a plain HTTP request on to HTTPS.
- The database, the live updates and the copies of your code are encrypted at rest.
- An answer to a visitor never lists a file of your code among its sources, and the lines of code behind a page are shown only to your team.
- Cactus trains no model on your code or on anything else it reads.
- Deleting a product deletes its pages, conversations, sources and settings from the database in one step, and its copies of your code.

## Report a security problem

Write to [hello@heycactus.ai](mailto:hello@heycactus.ai) with any security problem you find in Cactus and how to see it again. You do not need an account.

The same address is in [heycactus.ai/.well-known/security.txt](/.well-known/security.txt), the file security tools read to find where to report.

What Cactus collects, how long it keeps it, and the companies that run parts of it are on the [privacy page](/privacy).
