Local-first heart-rate relay, with clear limits on storage and external requests.

WearStream is a companion app system that can read live heart-rate data from a supported source, show it on the user's devices, relay it to a desktop app on the same local network, and send local VRChat OSC or chatbox output.

WearStream does not require a WearStream account or cloud relay service. The mobile apps do not include advertising or analytics SDKs. WearStream is not a medical app or medical device.

• Live heart-rate readings from the source selected by the user.
• Sensor, stream, battery, and connection status needed to operate and explain the relay.
• Basic local device information, such as a device model or desktop name, used in local heartbeat and connection status messages.
• The local relay URL, network address, and pairing preferences needed to connect the phone and desktop.
• Workout access on Apple Watch so HealthKit can provide live heart-rate samples during a streaming session.

WearStream uses this information to display BPM, maintain the user-started connection, recover from short interruptions, diagnose setup problems, and produce the outputs the user enables.

Heart-rate telemetry is sent only along the user-started relay path between the user's source device, phone, desktop, and enabled local output. WearStream does not upload heart-rate data to a WearStream server, sell it, or share it with advertisers or data brokers.

The normal phone-to-desktop relay uses a local WebSocket on the user's network. Local cleartext connections are intended only for networks the user trusts. Non-local endpoints should use encrypted wss:// connections.

• The Android phone keeps pending telemetry only in memory and does not keep a heart-rate history.
• The iPhone can keep up to 120 pending serialized relay payloads in private app preferences so it can retry a short desktop interruption. Sent payloads are removed from that queue.
• Apple Watch finishes the HealthKit workout session used for live collection. This can create a workout entry in Apple Health, where the user can review or delete it.
• Pairing, appearance, output, and other app settings are stored locally so updates and restarts preserve the user's choices.
• Bounded connection diagnostics may be shown in the apps. Windows can write startup failure details under the user's local WearStream application-data folder.

WearStream has no server-side account or cloud retention system for heart-rate history.

The Windows and macOS desktop apps can check wearstream.app and the public WearStream GitHub Releases API for current desktop version and download information. These update requests do not include heart-rate telemetry.

Public downloads are hosted by GitHub. Visiting the website, opening a release page, or downloading an app is subject to the network and logging practices of the user's browser, network provider, GitHub, and the GitHub Pages service.

• Wear OS requests heart-rate access and, on supported versions, background health access so a user-started stream can continue after the watch screen sleeps.
• Apple Watch requests heart-rate read and workout write access for its HealthKit workout session.
• Phone apps use local-network, paired-device, camera/QR, notification, or foreground/background capabilities only where the selected relay feature requires them.

Users can deny or later revoke platform permissions. Features that depend on a revoked permission will stop working until access is restored.

Users should pair WearStream only on devices and local networks they trust. No software or local network transport can be guaranteed completely secure.

WearStream is not directed to children and is not designed for child-focused use.

WearStream is not intended for diagnosis, treatment, prevention, emergency response, or clinical monitoring. Do not rely on it for medical decisions.

This policy may be updated when app features, platform requirements, or data practices change. The updated date at the top identifies the current version.

Questions or privacy requests: wearstream.support@gmail.com