Privacy policy

What the app keeps on your phone

• Your bike's pairing. Android keeps the Bluetooth pairing, and the app's association with the bike, so the app can connect when the bike is nearby.
• What it reads from the bike: its charge, ride modes, charge target and schedule, odometer, energy and efficiency, dash gauges and firmware revisions, and the error codes it reports.
• Your rides. A ride holds what the bike sends while you ride: its speed, lean, power, charge and its GPS position throughout, including where the ride started and ended. It also holds the air pressure from your phone's barometer. The app keeps your last ten rides, plus any you pin.
• The bike's event logs, if you download them in Garage. They include the bike's VIN.
• Your settings, such as custom ride modes, drafts not yet written to the bike, and auto capture.

FST ReGen doesn't use your phone's location, and never asks for it. A ride's positions come from the bike's own GPS. The app asks for two permissions: Nearby devices, to connect to the bike, and notifications, for ride capture and charging.

What leaves your phone

• The Google map in Relive. Relive draws a ride over a Google map, using Google's Maps SDK for Android, which loads only when you open Relive. The map tiles it fetches tell Google roughly where the ride was, though the ride's path is drawn on your phone. The SDK also sends Google its own usage data: your IP address, details of the request such as your phone's model and Android version, crashes inside the SDK, a pseudonymous identifier for counting the SDK's users, and how you pan and zoom the map. Google handles all of this under Google's privacy policy, and lists it on its Maps SDK data disclosure page.
• Backups. If your phone's backup is encrypted end to end, which takes a screen lock, Android backs up your rides and some of the app's settings to your Google account. Otherwise the app stays out of the cloud backup entirely. The bike's logs never go into a cloud backup. A direct transfer to a new phone carries your rides, logs and settings across.
• Files you export. You can export a ride or a log through Android's Save dialog, to wherever you choose. An exported ride holds everything recorded, including the bike's position throughout, and so where the ride started and ended, which may be your home. An exported log is named with the bike's VIN. Once a file leaves the app, it's yours to look after.
• This page. The Privacy policy row in the app's About screen opens this page in your browser. The app itself doesn't fetch it.
• Google Play. Installing and updating the app through Google Play is covered by Google's privacy policy. Play gives me statistics about installs, and crash reports from people who've chosen to share usage and diagnostics with Google. They don't tell me who you are.

What I receive

Nothing from the app. FST ReGen has no servers of mine to send anything to. If you email me, I have your email address and what you wrote, and I use them only to reply.

Deleting your data

• Delete a ride from its menu on the Rides tab, an error code from Error codes on the Bike tab, and a log from Logs, in Garage.
• Change bike, in Garage, deletes what the app kept from that bike, apart from your rides and logs.
• Uninstalling the app, or clearing its storage in Android's settings, deletes everything it kept on your phone.
• Your Google account's backup settings control the backup. Google's own tools cover what the Maps SDK sent to Google.

Children

FST ReGen is made for motorcycle owners, and it isn't directed at children.

Changes to this policy

If what the app keeps or sends changes, I'll update this page and the date at the top, and say so in the app's release notes.

Contact

Questions or requests about your data: apps@banasiak.com.