Privacy Policy

Your data, plainly

MotoSetGo has no user accounts. You never give us your name, email or a password, and you never sign in. Here's exactly what we do store, and why.

Effective 24 October 2026 Provider MotoSetGo LLC Contact admin@motosetgo.com

The short version

We can't identify you as a person, because we never asked who you are. The app stores the things you enter — your bikes, their suspension settings, your rider profile and your tuning history — on our servers so it can work. It also records how well its own advice performed, and a short summary of each Ride Lab report, so the advice and the analysis get better over time.

We also measure which install campaigns bring riders who use the app (§2d). We do not sell or rent your data, and we do not show ads.

1. No account, and what we use instead

You don't create an account. When you first open MotoSetGo, the app quietly creates an anonymous rider ID — a random identifier with nothing personal attached. It is stored on your device in the operating system's secure storage, and it's what tells our database which bikes and history are yours.

This identifier is not linked to your name, email, phone number, social account, or your Apple or Google ID. We cannot use it to contact you, or to recognise you anywhere else.

What that means, in both directions:

  • Good: we hold no contact information about you at all, because we never asked for any.
  • Worth knowing: because the identifier lives only on your device, uninstalling the app or moving to a new phone means losing access to your garage and history. It can't be recovered or transferred — not by you, and not by us, because nothing ties it to you rather than to that installation. Your subscription is separate and does restore (see §5).

2. What we store, and why

Everything below is stored on our database, hosted by Supabase in the United States (AWS us-west-2, Oregon).

2a. What you enter

WhatExamplesWhy
Rider profile A profile label you choose, your weight, whether you carry a passenger, luggage load, riding style Suspension setup depends on the load the bike carries. Weight drives sag targets and spring-rate advice — the engine can't be right without it.
Your bikes Make, model, year, trim, market Identifies the correct specs, adjuster ranges and sag targets.
Suspension settings Preload, compression, rebound, tire pressures, ride height The starting point every recommendation is measured from.
Tuning history Diagnosis sessions, adjustments you made, and whether each felt better, the same or worse So you can see what you changed and undo it, and so the app doesn't repeat advice that didn't work.

We deliberately do not ask for your name, email, address, phone number, date of birth or photos. The app requests no camera, contacts or microphone permission. It asks for location only when you record a ride in Ride Lab, and only to measure speed and distance — see §2c. If you turn on notifications, the reminders are scheduled on your phone; nothing is sent. There is no server push, no device token and no new identifier.

A note on weight. We ask for it purely as a load input for suspension maths. We don't treat it as health or fitness data and we don't infer anything from it. It goes into the setup calculation, and — because effective spring rate scales with the total load on the bike — into a Ride Lab report row as a load figure (§2c).

2b. How the app performed

To improve the diagnosis engine, the app records what it recommended and how it turned out:

  • The symptom you picked and your answers to the follow-up questions
  • A snapshot of the rider profile, bike and suspension settings at the moment of the recommendation
  • The full ranked list of causes the engine produced, with their scores and the engine version that produced them
  • Which recommendation you acted on, and how you rated the result
  • Basic interaction signals — how long the choice took, how many options you opened — used to correct for position bias when the rankings are re-tuned
  • The app version

This is what lets a future version rank causes by what actually worked for real riders, rather than by expert judgement alone. It carries the same anonymous ID as your other data, and no contact information, because we hold none.

These records are append-only: once written, nothing in the app can edit or delete them. That's deliberate, so the record of what the engine actually did stays trustworthy. It doesn't put them beyond your reach — see §7.

2c. Your Ride Lab reports

