Skip to document
MoonGit

MoonGit Privacy Policy

Version: 2026-10-11.5

Status: Final — approved by the owner on 2026-10-11.

Effective date: 2026-10-11.

1. Who provides MoonGit

MoonGit is provided by Ashtamkea LLC, a Delaware limited liability company. Contact support@ashtamkea.com about privacy, support, access, correction, or deletion requests. Business mailing address: Ashtamkea LLC, c/o Legalinc Corporate Services Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, USA Telephone: +972 54 264 0653

This policy covers the MoonGit desktop app, its optional connections and agent access, and information you voluntarily send to Ashtamkea for support. Ashtamkea is responsible as controller for the support information it receives and the purposes described below. It does not receive or host your local repositories merely by supplying the app. App stores, Git hosting services, AI providers, and agent clients process information under their own policies and agreements. This policy does not describe website hosting, cookies, or website analytics; any such practices require a separate, accessible notice before collection begins.

2. Information kept on your computer

MoonGit reads repository files and Git metadata to display history, changes, commit authors, and other requested Git information. It stores preferences, repository and bookmark paths, workspace state, commit drafts, non-secret connected-account metadata, cached hosting information, local diagnostics, and your accepted terms version, document hash, and acceptance time in its application data directory. Acceptance records are local and are not sent to Ashtamkea or included in portable settings exports.

On supported platforms, MoonGit stores saved hosting and AI credentials through the operating-system credential vault, separately from settings and portable exports. Native Git, SSH, and external credential helpers may separately store credentials or keys under their own configuration. Git author and committer names and email addresses are stored in Git configuration and commits and can be shared when you push commits to a remote. Repository content and Git configuration can remain after uninstalling MoonGit. Portable settings exports can contain local paths, preferences, and non-secret account metadata; treat them as private even though MoonGit excludes saved provider secrets and terms acceptance records.

MoonGit contains no telemetry, advertising tracker, automatic crash uploader, or background application update check. Ashtamkea does not receive repository content, local paths, or local acceptance records merely because you open the app. An operating system or app store may separately process installation, purchase, usage, update, or crash information under its own policies. We do not claim that third-party services collect no data.

3. Network activity you choose

Git remote commands send and receive repository information through your chosen Git remote. Connected hosting features contact the accounts and servers you configure, including account refreshes while those features are in use. Those servers receive the data necessary for the request and ordinary connection information such as your IP address. Authorizing a connection does not give MoonGit ownership of your content.

AI provider connection tests and model-list requests contact the configured local or remote endpoint using the configured authentication, without sending repository diff content. When you request a built-in AI commit message, MoonGit sends staged filenames, change metadata, bounded staged diff excerpts for nonbinary files, and your configured prompt instructions to that endpoint. Filenames and change metadata can be sent even if a patch is omitted. MoonGit does not automatically include unstaged file content in this built-in request; anything you put in custom instructions is also shared. Staged content and instructions may contain confidential data, secrets, or other people's personal information.

By default, MoonGit displays the destination and asks for confirmation before sending each built-in AI generation request. You can choose not to be asked again or turn off confirmation in AI settings. That preference applies to subsequent requests, including requests after changing repositories or the configured provider; it is not limited to the destination of your first confirmation. With confirmation off, invoking generation sends the request without a separate permission prompt. Review the current destination and content before invoking it. Restore confirmation in AI settings to review future requests individually. Cancelling the confirmation prevents that request from being sent; cancelling after transmission cannot recall data already received by a provider.

You can leave AI unconfigured or disconnect it in Settings. Normal local Git features do not require AI. Data already received by a remote provider is subject to that provider's retention, training, security, and deletion practices. Check the provider's policy and your account settings; MoonGit does not guarantee that providers never retain data or use it for training. A local AI endpoint may run entirely on your computer, but its own configuration determines whether it contacts other services.

4. Optional agent and MCP access

MoonGit MCP is a separate optional integration that you enable in Advanced features and connect to a compatible agent client. Its helper exchanges requests and results with MoonGit over a local connection; MoonGit does not open a network port for this integration. Local transport does not mean that the receiving agent keeps the results on your computer. Your agent client may send them to remote AI services or retain them in conversations, logs, or other storage under its own settings and policies.

The local connection is restricted to your operating-system user account, not to a list of individually approved clients. MoonGit does not separately identify and approve each agent. Other compatible processes running under the same account may connect while access is enabled, even if they are not the client you registered. Registering a helper in one agent's settings does not grant that agent exclusive access. Take account of other applications running under your account before enabling MCP.

