Privacy Policy

This policy explains how Screen Share (the “Extension”, “we”, “us”, or “our”) handles information when you use the Chrome extension, our website, or a live viewer page. It applies to this policy page at https://screen-share.uk/privacy.

[01]What Screen Share does

Screen Share lets a presenter choose a browser tab, application window, or display and send its live video to people who receive a viewer link or join code. Viewers open the link or enter the code in a browser; they cannot control the presenter’s computer. The Extension captures video only. It does not capture microphone, camera, tab audio, or system audio.

The viewer link and five-character join code are access credentials, not identity checks. Anyone who knows either can join while the share is active, without a viewer account or individual approval from the presenter. Send them only to intended viewers.

[02]Information we handle

We handle the following information to provide and protect the service:

Live screen video. When a presenter starts a share, the selected source’s visible video and cursor are transmitted in real time to authorized viewers. This can include personal, confidential, or sensitive information shown on that source. Do not select or show information you do not intend to share.
Account and session data. The Extension creates an account without requiring your name or email and stores an authentication session identifier. These identifiers let us associate shares with the same account; they do not make your use completely anonymous. Our service stores account and share identifiers, join codes, cryptographic hashes of access secrets, media-room names, recording settings, share status, timestamps, host connection activity, and expiry data.
Invites and phone numbers. A presenter can copy a viewer link or short join code, or open WhatsApp with a prepared invite. Recipient phone numbers entered for WhatsApp are handled in the Extension and passed to WhatsApp; they are not sent to our backend.
Optional Google profile data. If we make Google sign-in available and you choose to use it, we may receive your Google account identifier, email address, name, and profile picture to link your account. Google sign-in is not required to start a share.
Recordings and feedback. When server-side recording is enabled, the selected screen video is also saved as described below. If you choose to submit a review, support request, or feedback form, we and the relevant provider receive the information you submit. Avoid including private screen content, access credentials, or sensitive personal information in feedback.
Technical and security data. Our servers and service providers may process IP address, browser/device details, request timestamps, error details, and similar operational logs to operate, secure, and troubleshoot the service.

[03]How we use information

Set up, deliver, maintain, and end a live share.
Provide and manage server-side recordings when enabled.
Review feedback you choose to submit.
Confirm that a presenter or viewer is authorized for a share.
Prevent abuse, investigate reliability and security issues, and improve the service.
Respond to a support, legal, or safety obligation where applicable.

We do not sell, rent, or trade personal information. We do not use screen content, viewer links, or browsing activity for advertising, behavioral profiling, or cross-site tracking.

[04]Chrome extension permissions

The Extension requests only the permissions required to start and maintain a share. It has no content scripts and does not read or alter the pages you visit outside a source you actively choose to share.

Permission	Why it is needed	What it does not do
`activeTab`	Lets the Extension use the current tab after you click its toolbar action, so you can choose that tab as the source.	It is temporary and does not grant persistent access to every tab.
`tabCapture`	Captures video of the current browser tab after you start a share.	It does not capture microphone, camera, or tab audio.
`desktopCapture`	Opens Chrome’s built-in picker so you can select a browser tab, application window, or display.	Chrome shows the available sources and you decide what, if anything, to share.
`idle`	Detects three minutes of computer inactivity or locking so the Extension can ask whether to continue sharing and stop if you do not respond.	It receives only the computer’s active, idle, or locked state—not keystrokes or mouse movements. This state stays in the Extension and is not sent to our servers.
`alarms`	Schedules inactivity checks, the session-limit warning, and automatic stopping, including after the background process restarts.	It schedules timers; it does not read page content or record your activity.
`offscreen`	Keeps the active video hand-off running while a share is in progress.	It is used only for the live-sharing workflow, not for background monitoring.
`storage`	Stores share and presenter-window state, recovery deadlines, and whether a share has succeeded so the Extension can show a rating prompt.	It does not sync screen recordings or browsing history to the Extension.

The Extension also has narrow host access to the Screen Share API and live-media server. It does not request access to all websites.

The Extension does not request permissions for browsing history, cookies, camera, microphone, contacts, downloads, clipboard, or the ability to change web-page content. Choosing Copy link writes the viewer link to your clipboard using the browser’s clipboard API; the Extension does not read your clipboard.

[05]Local browser storage

The Extension keeps an authentication session identifier in its own local browser storage. It also stores a persistent flag indicating that a share has succeeded, used to show a rating prompt. These values remain until the Extension’s local data is cleared or the Extension is removed.

Browser session storage holds share credentials, the join code, selected-source identifiers, status, and inactivity and shutdown deadlines. Presenter-window state can include the selected tab’s title and identifier and window position and size. This supports source selection, window restoration, and recovery after the background process restarts. The last share state, including ended or failed status, can remain after sharing stops until it is replaced, cleared, or the browser session ends. It is not automatically deleted on stop.

