Privacy policy

Effective 2 August 2026. The TabStage extension's presentation workflow is local-first: it has no backend, account system, or remote presentation service.

The gettabstage.com website separately uses Formspree to process Founding 100 applications and, only after analytics consent, Google Analytics to measure website usage. These website services do not receive captured tab or webcam media — see "The Founding 100 application form" and "Analytics and external servers" below.

What TabStage does

TabStage is a Chrome extension that captures one Chrome tab and presents it live inside a styled layout, so you can share a polished view of that tab through screen-sharing tools. It is a live presentation tool. It does not record, export, or store video.

What TabStage accesses

DataPurposeLeaves your device?
The active tab's video stream, via chrome.tabCaptureDisplayed live inside the Studio's presentation stageNo
Webcam video, only if you explicitly enable itDisplayed as an overlay bubble inside the Studio stageNo
Tab title, temporary and in memoryShown in the Studio's top bar while a session is liveNo
Title and subtitle text you type into the StudioRendered on the stage as on-screen textNo
Visual preferences: template, padding, radius, shadow, scale, frame, and webcam position, shape, size, and mirroringRestored the next time you open the StudioNo. Stored only in chrome.storage.local on your device

What TabStage never does

  • Never uploads, transmits, or remotely stores tab video, webcam video, browsing content, page URLs, or the text you enter.
  • Never inspects or reads the content of the source page. TabStage includes no content scripts.
  • Never captures tab audio, system audio, or microphone audio.
  • Never includes analytics SDKs, advertising SDKs, tracking pixels, crash reporters, or any other remote telemetry.
  • Never loads scripts, styles, fonts, or images from a remote server. Every asset is bundled inside the extension package.
  • Never sells or shares your information.
  • Never starts a capture without your explicit action.

Permissions and why they are needed

TabStage requests the smallest Manifest V3 permission set that makes the product work.

PermissionWhy it is required
activeTabGrants temporary access to the tab you clicked the TabStage icon on, tied to that click.
tabCaptureLets the Studio page obtain a live video stream of that tab.
storageStores your visual preferences locally and keeps transient session state so a service worker restart does not lose an active session.

TabStage does not request <all_urls>, broad host permissions, scripting, desktopCapture, downloads, or offscreen.

Analytics and external servers

TabStage the extension contains no analytics SDK, no advertising SDK, and no backend API — it does not send data to any external server. This marketing website (gettabstage.com) uses Google Tag Manager and Google Analytics to understand which pages are visited, but only after you accept analytics in the consent banner shown on your first visit; if you decline, or before you make a choice, no analytics request is sent. Analytics never receives the contents of any form on this site, your name, or your email address — it only records usage information such as page views and button interactions. You can change your choice at any time using "Cookie preferences" in the footer of any page. The one thing on this website that transmits identifying data is the Founding 100 application form, described below.

The Founding 100 application form

Applying for Founding 100 access is a website action, separate from the extension and from your presentation data. When you submit the application form on this site, the information you type into it — your name, contact email, and the other fields on the form — is sent to our configured form service (currently Formspree) so we can review your application and contact you about the beta. That data is used to review your application, communicate about your beta access, and manage Founding 100 participation, and for nothing else. It is not connected to anything the extension itself does: the extension has no knowledge that you applied, and applying does not transmit any captured tab video, webcam video, scene, logo, or background asset.

Data retention

Visual preferences persist in chrome.storage.local until you change them, clear extension data, or uninstall TabStage. Captured tab pixels, webcam frames, and session media are never written to disk or storage. They exist only as live in-memory streams for the duration of a session and are released when the session stops.

Camera access

Webcam access is off by default. Chrome's camera permission prompt appears only after you explicitly enable the webcam toggle in the Studio. If you deny or later revoke camera permission, your tab presentation continues unaffected.

Removing locally stored settings

To clear everything TabStage has stored, open chrome://extensions, find TabStage, and either use the extension's site data controls or remove the extension. Uninstalling TabStage deletes its local storage.

Changes to this policy

If TabStage's data handling changes in a future version, this page and the corresponding Chrome Web Store privacy disclosures will be updated to match.

Contact

Questions about this policy can be sent to privacy@gettabstage.com.

This site uses privacy-conscious analytics to understand how the site is used. No form contents or personal details are ever sent to analytics. Read the privacy policy.