Privacy Policy

Effective 5 October 2026. Last updated 7 October 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

These, and no others. Each has its own section below.

Nothing in your logbook is part of any row but the one for cloud sync. No note, no cost, no photo, no odometer reading and no car goes to analytics, to Meta, to Apple, 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; which step of adding a car is on screen, so we can see where people stop; 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 reminder being edited or deleted, and which of the common kinds it was; 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; your first car and your first entry, once each; the paywall opening, and from where; a purchase being started, cancelled, completed or restored, with which of the three products and, for a completed one, its price, currency and the store's transaction number; the review prompt being shown, and your answer to Motored's own "Do you like using Motored?" question, with which moment raised it, and whether a yes went on to the store's rating card or its review page; the Rate Motored link in Settings being tapped; each step of setting up a new car being answered or skipped, with how many modifications were picked; a "Get Pro" prompt being tapped, and which one; a modification being saved with a before or after photo, never the photo itself; the 3D car on the home screen being turned, once a launch; which screen of the app is open, by its kind and never its contents (for example "a car's entry"); whether you allowed reminders; a reminder being tapped; the ads notice being shown and your answer to it, your answer to the iPhone tracking question, and either switch in Settings being changed; 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.
• A few properties of 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; whether cloud sync is on; your answer to the ads notice; and, on iPhone, your answer to the tracking question. The counts are bands and never exact numbers, and none of these carry anything 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 a name or email address and carry no content. You can object at any time — see §14.

Turning it off. Settings ▸ Usage analytics in Motored stops it on that phone from then on. To have events already recorded deleted, write to support@ripeseed.io with enough for us to find them. 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.

5a. Ad measurement with Meta and Apple

We advertise Motored on Facebook and Instagram, which are run by Meta, and in the App Store through Apple Ads. To know which ads are worth paying for, the app reports a few events back. Motored itself shows no ads.

Meta

Motored includes Meta's software development kit. From version 0.1.1, once you have added your first car, it tells Meta that the app was installed and opened, when you add your first car and log your first entry, when the paywall opens, and when a purchase is started, with the product and its price. When you buy Pro, RevenueCat (§7) tells Meta which product was bought and for how much. Meta receives with those events: an identifier its kit generates on your phone, the app version, the device model and operating system, your language and time zone, your IP address, and, if a Meta ad opened the app, the ad campaign it came from. On iPhone, if you allow tracking, it also receives the advertising identifier (IDFA). On Android it receives the Advertising ID.

Meta uses this information to provide measurement services, target and deliver ads, including to tell us which ads led to installs and purchases and to show our ads to people likely to want Motored. Meta may combine it with what it holds about you if you use its services, under its own privacy policy. The kit contacts Meta when the app starts to fetch its own settings, but no event is sent until you have seen the notice and, on iPhone, answered the tracking question.

• On iPhone, Apple's tracking question decides whether Meta gets your advertising identifier. If you ask Motored not to track, the identifier is not sent and Meta measures our ads only in aggregate. In the EEA, the UK and Switzerland nothing is sent to Meta at all unless you allow tracking.
• On Android in the EEA, the UK and Switzerland, the app asks you directly, and the app sends Meta nothing unless you say yes. A purchase still reaches Meta through RevenueCat, without any identifier that ties it to you (§7).
• Turning it off. Settings ▸ Ad measurement in Motored stops it on that phone. On iPhone you can also turn tracking off in iOS Settings ▸ Privacy & Security ▸ Tracking. On Android you can delete or reset the Advertising ID in your phone's settings. Meta's own controls are in its Accounts Center, under "Your activity off Meta technologies" and "Ad preferences".

Legal basis. Where the UK or EU GDPR applies, we rely on your consent, which you can withdraw at any time as above. For collecting this data through Meta's kit and sending it to Meta, RipeSeed LLC and Meta Platforms Ireland Ltd are joint controllers under Meta's Controller Addendum; what Meta does with it afterwards, Meta controls alone.

Google Ads

We also advertise on Google. Google Ads learns which of its ads brought people to Motored from the Firebase Analytics events in §5, in particular your first car, your first entry and a completed purchase with its price. Whether Google may use them for that follows the same rule as Meta: before your first car, in Europe without a yes, and whenever ad measurement is off, Firebase marks the events as not to be used for advertising and sends no advertising identifier. With a yes, Google may use them to measure our ads and receives the advertising identifier where your phone provides one (on iPhone, only if you allowed tracking), and may use them to show our ads to you and to people like you, including after you have left the app. With a no, none of this happens. Google's handling is described at policies.google.com/technologies/ads.

Apple Ads

On iPhone, Motored asks Apple's AdServices framework for an attribution token and gives it to RevenueCat, which sends it to Apple. Apple answers whether the install came from an Apple Ads campaign and, if so, which campaign, ad group and keyword. RevenueCat files your purchases under that campaign so we can see what our App Store ads earn. The token carries no identifier that follows you across other companies' apps, and Apple does not count it as tracking, so it does not depend on the tracking question.

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 also sends your purchases to Meta and matches them to the install Meta's kit reported, and receives the Apple Ads token described in §5a. On iPhone it sends a purchase to Meta only if you allowed tracking. On Android it sends every purchase, but Meta's identifier and the Advertising ID go with it only once you have said yes to ad measurement; without them Meta can count the purchase but cannot tie it to you or to an ad. Turning ad measurement off stops Motored passing RevenueCat Meta's identifier from then on. 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 these, 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 ads in the app. Motored shows no advertising and contains no ad network. The advertising identifier goes only to Meta, only for measuring our own ads, and only as §5a describes.
• No sale of personal information. We never sell it. California's meaning of "sharing" does cover the ad measurement in §5a; see §15.
• No account unless you want one, and none for a free logbook. No phone number, ever. An account exists only to carry Pro to another phone (§11).
• 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.
• Ad measurement events are kept by Meta under its own retention rules, described in its privacy policy. We see them only as campaign totals.
• 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, and to withdraw consent where we rely on it (ad measurement, §5a) without affecting what was done before. Requests about the data Meta holds can go to us or to Meta directly; we will pass ours on. 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 a name or email address. 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 personal information. From version 0.1.1 the ad measurement in §5a sends identifiers (the advertising identifier and Meta's own), internet or network activity (installs, opens and purchases) and coarse location inferred from an IP address to Meta and, with the same answer, lets Google use the events in §5 to measure our ads, which California treats as sharing for cross-context behavioural advertising. You can opt out in the app with Settings ▸ Ad measurement, or on iPhone by turning tracking off. We do not use or disclose sensitive personal information for any purpose that would require an opt-out. Everything else in §4 goes only to the service providers named there, only for the purposes named there.

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

16. International transfers

RipeSeed LLC, Google, Amazon Web Services, RevenueCat, Apple and Meta Platforms, Inc. are 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, and, for Google and Meta, on their certification under the EU-U.S. Data Privacy Framework and its UK Extension. Every company that receives data from Motored is bound to protect it at least as well as this policy does.

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. The ad measurement in §5a is such a change: version 0.1.1 shows anyone updating from an earlier version a notice before sending anything to Meta or Google.

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.