Privacy Policy

No account, no sign-in

Loam Moto has no user account. You do not log in, and we do not require your name or email to use the app.

Data stored on your device

The app stores the following locally. This data stays on your device unless you choose an action described below.

• Garage data, including bikes, components, service history, reminders, and settings.
• Ride data, including distance, time, ride metadata, and GPS tracks saved as GPX files.
• Gear, Kit Bag, Closet, Workshop, Adventure, and packing data.
• Optional saved locations, such as a privacy-zone centre and parked-bike position.
• An optional emergency contact used by the manual SOS helper.

Location

• When you start a ride, Loam Moto collects precise location to record the route and calculate distance, speed, and riding time. Recording continues in the background when the screen is off or the app is closed or not in use, until you stop the ride.
• The production version does not automatically start rides or monitor a saved geofence while idle.
• One-time location fixes are used when you explicitly save a privacy-zone centre or parked-bike position, or use the find-my-motorcycle feature.
• GPS tracks are stored on your device and are not included in cloud backup.
• If you trigger manual SOS, the app opens your device’s messaging and phone apps with your emergency contact and a message that can include your current location. You decide whether to send the message or place the call. Loam does not receive this data and does not provide emergency dispatch.
• When you explicitly display a route or parked position on a map, the app requests tiles from OpenStreetMap or OpenTopoMap. The provider receives the requested tile coordinates, IP address, and standard network information needed to return the map.

Optional encrypted cloud backup

If you enable backup, the app encrypts a snapshot on your device using AES-GCM before upload. It can include garage, gear, closet, workshop, and ride metadata. It excludes GPX tracks, local photo paths, maximum ride speed, and harsh-event counts.

Our server receives only an opaque backup identifier, an authentication hash, encrypted ciphertext, and operational metadata such as revision and update time. We cannot read the encrypted contents. The recovery code is the only key; keep it safe because we cannot recover it for you. Up to five earlier encrypted snapshots may be retained for restore. Backups with no update for 365 days are deleted automatically.

To request earlier deletion, contact support@loamlog.com. We will explain how to provide the backup identifier without sending the secret part of your recovery code.

Reminders and push notifications

If service or charge reminders are enabled, the app sends a Firebase Cloud Messaging token, device time zone, and a generic reminder schedule to our backend. The schedule contains dates or times, random local item identifiers, and localized generic text; it does not contain bike make, model, GPS tracks, or ride locations.

Turning reminders off uploads an empty schedule. Push records expire after 60 days without re-registration. Delivery uses Google Firebase Cloud Messaging, which also processes a per-installation Firebase identifier, app version, and basic operating-system and device metadata needed to provide and maintain the messaging service.

Feedback and support

If you submit the in-app feedback form, the app sends the feedback type and message, optional reply email, app version, and operating-system name and version. Our backend forwards this to a private Discord support channel. We use it only to respond, diagnose problems, and improve the app. Feedback is kept only as long as reasonably needed for those purposes, and you may request its deletion by email.

Bike photo, specification, catalog, and shop requests

When you request a bike photo or stock-part lookup, the app sends the bike make, model, and year to our backend. The backend may query image-search or specification providers and returns results to the app. Catalog and curated shop lists are also fetched from our backend. These requests do not include ride tracks or your Loam data, although normal network information such as an IP address is processed to deliver and rate-limit requests.

Purchases and activation

Google Play or Apple processes the one-time unlock and provides the app with purchase and entitlement status. We do not receive payment-card or billing details. Custom activation codes are disabled on iOS and cannot grant access. On Android only, offline activation codes are verified on the device and are not sent to our server.

Watches and sharing

If you use a paired Wear OS, Apple Watch, or Garmin device, ride commands and live status pass through the applicable platform’s device-to-device services. They are not sent through the Loam backend.

Ride export, GPX sharing, affiliate or shop links, and manual SOS are initiated by you and use the destination app, browser, or share sheet you select. Those destinations handle data under their own privacy terms.

What we do not do

• No advertising SDKs or advertising identifiers.
• No analytics or cross-app tracking SDKs.
• No sale of personal data.
• No use of personal data for advertising or data-broker purposes.

Data retention and deletion

• On-device app data is removed when you uninstall Loam Moto. Android system backup is disabled for the app.
• Encrypted cloud backups are deleted after 365 days without an update, or earlier on a verified request.
• Push records expire after 60 days without re-registration.
• You may request deletion of support feedback by contacting us.

Children

Loam Moto is not directed to children. It is intended for licensed riders and people riding under appropriate legal supervision.

Service providers and international processing

Depending on the optional features you use, data may be processed by Cloudflare, Google Firebase Cloud Messaging, Discord, OpenStreetMap, OpenTopoMap, image or specification providers, Google Play, Apple, Garmin, and the paired-device platform. Processing may occur outside your country. We use these providers only to deliver the features described above.

Accessibility

Loam Moto aims to be usable by everyone and follows the accessibility guidance of the platforms it runs on. If you encounter an accessibility barrier, email support@loamlog.com and we will do our best to help or provide the information another way.

Data controller

Loam Moto is developed and operated by Yev Gavrikov, an individual developer based in Israel, who acts as data controller. Depending on where you live, you may have rights to access, correct, delete, or restrict processing, object to processing, or complain to a data-protection authority. Because the app has no account and encrypted backups are unreadable to us, we may need limited information to locate a support message or opaque backup record. Contact: support@loamlog.com.

Changes to this policy

We may update this policy. Material changes will be reflected by the effective date above and, where appropriate, noted in the app.

Contact

Questions, privacy requests, or deletion requests: support@loamlog.com (Loam).