Privacy Policy

Effective date: November 21, 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.


1. What never leaves your machine

Local HTTPS, traffic inspection and the MCP endpoint all run on your computer. That means we do not receive:

  • the requests and responses captured by Inspect, including their bodies
  • your local certificate authority or its private key
  • traffic between your browser and an app on .local
  • the contents of the apps you run

Public URLs are the exception, and section 3 is about them.

2. Your account

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.

Sign in with Google — Google user data

You can sign in or sign up with your Google account instead of a password. This is the only way Piperace accesses Google user data, and it is optional.

  • What we access: the basic sign-in scopes email and profile. From them we use your verified email address and Google's account identifier; we do not keep your name or profile picture. We do not request access to your Gmail, Drive, Calendar, contacts or any other Google service.
  • How we use it: only to identify you, create or link your Piperace account, and sign you in. If an account with the same email already exists, Google sign-in is linked to it rather than creating a second one.
  • How we store it: your email and Google's account identifier are stored in our database like any other account data and kept while the account exists (section 9). We do not store your Google password, and we never receive it.
  • What we share: nothing. Google user data is not sold, not shared with advertisers or data brokers, and not used for advertising, profiling or training AI models. It is passed on only where the law requires it.

Piperace's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke Piperace's access at any time in your Google Account permissions, and ask us to delete your account (section 10).

3. Traffic through your public URLs

A public URL routes visitors through our servers, so we can see the shape of that traffic. We store, for up to 30 days:

  • URL paths and HTTP methods
  • status codes and response times
  • bytes in and out
  • the IP address of the machine running the client, and of each visitor

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.

4. Device fingerprint

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.

5. Usage statistics

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.

6. Payments

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.

7. If you write to us or comment

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.

8. Who else touches your data
  • Creem — payments, tax, invoices, refunds
  • Amazon Web Services — the servers your tunnels run on, DNS, and the bucket that serves downloads
  • Bugsnag — crash and error reports from our own software
  • Google — "Sign in with Google" (see section 2), and measuring which of our ads lead to a visit or a download, on this website only

We do not sell your data, and we do not run advertising or third-party analytics on your tunnel traffic.

9. How long we keep things
  • Traffic metadata and our own diagnostic logs — 30 days
  • Account, subdomains and subscription records — while the account exists
  • Usage statistics — kept as long-term aggregates, one row per install per day
10. Your rights

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.

11. Changes

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.

12. Contact

Questions about this policy, or a request about your data: [email protected].

See also our Terms of Service and Refund Policy.