Ride Lab records a ride with your phone's own sensors and works the whole analysis out on the phone. The recording itself never leaves your phone. The first time a complete ride is analysed, the app sends us one short row of results, so the analysis gets better for everyone riding that model:

  • Which bike, and the figures the analysis used — the catalogue name of the motorcycle (make, model, trim), the ID of your own garage entry for it, and the wheelbase and curb weight the catalogue gave us
  • The load it was carrying — your riding weight from your profile, whether you carried a passenger, the luggage load, and the riding style you picked
  • The shape of the ride — how long you rode, how much of that was moving, how long the phone held no GPS fix, the distance, your median speed and your top speed, and how rough the ride was
  • The measurements — suspension frequencies and the damping index, effective spring rate and the mass it was worked out against, the speed the bike is busiest at, wheel hop, idle rpm, the comfort figures, your steepest lean angle and the speed you were doing at it, tire grip peaks and how many there were, dive under braking and squat on corner exit with the quality of each fit, and any weave or wobble episodes with their size
  • The verdicts you were shown — the plain-language conclusions from your report, with how confident each one was, and whether it was backed by more than one ride
  • Technical context — the app version, the analysis version that produced these numbers, iOS or Android, your phone model on Android, the sample rate the sensors actually achieved, the kind of mount, and when the ride was saved

What it does not contain, and cannot. No latitude or longitude, no route, no map, no raw sensor data, no filename, and none of the notes you typed on a ride. There is no way to work out where you rode from it. The row is built by naming every field one at a time rather than by copying the report, so nothing can be added to it by accident.

It carries the same anonymous rider ID as your other data, and no contact information, because we hold none. The bike is identified by its catalogue name so that rides on the same model can be compared with each other; that name says nothing about you.

These records are append-only, the same as §2b: once written, nothing in the app can edit or delete them, so the record of what the analysis actually produced stays trustworthy. It doesn't put them beyond your reach — see §7.

2d. Smaller things

  • Whether the plans screen earned a sale. When the plans screen opens, the app counts what happened: it opened, the plans loaded or did not, you tapped a plan, the store said yes, no or not now. We keep the platform, app version and which screen sent you there. No rider ID travels with these counts, so we cannot tell which rider bought.
  • Which install campaign brought you. When you install MotoSetGo, the store can report which campaign brought you to the app. On Android, we read the Play Install Referrer. We keep its source, medium, campaign and search term when present. We also keep selected query key names, without their other values. On iOS, the app sends an Apple attribution token directly to Apple. We keep Apple's attribution result and, when available, its campaign, ad group, keyword, conversion type and claim type. We do not store the token or the full referrer string. We keep these fields with your anonymous ID, platform, app version and the time we record them. We join them to the app's first-open and recommendation records. This tells us which campaigns bring riders who use the app. We do not use this data to personalize ads or send your recommendation activity to Apple or Google.
  • Searches that found nothing. If you search for a bike and we return zero results, we log what you typed. That's how we decide which makes and models to add next. Only the search text — no results, no browsing history.
  • Feedback you send. If you use the feedback form we store your message, the category you chose, your app version and your platform. Please don't include personal details — there's no need, and we'd rather not hold them.
  • Crash and error reports. If the app hits an unexpected error, we record what went wrong — the error message, a technical stack trace (code locations in the app, not your data), your app version and your platform — so we can fix it. These are tied to your rider ID and stored in our own database; we do not use a third-party crash service.
  • A count of website page views. When you open a page on motosetgo.com we record the page, the date and the site that linked you here. There is no analytics script and no cookie, and we do not store your IP address, browser or country. To count separate visitors in a day we use a one-way code that resets daily. Website only, not the app.

3. What we do not do

  • We do not sell or rent your data. To anyone. Ever.
  • We do not show ads or request your device's advertising identifier. The app uses Google's Install Referrer library on Android and Apple's AdServices framework on iOS to measure install campaigns (§2d). We do not use campaign data to personalize ads. Our crash and error reports still go to our own database.
  • We do not collect your location. Ride Lab reads your phone's GPS while you are recording a ride, to measure speed and distance, and that stays on the phone: no position, no route and no map is ever sent to us (§2c).

4. Who else touches your data

  • Supabase — our database and hosting provider (United States). They store the data on our behalf and don't use it for their own purposes.
  • Apple and Google — handle all payments. See §5. Apple and Google also provide store attribution (§2d). On iOS, the app sends the attribution token directly to Apple's service.
  • RevenueCat — manages subscription state. See §5.

We may also disclose data if legally required to, or to protect the safety and rights of riders or ourselves — the standard exception, and one we don't expect to use.

5. Subscriptions and payment

MotoSetGo is free for 30 days, then requires a subscription to continue.

