Privacy policy

Last updated: November 2, 2026

Recording a ride does not require a ScooterLog account. Your ride history is stored on your devices. Private iCloud sync and heart-rate access are optional.

This policy covers the ScooterLog iPhone and Apple Watch apps and this support website. ScooterLog is maintained by jamierytlewski. For privacy questions or requests, email privacy@j4m13.dev.

Location and ride history

With your permission, ScooterLog uses precise location to record a ride you start. It stores accepted GPS coordinates, timestamps, accuracy and speed readings, a ride identifier, the recording device type, and ride timing and distance. Recording can continue in the background until you end the ride or recording is interrupted. When you open the app again, a previously requested recording may resume if permission is still available.

Route planning can request a foreground location fix before you start a ride. Previewing a route does not itself save a recorded ride. Saved places contain the names you choose and their coordinates.

Rides and saved places are stored in the app's local storage. ScooterLog uses Apple's WatchConnectivity service to exchange live ride status, current guidance, completed rides, saved places, and deletion information between your paired phone and watch. Live Activities show selected ride metrics on system surfaces such as the Lock Screen and Smart Stack. Consider those surfaces when choosing your device's privacy settings.

The app does not send your ride history to a developer-operated server. It does not use advertising, third-party analytics, or cross-app tracking, and does not sell your information.

Optional heart rate

Heart-rate access is off until you choose to enable it and authorize HealthKit access. The app can show a recent readable heart-rate sample and its measurement time. This does not guarantee continuous or current readings.

On Apple Watch, a separately confirmed live-heart-rate option starts an Other workout session to obtain sensor readings. ScooterLog ends that session and discards its workout builder without saving a completed workout. watchOS may nevertheless retain Health samples or affect activity rings. Ending GPS recording also ends this optional session.

ScooterLog does not include heart-rate readings in ride files, companion transfers, iCloud uploads, or JSON/GPX exports. It does not send Health data to the developer or use it for advertising. You can turn the display off in the app and manage or revoke Health permissions in Apple's Health or Settings apps. Health information already retained by watchOS is managed separately there. ScooterLog is not a medical, diagnostic, or emergency-monitoring service.

Apple Maps and directions

Maps, place search, route calculation, and rerouting use Apple's MapKit services. Place search sends the text you type, including partial text for suggestions, and, when available, a search area near your last known location to Apple. Directions send the selected origin, destination, and routing mode. Rerouting can send an updated origin based on your current location. Displaying maps also involves requests to Apple.

These requests are necessary to provide the features you use and are handled under Apple's Maps privacy information and Apple's privacy policy. They do not upload your entire saved ride archive to the developer. Walking and cycling routes are not a guarantee of scooter access, legality, or safety.

Optional private iCloud sync

On iPhone, you can enable Sync rides and saved places and tap Sync now. This uploads completed ride files, including their recorded locations and timing, and saved-place names, coordinates, and place-deletion information to your private CloudKit database in your Apple iCloud account. It also downloads your saved cloud records. Active rides and Health data are excluded. The watch syncs with the phone rather than directly with CloudKit.

This is manual sync, not a continuous background backup. The developer does not have access to your private CloudKit records through the app's normal developer tools. Apple operates iCloud under its own terms and privacy policy. Do not interpret private storage as a promise of end-to-end encryption.

Turning sync off stops future sync operations; an operation already submitted may finish. Turning sync off does not delete records already in iCloud.

Sharing, retention, and deletion

Exporting rides

History > Download all activities prepares completed rides as JSON and GPX files and opens the system share sheet. These files contain sensitive route coordinates and times, but not heart-rate data. Only share them with people and services you trust. Copies you save or send are controlled by you and the receiving service; deleting a ride in ScooterLog does not erase exported copies.

Local data and permissions

The app retains local rides and saved places until you delete them or remove the app's data. Delete a ride from History; the app asks the paired device to delete its copy and, when iCloud sync is enabled, removes the cloud ride on a subsequent sync. A small ride-deletion marker remains locally to prevent accidental reimport from the companion. Saved-place deletion information may also be retained and synced to prevent deleted places reappearing.

You can revoke location access in device Settings. This prevents authorized location recording but does not erase existing history. Removing the app from each device removes its local app storage; deleting only the phone app may leave a watch copy. Device and iCloud backups are managed separately by Apple and your backup settings.

Cloud deletion

Delete private iCloud data removes this app's ride and saved-place records from your private CloudKit database and turns app sync off after success. It does not erase local or watch copies. Re-enabling sync can upload those copies again. Remove unwanted local copies as well.

Ride-deletion markers are not synced through iCloud. A different iPhone with a remaining local copy can upload that ride again. Delete it on each device that holds it. To remove all copies under your control, delete cloud data first, remove local copies on each device, and separately manage exports and backups.

Support requests and this website

If you email support, the developer receives your email address and the message or attachments you choose to send, processed through email providers. The public contact address forwards messages to the maintainer; replies may come from a different email address. This information is used to respond, troubleshoot, and handle privacy requests, not for advertising. Correspondence is kept as needed to resolve the request and meet applicable legal obligations. Ask for deletion by emailing privacy@j4m13.dev; records that must legally be retained may be excluded. Do not send passwords, Health records, or unredacted home/work routes.

GitHub issues and pull requests are public. Avoid posting personal information there. This website is hosted on GitHub Pages; GitHub may process technical request information such as IP addresses for hosting and security under the GitHub privacy statement. This site adds no analytics scripts, advertising, cookies, or contact forms.

Apple may provide diagnostics and beta feedback according to your Apple sharing settings and TestFlight's terms. If you send feedback or reports to the developer, include only what is needed and redact personal details. TestFlight is a separate Apple service.

Your requests and policy changes

Depending on your jurisdiction, you may have rights to access, correct, or delete personal information handled by the developer, and other privacy rights. Contact the address below to make a request. The developer cannot directly retrieve or erase records that exist only on your devices or in your private iCloud database; use the controls described above for those copies.

This policy will be updated if the app's practices change. The date at the top identifies the latest revision. Review the policy again when enabling new features.

Privacy and support contact: privacy@j4m13.dev