Privacy policy

BikeComputer · last updated 5 November 2026

BikeComputer is a private home project, used only within our household. This page explains what data it handles and what happens to it.

What data we handle

• Ride summaries: start and end time, riding time, distance and average cadence of each ride on the exercise bike.
• Rider details: the rider's name and email address, so we know whose Google account a ride belongs to.
• Google access tokens: after a rider connects their Google account, the token that lets BikeComputer create workouts in that account.

Why we use it

Only to create a workout with the ride summary in the rider's own Google Health account. Nothing else.

What we access in your Google account

• Permission to create exercise data (the workouts).
• Permission to read exercise data, only to check the workouts BikeComputer created.

BikeComputer does not read your other health data, contacts, email or files.

Where it is stored

Rider details and Google tokens are stored on a server in our home. The tokens are stored encrypted. Ride summaries are passed on to Google Health and are not kept by BikeComputer. Rides by a "guest" are not stored or uploaded at all.

Sharing

We do not sell or share any data with third parties, and we do not use it for advertising. The only place ride data goes is the rider's own Google Health account.

Google API Services User Data Policy

BikeComputer's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Removing your data

• Disconnect Google in BikeComputer, or remove its access at myaccount.google.com/connections.
• Ask the administrator to remove your rider details; your Google token is then deleted and revoked as well.
• Workouts already in Google Health stay there until you delete them in the app.