Privacy Policy & Trust Commitments
git-grass is built by developers, for developers. Privacy is an engineering invariant, not a marketing claim.
Our Core Privacy Pledge
Source Code & Git Safety
- Git Credentials: Your SSH private keys, GPG signing keys, Git configuration, and GitHub tokens remain exclusively on your local workstation. The cloud backend has zero Git access.
- Local Commit Execution: The mobile web browser never executes Git commands. It sends an authenticated message to your local workstation server (:4242), which executes the commit locally.
- Staging Protection: Before your break, git-grass snapshots the staged tree SHA using
git write-tree. It verifies that this tree has not changed before executing the commit upon your return.
What Metadata is Sent to the Hosted AI?
When you configure git-grass to use the Render hosted AI backend, the CLI transmits only high-level classification metadata:
{
"repositoryName": "distributed-cache",
"projectDescription": "In-memory caching cluster",
"category": "systems",
"durationMinutes": 15,
"detectedKeywords": ["redis", "cluster", "node"]
}
Zero code lines, zero file paths, zero function names, and zero author emails are included. If you prefer not to send any metadata, do not configure a hosted backend URL—git-grass will rely completely on bundled offline challenges.
Trust vs. Surveillance
We believe developer wellness tools must treat developers as autonomous professionals. git-grass deliberately does not use:
- GPS or location geofencing.
- Camera verification or photo check-ins.
- Biometric heart-rate or pedometer tracking.
- Keyboard logging or window sniffing daemons.
Instead, git-grass provides mindful friction: an authoritative 10-minute workstation timer and an observational question to capture what you saw outdoors.
Zero Telemetry & Zero Trackers
This website and the git-grass CLI include zero analytics trackers, zero cookies, zero third-party font calls, and zero telemetry pings. Your usage data is never collected or monetized.
Security Inquiries
To report a potential vulnerability or ask privacy questions, please email snehatiwari474@gmail.com or open a private GitHub security advisory.