Privacy Policy

How AgentGit collects, uses, and shares personal information.

Effective date: September 1, 2026

Introduction and Scope

Einsia AI Technology (SG) PTE. LTD. (“Company”, “we”, “us”, or “our”) provides AgentGit, a platform for recording, versioning, hosting, searching, sharing, and continuing AI agent sessions. This Privacy Policy explains how we handle personal information in connection with agent-git.com and the websites, hosted Hub, command-line tools, APIs, collaboration features, and remote-control services we operate (collectively, the “Services”). Personal information means information that identifies, relates to, or can reasonably be linked to an individual.

This Policy covers information we receive or process. Installing or using a local AgentGit tool does not, by itself, mean that all locally stored content is uploaded to us. Third-party agent runtimes, model accounts, integrations, and independently operated Hubs have their own data practices. An operator who deploys a self-hosted Hub is responsible for that deployment and its processing of personal information. This Policy continues to apply to information separately sent to Services we operate.

If you use AgentGit for an employer or other organization, its administrators may manage access to organization resources and the information you contribute to them. Its policies and any applicable agreement with us may also govern that use. Joining an organization does not make its repositories private; the applicable visibility and access settings determine who can access each resource.

Information We Collect

Account, Profile, and Support Information

We process account details such as your username, email address, display name, profile image, authentication information, account settings, and organization or collaboration memberships. If you sign in or link an account through an external authentication provider, we receive the identifiers and profile information made available through that connection, such as your provider account identifier, name, and verified email address.

We also process information you send when requesting support, reporting a problem, providing feedback, or exercising a privacy right. This may include correspondence and diagnostic material you choose to provide.

Repository and Session Content

When you upload, synchronize, import into a hosted feature, or otherwise make content available to our Services, we process that content and its associated metadata. Depending on the runtime and features you use, this may include:

  • Prompts, instructions, conversation history, AI responses, and other session events retained by the runtime.
  • Tool calls, their arguments and results, commands, execution output, code snippets, file contents, changes, and file paths included in a session.
  • Shared instructions, memory, skills, documentation, attachments, repository descriptions, and other files you submit.
  • Repository and branch names, commit history, timestamps, author information, model or runtime identifiers, source-repository references, comments, and collaboration activity.

Content can contain information about other people, confidential material, or credentials. You should provide only information you are authorized to process and share. Secret detection and related safeguards can reduce accidental disclosure but cannot identify or remove every sensitive item.

Local Operation, Synchronization, and Remote Control

Local AgentGit tools can retain session history and shared files on your device. Content reaches a hosted Hub through operations such as pushing, synchronizing, sharing, or using features that send it to that Hub. Configured integrations can record sessions automatically, and remote-control workflows can automatically synchronize completed activity. The information transmitted depends on the features you enable and the Hub you select.

When you connect a machine or use remote-control features, we process the information needed to identify the machine, route requests, and maintain the workspace. This can include machine names and identifiers, platform and software versions, connectivity status, workspace names and paths, repository references, instructions, execution events, approval decisions, and permission information. Relevant commands, responses, and terminal output may pass through the Services. Some workspace and approval events are retained to support continuity, coordination, and security.

Technical and Usage Information

Depending on how you access the Services, we process technical information such as IP addresses, browser and operating-system information, application versions, request timestamps, pages or features accessed, session identifiers, and performance or security events. Operational and error records can contain resource identifiers and relevant request or task context. We use these records to operate the Services, investigate failures, and prevent misuse.

If we introduce paid features and you purchase them, we may process the billing contact details, transaction records, payment status, and payment-provider references needed to administer your purchase. The applicable purchase flow will explain payment processing; this does not mean payment details are required to use currently free features.

How We Use Information

We use information for the following purposes, subject to the limits and choices explained in this Policy:

  • Creating and securing accounts, authenticating users, and managing access to repositories and workspaces.
  • Recording, hosting, synchronizing, restoring, searching, displaying, and sharing session content and repository history.
  • Providing collaboration, remote control, AI summaries, search answers, and other requested features.
  • Maintaining reliability, resolving technical problems, answering support requests, and preventing fraud, abuse, and unauthorized access.
  • Understanding service performance and developing or improving the Services, including eligible AI development and training uses described below.
  • Administering any purchases, sending service and security notices, complying with law, and establishing, exercising, or defending legal claims.

We do not sell your personal information.

AI Processing, Training, and Your Choices

Providing AI Features

