Last updated 9 September 2026.
Peerglass is built so that there is very little about you to hold. This page describes what actually happens, not what is merely permitted.
Peer-to-peer sessions send video directly between browsers. It is encrypted in transit and never reaches our servers, so we cannot see, record or retain it. Sessions large enough to need our broadcast servers pass through a third-party media service (LiveKit) in transit; that video is not recorded by us either.
The server logs ordinary operational information such as IP addresses and error messages, used to run the service and to enforce abuse limits. Your IP is also held in memory while a session runs, to apply per-address limits. We also keep aggregate daily counts — pages served, sessions started, viewers turned away — as plain numbers with no identifiers attached, for 90 days.
Payments are handled by our payment provider, who acts as merchant of record. They collect the billing details needed to take payment and to meet tax obligations. We do not see or store your card details. The provider's subscription or payment identifier lives in your own browser, inside the plan token; we keep no copy. When you activate, restore or renew a plan, that identifier is sent to the provider to confirm the subscription is still active, and the country on the receipt is read for tax purposes and not stored. Pasting a receipt link or id at /restore sends it to the provider the same way.
Because we hold no account, there is generally nothing to export or delete. To ask about data held by our payment provider, or anything else, write to support@peerglass.app.