Tab Controller — Privacy Policy
Last updated: September 2026
Tab Controller is a Chrome extension that lets a user grant a trusted, paired peer temporary remote control of exactly one of their browser tabs, with explicit on-screen consent. This policy explains what data is involved and how it's handled.
What data Tab Controller handles
During an active, consented remote-control session:
- Screen content of the shared tab — a live screencast of the shared tab is streamed to the paired peer so they can see what they're controlling. This is peer-to-peer via a relay server that only forwards messages between the two paired sessions; the relay does not store, log, or inspect this content.
- Input activity — the controlling peer's clicks, scrolls, and keystrokes are transmitted to the shared tab in order to control it. Same relay-forwarding model as above: passed through in real time, not stored.
Stored locally on your own device only (via chrome.storage.local, never transmitted to us):
- Whether a purchased license key has been activated, and the license's activation instance ID (used only if you later deactivate that license on this device).
Sent to third parties you directly interact with:
- If you activate or deactivate a license key, that key is sent directly from your browser to LemonSqueezy (our payment/licensing provider) to validate it. We do not receive, see, or store your license key, payment details, or any purchase information ourselves — that transaction is entirely between you and LemonSqueezy, governed by LemonSqueezy's own privacy policy.
What we do not do
- We do not collect, log, or store your browsing history.
- We do not collect personally identifiable information, financial/payment information, authentication credentials, personal communications, or location data.
- We do not sell or transfer your data to third parties outside the LemonSqueezy licensing interaction described above.
- We do not use any data for purposes unrelated to providing the remote-control feature itself.
- We do not use any data to determine creditworthiness or for lending purposes.
- Session recording (a paid feature) happens entirely on your own device — recordings are never uploaded anywhere; you choose if and when to save the file locally.
Consent and control
No remote-control session can begin without the tab owner explicitly approving an on-screen consent prompt naming what is about to happen. Chrome's own "this tab is being debugged" indicator remains visible for the duration of any session and cannot be hidden. Either party can end a session at any time.
Data retention
The relay server holds session state (a room code pairing two peers) only in memory, only for the duration of an active session, and discards it immediately when the session ends. Nothing about a session is written to persistent storage on our servers.
Changes to this policy
If this policy changes, the "Last updated" date above will be revised.
Contact
Questions about this policy can be directed to the developer by email at justmakeitforfun@gmail.com.