Hemm is an early-stage project operating under the name Hemm Docs, based in Ghana. Hemm Docs is not yet a registered company. For privacy questions, email hello@hemm.dev.
Who this policy covers
This policy describes information handled through Hemm’s website and early-access documentation service. When a team connects its repositories, that team controls the content it shares with Hemm. Any separate agreement with that team also applies.
Information we handle
- Account information: GitHub identity, account and installation identifiers, access permissions, and authentication information needed to sign you in.
- Connected content: repository metadata, pull-request changes, and documentation within the configured review scope.
- Review records: findings, suggested changes, your decisions, and operational records that help us run and troubleshoot reviews.
- Messages and technical information: information you send us and request or security information processed when you use the service.
How we use it
We use this information to authenticate users, check repository access, identify documentation affected by code changes, generate suggestions, record review decisions, respond to messages, and maintain the service.
AI and service providers
Hemm uses GitHub for authentication and repository access and the OpenAI API to generate review suggestions. Relevant code changes and documentation may be sent to OpenAI for this purpose. Hosting and network providers also process information needed to deliver and secure the service.
Only connect content you are authorised to share with these services. Provider processing and international transfers must be assessed for your team’s requirements before connecting sensitive content.
Joining the waitlist
When you join, we store your email address, signup date, and confirmation-email status so we can manage early access. Resend processes your email address and the messages we send. Joining asks us to send a confirmation and contact you about Hemm early access; it does not subscribe you to unrelated marketing.
We temporarily keep hashed network identifiers to limit automated signups. Rate-limit records expire within 24 hours and are cleared on subsequent requests. To leave the waitlist or request deletion, email hello@hemm.dev.
Cookies
The application uses session cookies to keep you signed in and support secure account access. Blocking these cookies may prevent sign-in from working.
Storage and retention
Hemm stores account, installation, configuration, and review records in its application database. Backups may contain copies of those records. Disconnecting a GitHub installation prevents future authorised access; it does not by itself erase existing records, backups, or comments already posted to GitHub.
Retention depends on the information’s purpose: maintaining an active account, providing review history, investigating security issues, meeting legal obligations, or recovering from failures. Contact us to request deletion or to ask about retention for your workspace. We do not currently promise a fixed automatic deletion period.
Your choices and requests
You can manage the GitHub App’s repository access through GitHub. To ask about access, correction, deletion, or other rights available under the laws that apply to you, use our contact page. We may need to verify your identity and authority over a workspace before acting.
You can also raise a privacy concern with Ghana’s Data Protection Commission. Rights and obligations may differ depending on where you are based.
Changes to this policy
We will update this page when our practices change and provide additional notice where required.