Privacy policy
What GitResolve handles, why it is needed, and the choices you have.
Information we process
We process your authentication profile, GitHub account and installation identifiers, authorized repository metadata, repair requests, selected source context, generated patches, test evidence and approval records. Uploaded screenshots and text files provide additional context when you choose to attach them.
How your information is used
We use this information to authenticate you, check repository access, investigate your request, test proposed changes, maintain a visible task history and protect the service against misuse. AI providers receive bounded context needed for the repair. Do not include secrets or information you are not authorized to share.
Providers and repository access
GitResolve relies on GitHub, Firebase and configured Google Cloud or partner model providers. Their applicable terms govern their processing. Installing the GitHub App limits access to the repositories you select. Repository writes require your exact-diff approval.
Storage and retention
Task records have a 90-day retention period; events and artifacts have a 30-day period. Physical database deletion depends on deployment TTL configuration and is not guaranteed to occur immediately at expiry. Temporary uploads expire after 24 hours, with cleanup while the API is running. Development deployments may use local storage.
Your choices
You can revoke the GitHub App through GitHub settings. Account and data deletion are not currently self-service features. The team must finalize a working privacy contact before public launch; the example addresses in the repository drafts are not active support channels.
Security and updates
Access checks, bounded execution, isolation and redaction reduce risk, but cannot guarantee that all sensitive content is detected. Browser storage persists your session and preferences. Policy updates will be reflected here as the project develops.