The selected tab’s title and window layout stay in the Extension; the captured video may still show a title or other information visible in the chosen source. Opening a viewer link can leave the link and code in your browser history. Copying it leaves it on your clipboard until replaced or cleared. Chrome’s extension and site-data controls let you clear local data, but doing so does not delete server records, recordings, or messages already sent.

[06]Live media, recording, and retention

Live video is delivered through LiveKit. The media service processes the selected screen video and connection information to deliver it to viewers. Screen video is not stored in our application database.

Server-side recording is disabled by default but can be enabled by the service operator for a deployment. When enabled, LiveKit automatically records the selected screen video and uploads it to the operator’s configured recording storage. This is a service-wide setting, not a per-share recording choice in the Extension. The current sharing flow does not ask for separate recording confirmation before capture starts. The operator can access stored recordings.

A share has a 30-minute limit measured from session creation, with a warning during the last minute. Activity, choosing Continue sharing, switching sources, or restarting the Extension’s background process does not extend that deadline. After three minutes of computer inactivity or locking, the Extension asks whether to continue and schedules stopping one minute later unless you choose Continue sharing. Capture remains live during that prompt. Sharing can also end earlier when you stop it, the source closes, or the presenter loses connection.

Ending a share stops further live capture and ends the media room and any active recording; it does not delete video already recorded. Shutdown or provider failures can delay cleanup. The application does not automatically expire or delete recording files. They remain in the configured storage until the operator deletes them or a separately configured storage retention rule removes them. Recording notifications sent to Telegram are not automatically deleted by Screen Share either.

Ended or failed live-share database records become eligible for automatic deletion 24 hours after the session ends. Periodic cleanup may be delayed by outages or errors. This cleanup does not delete recordings, Telegram messages, accounts, or authentication sessions. Account and authentication records have no automatic expiry in the application. Operational logs and submitted feedback are retained separately by us and the relevant providers for service, support, security, and applicable legal needs.

[07]Service providers and disclosures

We disclose information only as needed to operate Screen Share:

LiveKit or our configured media provider processes live media, connection details, and any enabled recording to deliver the share.
Recording storage providers, including Bunny.net when configured, receive recorded screen video and storage metadata. The recording workflow uses Bunny.net dashboard links for operator access to the recording folder.
Telegram, when notifications are configured, receives a recording notification containing a Bunny.net dashboard link with the storage-zone identifier and session-specific folder path. The notification goes to the operator’s configured chat; this workflow sends a link, not the video file itself.
Google processes optional sign-in under Google’s privacy terms if you choose that sign-in method. If you leave a Chrome Web Store review, Google processes the review and the profile information displayed with it under its own terms.
WhatsApp receives the recipient phone number and prepared invite when a presenter opens WhatsApp to share it. The presenter reviews and sends the message there.
Sentry receives server error, log, and performance information when monitoring is enabled in production. The current configuration enables collection of personal information by the monitoring SDK, so diagnostic events may include IP addresses, request URLs, request data, browser details, and other request context—not only anonymous error counts.
Feedback-form providers process information you submit through linked feedback forms or the form embedded on the uninstall page, when configured. Loading an embedded form connects your browser to its provider even if you do not submit it; that provider may receive your IP address and browser details and use its own cookies or storage under its privacy policy.
We may disclose information when required by law, to protect rights and safety, or as part of a lawful business transfer.

These providers process information under their own terms and privacy practices.

[08]Security and your choices

We use reasonable technical measures to protect access to Screen Share. In a public deployment, the website, API, and media service should use secure encrypted connections. No method of transmission or storage is completely secure, so please do not share highly sensitive information unless you understand and accept the risk.

You control when sharing starts, which source is selected, and when it stops. Stopping a share is intended to close the live media room and prevent further viewing through that session; follow any shutdown error shown by the Extension if stopping cannot be confirmed. Stopping does not erase existing recordings, invitations, or copies made by viewers. Viewers may independently take screenshots or recordings, which Screen Share cannot prevent or delete.

You can remove the Extension or clear its data using Chrome’s controls. For access, deletion, or other privacy requests, use the support email in our Chrome Web Store listing. Include relevant dates and session details if available, but do not send authentication tokens or passwords. Clearing local data or uninstalling does not send us a server-side deletion request. Requests involving recordings, provider-held data, or notification messages require separate review and cleanup.

[09]Children’s privacy

Screen Share is not directed to children under 13. We do not knowingly collect personal information from children. If you believe a child has provided personal information to us, contact us through the support email in the Chrome Web Store listing so we can review and take appropriate action.

[10]Changes and contact

We may update this policy when our service, data practices, or legal obligations change. We will post the updated policy at the address above and revise the “Last updated” date.

Questions, concerns, and privacy requests can be sent to the support email listed in the Screen Share Chrome Web Store listing.

Last updated: September 11, 2026