Privacy Policy — Local Share

1. Who we are

This privacy policy describes how Local Share handles information when you use:

• the Local Share web app / PWA at https://share.webinvade.rs (“the Web app”), and
• the Local Share Chrome extension side-panel companion (“the Extension”).

Local Share helps you send links, text, and files between devices in the same Local Share room using WebRTC peer connections, with signaling provided by the Local Share service at share.webinvade.rs.

Both clients are published by WEB INVADERS.

Contact for privacy questions: share@webinvade.rs

For a feature comparison between the Web app and Extension, see Web vs extension comparison.

2. Summary

Applies to both the Web app and Extension:

• No account is required.
• Transfer contents (files, text, links, clipboard content you send) are delivered device-to-device over WebRTC when a peer connection is available. They are not stored by Local Share as a cloud file archive.
• Both clients contact https://share.webinvade.rs for room signaling (join, poll, signal, leave) and may use a public STUN server to help establish peer connections.
• We do not sell your personal information.
• Data is used only to provide Local Share features you choose to use—not for unrelated advertising.

Where settings are stored:

• Web app: in your browser (localStorage, and short-lived IndexedDB for staged shares from the OS Share menu).
• Extension: in Chrome local storage (chrome.storage.local).

3. Information we process

3.1 Shared — signaling metadata (share.webinvade.rs)

To discover peers and set up WebRTC, the Web app and Extension send signaling-related information to https://share.webinvade.rs, which may include room membership and room codes, device display names and local device identifiers used in the room, and WebRTC session/ICE signaling messages.

Peer presence on the signaling service is short-lived (ephemeral). Join requests may be rate-limited by IP to protect the service.

File contents of a peer-to-peer transfer are not intended to be uploaded to the signaling server as cloud storage.

3.2 Shared — data you choose to send

When you explicitly send files, text, links, or clipboard content to another device you select, that content is processed to deliver it to your peer(s). Data is read or accessed only when you initiate the corresponding send action—not continuously in the background.

3.3 Web/PWA — stored on your device

Depending on your settings and usage, the Web app may store in localStorage:

• device display name and local device identifiers,
• trust / auto-accept preferences and decline-guard state,
• UI language preference and in-app UI hints (e.g. tutorial flags),
• peer interaction preferences.

The Web app may also use IndexedDB to hold a short-lived pending share when you send content to Local Share from another app via the OS Share menu (share_target). This staging data is used until you complete or dismiss the send, or until you clear site data.

A service worker may cache the Web app shell (static assets) for offline loading. It does not retain your transfer contents as a cloud library.

This data remains on your device unless you clear site data for share.webinvade.rs or uninstall the PWA.

3.4 Web/PWA — OS Share intake

If you install Local Share as a PWA and share from another app (e.g. Photos, a browser, or a messenger) via Share → Local Share, the Web app receives the title, text, URL, and/or files you chose to share. That content is processed locally to stage a transfer to a peer you select—it is not uploaded to cloud storage as a product feature.

3.5 Chrome extension — stored on your device

Depending on your settings, the Extension may store in Chrome local storage (chrome.storage.local):

• device display name and local device identifiers used in the room,
• room / connection preferences,
• notification and keep-alive preferences,
• trust / auto-accept preferences,
• UI language preference.

This data remains on your computer unless you clear extension storage or uninstall the Extension.

3.6 Chrome extension — browser-integration data

Chrome extension only. When you use Extension-specific features, the Extension may access:

• the active tab URL when you choose “send current tab link”,
• selected text, a link, or page context via right-click context menus,
• clipboard text or images when you choose a clipboard send action,
• a specific image, video, or URL fetched over HTTP(S) when you choose to send it as a file.

A content script on https://share.webinvade.rs runs only when you choose to sync trust settings from an open Local Share Web app tab. It does not monitor all browsing.

3.7 What we do not collect as a product feature

Local Share is not designed to collect payment card numbers, government IDs, or health records, or to build advertising profiles from your general browsing history.

4. How we use information

We use the information above solely to:

• provide Local Share’s purpose: joining rooms and sending/receiving links, text, and files with your peers,
• remember your preferences on your device,
• establish and maintain peer connections (signaling + STUN),
• show optional notifications about transfers you are involved in (Web app when the tab is open/backgrounded; Extension also when keep-alive is enabled).

We do not sell personal information. We do not use Local Share data for unrelated advertising.

5. Third parties and network services

Chrome itself may process data under Google’s policies when you use the browser, notifications, the Chrome Web Store, or Extension APIs.

6. Permissions and capabilities (plain language)

6.1 Web / PWA

The Web app may request or use:

• Notifications — optional alerts when you receive a transfer; typically requires Local Share to remain open in a browser tab (closing the tab ends room presence).
• Clipboard — read when you paste to send; not read continuously.
• File picker and drag-and-drop — when you choose files to send.
• Installable PWA — optional add-to-home-screen; enables OS Share menu intake on supported platforms.
• Service worker — caches app assets and handles staged Share-menu intake locally.

6.2 Chrome extension

The Extension declares Chrome permissions needed for its features, including side panel UI, local storage, optional background WebRTC (offscreen document), notifications, tabs/scripting for send-link and trust-sync, clipboard read on send, and context menus. Host access to share.webinvade.rs is for signaling and the companion web app. Broader http/https host access exists so you can send page media/URLs you select—not to monitor all browsing.

7. Retention

• Web app local settings (localStorage): until you clear site data for share.webinvade.rs or uninstall the PWA.
• Web app pending share (IndexedDB): until you send, dismiss, or clear site data.
• Extension local settings: until you clear them, reset the Extension, or uninstall.
• In-transit transfer data: held only as needed to complete the transfer you started; not retained as a long-term cloud library.
• Signaling metadata: retained by the Local Share service only as long as needed to operate rooms and connectivity (ephemeral peer presence; short TTL).

8. Children’s privacy

Local Share is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children.

9. Your choices

Web / PWA:

• Stop using Local Share by closing the tab or uninstalling the PWA.
• Clear site data for share.webinvade.rs in your browser settings.
• Deny or revoke notification permission; related alerts will not work until allowed.
• Avoid using Share → Local Share if you do not want other apps’ content staged in Local Share.

Chrome extension:

• Disable or uninstall the Extension at any time via chrome://extensions.
• Deny clipboard, notification, or similar OS/browser prompts; related features will not work until allowed.
• Turn off keep-alive or notifications in Extension settings.
• Avoid send-media context-menu actions if you do not want the Extension to fetch a page resource.

10. International processing

Signaling and STUN involve network requests that may be processed on servers outside your country. By using Local Share, you understand that connectivity features require those network calls.

11. Changes to this policy

We may update this privacy policy when the Web app, Extension, or legal requirements change. The Effective date at the top will be revised. Continued use after an update means you accept the revised policy for that version of the product you use.

12. Contact

Privacy questions about Local Share: share@webinvade.rs
Web app: https://share.webinvade.rs
Presentation: https://webinvade.rs/share/
Chrome extension: https://webinvade.rs/share/#chrome-web-store
Publisher: WEB INVADERS
Policy URL: https://webinvade.rs/share/privacy-policy/
Feature comparison: Web vs extension comparison

13. Chrome Web Store User Data Policy (Extension only)

The Chrome extension is intended to comply with the Chrome Web Store User Data Policy, including Limited Use requirements: user data obtained through the Extension is used only to provide or improve user-facing features that are prominent in the Extension’s single purpose.