AgentGit uses service-side AI features, including summaries of public sessions and AI-assisted search. To provide an AI feature, we may send the relevant request and content to an AI service provider acting on our behalf. Input can include a prompt, an attachment, or context retrieved from repositories the requesting user is authorized to access. Output means the response or other material generated by that feature.

Private repositories are searchable only by users with the required access. An authorized AI search may process excerpts of private content through an AI service provider to produce an answer for the authorized user. That processing does not make the repository public. Processing content to answer a request is distinct from using it to train a model.

Development and Training

Subject to applicable law, the AgentGit Terms of Service, applicable content licenses, and the restrictions described here, we may use public repository content to develop, train, and improve our AI models and features. We respect a repository owner’s “no training” declaration. Public availability does not override another person’s rights or an applicable restriction on training.

We do not use private repository content merely stored in the Services for model training. If content is provided as Input to an AgentGit AI feature, including as authorized retrieved context, we may use that Input and the resulting Output to develop, train, and improve our AI models and features unless an applicable training opt-out or “no training” declaration applies. A collaborator’s use of an AI feature does not override the source repository owner’s training restrictions or supply rights that the collaborator does not have.

We do not authorize third-party AI model providers to use your Input or Output for their own independent model training. Providers acting on our behalf must process the information for the authorized purposes and under appropriate confidentiality and data-protection obligations. If applicable law requires additional consent for a training use, we will obtain it before that use.

How to Opt Out

You may opt out of the use of your AgentGit AI Input and Output for training by emailing the Contact Email from your account email address or otherwise providing enough information for us to verify your request. We will apply valid requests prospectively without undue delay and confirm their implementation. Where the repository declaration feature is available, a repository owner can also mark its content “no training”. You may contact the same email address for help applying or clarifying that restriction.

These choices restrict training; they do not prevent the processing needed to provide an AI feature you request, or necessary security, support, and legal processing. A training opt-out does not automatically reverse completed model training. Your statutory rights, including any applicable rights to object, withdraw consent, or request deletion, remain available. Independently operated runtimes or model services you connect are governed by their own policies and controls.

Cookies and Similar Technologies

We use cookies, browser storage, and similar technologies for functions such as sign-in, authentication security, session continuity, and remembering preferences. You can manage cookies and browser storage through your browser, although deleting or blocking them can affect sign-in and other features.

If we use non-essential analytics or similar technologies that require consent under applicable law, we will obtain that consent and provide the required controls. This Policy does not treat use of the Services as blanket consent to optional tracking.

Where applicable law requires a legal basis, we rely on the basis appropriate to the activity: performing our agreement with you for requested Services; complying with legal obligations; consent where required; and legitimate interests where permitted, such as protecting the Services and improving their reliability, balanced against your rights and interests.

For optional model training, we obtain consent where required. In other cases where applicable law permits reliance on legitimate interests, we may rely on our interest in developing and improving AgentGit AI models and features only after assessing that this interest is not overridden by your rights and interests. You may object to such processing and use the training choices described above. Optional training is not treated as necessary to perform the basic hosting agreement. All training remains subject to the applicable content restrictions and choices in this Policy; a contractual content license does not replace a legal basis required by privacy law.

Sharing and Access

  • Other users and the public. Repository visibility, collaboration permissions, and your sharing actions determine access. Public content and associated public profile or activity information can be viewed, indexed, copied, or forked by others. Recipients of a valid sharing link may access the content covered by that link, subject to any supported restrictions. Revoking access or changing visibility cannot reliably recall copies already obtained by others.
  • Organization and workspace administrators. Administrators and authorized collaborators may access content and activity within resources they administer or are permitted to use. Their access depends on the applicable resource permissions.
  • Service providers. We use providers for functions such as infrastructure and hosting, authentication, AI processing, communications, support, diagnostics, and security. We disclose information needed for their assigned services and require appropriate restrictions and safeguards. Details about recipients and applicable transfer protections may be requested at the Contact Email.
  • Connections you choose. Information may be exchanged with an external runtime, integration, or Hub as necessary to provide the connection you or an authorized administrator enables.
  • Legal and safety purposes. We may disclose information when required by law or legal process, or where lawfully necessary to investigate misuse, protect rights and safety, or establish, exercise, or defend legal claims.
  • Corporate transactions. Information may be transferred as part of a merger, acquisition, reorganization, or transfer of the relevant business or assets, subject to applicable protections and any legally required notice.

