Privacy Policy
Last updated: July 26, 2026
This policy describes how the Share applications and optional self-hosted signaling service handle information. It is written for users and for store listings (including Google Play and the Apple App Store). It is not legal advice; if you need formal counsel for your jurisdiction, consult a professional.
1. Who we are
“Share” refers to the Share peer-to-peer file transfer software (web client, Android host, iOS host, desktop hosts) and related marketing materials. Contact for privacy questions: use the email address published on the Support page when available, or open an issue on the project’s GitHub repository.
2. What Share is designed to do
Share helps people in the same room (or on the same local network / phone hotspot) send files directly between devices using WebRTC. A lightweight signaling service only helps devices discover each other and exchange connection setup messages. It is not a cloud drive and is not intended to store your files for later download.
3. Information we process
Depending on how you use Share, the following may be processed:
- Display name — the name you enter so others in a room can see who is online. It is shown to people in the same room and may be held in memory by the signaling host while you are connected.
- Room identifiers — short codes or room IDs you create or join.
- Connection / signaling data — WebSocket or similar messages needed to join a room, list peers, and exchange WebRTC session descriptions and ICE candidates (network path hints so devices can open a peer connection).
- File metadata during a transfer — such as file name, size, and type, shared between the devices participating in that transfer so the other person can accept or decline.
- Local preferences on your device — for example theme (light/dark) or display name, stored in your browser or app storage (e.g. localStorage) on your device.
- Diagnostic logs (optional) — if you enable debug logging, technical events may be shown on your screen and, when a host is configured to receive them, may appear in the host’s server console to help troubleshoot connection issues. Avoid enabling verbose logging if you do not want technical details captured.
4. File contents
Share does not intend to store the contents of your files on a Share server. File bytes are sent over a peer-to-peer data channel between participants. The optional host (including a phone hosting a room or a self-hosted TrueNAS/server instance) is designed to serve the app UI and relay signaling only—not to keep a copy of transferred files for later retrieval.
If a transfer fails partway, incomplete data may exist temporarily in memory on the participating devices until the transfer is cancelled or completed. Completed downloads are saved using your device’s normal download or share mechanisms under your control.
5. Network and third-party infrastructure
- Self-hosted or LAN hosts — If you or someone else runs the signaling server on a private network (e.g. home NAS, phone hotspot host), connection metadata is handled by that host under that operator’s control.
- STUN — To help establish peer connections, clients may contact public STUN servers (for example Google’s public STUN endpoints) to learn network address information. Those providers process technical connection data under their own terms. When a device is offline and only local (host) candidates are used, STUN may not be needed.
- No TURN in the default design — Share does not rely on a TURN relay by default. If a future version adds optional TURN, encrypted traffic could traverse a relay under that configuration; any such change should be disclosed in an updated policy.
- This marketing website — If hosted on GitHub Pages or similar, the host provider may process standard web server logs (IP address, user agent, pages requested) under that provider’s privacy policy.
6. Permissions (mobile apps)
Native apps may request permissions only as needed to host or transfer, for example:
- Network access (to serve/join rooms and transfer files)
- Foreground service / keep-awake while hosting (Android)
- Access to photos or files you explicitly choose to send
- Local network / nearby device related APIs where required by the OS
We do not use these permissions to harvest your photo library in the background.
7. Children
Share is not directed at children under 13 (or the minimum age required in your region). Do not use the service if you are under the applicable age without appropriate guardian consent where required by law.
8. Data retention
Room membership and signaling state are expected to be ephemeral (in memory) for the life of connections and rooms on the host. Local preferences remain on your device until you clear site/app data. Marketing-site logs, if any, follow the host provider’s retention.
9. Your choices
- Do not join rooms or send files you do not want peers to see.
- Leave a room or close the app to disconnect.
- Clear browser/app storage to remove local preferences.
- Self-host if you want full control over the signaling environment.
10. Security
WebRTC data channels use encryption in transit between peers. Signaling on a local network may use cleartext HTTP/WebSocket when designed for LAN/hotspot convenience; treat untrusted networks carefully. No method of transmission is perfectly secure.
11. International users
If you self-host or join a host in another country, signaling metadata may be processed in that location. Peer-to-peer transfer paths depend on the networks of the participants.
12. Changes
We may update this policy as the product evolves. The “Last updated” date will change when we do. Continued use after updates means you accept the revised policy where permitted by law.
13. Store-specific notes
- Google Play — This page is intended to satisfy the requirement for a public privacy policy URL for apps that handle user data as described above.
- Apple App Store — Same policy applies to iOS/iPadOS builds; use the Support page for user assistance links.
- Microsoft Store / desktop — Desktop builds follow the same data practices; file handling uses the OS file picker and downloads folder semantics.