While access is enabled, connected clients can request data from local repositories accessible to MoonGit, including repositories that are not open in a tab. Available information includes repository paths, filenames, working-file content, staged and unstaged diffs, commit history and author information, branches, stashes, and other Git metadata, as well as workspace, bookmark, and non-secret connected-account information. This access is broader than the built-in AI commit-message request and is not limited to staged content. MCP does not provide a credential-retrieval tool, but repository files and diffs can themselves contain credentials or personal information; do not assume those contents are automatically redacted.

Clients can also navigate MoonGit and change bookmarks and bookmark folders. The current MCP tools do not provide Git mutations or direct hosting-provider requests. Enabling MCP permits supported requests without a separate MoonGit confirmation for each read or bookmark edit; the built-in AI confirmation preference does not control this integration. Enable it only for clients you trust and content you are authorized to share. Disable MoonGit MCP in Advanced features to stop further access through this integration. Doing so does not delete information already received by a client or its providers; use their controls or contact them about their copies. Disabling MCP does not revoke separate operating-system accessibility or filesystem permissions you have granted to other applications.

5. Support, purposes, and legal bases

MoonGit keeps local diagnostic information for troubleshooting. The optional diagnostic export contains selected event times, severity, diagnostic references, and version information; its redaction excludes log messages, local paths, account identifiers, remote URLs, and credentials. Review any file before sharing. Exporting a file does not upload it automatically.

If you contact support or send a diagnostic file, Ashtamkea receives your contact information, message, and attachments and uses them to respond, troubleshoot, and manage the request. Providing support information is voluntary, but we may be unable to answer or investigate without relevant details. Do not send credentials, unnecessary personal information, or repository content you do not want to disclose. If you act for an organization or share another person's information, ensure that you have authority to do so.

We may receive information about people other than the sender through support messages, screenshots, logs, or repository excerpts supplied by a user or their organization. Depending on what is submitted, this can include names, email addresses, commit attribution, comments, and identifiers appearing in the material. We use only information needed to investigate the request and handle it under the purposes, retention rules, and rights described in this policy. The sender's authority does not replace our own data-protection obligations. Where applicable law requires us to notify someone whose information we obtained indirectly, we provide the required information within the applicable period, unless a lawful exception applies. You may contact us about your information even if someone else supplied it.

Routine support does not require sensitive personal information, such as health information, political or religious beliefs, or biometric identifiers, or information about criminal allegations or convictions. Redact it before sending files. If unnecessary information of this kind reaches us, we limit access and delete or redact it promptly, subject to any applicable legal preservation duty. Before retaining or using it for an investigation, we must establish both an applicable legal basis and any additional condition required for that type of information; ordinary legitimate interests alone do not establish those additional conditions.

Where the EU or UK GDPR applies, we process information necessary to provide support required by our contract with you on the basis of that contract. For general enquiries, support for an organization's users, and proportionate follow-up troubleshooting, we rely on our legitimate interests in answering requests and maintaining a reliable product, balanced against your rights. We process information needed to meet applicable legal duties on the basis of those duties, and retain information necessary for legal claims on the basis of our legitimate interest in establishing, exercising, or defending those claims. If a separate activity relies on consent, we will identify it when requesting that consent; accepting the software terms or emailing support is not blanket consent to unrelated processing.

Google Workspace provides our support email service. Under the applicable processing agreement, Google processes support messages and attachments on our behalf and uses subprocessors. People authorized to handle support may access information needed for that work. Relevant information may also be disclosed to professional advisers or competent authorities where necessary to address a legal claim or comply with law. Those disclosures do not authorize unrelated advertising or marketing use of your support correspondence.

6. Retention, deletion, and your controls

Local preferences, caches, and acceptance records remain in the current application data until you remove them or replace them using the app's controls. Changing current records does not erase older copies in backups or exports. MoonGit creates local database backups before database upgrades; these can contain older preferences, paths, account metadata, drafts, caches, and acceptance records. The app retains a configured number of verified migration backups (three by default), rather than deleting them after a fixed number of days. Unreadable or incomplete backups may be kept for manual recovery outside that count. It may also preserve an unreadable legacy settings file as a recovery copy. These copies remain on your computer and are separate from support-email backups held by service providers.

To remove local historical copies, close MoonGit and remove the relevant backups and recovery copies from its application data directory, along with any portable exports or other copies you made. Removing recovery copies prevents their later use for recovery. Local diagnostic retention follows the app's configured log rotation. Uninstalling may leave application data and vault credentials behind. Disconnect hosting or AI accounts and remove stored keys in Settings before deleting application data if you want to remove saved credentials. Deleting MoonGit's application data does not delete your repositories, commits, Git configuration, or data already held by third parties. Removing local acceptance records requires terms acceptance again on a later launch.

