3. Information We Collect

Last Updated: November 14, 2025

This section outlines the categories of data .git collects when you use our platform, APIs, documentation, or support services. We collect information only to provide, secure, and improve our developer infrastructure.

3.1 Information You Provide Directly

When you interact with .git, you may voluntarily provide information that we store to manage your account and deliver our services:

  • Account Credentials: Email address, password hash, and optional profile information (display name, avatar, organization affiliation).
  • Repository & Project Data: Names, descriptions, README files, and metadata you explicitly push or configure through our CLI or dashboard.
  • Team & Access Management: Role assignments, team member invitations, and permission scopes you configure.
  • Billing & Payment: Invoice addresses, tax IDs, and payment method tokens processed securely via PCI-DSS compliant partners (e.g., Stripe). We do not store raw credit card numbers.
  • Support & Communications: Messages, logs, or files you submit when contacting our support team or participating in community forums.
💡 Note: You may leave certain profile fields blank. Only an email and password are required to create a personal account.

3.2 Automatically Collected Information

To ensure platform stability, security, and optimal performance, we automatically collect technical and usage data when you access .git:

  • Device & Network Data: IP address, browser/user-agent, operating system, and locale settings.
  • Deployment & Build Metrics: Build duration, success/failure status, resource consumption (CPU, memory, disk), and deployment frequency.
  • Error & Crash Reports: Stack traces, unhandled exception logs, and service health telemetry generated by our hosted runners.
  • Security Events: Failed login attempts, unusual API usage patterns, and DDoS mitigation triggers.
  • Session Analytics: Page views, feature usage frequency, and navigation paths within the dashboard to improve UX.

We do not track or store repository source code content, secrets, or environment variables beyond what is strictly required to execute your builds and deployments. All artifacts are encrypted at rest and in transit.

3.3 Information from Third Parties

.git integrates with external services to streamline your workflow. When you authorize these connections, we may receive limited data:

  • VCS Providers: GitHub, GitLab, or Bitbucket webhooks and API tokens to sync branches, commits, and pull request metadata.
  • CI/CD & Infrastructure Partners: Status updates from container registries, DNS providers, or cloud compute APIs you link.
  • Identity Providers: SSO/SAML assertions if your organization uses Okta, Auth0, or similar services for login.
  • Analytics & Monitoring: Aggregated, anonymized usage statistics from partners like Datadog or Sentry (if integrated).

We only process third-party data under the scopes you explicitly grant during integration setup. You can revoke access at any time in your dashboard settings.

3.4 Cookies & Tracking Technologies

We use essential and functional cookies to maintain secure sessions and remember your preferences. We do not use third-party advertising trackers.

  • Essential Cookies: Authentication tokens, CSRF protection, and session management (strictly necessary).
  • Preference Cookies: Theme selection (dark/light), dashboard layout, and notification settings.
  • Analytics Cookies: First-party, privacy-focused usage tracking to measure feature adoption and error rates. No personal identifiers are linked to these cookies.
  • Local Storage: Temporary CLI cache, draft configurations, and offline queue data (stored exclusively on your device).

You can manage or disable non-essential tracking via your browser settings or the Cookie Preferences Panel in your account dashboard.

3.5 How We Use Collected Information

All data collected under this policy is used exclusively for the following purposes:

  • Delivering, securing, and maintaining the .git platform and associated APIs
  • Processing deployments, managing build environments, and ensuring uptime
  • Verifying identity, preventing fraud, and complying with legal obligations
  • Billing, invoicing, and managing subscription tiers
  • Providing technical support, responding to inquiries, and improving documentation
  • Analyzing platform performance and developing new developer tools
  • Sending service notifications, security alerts, and optional product updates

We do not sell, rent, or trade your personal information to data brokers or third-party advertisers.

3.6 Your Rights & Choices

Depending on your jurisdiction, you may have the following data rights:

  • Access & Export: Request a copy of all personal data we hold about you in a machine-readable format.
  • Rectification: Update or correct inaccurate account or billing information.
  • Deletion: Delete your account and associated data (excluding records required for legal, security, or billing compliance).
  • Opt-Out: Unsubscribe from marketing emails or disable non-essential analytics at any time.
  • Portability: Export your project configurations, deployment logs, and team settings.

To exercise these rights, visit your Account Settings > Privacy & Data or contact our Data Protection Officer. We will respond to valid requests within 30 days.

3.7 Contact Us

If you have questions about this section, how we handle your data, or wish to submit a data request, please reach out:

  • Email: privacy@.git.dev
  • Data Protection Officer: dpo@.git.dev
  • Mail: .git Inc., 100 Developer Blvd, Suite 404, San Francisco, CA 94107, USA

We are committed to transparency and will update this policy as our services evolve. Material changes will be communicated via email or platform notice at least 30 days before taking effect.