Effective date: July 24, 2026 · Русская версия
SyncWave is an app for playing music in sync on nearby phones, broadcasting audio or your screen to people nearby, live-streaming to YouTube/Twitch, and sharing your screen with a friend over the internet. It is developed by an independent developer ("we").
SyncWave has no accounts, no analytics, no advertising, and no trackers. We do not collect, store, or sell your personal data. Everything the app needs is kept on your device.
The app saves locally: your display nickname, app settings (language, preferences), the last screen-sharing room code you entered, and — if the app crashes — a technical crash log kept in the app's private storage. None of this leaves your device unless you copy and send it yourself.
Microphone (RECORD_AUDIO) — used only while you run a live stream or a broadcast, to capture your voice and (on Android 10+) the audio of apps you play. Audio is never recorded to files or sent anywhere except the stream/broadcast you started.
Screen capture (MediaProjection) — used only after you explicitly confirm the system screen-capture dialog, to broadcast your screen to nearby listeners, to a streaming service you chose, or to a friend viewing your screen. Capture stops when you stop the session, and nothing is stored.
Bluetooth, Wi-Fi and Location (Nearby) — SyncWave uses Google Nearby Connections to find and link phones in the same room. Android requires Bluetooth-scan and location permissions for this discovery to work. Your geographic location is never read for its own sake, never stored, and never transmitted.
Internet — used for live streaming (RTMP to the ingest server of YouTube/Twitch or another service you configure) and for screen sharing over the internet (WebRTC).
Notifications — used to show the ongoing-session notification Android requires for broadcasting and screen sharing.
To connect you with a friend, the app exchanges short technical connection messages (a 6-digit room code and WebRTC session data, which includes your device's network addresses) through our signaling server. Video and audio go peer-to-peer whenever possible; if a direct connection is impossible, media is relayed through our TURN server. All media is encrypted end-to-end by WebRTC (DTLS-SRTP), including when relayed — the relay cannot read it.
The signaling server keeps no database. Rooms exist only in memory and are discarded as soon as everyone leaves. Room codes and participants' addresses are not written to its logs, and the TURN server's session logging is disabled. We do not keep records of who connected to whom, or when.
One caveat we would rather state plainly: unless the server is deployed with a TLS domain, the signaling exchange itself travels over an unencrypted WebSocket connection. Media stays encrypted regardless, but the connection-setup messages could in principle be observed on the network path. Media relaying uses a temporary credential issued per session and valid for one hour.
Your stream key and stream settings are stored only on your device. Video and audio are sent directly to the streaming service you configured (e.g. YouTube or Twitch); their processing of the stream is governed by their own privacy policies.
The app uses Google Play services (Nearby Connections) on your device. For establishing internet screen sharing it may contact a public Google STUN server (stun.l.google.com) to discover your device's public address — a standard step in WebRTC connection setup. We do not share any data with third parties, because we do not collect any.
SyncWave is not directed at children and collects no data from anyone, including children.
If this policy changes, the updated version will be published at this address. Questions: open an issue at github.com/Komsomol39/syncwave-releases.