We never see or handle your payment details. All purchases go through the App Store or Google Play using the store account you already have. Your card number, billing address and name are handled entirely by Apple or Google and are never transmitted to us.

We use RevenueCat to track whether a subscription is active. It receives the purchase receipt from the store and returns a subscriber ID and an entitlement status — active or expired, and which tier. That status stays on your phone. We do not store it on our servers.

Because your subscription lives with your Apple or Google account rather than with us, it restores on a new device even though your garage does not (§1). Manage or cancel it in your store account's subscription settings — not in our app, since we have no account to cancel.

6. How long we keep things

We keep data for as long as it still serves the purpose it was collected for, rather than to a fixed calendar deadline:

  • Your data — kept while you're using the app, because that is the app. Deleting a bike or a history entry deletes those rows for real, immediately. Ask us to delete everything (§7) and we will.
  • Engine records — kept for as long as they're useful for improving the diagnosis engine. Their value is specifically long-run: knowing that a recommendation worked for a certain bike and rider years ago is exactly what makes the advice better now. They hold no contact information of any kind.
  • Ride Lab report rows (§2c) — kept on the same footing and for the same reason. Their value is that rides accumulate: what a model measures across many riders and many roads is what turns a number into a confident verdict, and a row discarded on a timer is a bike missing from that picture. They hold no contact information and no location of any kind.
  • Feedback and zero-result searches — kept until we've acted on them, then cleared periodically.

7. Your rights, and how to use them

Depending on where you live — the EU and UK under GDPR, California under CCPA/CPRA, and elsewhere — you have rights to access, correct, delete or export your personal data, and to object to certain processing. We don't discriminate against anyone for exercising them.

Because there is no account, an email from you tells us nothing about which rows are yours — so the app gives you the missing piece. Open Help → "Your data & privacy" and you'll find your rider ID, the random identifier your data is filed under. There's a button there that opens an email to us with the ID already filled in.

  • To delete everything: send us that rider ID. We'll delete every row filed under it — your profile, bikes, settings, history, the engine records (§2b) and your Ride Lab report rows (§2c) — and confirm when it's done. It's handled by a person, so allow us a few days.
  • To delete something specific: just delete it in the app. Deleting a bike or a history entry is a real deletion, not a hide.
  • To get a copy of your data, or correct it: send us the rider ID and tell us what you need.

One genuine limitation, stated plainly rather than buried. That rider ID exists only on your device. If you uninstall the app without sending it to us first, neither you nor we can ever locate that data again — we'd have nothing to search by. It becomes unreachable rather than deleted. If you want it gone, ask us before you uninstall.

The flip side is real privacy: what we hold genuinely cannot be tied back to you as a person — not by us, not by a future owner of the business, and not by anyone who compelled us to produce it.

Questions or requests: admin@motosetgo.com.

8. Children

MotoSetGo is intended for licensed motorcycle riders and is not directed at children. We don't knowingly collect data from anyone under 13, or under 16 in the EU and UK. Since we collect no identifying information we have no way to determine a user's age — but if you believe a child has used the app and you want their data removed, contact us and we'll help as far as §7 allows.

9. Security

Data is transmitted over encrypted connections (HTTPS/TLS) and stored in a database protected by row-level security, meaning each anonymous ID can only ever read its own rows. The engine-record tables are insert-only and cannot be read back by the app at all. The session token on your device is held in the operating system's secure storage — iOS Keychain or Android Keystore.

No system is perfectly secure, but we hold no passwords, no payment details and no contact information, so there is very little here worth stealing.

10. International transfer

Our servers are in the United States. If you use MotoSetGo from the EU, the UK or elsewhere, your data is transferred to and stored in the US, under the safeguards our hosting provider offers for such transfers.

11. Changes

If we change this policy we'll update the date at the top and, for anything significant, tell you in the app. Continuing to use MotoSetGo after a change means you accept the updated policy.

If the business changes hands

If MotoSetGo LLC is sold, merged or otherwise transferred, the data described here transfers with it and remains governed by this policy — any new operator inherits the same commitments and cannot weaken them without notifying you under §11. We'll update the provider name above if that ever happens.

12. Contact

admin@motosetgo.com — questions, requests, or anything that reads wrong here.