Privacy

Effective July 15, 2026

Who operates RingView

RingView is an open-source Pebble application operated by Nick Winans. This policy applies to the RingView watch app, its paired-phone companion, and this website.

What RingView accesses

After you choose to connect and authorize access through Oura, RingView requests only Oura’s daily and heartrate permissions. It uses that access solely to retrieve and display your recent readiness, sleep, activity, stress/recovery, and heart-rate summaries on your Pebble. It does not request profile, email, workout, tag, session, location, or other Oura permissions.

Processing and sharing

RingView has no account system or backend. API requests go directly from the paired device to Oura over HTTPS, and responses are processed on that device. RingView does not sell your data or share it with advertisers, data brokers, or other third parties. Only compact scores, durations, downsampled history values, data dates, status, and a last-updated timestamp are sent to your watch. The access token is never sent to the watch.

Storage and retention

The OAuth access token and cached display data remain in PebbleKit JS storage on your paired device. An expired token is not used. Cached values are kept only to provide RingView’s last-known display and are replaced when newer data is retrieved or removed when you use Disconnect and delete. The watch stores the same minimal last-known display values. RingView does not retain Oura data on a server.

Deletion and revocation

PebbleKit JS storage may survive uninstalling and reinstalling a watch app. To revoke RingView’s access and remove its stored token and cached data, open RingView’s settings in the Pebble mobile app and use Disconnect and delete. RingView immediately clears its paired-device storage, asks Oura to revoke the token, and tells the watch to clear its cache on the next connection. Uninstalling the watch app clears its watch-side storage.

Tracking

This site has no analytics, advertising, trackers, cookies, or backend calls. It is not involved in normal RingView authorization. During connection, RingView’s embedded settings view communicates directly with Oura’s authorization service.

Changes

This policy may be updated to reflect changes to RingView. The effective date above will be revised when that happens.

Contact

Questions may be sent to ringview@winans.io.