Removing a hosting or AI connection deletes its saved MoonGit credential when local removal succeeds; it does not by itself revoke an OAuth grant, invalidate an API token at the provider, or remove copies used by other applications. To revoke that authorization or invalidate a token, use the provider's account or security settings. SSH keys and native Git credential helpers have separate controls. Check any failure notification before assuming a saved credential has been removed, and revoke credentials at the provider if you need to prevent their further use.

For support information held by Ashtamkea, request access, correction, or deletion at support@ashtamkea.com. We keep support correspondence and attachments while a request is being handled and for up to 365 days after it is closed, to handle follow-up questions and related troubleshooting. A request closes when it is resolved, withdrawn, or no further support work is being pursued. Inactive requests are reviewed rather than kept open indefinitely. At the end of the retention period, we delete the correspondence and attachments from active records or irreversibly anonymize them, unless a longer period is required by law or necessary for an ongoing dispute or legal claim. These rules also apply to support copies we control outside the mailbox. Exception records are limited to what is needed and deleted when that need ends. A valid deletion request may require earlier deletion.

Deletion from active records does not necessarily remove provider backup and recovery copies immediately; those copies follow the provider's applicable deletion and recovery timelines. We cannot retrieve or delete data stored only on your computer, in your Git remotes, or by independent hosting, AI, or agent providers. Contact those providers about their copies.

7. Security and international processing

MoonGit uses local storage and, for saved provider credentials on supported platforms, operating-system credential protection. Preferences, repositories, and exported files are not protected merely because credentials are in a vault. No software or storage method can guarantee absolute security. Protect your computer, backups, credentials, configured endpoints, and agent access.

Google and its subprocessors may process support information outside your country, including in the United States, where legal protections may differ. Google's processing terms and subprocessor information are available at https://workspace.google.com/terms/dpa_terms.html and https://workspace.google.com/terms/subprocessors.html. Its processing terms describe contractual safeguards for transfers, including standard contractual clauses where applicable; which safeguards apply depends on the relevant entities, locations, and agreement.

Contact support@ashtamkea.com for information about the safeguards applicable to support-data transfers or to request a copy, subject to necessary confidentiality redactions.

Remote hosts, AI services, and agent clients you choose may make separate international transfers under their own arrangements. Their policies and your account settings explain those arrangements; Ashtamkea's support-email arrangements do not cover them.

8. Your legal rights

Your right to object

Where the EU or UK GDPR applies, you may object at any time to our processing based on legitimate interests on grounds relating to your particular situation. Email support@ashtamkea.com to make an objection. We will stop that processing unless we demonstrate compelling legitimate grounds that override your interests, rights, and freedoms, or the processing is needed to establish, exercise, or defend legal claims.

Other rights and how to exercise them

Depending on applicable law and the basis for processing, you may have rights to access, correct, delete, or restrict processing and receive portable information. Where we rely on consent, you may withdraw it without affecting the lawfulness of earlier processing. Rights can have legal exceptions; they do not always require deletion of records needed to comply with law or address legal claims.

Contact support@ashtamkea.com to exercise rights concerning information held by Ashtamkea. We may request proportionate information to verify your identity or authority and will respond within the period required by applicable law. If we cannot fulfill a request, we will explain the reason and applicable complaint or appeal options. You may complain directly to the competent data protection authority, including, where the GDPR applies, in your place of habitual residence, place of work, or the place of the alleged infringement. You do not need to contact us first to exercise that right.

MoonGit is a developer tool and is not directed to children. Do not send Ashtamkea children's personal information through support. If you believe such information has been sent, contact us so it can be addressed under applicable law.

9. Policy changes

This policy has a version and effective date. Review it in onboarding or About → Legal, including when using the app offline. The published copy will be available at https://moongit.app/privacy. For a material change to the app's data practices, we will present the updated policy and an explanation through the startup Terms & Privacy process or a notice at the affected feature before the changed processing begins. A silently replaced document in About is not the notice for a material change. The app does not contact Ashtamkea in the background to check for new policies.

For a material change affecting support information we already hold, we will notify affected people using available contact details before applying the change, with any alternative notification or exception handled as applicable law permits. We will identify the change, when it takes effect, and available choices. Separate permission will be requested where required; terms acceptance or acknowledgment of a privacy notice is not consent to optional data sharing or tracking.