We treat private repository content as confidential. Personnel access is limited to authorized purposes, such as responding to a support request, investigating security issues or abuse, maintaining service integrity, or meeting legal obligations. Private visibility does not mean that the content is inaccessible to the systems and authorized providers needed to operate the Services.

International Data Transfers

We and our service providers may process information in countries other than your country of residence. Those countries may have different data-protection laws. Where applicable law requires safeguards for an international transfer, we use the applicable legal mechanism and safeguards, such as an adequacy decision or appropriate contractual protections. We will provide information about the applicable safeguards and how to obtain a copy, where required, on request at the Contact Email.

Retention, Account Closure, and Deletion

We determine retention by the information’s purpose, the service relationship, applicable legal requirements, and whether the information is still needed. In particular:

  • Accounts and hosted content. We retain information while needed to maintain your account, provide the repositories and history you choose to keep, and support related collaboration. A verified account-closure or deletion request triggers review and deletion or anonymization of information we no longer need, subject to applicable law and the exceptions below.
  • Workspace, operational, security, and support records. Retention depends on the duration of the workspace or support matter, the need to investigate and resolve incidents, prevent abuse, and maintain service integrity. We delete or anonymize records when those purposes no longer require identifiable information.
  • Legal and transaction records. We retain information where needed to meet statutory obligations or establish, exercise, or defend legal claims, and review retention when the relevant obligation or matter ends.
  • Backups and recovery copies. Deletion from active systems may precede removal from backups. Residual copies remain subject to access restrictions and are removed through the applicable backup replacement or deletion cycle. Where deleted information is restored for recovery, applicable deletion requests must be reapplied.

You may request account closure or deletion by emailing the Contact Email. We may verify your identity and authority over the affected resources. We address requests within the periods required by applicable law and explain any applicable reason for retaining information. You can contact us for information about the retention criteria applicable to a particular category of data.

Version history can preserve content after it is removed from a current view or branch. Reverting an event, changing a view, or revoking a link is not a request to erase all underlying history. Account closure also does not necessarily remove contributions to resources controlled by others or copies that others have forked, downloaded, or exported. We will assess valid privacy requests concerning information under our control, subject to applicable law; we cannot guarantee deletion of copies held independently by third parties.

Security

We use technical and organizational safeguards appropriate to the information and risks, including access controls, authentication, transmission protection, and measures to investigate security incidents. Encryption features depend on the feature and configuration; a private repository or a particular encrypted sharing mode is not a promise that every AgentGit data flow is end-to-end encrypted.

No system can guarantee absolute security. You are responsible for protecting account credentials, connected machines, and sharing links. If a personal-data incident requires notice, we will notify affected individuals and authorities as required by applicable law.

Your Privacy Rights

Depending on applicable law, you may request access to or a copy of your personal information, correction, deletion, restriction, or portability; object to certain processing; or withdraw consent where processing relies on consent. You may also have the right to complain to the competent data-protection authority. Withdrawing consent does not affect processing that was lawful before withdrawal.

Send requests to the Contact Email. We may request proportionate verification information and will respond within applicable legal time limits. Where another organization determines the processing of the information concerned, we may direct you to that organization or assist it in addressing your request, as appropriate.

For users in the EEA, the United Kingdom, or other jurisdictions with similar protections, the legal bases, transfer safeguards, objection rights, and consent choices described above apply as required by local law. California and other eligible US residents may also have rights to know the categories, sources, purposes, and recipients of personal information, to correct or delete it, to receive it in a usable form, and to exercise applicable opt-out rights. We do not discriminate against individuals for exercising protected privacy rights. Authorized representatives may submit requests where permitted by law, subject to verification of their authority.

Children’s Privacy

The Services are not intended for children under 13 or a higher minimum age required by local law. Users who meet the minimum age but are below the age of majority where they live must have permission from a parent or legal guardian. If we learn that we have collected personal information from a child who does not meet the applicable requirements, we will take appropriate steps to delete it. A parent or guardian may contact us at the Contact Email about such information.

Changes to This Policy

We may update this Policy as the Services or our practices change. We will publish an updated date and provide reasonable advance notice of material changes through the Services or an appropriate communication channel, except where a more immediate change is required by law or necessary for security. We will obtain additional consent where legally required; a policy update does not replace that requirement.

Language and Contact

If this Policy is translated, the English version controls in the event of an inconsistency, except where applicable law requires otherwise.

For privacy questions, training choices, account closure, deletion, or other rights requests, contact:

Einsia AI Technology (SG) PTE. LTD.
Email: support@einsia.ai (the “Contact Email”)
Website: agent-git.com