Privacy

Last updated July 17, 2026.

What we collect

Ahem records first-party product analytics such as page views, button clicks, referral source, and a random browser session identifier. If you request beta access, we store the email address, repository host, and optional repository URL you submit. When you connect a repository, we store your work email, instance and repository identifiers, and the credentials needed to operate the connection.

Credentials

Forgejo/Gitea access tokens and webhook secrets are encrypted at rest. The token is used only to read the selected repository, install and receive its webhook, publish commit statuses, and post review comments. You can revoke access at any time from your repository host.

Code review data

Ahem fetches the selected repository with Git and inspects bounded change data. Repository code is never executed. Relevant diff, file, pull-request, and repository-memory context is sent to AI model providers through routes configured for zero data retention and no provider data collection. Review results, routing, usage, cost, and operational errors may be retained to operate and improve Ahem.

Why

We use this information to operate Ahem, review connected pull requests, measure whether it is useful, prevent abuse, and contact people who requested access. We do not sell personal information or use third-party advertising trackers.

Retention and requests

Connection data is retained while a repository is connected; beta leads are retained while the beta is active or until deletion is requested. Aggregate event data may be retained for product analysis. Email [email protected] for access, disconnection, or deletion.