Privacy policy

Your data in WearStream.

Last updated: November 1, 2026

Overview

What WearStream does

WearStream reads live heart rate from your watch and relays it through your phone to a desktop app on your local network. You can display it in VRChat through chatbox or avatar OSC output.

This policy covers WearStream's phone, watch, and desktop apps and this website. Apple-specific sections describe the iPhone and Apple Watch apps currently in development.

You do not need a WearStream account, and the relay does not use a WearStream cloud server. The mobile apps contain no advertising or analytics SDKs. WearStream is not a medical app or medical device.

Data

Data the apps access

  • Live heart-rate readings and their timestamps from your selected source.
  • Sensor, stream, battery, and connection status needed to operate and explain the relay.
  • Basic device information, such as a device model or desktop name, used in connection messages.
  • Random app-installation identifiers used to distinguish Android sources and sample-data modes. These are not hardware or account identifiers.
  • 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.

The apps use this information to display heart rate in beats per minute (BPM), keep your relay connected, retry after interruptions, show connection problems, and send the outputs you enable.

Relay

Where heart-rate data goes

When you start streaming, WearStream sends readings between your watch, phone, desktop, and the outputs you enable. WearStream does not upload heart-rate data to its own server, sell it, or share it with advertisers or data brokers.

Local-first does not mean exclusively local. On Wear OS, readings and connection metadata travel between your watch and Android phone using Google Play services' Wearable Data Layer. It uses Bluetooth when available. When Bluetooth is unavailable, Google Play services may relay this data through Google's servers over Wi-Fi or mobile data. Google describes this cloud transfer as end-to-end encrypted. WearStream does not control that route or provide a mode that blocks cloud fallback. See Google's Data Layer documentation and Google's privacy policy for information about the platform service.

If you enable VRChat output, your heart rate can be visible to other players through your chatbox or avatar. Data sent to VRChat is also subject to VRChat's privacy policy. You can disable chatbox and avatar output in WearStream and keep readings on your desktop.

The usual phone-to-desktop connection uses an unencrypted local WebSocket (ws://) without a login. Use it only with devices and local networks you trust. Release builds restrict these connections to local addresses; non-local addresses require encrypted wss://.

Storage

What stays on your devices

  • The Android apps do not keep a heart-rate history. The phone holds readings waiting to be sent only in memory.
  • The iPhone app can save up to 120 unsent relay messages in private app preferences for retries. These messages can include heart-rate readings and remain across app restarts until sent or removed with the app's data. When the queue fills, older messages are dropped.
  • Apple Watch uses a HealthKit workout session to read live heart rate. Ending the session can create a workout entry in Apple Health, which you can review or delete there.
  • Pairing, appearance, output, and other settings are stored on your devices. Desktop settings can also have a local recovery backup.
  • New Android source identifiers are stored privately outside Android backups. Updates retain them; clearing app storage removes them.
  • The apps show recent connection diagnostics. Windows can also write startup and connection logs in its WearStream application-data folder. Current builds limit these to two files of 256 KiB each and leave heart-rate values out of sample-validation messages. Older builds may have larger logs. Diagnostic files may contain local addresses, device names, or file paths.

WearStream has no server-side heart-rate history. Device backups and Apple Health syncing are separate from the live relay: depending on your device and account settings, they may copy app data or Health records to your backup or cloud provider.

Your choices

How to stop sharing and remove data

  • Stop watch streaming and the phone or desktop relay to end the live connection. You can turn off VRChat outputs separately.
  • On Android and Wear OS, clear WearStream's app storage in device settings to remove saved app preferences. You will need to pair and configure the apps again.
  • On iPhone, delete the app to remove its saved preferences and retry queue. Offloading the app keeps its data.
  • For desktop data, quit WearStream and remove its settings folder: %LOCALAPPDATA%\WearStream on Windows or ~/Library/Application Support/WearStream on macOS. This removes saved preferences and their recovery copies; the Windows folder also contains diagnostic logs. Uninstalling the desktop app alone may leave these files behind.
  • Delete Apple Health workout records in Apple Health. Removing WearStream does not remove those records. Manage device backups and synced copies through your platform or backup provider.

You can revoke permissions in device settings. This stops features that need those permissions, but does not delete data already stored. For support or testing emails, use the contact address below to request deletion.

Internet access

Downloads and desktop update checks

The Windows and macOS apps can request version and download information from wearstream.app and the public WearStream GitHub Releases API. These requests do not include heart-rate readings.

Public downloads are hosted on GitHub. Downloading an app or checking for updates sends ordinary web-request information, such as your IP address, to the hosting service. See GitHub's privacy statement for its data practices.

Website privacy

Website hosting

This website, wearstream.app, is hosted on GitHub Pages. When you visit, GitHub logs and stores your IP address for security purposes, whether or not you are signed in to GitHub.

See GitHub's Pages data-collection notice and GitHub's privacy statement for details about its data handling.

The WearStream website does not add analytics, advertising trackers, or cookies. Its example BPM display uses simulated numbers in your browser. Visiting the website does not send heart-rate readings from your apps.

Permissions

Why permissions are requested

  • 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.
  • The Android phone relay uses a connected-device foreground service and a network-state permission for its user-started desktop connection. This does not grant access to the phone's health sensors or change your network settings.
  • Apple Watch requests heart-rate read and workout write access for its HealthKit workout session.
  • Phone apps use local-network and paired-device access to connect your devices. Camera access is used to scan pairing QR codes. Notification and foreground/background capabilities keep a session running and show its status where the platform requires them.

You can deny or revoke permissions in device settings. Features that need that access will stop until you restore it.

Safety

Safe use

Pair only with devices you trust, keep your firewall enabled, and use a trusted local network. The local relay does not guarantee protection from other devices on that network.

WearStream is not directed to children.

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

Contact

Support and testing emails

If you email WearStream, we receive your email address, message, and any attachments you send. We use them to answer your request, troubleshoot a problem, or arrange testing access. Please leave out health readings, passwords, and unrelated personal information.

Support and testing correspondence is held in our Gmail mailbox until deleted. Gmail is provided by Google under Google's privacy policy. If you join the Android test, Google Play also manages your test enrollment through your Google account.

For privacy questions, to request deletion of correspondence, or to ask us to remove your testing contact details, email wearstream.support@gmail.com.

Updates

Policy changes

We update this policy when features, platform requirements, or data practices change. The date at the top shows when it was last revised.