Privacy Policy

Effective 23 August 2026. Last updated 23 August 2026.

1. Who this covers

This policy covers the Motored mobile app for iOS and Android, and this website at motored.products.ripeseed.io. It does not cover the App Store or Google Play themselves, or the NHTSA database described in §6 — those are run by other people under their own policies, which we link to where they apply.

2. Who we are

Motored is made and published by RipeSeed LLC, a Delaware limited liability company. For the purposes of the UK and EU General Data Protection Regulation, RipeSeed LLC is the data controller for the limited personal data described in §4.

We publish a monitored mailbox rather than a postal address, which is what identity-and-contact-details means in practice for a company this size. If a supervisory authority or a customer needs a postal address, ask and we will give you one.

Contact: support@ripeseed.io.

3. What Motored keeps on your phone

Everything you write into Motored is stored in a database and a folder inside the app's own private storage on your device. We do not receive any of it. It is not uploaded, not backed up to us, and not readable by us. That list is:

• Your cars — nickname, year, make, model, trim, VIN, engine details, transmission, drivetrain, paint code, licence plate, the date you bought it, odometer readings, and the icon and colour you picked.
• Your entries — services, repairs, modifications, fuel fill-ups and charges: what was done, the date, the odometer reading, the cost, your notes, the gallons or litres or kWh, the station, the category, and whether you or a shop did it.
• Your reminders — the intervals you set and when each was last done.
• Your photos — anything you attach to a car or an entry is copied into Motored's own folder. The copy lives there until you delete the entry or the app.
• Your settings — units, currency, whether reminders are on, and a few flags the app uses to avoid asking you the same thing twice.
• Weekly safety copies — Motored writes a snapshot of your logbook to its own folder about once a week, and keeps the newest three. They never leave the phone unless you export them.

Your phone's own operating-system backup — iCloud Backup or Google's Android backup — may include this app data if you have that turned on. That is a setting on your device, between you and Apple or Google, and we are not a party to it.

4. What leaves your phone

Four things, and no others. Each has its own section below.

Nothing in your logbook is part of the first four rows. No note, no cost, no photo, no odometer reading and no car goes to analytics, to the payment services, or to anyone else — with two exceptions, both of which you choose: the VIN, for the one decode request you asked for, and your logbook itself, once you turn on cloud sync. Sync is described in full in §11. If you never turn it on — and a free logbook is never asked to — the last row never happens.

5. Analytics, in detail

Motored sends usage events to Firebase Analytics, Google's product-analytics service. For a free logbook there is no login and no profile, so these events are tied to a device and not to a person. If you buy Pro and create an account, the events from your devices are tied to your account identifier so that one person on two phones is counted once — see the last item below. Google receives:

• An app instance identifier generated on your device the first time the app runs, so that two events from the same phone can be counted as one visit rather than two. It is not derived from your device's hardware identifiers, and deleting the app ends it.
• Named events with small, fixed labels. The complete list of what Motored deliberately sends is: a car being added, and whether by VIN, by lookup or by hand; a car being deleted; an entry being added, edited or deleted, and which of the four kinds it was; a reminder being set, and whether by time or by mileage; a VIN decode being attempted, and whether it succeeded; an export or a backup being made; a backup being restored, with a count of cars and entries; the paywall opening; a purchase being started, and which of the three products; the review prompt being shown; and, if you have an account, signing up; signing in, and whether with an email address, with Apple or with Google; signing out; resetting a password; deleting the account; and a sync being run or a conflict being settled.
• Automatic app-lifecycle events that the analytics library sends on its own: the app being installed, updated, opened and backgrounded.
• Technical properties attached to those events: the app version and build number, the operating system and its version, the device model, the screen size, and your language and time zone.
• Your IP address, from which Google derives an approximate location — country, and usually region and city. Google uses the address for that and does not store it against events for our use.
• Four bands about your use of the app, attached to your device rather than to any event: whether you keep one car, two, or three and more; whether you have logged nothing, one to three entries, four to ten, or eleven and more; whether Pro is active; and whether cloud sync is on. They are bands and never exact numbers, and they carry nothing you typed.
• Your account identifier, only if you have an account. It is the random identifier Firebase issues you, not your email address, and its only purpose is to stop one person with two devices being counted as two people. Signing out ends it.

What analytics never contains: the text of anything you typed, any cost or price you entered, any note, any photo, any odometer reading, any car's make, model or VIN, any station or shop name, and any file you exported. The labels are categories, not contents: the event says an entry of kind "fuel" was added, never what was in it.

