Tangeparty
Privacy policy
Last updated:
This policy explains how Tangeparty handles data in the extension, room service and this page. For privacy questions or requests, contact fran.josealiaga@gmail.com.
What is used and shared
The extension reads supported streaming-page addresses and player state to identify the episode and synchronize playback. Network sharing for a room starts when you create or join it.
- Room service: Cloudflare hosts the signaling service. It processes room codes, random participant IDs, membership, the host's episode identifier, and WebRTC connection-setup messages. Connection setup can contain IP addresses and other network information.
- Other participants: room members receive episode IDs, playback positions, play/pause state, speed and synchronization timestamps over WebRTC. Other participants may learn your public IP address through connection setup. Anyone with the room code can attempt to join; share it only with people you trust.
- Connectivity: Cloudflare STUN helps establish connections. When TURN relay is enabled and needed, Cloudflare relays encrypted WebRTC synchronization traffic. These services process IP addresses and network metadata. Tangeparty does not send the episode's video or audio through the room service or relay.
Production signaling uses encrypted WebSockets, and WebRTC synchronization traffic is encrypted. Data is used to provide rooms, synchronize playback, follow episode changes and prevent abuse. Tangeparty does not sell user data, use advertising or analytics trackers, or build browsing profiles. It does not collect streaming passwords, login cookies, payment details, microphone or camera data. Streaming websites handle your account and media under their own policies.
Storage and retention
- Active rooms: participant and host-episode state is held for the active room. Participant state is cleared when that participant is removed; the host leaving closes the room and clears its membership. The application does not keep a watch-history database or archive synchronization messages.
- Public status: the status page shows aggregate active-room and connected-tab counts. Internally, reporting stores opaque room-object IDs, counts and update revisions; it stores no participant IDs, episode IDs or playback events. Closed entries are removed after a short delay on the next status check. Stale counts are verified against live rooms when the dashboard is checked, with background checks completing any backlog. Closed rooms clear their local reporting revision after a five-minute grace period; reopening cancels that cleanup. This is operational reporting, not a watch-history or individual-visitor analytics database.
- Abuse prevention: when TURN is enabled, the service hashes your IP address and stores a per-network admission counter. These hashes are pseudonymous, not anonymous. Counters cover one-minute windows; stale network entries are removed on the next admission request. Daily totals contain counts and reset on the next admission after the UTC day changes. This cleanup runs on requests, not an automatic deletion timer.
- Your browser: a local episode-navigation ticket contains the room code, episode ID, automatic-follow choice and expiry. It is valid for 60 seconds and removed when consumed or when its tab closes. Unused tickets can remain in extension storage until removed or the extension is uninstalled. Other active room and playback state is kept in memory.
- Diagnostics and contact: browser diagnostic output stays local unless you choose to share it. If you email a question or report, your address and message are used to respond and retained as needed to resolve it. Do not send account credentials or unredacted private logs.
Cloudflare processing
Cloudflare also processes request and connection metadata, including IP addresses and request times, to deliver and secure the service and this page. Its infrastructure may process data outside your country and retain operational or security records under its applicable service policies. See Cloudflare's privacy policy.
Your choices and requests
Leave the room to stop participating, disable automatic episode following in the popup, or uninstall Tangeparty to remove its local extension storage. You can request access, correction or deletion of data I hold, or raise privacy concerns, by emailing fran.josealiaga@gmail.com. Additional rights depend on applicable law. I cannot remove information already received or independently saved by another participant.