← Peerglass

Privacy

Last updated 26 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.

Your screen

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.

What we store

• No accounts. There is no signup, no password, no email address held by us.
• Sessions are held in memory only while they run, and disappear when they end or the server restarts.
• A paid plan is a signed token in your own browser's local storage. We store no customer record against it.
• Recordings are written by your browser to your own disk. They never reach us.

What we see in passing

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.

MYLABS AI Companion (Windows app)

MYLABS AI Companion, previously called MYLABS Companion, is the Windows helper for the MYLABS AI product family, made by MYLABS AI SOLUTIONS OPC PVT LTD. This release supports Peerglass: it turns taps and text from a viewer you allowed into real input on your PC. It runs only on your PC and sends nothing to us: it makes no network requests of its own and collects no analytics. Version 1.2 and later also support independently paired ClearHours and DocStudio desktop notifications. Those adapters receive fixed event names, not account tokens, work details, filenames or document contents, and cannot perform remote input. Windows may display or retain notifications according to your Windows settings.

• It listens on this computer only — the loopback address 127.0.0.1, port 8787 — never on your network. Peerglass.app can pair for remote input. Version 1.2 also accepts the exact clearhours.app and docstudio.work origins for notifications only. Each app has separate credentials and permissions, granted by entering a code shown on this PC.
• What it stores, in your Windows app-data folder: a random pairing token, and for each browser you paired a random key (encrypted with Windows' per-user data protection) with the dates it was paired and last used, and in version 1.2 the app's exact website origin. Version 1.3 also stores your optional avatar's visibility, position and notification-mute preference locally. Avatar messages are not saved. A browser unused for 90 days is forgotten. You can forget any browser, and regenerate the token, from the tray menu.
• What your browser stores: after pairing, the page keeps that browser's key in the browser's own storage for the paired app's website, in a form page script can use but cannot read out. Clearing the site's data removes it. The app sends the key to the page once, over this PC's own loopback connection, when you pair; it never crosses the connection again, and from then on the page and the app each prove they hold it. The pairing token never crosses the connection.
• It keeps none of the input it performs. Once you arm it, it performs the pointer moves, clicks, scrolls and text that a viewer you allowed sends through your own Peerglass tab. It does not record or log that input, and it does not capture your screen — your browser does the sharing, as described above.

The optional avatar in Companion 1.3 opens the supported websites and shows fixed app notifications. It adds no microphone access or AI chat. Hiding it keeps Companion running. Mute pauses routine app notifications; pairing dialogs and remote-control safety alerts stay on. These controls do not change your browser pairings or grant remote control.

Payments

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.

Third parties

• Fly.io — hosting, Singapore.
• LiveKit Cloud — broadcast media for larger sessions.
• Cloudflare — connection relay when a direct connection cannot be established.
• Our payment provider — checkout and billing.
• Plausible — cookie-free page-view counts, when we have it switched on. It sees the address of the page you opened and a hashed IP it does not keep; never the session, the stream, or who was in it.

Your rights

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.