Privacy & security
What leaves your machine
The complete data flow, which is short enough to fit on one page: one outbound call, two values in it.
The scan stays here#
Scan results are never uploaded. Your projects, ports, branches, folder paths and metrics are read on your machine, rendered on your machine, and discarded on your machine. There is no account to sync them to and no server that would accept them.
The one call#
Pip makes exactly one kind of outbound request: licence activation. It carries:
- Your licence key
- So we know which seat it is.
- A device hash
- Salted and truncated — a one-way value that distinguishes machines without describing one.
The licence itself is then stored encrypted with Windows DPAPI, so it is readable only by your Windows user account on that machine.
The window cannot reach out#
The interface has no file access, no network access and no shell access. Its entire privilege surface is thirteen typed commands into the Rust core — a list short enough to audit in an afternoon.
Fonts ship inside the binary. There are no CDNs, no remote assets and no analytics beacons, which also means nothing breaks when you are offline.
In legal terms#
Note
This page is the plain-language version. The binding one is the Privacy Policy, which also covers billing, support correspondence and crash diagnostics — the things that involve us because you sent them to us.
Did this page not answer it? Tell us what you were looking for — that is how Pip's documentation gets written.