Let's Git It Privacy Policy
Effective July 17, 2026
Let's Git It is local-first. Repository paths, source files, commit content, Git credentials, AI prompts, and local MCP data stay on your device unless you deliberately send information to a provider or remote forge.
Anonymous usage events are enabled by default and can be disabled at any time in Settings > General > Privacy. These events contain only a random installation identifier, event name, app version, platform, time, and a limited reminder-dismissal reason. We collect app starts and support-reminder dismissals. We do not include repository paths, source code, credentials, personal files, commit content, or AI prompts.
When you create a website account, donate, start monthly support, or purchase an add-on, we process the account and transaction details needed to provide that service. Card details are handled by Stripe and are not stored by Let's Git It. Stripe customer, checkout, subscription, invoice, charge, and refund references are retained for billing support, reconciliation, fraud prevention, and legal obligations.
Developer applicants must declare whether the applicant is a human developer or an AI agent. For AI agents, we also collect the responsible human's name and email, model provider and name, and intended use. Approved developers can create scoped API tokens. We store only token hashes, access abilities, timestamps, and expiration data, not plaintext tokens. Material application changes return the account to review and revoke existing developer tokens.
We use reasonable administrative and technical controls, including encryption for stored service credentials, access controls, audit records, rate limits, and application firewall rules. We retain records only as long as needed for operations, security, legal obligations, and aggregate product analysis.
You may request access, correction, or deletion of website account data by emailing [email protected]. Security and transaction records may be retained when legally required.
Questions: [email protected]
Let's Git It is local-first. Repository paths, source files, commit content, Git credentials, AI prompts, and local MCP data stay on your device unless you deliberately send information to a provider or remote forge.
Anonymous usage events are enabled by default and can be disabled at any time in Settings > General > Privacy. These events contain only a random installation identifier, event name, app version, platform, time, and a limited reminder-dismissal reason. We collect app starts and support-reminder dismissals. We do not include repository paths, source code, credentials, personal files, commit content, or AI prompts.
When you create a website account, donate, start monthly support, or purchase an add-on, we process the account and transaction details needed to provide that service. Card details are handled by Stripe and are not stored by Let's Git It. Stripe customer, checkout, subscription, invoice, charge, and refund references are retained for billing support, reconciliation, fraud prevention, and legal obligations.
Developer applicants must declare whether the applicant is a human developer or an AI agent. For AI agents, we also collect the responsible human's name and email, model provider and name, and intended use. Approved developers can create scoped API tokens. We store only token hashes, access abilities, timestamps, and expiration data, not plaintext tokens. Material application changes return the account to review and revoke existing developer tokens.
We use reasonable administrative and technical controls, including encryption for stored service credentials, access controls, audit records, rate limits, and application firewall rules. We retain records only as long as needed for operations, security, legal obligations, and aggregate product analysis.
You may request access, correction, or deletion of website account data by emailing [email protected]. Security and transaction records may be retained when legally required.
Questions: [email protected]