Privacy Policy.

Overview

This Privacy Policy applies to SonicRelay, package name com.vitorhugo.sonicrelay.sonic_relay, published by Vitor Hugo Alves Ferreira. SonicRelay is a mobile viewer for a low-latency personal audio streaming suite. It lets you listen to audio streamed from your own paired Windows publisher app through a SonicRelay backend, WebSocket signaling, and WebRTC media transport.

SonicRelay has no user accounts. There is no sign-up, no email address, no password, and no profile. Identity belongs to the device itself: on first launch the app registers with the backend and receives a device identifier and a secret credential. That is the whole of what identifies you to the service.

The Android app is the viewer. It receives remote audio playback from your paired Windows publisher. It does not record the phone microphone, does not record video, does not access location, does not read contacts, and does not include advertising or analytics SDKs.

Data collected or processed

SonicRelay processes device and connection data only to identify trusted devices, pair them with each other, join private streaming sessions, and operate the real-time connection:

• A backend-issued device identifier, plus a device credential whose secret is stored only on your device. The server keeps a keyed hash of that secret and never the secret itself.
• Short-lived access tokens (minutes) issued against that credential and held in the device's secure storage. There are no long-lived refresh tokens.
• Device registration data: a device name taken from the device model or its user-assigned name, device type, platform, and status.
• Pairing records linking your viewer to your publisher device, and short-lived pairing challenges stored only as a keyed hash of the code.
• Session data: session identifiers, participant identifiers, join and leave events, connection status, and temporary join codes held only as a keyed hash with a short expiry.
• Optional relay (TURN) preferences you configure, including a custom relay address and credentials if you enter them.
• Server infrastructure receives standard technical metadata such as IP address, timestamps, user agent, and request logs.

WebRTC signaling carries SDP descriptions and ICE candidates so the audio connection can be established. These are relayed between your devices in transit, are not stored in the backend database, and are excluded from production logs.

The app may report connection quality readings (packet loss, jitter, round-trip time, selected transport). These are aggregated into operational metrics that carry no device or session identifier, and are not stored per device.

Permissions

• Camera — used only to scan the QR code shown by your Windows publisher when pairing. The camera preview is not recorded, not stored, and not transmitted; only the pairing code read from the QR image is used.
• Internet, network and Wi-Fi state — to reach the backend and to detect when connectivity drops so playback can recover.
• Foreground service and media playback — to keep audio playing while the app is in the background.
• Notifications — to show the playback notification required for background audio.
• Wake lock — to keep the stream alive while the screen is off.

Audio handling

SonicRelay is designed for live audio transport. The Android viewer receives and plays a remote audio track from the Windows publisher. The Android app does not upload microphone audio from the phone. The backend handles device identity, pairing, sessions and signaling only; audio flows peer-to-peer when possible, or through a TURN relay when the network requires it, and never through the backend API.

Live audio streams are not recorded, stored, sold, or used for advertising. If a future version adds recording, analytics, crash reporting, microphone capture, cloud storage, or any new third-party SDK, this policy and the Google Play Data safety form will be updated before that version is released.

How data is used

• Identify the device and maintain a secure session.
• Pair your viewer with your publisher, and let you revoke that pairing.
• Allow the viewer to join a private streaming session by code.
• Route WebSocket signaling messages between authorized participants.
• Establish and maintain the WebRTC audio connection.
• Protect the service against abuse, invalid sessions, and unauthorized access.

Sharing and selling data

The developer does not sell personal or sensitive user data. SonicRelay does not include advertising SDKs and does not share personal data with advertisers or data brokers. Data may be processed by infrastructure providers used to host the backend, WebSocket signaling, TURN relay, DNS, TLS, logging, or deployment systems, only as needed to operate and secure the service.

Security

• Production API traffic uses HTTPS and WebSocket traffic uses WSS.
• The device credential is held in the platform's secure storage, and the server stores only a keyed hash of it.
• Access tokens are short-lived; rotating or revoking a device credential invalidates every token already issued for it.
• Pairing codes and session join codes are temporary and stored only as keyed hashes.
• SDP and ICE candidate payloads are not written to production logs.
• TURN credentials are time-limited.

Retention and deletion

Everything SonicRelay collects is deleted automatically within 90 days of being collected. A background job on the backend runs daily and permanently deletes records once they reach the retention limit. Age is measured from when a record was created, not from when it was last used, so continuing to use the app does not extend how long earlier data is kept.

Deletion is permanent. Records are removed outright rather than flagged as deleted, and no copy is kept in an archive or audit table. In practice the cleanup runs at 82 days, ahead of the 90-day limit, so that a delayed job or a database backup taken shortly before deletion cannot cause data to outlive the limit.

Because a device identifier is itself collected data, it is not kept indefinitely either. A device in regular use is automatically issued a new identifier roughly every 60 days, and the previous one is permanently deleted along with any record of what replaced it. This happens in the background; your pairings and any active session continue to work. A device that stops connecting is deleted outright when it reaches the retention limit, after which it must register and pair again.

Some data is deleted much sooner: pairing challenges and session join codes expire within minutes and are cleared within about a day, and a participant record from a session you have left is removed within about a day.

You can also delete data yourself, at any time. In the app, Settings → Reset device identity removes the credential stored on the device, and Settings → Manage pairings revokes a pairing. Clearing the app storage or uninstalling the app removes local data from the device. For anything else, contact the address below.

Children

SonicRelay is not directed specifically to children. It is intended as a personal audio utility for users who can set up a Windows publisher app and a paired mobile viewer.

Contact

For privacy questions, deletion requests, or Play Store review support, contact:[email protected].

Changes

This policy may be updated when SonicRelay changes how it handles data, permissions, backend infrastructure, third-party services, or platform requirements. The latest version will be published on this page.