Room coordination data
The signaling service processes room codes, device names, host or guest roles, connection identities, private resume credentials, track metadata (file name, size, format and duration), playback timelines, and WebRTC connection messages such as SDP and ICE candidates. This information helps devices find one another and coordinate playback. Connection providers may also process IP addresses.
Invitation links and QR codes contain the public room code, never private resume tokens. Resume credentials are kept in live application and server memory, not local browser storage.
Your music takes the direct route
Audio bytes are transferred directly between the host and guests using encrypted WebRTC DataChannels. The signaling service does not carry audio bytes. Your browser decodes complete files into memory; WaveSync does not upload your library to the signaling server or save audio in its offline cache.
The host selects files explicitly. Only selected and optionally next-queued tracks are transferred. File and decoded-memory limits apply. Encryption protects transport, but is not a guarantee against a compromised device or an invited participant retaining received audio.
What this browser remembers
WaveSync uses local storage for your device name, theme, accent, repeat/shuffle preferences, settings, optional last volume, and up to 20 recent track names with ISO-formatted playback timestamps. There is no automatic expiry for these browser preferences. Channel choices are independent per browser.
The service worker caches a versioned application shell for offline opening. Offline access does not make room signaling or transfers work without a network. No application analytics or application tracking-cookie code is included in this source; hosting-provider practices are separate.
Rooms are temporary
Room state is held in server runtime memory. Host recovery credentials are valid for a 30-second disconnect grace period; guest recovery credentials for 120 seconds. These are recovery windows, not guaranteed physical deletion deadlines. Metadata can remain while participants stay connected; runtime restarts can lose the room. Explicit host departure ends the room immediately.
Cleanup scheduling and storage behavior depend on the configured signaling deployment. No durable-room or background-playback guarantee is made.
Network and hosting providers
The configured signaling and WebRTC providers may process connection metadata according to their own policies. This application does not establish their logging or retention periods.
STUN is not a relay service. Restrictive networks, NAT or client-isolated hotspots can prevent direct connections. Browser estimates of connection or audio timing are not measurements of Wi-Fi hardware quality or acoustic synchronization.
Your controls
In Settings → Privacy, reset preferences or clear WaveSync’s locally stored preferences and history after confirmation. These actions do not delete server data or terminate an active room. Leave the room to disconnect. To remove cached app files as well, use your browser’s site-data controls for this origin; those controls may also affect other apps hosted on the same origin.
Browser notifications and event sounds are optional and off by default. Notification permission is requested only through your explicit choice. Browser audio activation and output selection remain subject to browser permissions and capabilities.