Privacy Policy

Last updated: June 2026

partyline (“partyline”, “we”, “us”) is published by DDR Consulting Ltd., a company incorporated in British Columbia, Canada. This policy explains what we collect and why. It is a general policy, not legal advice.

There is no hosted partyline. This site is documentation and marketing; there is no sign-up, no hosted app and no database behind it. The software runs on a server you install and operate, so your accounts, teams, projects, sessions and session keys live on your instance — we never receive them and cannot access them. Whoever runs that box is the data controller for what is on it. This policy therefore covers only two things: what this website collects, and what the CLI sends.

What this website collects

  • Analytics — we use Google Analytics on these public pages to understand traffic and where visitors go. It sets its own cookies and shares aggregate usage data with Google. We run no advertising cookies and we do not sell your data.
  • Nothing else. There is no account to create here, so there is no email, name, avatar or profile for this site to hold.

What the CLI sends

  • A once-a-day anonymous ping carrying only a random install id, the CLI version, and the operating system — no identity, no paths, no content. You are shown a notice before the first one is ever sent. Opt out with PARTYLINE_TELEMETRY=0 or DO_NOT_TRACK=1.
  • A version check, at most once a day. Opt out with PARTYLINE_NO_UPDATE_CHECK=1.
  • Both are off unconditionally once the CLI is pointed at your own instance, and off in CI. Details: Telemetry.

Your terminal sessions are encrypted

Live sessions are encrypted in transit. Terminal data is encrypted on your machine before it leaves. The default relay (pppp.sh) is blind— it forwards ciphertext it can't read and never holds the key, and it sees connection metadata only (the routing code, timing, and data volume), never what is on your screen.

So your team can see the join link in the web app and in invites, the session's encryption key is escrowed with the control plane — which is your own instance. Sessions are therefore encrypted in transit and unreadable by the relay, but this is not zero-knowledge: whoever administers your box holds that key. We never do, because we operate no instance. Treat the join link like a password — anyone who has it can join and decrypt the session.

Who we share data with

For this website, one provider: Google Analytics (traffic analytics on these public pages; sets cookies, aggregate usage processed by Google). We do not sell your personal data.

Everything else a running partyline touches — its identity provider, its email sender, object storage, error reporting, a connected Slack workspace — is configured by whoever operates that instance, in that instance's own environment. They are that operator's subprocessors, not ours, and none of it is routed through us. Self-host lists every one of those settings.

Retention & your rights

This site keeps no account data, so there is none for us to retain. Your account, team and session data is held by the instance you use — direct access, correction and deletion requests to its operator. For the anonymous CLI ping, the install id is a random value on your own machine and deleting ~/.partyline/telemetry.json severs it. Questions to us are welcome either way. partyline is not directed to children under 16.

Changes & contact

We'll update this page if our practices change. Questions or requests: privacy@partyline.sh.