Privacy Policy
1. Introduction & Core Positioning
This Privacy Policy describes how GitPlace (“GitPlace”, “we”, “us”, or “our”) handles information in connection with the GitPlace Visual Studio Code Extension (the “Extension”) and the gitplace.dev website (the “Website”).
GitPlace is positioned and designed as local-first Git development workspace management software. GitPlace is not a cloud Git repository hosting service, cloud backup service, or remote synchronization provider. The Extension is designed to operate directly on the user’s local machine within Microsoft Visual Studio Code.
2. Scope: Website vs. Extension Processing
To ensure legal and technical precision, we clearly distinguish between information processed by the Website and information processed by the Extension:
A. GitPlace Website (gitplace.dev)
The Website provides product information, documentation and installation links. It processes standard HTTP request logs and optional contact communications submitted by users.
B. GitPlace VS Code Extension
The Extension executes locally inside Visual Studio Code on your device. Its core Git and workspace functionality processes repository data locally and does not transmit that data to GitPlace servers.
3. Repository and Workspace Data
Under the current architecture of the GitPlace Extension:
GitPlace’s current local Git/workspace functionality does not transmit repository source code, commit history, branch information, file paths, .env files, credentials, or workspace metadata to GitPlace servers or third parties for the purpose of providing its local Git/workspace functionality.
When you use GitPlace features (such as creating branch workspaces, inspecting git changes, executing commit history searches, diffing files, or applying local setup stashes), the Extension reads and manipulates files locally on your machine using your local Git binary and filesystem. Reading local data to fulfill a user-requested command is strictly distinct from transmitting that data externally.
4. Data Processing & Transmission Summary Table
The following table summarizes the data handling of the current version of the GitPlace Extension:
| Data Category | Processed Locally | Sent to GitPlace | Stored by GitPlace |
|---|---|---|---|
| Repository source code | Yes, when required locally | No | No |
| Commit history & messages | Yes | No | No |
| Branch information & SHAs | Yes | No | No |
| File paths & directory structures | Yes, when required | No | No |
| .env files & local configs | May be locally encountered where required | No | No |
| Git credentials & SSH keys | May be used by local Git/OS mechanisms where applicable | No | No |
| Workspace configuration & metadata | Yes | No | No |
5. Credentials, Authentication and Secret Files
GitPlace does not intentionally transmit Git credentials, authentication tokens, SSH private keys, passwords, .env secrets, or similar credentials to GitPlace servers.
If the Extension invokes standard Git operations (such as branch checkout, fetch, or worktree provisioning), authentication is handled via the existing Git credential helpers, SSH agents, or operating system keychains configured on your machine. Access to local files is strictly limited to what is technically required to perform user-requested workspace operations.
6. AI and Machine Learning Models
GitPlace does not currently send repository contents, source code, commit history, or workspace data to artificial intelligence (AI) or large language model (LLM) providers.
This statement describes the current version of GitPlace. Any future feature that introduces AI/LLM integration or changes how user data is processed will be separately disclosed and the applicable policies will be updated before such functionality is released.
7. Telemetry, Analytics and Error Reporting
Extension: GitPlace does not currently transmit repository content, source code, or Git metadata as telemetry. Extension error handling is managed locally within the VS Code runtime environment.
Website: The website (gitplace.dev) is statically served. Standard web server access logs (such as IP address, user-agent and requested path) may be processed transiently by hosting infrastructure strictly for operational stability, security and defense against abuse.
8. Personal Data in Local Repositories
GitPlace acknowledges that Git repositories inherently contain developer and contributor information, including author names, email addresses, commit timestamps, usernames and potential personal data in source code or documentation.
GitPlace may locally process information contained in repositories, including information that may constitute personal data, when necessary to provide user-requested functionality. Under the current local-first architecture, GitPlace does not transmit that repository information to GitPlace servers.
9. Applicable Privacy Frameworks
GitPlace is developed and operated by an entity based in India and is made available to users worldwide. GitPlace is designed to respect applicable privacy and data protection principles, including:
- India: The Digital Personal Data Protection Act, 2023 (DPDP Act) and applicable rules in force. Data processing adheres to principles of purpose limitation, data minimization and reasonable security safeguards.
- European Economic Area & UK: Where applicable under the General Data Protection Regulation (GDPR) and UK GDPR, users have rights of access, rectification, erasure and objection regarding any personal data held directly by us (such as support communications).
- United States: California Consumer Privacy Act (CCPA/CPRA) and state privacy statutes. We do not sell or share personal information as defined by California law.
10. Policy Updates & Change Control
If GitPlace introduces future features that change how user data is processed (such as optional cloud workspace sync, team accounts, remote backup, or third-party integrations), we will update this Privacy Policy, update the VS Code Marketplace listing and provide appropriate notice or consent mechanisms prior to the introduction of such functionality.
11. Contact Information & Grievance Redressal
For any questions, privacy inquiries, or grievances regarding this Privacy Policy, you may contact our team: