AnchorGit Privacy Policy

1. The Zero-Knowledge Code-Blind Model (Core Pillar)

Explicit Declaration: AnchorGit never reads, transmits, ingests, or stores your source code, raw diffs, or file contents on cloud servers.

All code diff parsing and SHA-256 HMAC signature calculations occur 100% locally on your workstation.

2. Information We Collect

• Account Information: Email address, name, username, bio, avatar URL, and hashed authentication credentials (via Devise/OAuth).
• Notarized Metadata (Synced to Cloud):
  • • High-level human rationale strings (e.g., "Switched session store to Redis").
  • • Metadata counters: Commit SHA, branch name, lines added (+LOC), lines deleted (-LOC), decision category, and active focus duration (deliberation_seconds).
  • • Cryptographic proofs: Diff SHA-256 hashes and HMAC signatures.
• Hardware Telemetry: Non-invertible, hashed workstation GUIDs derived locally from hardware serials. Plaintext CPU/motherboard serial numbers are never transmitted.

3. Public vs. Private Visibility Controls

• Public Profile (/p/:username): Decisions explicitly set to is_public: true are visible on your public portfolio ledger.
• Private Workspace Logs: Decisions flagged as is_public: false or scoped to internal enterprise organizations are accessible only by authenticated account members.

4. Data Security & Storage

All cloud communications occur over TLS 1.3 encrypted connections. Database records are stored in enterprise-grade infrastructure with restricted role-based access controls (RBAC).

5. Data Retention & User Rights

• Users can regenerate API keys at any time to instantly revoke workstation pairings.
• Users retain the right to delete their account and associated decision ledgers at any time via the console or by contacting support.