Legal basis. Where the UK or EU GDPR applies, we rely on our legitimate interests in understanding how the app is used well enough to keep improving it, balanced against the fact that these events are not linked to an identified person and carry no content. You can object at any time — see §14.

Turning it off. Motored does not yet have a switch in Settings for this, and adding one is on our list. In the meantime, write to support@ripeseed.io and we will tell you how to stop it on your device and, if you can give us enough to find them, delete the events already recorded. Uninstalling the app also ends the identifier described above.

Google's privacy policy is at policies.google.com/privacy, and how Firebase handles this data is described at firebase.google.com/support/privacy. If a given build ships without Firebase configuration, Motored sends nothing at all and this section does not apply to it.

6. VIN decoding

When you scan or type a VIN and ask Motored to look it up, the app sends that VIN and nothing else to the vPIC service run by the National Highway Traffic Safety Administration, part of the United States Department of Transportation. It sends back the year, make, model, engine and drivetrain it has on file, which Motored writes into the car for you.

This happens only when you ask for it. Typing a car in by hand never contacts anything. A VIN identifies a vehicle rather than a person, but a vehicle you own can be connected to you, so we treat it as personal data and mention it here rather than burying it. NHTSA is a US government agency and its handling is governed by its own privacy policy, not ours.

7. Purchases

Motored Pro is sold through the App Store and Google Play. We never see, receive or store your card number, billing address or store account. Apple or Google takes the payment and tells us only whether an entitlement is active.

We use RevenueCat to check that entitlement. RevenueCat generates its own anonymous app-user identifier on your device — we do not give it your name or email, because we do not have them — and receives the store's purchase receipt, which product was bought, whether a subscription is active, and basic device and platform information. RevenueCat's privacy policy is at revenuecat.com/privacy.

If a build ships without purchase keys configured, the app never contacts RevenueCat and nothing here applies to it.

8. Permissions

Motored asks for three things, each at the moment it is needed rather than on first launch, and each one is refusable. Refusing costs you that one feature and nothing else.

Motored does not ask for your location, your contacts, your calendar, your microphone, your health data, Bluetooth or nearby devices, and it has no reason to.

9. Notifications

Every reminder Motored shows is scheduled on your phone, by your phone. The app has no push-notification capability at all — the entitlement that would let a server send it anything is deliberately removed from the build, so no push token exists and there is nothing for us to send to. We cannot notify you, and neither can anyone else. Turning reminders off in Settings cancels everything that was scheduled.

10. What we never collect

• No advertising, and no advertising identifiers. Motored contains no ad network and does not read the IDFA on iOS or the Advertising ID on Android. It never shows App Tracking Transparency's tracking prompt, because it does not track you across other companies' apps or websites.
• No sale or sharing of personal information as either is defined under California law, and no cross-context behavioural advertising. We have never done this and have no plan to.
• No account, no email address, no password, no phone number. There is nothing to sign up for.
• No precise or background location. The app never requests it.
• No session replay, no screen recording, no heatmaps, no keystroke capture.
• No data brokers. We do not buy personal data about you, and we do not enrich or combine what little we have with anything bought from anyone else.

11. Accounts and cloud sync

Motored works with no account at all. A free logbook is never asked to sign up, works offline, and nothing in it is ever uploaded. That has not changed and is not going to.

Cloud sync is part of Pro, and it is offered after you buy, never before. It is something you turn on, and a switch in Settings turns it off again at any time. Turning it off stops this phone sending anything; it deletes nothing, so the copy already in the cloud stays until you delete your account. Until you sign in, no logbook content leaves your phone.

What is stored, and where

• Your account. An email address and password, or a Sign in with Apple or Google sign-in, held by Firebase Authentication (Google LLC, United States). We never see your password. If you use Sign in with Apple and choose to hide your address, we only ever get Apple's relay address.
• Your logbook. One file holding your cars, entries and reminders, exactly as the backup file you can export yourself, plus each photo you attached. It is stored in Amazon S3 in Northern Virginia, in a private bucket, filed under your account identifier and nothing else.
• Nothing else. There is no database of you, no profile, no contact list, and no advertising identifier anywhere in this.

Who can read it

The bucket is private and blocked from the public internet. Your phone holds no keys to it. Each time it syncs, it proves who it is with your Firebase sign-in, and a small service of ours returns a link that works for five minutes and for one file — yours. That service also asks RevenueCat whether Pro is active, so that only paying accounts can store anything. It never reads your logbook and never keeps a copy.

