Skip to content
playNshare

Privacy

What goes where.

An exact account of the data playNshare handles, written to match how the software actually behaves.

Template — review before launch

This page describes the software’s behaviour. The operator of a public deployment must review it with legal counsel, add their identity and contact details, and adapt it to the laws that apply to them. It has not been reviewed by a lawyer.

Sent peer-to-peer (never to our server)

  • The video stream from the Watch Together creator to the guest.
  • Camera and microphone audio/video, if you turn them on.
  • The contents of files sent with Quick Share.

These travel over encrypted WebRTC connections directly between the two browsers. If a direct connection is not possible, they pass through a TURN relay, which forwards encrypted packets and does not store them.

Handled by our server

  • Signaling: the technical connection descriptions (SDP and ICE candidates) the two browsers exchange to connect. These include network addresses. They are relayed in real time and not stored.
  • Room events: presence, play/pause/seek commands, playback position, buffering status, camera/mic on-off flags.
  • Game actions: every move, dice roll and trivia answer.
  • Quick Share coordination: reservations, transfer progress (byte counts) and completion.

Stored in the database

  • Guest sessions: a SHA-256 hash of the random token, creation and last-seen times. Deleted when expired (30 days of inactivity by default).
  • Rooms: code, type, game type, status, timestamps, an HMAC of the invite key, and each participant’s display name and role. Deleted 24 hours after the room closes or expires.
  • Game sessions: current state and move history. Deleted with the room.
  • Share links: a hash of the link token, file name, size, type, SHA-256 fingerprint, status, expiry and reservation data. Deleted 7 days after the link expires.

We do not store video or file contents, camera or microphone media, or chat (there is no chat).

Server logs

Like any web server, ours processes your IP address and browser user agent to serve requests and apply rate limits. Operational logs record errors and events; tokens, SDP and ICE candidates are redacted. Log retention is set by the operator.

Stored in your browser

  • Your guest token, your last display name, invite keys for rooms you created, and the list of share links you created (local storage).
  • Partially received files during a Quick Share transfer (Origin Private File System), removed when you leave the page or the transfer is finished.

No advertising or third-party analytics scripts are included. Fonts are self-hosted.

Limits of anonymous links

  • Anyone with a room link or share link can use it. Share them only with the intended person.
  • Guest sessions are not verified identities — a display name proves nothing.
  • In a direct peer-to-peer connection, the other person’s browser can learn your IP address. Operators can force TURN-only mode to prevent this.
  • A one-time link cannot stop a recipient from keeping, copying or forwarding a file.

Your choices

  • Leave a room or cancel a share link at any time.
  • Clear this site’s data in your browser to remove your guest token and local history.
  • Camera and microphone are always optional.