Privacy, without the fog.

Information we collect

• Account identifiers such as your name, email address, avatar, and GitHub username when available.
• Repository URLs, selected branches, job status, generated reports, usage credits, and workspace activity.
• Essential technical information needed for security and reliability, such as request timing, error details, and rate-limit identifiers.

How repository analysis works

RepoMind currently analyzes public GitHub repositories. It clones a temporary read-only snapshot, inspects its structure and dependencies, stores the generated report in your workspace, and removes the temporary working copy after processing.

RepoMind does not commit to, push to, or modify the repository it analyzes.

Why we use the data

• Provide authentication, repository analysis, reports, workspace history, and credit accounting.
• Protect the service from abuse and investigate failures.
• Improve reliability using aggregated operational signals and error reports.

Service providers

Depending on deployment configuration, RepoMind may use GitHub for repository access and sign-in, Supabase for authentication and storage, Redis or Upstash for queues and rate limiting, Google Gemini for report generation, and Sentry for error monitoring. These providers process only the information needed to deliver their part of the service under their own terms.

Retention and security

Account records and saved reports are retained while your workspace is active or until they are removed through an operational cleanup or verified deletion request. Temporary repository clones are removed after a job completes or fails. No internet service can promise absolute security, but RepoMind uses access controls, restricted server credentials, and encrypted transport in production.

Your choices

You may export your current workspace from Settings. You may also request correction or deletion of your account and saved reports through the support process described on the Data controls page. Identity verification may be required before a destructive request is completed.

Policy changes

Material changes will be reflected on this page with a revised effective date. Continued use after a change means the updated policy applies to future use.