Privacy & Security Standard
Last synchronized: April 2, 2026. Your intelligence is your own.
1. Zero-Data-Transfer Architecture
GitSight is engineered on a rigid "Local-First" philosophy. Unlike traditional SaaS tools that require full repository access or transmission of log files, GitSight never transmits your source code, raw Git logs, or individual commit metadata to our servers.
All parsing, semantic grouping, and analytical computations are executed exclusively within your browser's local sandbox.
2. Information We Collect
We only collect the absolute minimum information required to manage your platform experience:
- Account & IdentityEmail address and profile name if you opt to create a Pro or Team account.
- Billing & TransactionsProcessed securely via Stripe. We do not store or see your primary credit card data.
- Operational MetricsAnonymous session metadata (e.g. "import started", "report generated") used to improve our local engine performance.
3. Intellectual Property Preservation
Your source code is your most valuable asset. By design, the GitSight engine does not have the technical capability to export your code content. It processes metadata patterns without ever touching the actual blob contents of your Git repository.
4. Browser Persistence & Cookies
GitSight uses `localStorage` and `IndexedDB` to persist your configuration, custom groupings, and analytical caches. This data remains on your machine and is never synced to a centralized GitSight cloud.
Standard session cookies are used exclusively for authentication and session management for licensed users.
Questions about our Security Standard? Contact Engineering Support