zkgit

Privacy

What we actually collect, written by the person who built it — not a law firm. If anything here matters to you legally, get your own read; this is a plain description of practice, not a reviewed legal document.

zkgit's whole pitch is that the server can't read your code. This page is the rest of the honest ledger already on the front page — everything else that touches this site or the waitlist, spelled out.

If you just visit this site

No cookies, no third-party trackers, no ad network, nothing that follows you elsewhere. As of this writing there is no analytics on this page at all — if that changes, this section will say exactly what's collected, and it won't be anything that identifies you individually or leaves this domain.

If you ask for an invite

The waitlist form sends your email address and whatever you wrote to zkgitd, where it's stored to review and act on. It's kept until the request is handled, and we don't currently auto-delete old ones — ask and we'll remove yours. It is never linked to any account you later create, even by us: approving your request mints a single-use invite code, and the code is recorded as spent without recording who spent it. That's enforced in the code, not just promised — see internal/adminstore in the source if you want to check.

If you have a zkgit account

The server holds:

The server cannot hold, by construction:

Encryption hides content, not the fact that content exists — someone watching the network still learns that you talk to this server and roughly how much you push. See the front page's "things it deliberately doesn't do" section for the rest of that trade-off.

Who else sees any of this

Nobody. No analytics vendor, no ad network, no data broker, no "trusted partners." If that ever changes for a specific product, it'll be named here before it happens, not after.

Contact

Questions, or want your waitlist entry removed: hello@jeffconsults.llc.

← Back