Privacy Policy
At Gitmomos, we believe that your code is your business. This Privacy Policy outlines our strict data handling practices, emphasizing our absolute commitment to the privacy of your intellectual property.
No Source Code
Your source code is never read or stored.
Metadata Only
Only commit hashes, dates and messages are synced.
Privacy-First
Tokens are encrypted and data is sent over TLS.
Information Collected
To provide you with our AI-powered productivity reports, Gitmomos reads only the following metadata, and only from the repositories you explicitly add after connecting GitHub or Gitea:
- Commit Messages: The text provided when you execute
git commit -m "...", for commits you authored. - Commit Hashes: The unique SHA-1 identifiers for your commits.
- Commit Timestamps and Authors: The commit date and the author name and email, used to find your own commits.
- Repository Metadata: The name, link and visibility of each repository you add, so you can see what is tracked.
- Account Information: Your email address and name, your timezone, and your GitHub or Gitea username and avatar.
- Access Tokens: The GitHub OAuth token or Gitea access token you provide, stored encrypted and used only to read the data above. Disconnecting deletes it.
Information NOT Collected
Zero Source Code Policy
Gitmomos never downloads, stores, analyzes, or transmits your source code files or diffs. It only calls the commit-listing APIs of GitHub and Gitea, which return commit metadata. Your code stays where it is hosted.
How Data Is Used
The collected metadata is utilized solely for the functional operation of the Gitmomos platform:
- Report Generation: Transforming technical commit messages into cohesive daily and weekly productivity reports using AI.
- Analytics: Generating high-level statistical graphs regarding commit frequency and timing.
- Account Management: Authenticating you on the web dashboard.
Data Security
All data in transit is encrypted using industry-standard Transport Layer Security (TLS). Data at rest is encrypted within our cloud database infrastructure. Provider access tokens are kept in an encrypted vault that is only readable by our background worker, never by the browser.
Third-Party Services
To deliver our service, we rely on trusted third-party infrastructure providers who adhere to strict security compliance:
- Supabase: Serves as our primary cloud backend, handling secure authentication, Postgres database storage, and Edge Functions.
- Google Gemini AI: Processes the commit message text to generate natural language reports. We only transmit commit messages and repository names to this API.
- GitHub and Gitea: The code hosts you choose to connect. We read commit metadata from them using the access you grant, and you can revoke it at any time from your provider's settings or by disconnecting in Gitmomos.
Data Retention
Commit metadata is retained as long as your account remains active, ensuring you have historical access to your productivity trends. You may delete a linked project at any time, which will permanently remove all associated commit metadata from our servers.
Your Rights
You have the absolute right to request access to the data we hold about you, request corrections, or mandate the complete deletion of your account and all associated metadata. These actions can be performed directly through the dashboard settings or by contacting our support team.
Contact Information
If you have any questions, concerns, or requests regarding this Privacy Policy or your data security, please reach out to us via our GitHub repository issues or email us directly at our official support channels.
Last Updated: June 2026