Effective date: September 3, 2026
Piperace puts a program on your machine and a tunnel on ours. This page says exactly what each half knows about you, because those are very different answers.
The short version: what runs locally stays local — your certificates, your captured requests and the traffic between your browser and your own app never reach us. What we hold is your account, what your tunnels carried, and enough about installs to know whether the product is any good.
Local HTTPS, traffic inspection and the MCP endpoint all run on your computer. That means we do not receive:
.localPublic URLs are the exception, and section 3 is about them.
If you sign in, we store your email address, a hashed password, an API token, your plan and your account status. If you use Piperace without signing up, we create a guest account instead, identified by a device fingerprint (see section 4) rather than by anything you typed.
A public URL routes visitors through our servers, so we can see the shape of that traffic. We store, for up to 30 days:
We do not store request or response bodies. This metadata exists to investigate abuse, answer lawful requests and keep the service running — not to profile you.
Our edge servers, which handle a request only while DNS for a new subdomain is still propagating, do not decrypt anything at all: they read the hostname from the TLS handshake and splice the connection through untouched.
The client derives a fingerprint from your hardware and sends us a SHA-256 hash of it. The raw hardware identifier never reaches us and cannot be recovered from the hash.
It does two jobs: it lets a guest keep the same account across restarts without signing up, and it lets us see when many accounts share one machine, which is how free-tier abuse looks. We record when each machine was first and last seen.
The client reports, once a day per install: which features were used (local HTTPS, public URLs, traffic inspection, the agent endpoint), how many apps are configured, how many requests were captured locally, the client version and the platform.
These rows are keyed on the install, not the account, so somebody who never signs up still counts — those are the people we most need to learn from. Counts only: no app names, no URLs, no captured content.
Payments are handled by Creem, who are the merchant of record. They take the card, charge the tax and issue the receipt. We never see or store your card details.
On our side we keep two identifiers Creem gives us — a customer id and a subscription id — and a log of the events they send us about your subscription, so we know which plan you are on and why. Invoices, payment methods and cancellation live in Creem's customer portal, reachable from your dashboard.
A support ticket stores your email, your message and the client version and platform you sent it from. A blog comment stores the name and email you typed, the comment, and the IP address and browser it came from — the last two only to stop spam.
We do not sell your data, and we do not run advertising or third-party analytics on your traffic.
Write to us and we will tell you what we hold about you, correct it, or delete your account and the data tied to it. Deleting an account releases its subdomains, so the names become available to others.
Billing records that we are required to keep for tax purposes are held by Creem under their own policy, and we cannot delete those on your behalf.
If this policy changes in a way that affects what we collect, we will change the effective date above and say so on the site rather than quietly editing the page.
Questions about this policy, or a request about your data: [email protected].
See also our Terms of Service and Refund Policy.