RipeSeed staff can technically reach the bucket, as the people who run it. We do not read customer logbooks, and we will not, other than on your explicit request for support. Everything is encrypted in transit and encrypted at rest.

How long, and how to end it

A synced logbook stays until you remove it. Delete account in the app deletes your account and everything stored under it, including every photo. Previous copies of the file are kept for 30 days so a bad sync can be undone, then deleted too. The logbook on your phone is untouched by any of this — deleting your account does not take your records away from you, and export and backup keep working.

Legal basis. Where the UK or EU GDPR applies, we process this to perform the contract you entered when you bought Pro and switched sync on. You can withdraw at any time by signing out or deleting the account.

12. How long things are kept

• Your logbook stays on your phone until you delete the entry, the car, or the app. Deleting the app removes the database, the photos and the weekly copies with it. We hold no copy to delete.
• Analytics events are kept by Google for as long as our property retains them, and no longer than 14 months, after which they are deleted or retained only as aggregate counts that identify nothing.
• A synced logbook is kept for as long as your account exists. Deleting your account deletes it — the cars, the entries, the reminders and every photo — straight away. Previous copies of the file are kept for 30 days so a bad sync can be undone, and then they go too.
• Your account — the email address or the Apple or Google sign-in behind it — is kept by Firebase Authentication until you delete the account, which you can do yourself in the app.
• Purchase records are kept by RevenueCat for as long as the entitlement exists plus the period their own policy and the stores' rules require, so that a restore on a new phone still works.
• Email you send us is kept while we deal with it and for up to 24 months after, so that a follow-up has its history.

13. Children

Motored is a tool for keeping records about a car and is not directed at children. We do not knowingly collect personal data from anyone under 13, or under the age of digital consent in their country where that is higher. If you believe a child has sent us something, write to support@ripeseed.io and we will delete what we can find.

14. Your rights

If you are in the UK, the European Economic Area, or another place with comparable law, you have the right to ask for access to your personal data, to have it corrected or erased, to have its processing restricted, to receive it in a portable form, and to object to processing carried out on the basis of legitimate interests. You may also complain to your supervisory authority — in the UK, the Information Commissioner's Office; in the EEA, the authority for your country.

Two honest limits. First, most of what you would want back is already entirely in your hands: your logbook is on your phone, and Motored exports the whole of it to CSV and JSON, with the photos, free of charge and without asking us. That is a stronger portability right than we could give you.

Second, the analytics described in §5 are not linked to an identified person. Where we genuinely cannot connect a request to a record, the GDPR does not require us to acquire more information about you just to be able to. We will say so plainly rather than pretend, and we will tell you what we can do instead.

Write to support@ripeseed.io. We aim to answer within 30 days and will tell you if we need longer.

15. California

Under the California Consumer Privacy Act as amended, you have the right to know, delete, correct, and to opt out of the sale or sharing of personal information, and not to be discriminated against for exercising any of them.

We do not sell or share personal information, and we do not use or disclose sensitive personal information for any purpose that would require an opt-out. In the last 12 months we collected only the categories in §4: internet or network activity (which app features were used), and coarse location inferred from an IP address. We disclosed them only to the service providers named there, only for the purposes named there, and under contracts that forbid them using it for anything else.

To exercise any right, write to support@ripeseed.io.

16. International transfers

RipeSeed LLC, Google, Amazon Web Services and RevenueCat are all in the United States, so the data in §4 is processed there. A synced logbook is stored in Amazon's Northern Virginia region. Where that involves moving personal data out of the UK or the EEA, we rely on the European Commission's Standard Contractual Clauses and the UK Addendum, which are part of our agreements with those providers.

17. Security

Your logbook sits inside the app's private storage, which the operating system keeps separate from other apps and covers with the device encryption that your passcode unlocks. Set a passcode — it is the single thing that most protects what is in Motored.

Every network request the app makes goes over HTTPS. A backup or export file, once you have shared it out of the app, is an ordinary file in whatever place you sent it, and is as protected as that place is. No system is perfect, and we do not claim otherwise.

18. Changes to this policy

When this policy changes we update the dates at the top of this page. If a change is material — a new recipient of your data, a new category collected, or a new purpose — we will say so in the app before the change takes effect, and we will not apply it retroactively to data already collected. §11 is the specific promise for the change we already know is coming.

19. Contact

support@ripeseed.io — a monitored mailbox, read by the people who build the app. Say which phone and which app version if you are reporting something specific; it is in Settings, at the bottom.

RipeSeed LLC, a Delaware limited liability company.