Privacy Policy

LookOver has a few optional, Premium AI helpers: logging a service from a sentence you type, scanning a photo or PDF of a receipt or a handwritten log, and suggesting a maintenance schedule for your machine. You choose when to use them. Every one has a manual option right next to it, and the app works fully without ever touching AI.

What we send when you use an AI feature

• Only what that feature needs: the text you typed, or the photo/PDF you chose to scan, plus your machine's make, model, and year. Before typed text is sent, we remove anything that looks like an email address, VIN, or phone number. When you scan a service record, the machine's VIN is included so the result matches the right machine.
• Your machine list, for Auto Add only: so Auto Add can tell which machine you mean (“changed the oil in my Yamaha”), it sends each machine's name, year, make, and model. Nothing else about them.
• Who processes it: OpenAI and Anthropic, through their standard business APIs. We also route these requests through Helicone so we can monitor performance and fix problems you report. For the photo and PDF scans, Helicone records only that a scan ran, never the image or the VIN.
• What we never send: your service history, reminder details, ride routes, or notes and files from machines you are not actively working with in that moment. The only exception is partner offers, which send reminder titles on their own (see Partner Offers).

We don't train AI on your data

Your entries and photos are used to give you a result, and that is it. We do not train AI models on your data, and our AI providers do not use data sent through their business APIs to train their models either. There is no LookOver “AI” quietly learning from your machines in the background.

What our AI does not do

It turns what you type or scan into a tidy service record, reminder, or schedule. That is the whole job. It does not look up service manuals, answer open-ended questions, or chat. AI features need an internet connection. Manual entry works offline, 20 miles from the trailhead.

When a reminder is for a job that needs a part, like servicing your air filter, LookOver may show a discount from a brand we partner with. Each one is labeled “Partner offer.” Partner offers are on by default, and you can turn them off anytime under More > General > Show partner offers.

How we match an offer to a reminder

To know which part a reminder needs, we send its title (for example “Clean air filter”) to OpenAI, which tags the part. We send the title only: no account, machine, notes, or other details. We skip any title that looks like it contains an email address or a long number. The tags are saved by title, not by rider, so when two riders have the same reminder title we only ask once. Helicone records only that a request ran, never the title.

What we record

When an offer is shown, and when you copy its code, tap Shop, or dismiss it, we record that event with your account so we can count real riders and stop showing you an offer you dismissed. We use this to report results to our partners as totals only, such as how many riders saw an offer. We never give a partner your name, email, account, machines, or anything else that identifies you.

When you shop

Tapping Shop opens the partner's website. The link tells them the visit came from LookOver, not who you are. Anything you do or buy there is covered by that partner's own privacy policy.

LookOver offers an optional ride tracking feature that uses GPS to track distance and duration for your machines.

• When collected: Only during ride tracking sessions you manually start. We never track you passively. If you use the Bluetooth ride trigger, tapping its prompt is how you start the ride yourself. It never starts GPS on its own.
• Background tracking: If enabled, continues while the app is backgrounded so your ride isn't interrupted.
• What we store: Ride summaries (distance, duration, date) and GPX route files linked to your machines.
• Your control: Disable anytime in device settings or simply don't use the feature.

Service Guidance (Premium): nearby shop lookup

When you open the “Take It In” tab on a reminder, LookOver sends your approximate location to Google's Places API to surface nearby service shops and dealers. This is a one-shot lookup, not continuous tracking. Your lat/lng is sent to Google for that single search and is not stored on LookOver's servers. If you never open the Take It In tab, no location is sent.

LookOver's Apple Watch app lets you record a ride without carrying your phone. Recording a ride asks for Health access, and it is fair to wonder why a maintenance app needs it.

The honest answer: on Apple Watch, only an active workout session keeps an app running with your wrist down. Without one, tracking would stop within seconds of the screen dimming and capture almost nothing of your ride. So LookOver records your ride as a workout.

• What we write: A workout for the ride you recorded, plus the active calories Apple Health attaches to it, saved on your watch. Those calories are what make the ride count toward your activity rings, which is why we save the workout rather than discarding it.
• What we read: Heart rate and active calories, and only while a ride is running. Apple's workout builder collects both to add the workout up, and the calories are what let it count toward your rings. LookOver never shows you either number, never reads your health history, and never asks for anything outside the ride in progress.
• Where it goes: Nowhere. Health data stays on your watch and iPhone under Apple's protection. It is never sent to LookOver's servers, never included in your cloud backup, and never shared with anyone.
• What reaches your phone: The ride itself, handed over directly from watch to phone. That is GPS points, distance, and time, exactly as if you had recorded on your phone. It carries no health information.
• Your control: You can decline Health access, or turn LookOver off under Health in the Watch app on your iPhone at any time. Rides started on the watch need it and will not run without it. The rest of LookOver is unaffected, and you can still record rides on your phone.

Location on the watch works the same way it does on your phone, covered in Location Data above: captured only during a ride you start yourself.

The Bluetooth ride trigger is an optional Pro feature. You pick a Bluetooth device you ride with, like your helmet comm, a speaker, your UTV, or the truck or car you drive to the trail. When that device connects, LookOver sends you a notification, and one tap starts a GPS ride on the machine you chose. When it disconnects, LookOver asks whether you want to end the ride. You turn it on under More > General > GPS Tracking.

It works differently on Android and iPhone, so here's exactly what each one does.

• What we read on Android: LookOver asks for Android's Nearby devices permission (Bluetooth connect), and only from the trigger's setup screen. It reads your list of paired devices only when you tap Choose device, so you can pick yours. After that it pays attention to that one device alone: whether it connected or disconnected, and whether it's still connected for audio. Every other device is ignored. LookOver never scans for nearby devices and never uses your location to find Bluetooth devices.
• What we read on iPhone: No Bluetooth data at all. You set up two automations in Apple's Shortcuts app, and iOS runs LookOver's Ride Device Connected and Ride Device Disconnected actions without telling LookOver which device set them off.
• What we store: On Android, the name and Bluetooth address of the device you chose, and the machine you picked, saved on your phone. On iPhone, the machine you picked and the time your device was last seen, saved on your phone, so the setup screen can show it's working.
• Where it goes: Your device's name and address are never sent to LookOver's servers and never included in your LookOver cloud backup. So we can tell whether the feature works, our analytics (Firebase) and error monitoring (Sentry) tools receive simple signals: when your device connects or disconnects, when a prompt is shown or tapped, how many seconds a dropout lasted, and whether the needed permissions are on. The same signals are included in a diagnostics report if you choose to send us one. None of them include your device's name or address.
• What shows on your screen: The device name appears in your own ride prompt notification (on Android, that can include your lock screen) and in the “Done riding?” banner in the app. That is shown on your phone only.
• Your control: It's off by default. Turn it off anytime under More > General > GPS Tracking, and LookOver stops watching for your device. Uninstalling LookOver removes what the trigger saved on your phone (Google's device backup, if you use it, is separate; see the Android note below). On Android you can also take back the Nearby devices permission in your phone's settings, and on iPhone you can delete the two automations in Shortcuts.

The trigger never starts GPS on its own. A ride starts only when you tap the prompt, and the same location permission and Pro requirements as any other ride still apply. Ending a ride takes a tap too. Tapping the prompt counts as starting the ride yourself, covered in Location Data above.

A note for Android: if Google's own device backup is turned on for your phone, it may include LookOver's on-device settings, which can include the device you chose. That backup belongs to your Google account and is handled by Google, not LookOver.

The calendar feed is optional. On the Calendar screen in the More tab you can get a private subscribe link for your garage and add it to Apple Calendar, Google Calendar, Outlook, or any calendar app that takes a link. Nothing goes out until someone adds that link to a calendar.

• What it includes: One all-day event per open reminder in that garage, showing the machine's name, the reminder's title and description, the day it's due, and whether it's approaching, due, or overdue. Completed, dismissed, and deleted reminders are left out. It doesn't include your name, email, location, costs, or files.
• Who receives it: The calendar service you subscribe with (for example Apple, Google, or Microsoft) fetches the link on its own schedule and stores those events under its own privacy policy. Anyone you give the link to can see the same events, so treat it like a password.
• Shared garages: Everyone in a shared garage uses the same link. An owner or admin can reset it anytime, which turns off the old link for every calendar subscribed to it, for example after someone leaves the crew.

To stop sharing, remove the subscription from your calendar app, and have an owner or admin reset the link if it went anywhere it shouldn't have.

LookOver runs ads on Meta (Facebook and Instagram) so we can reach more riders. To know which ads actually work, we use Meta's App Events SDK on iOS to measure conversions. This is only active if you tap Allow on the iOS tracking prompt the first time you open the app.

What we share with Meta (only if you tap Allow)

• Your device advertising identifier (IDFA). A device-level ID that Apple controls. It is not tied to your name, your account, or anything you typed into the app.
• A one-way hash of your email and name. We never send your raw email or name. The SDK turns them into SHA-256 fingerprints before transmission so Meta can match them to an ad click without ever seeing the details themselves.
• App events. Anonymous signals like “installed the app,” “completed signup,” “started a trial,” “subscribed.” No details about which machines you own or what services you logged.

What we never share with Meta

• Your machines, makes, models, VINs, or photos.
• Your service records, costs, or notes.
• Your reminders or maintenance schedules.
• Your ride tracking routes or GPS data.
• Your raw email or phone number.

How to opt out

• At the prompt: Tap “Ask App Not to Track” when you first open the app.
• Later, on iOS: Open the Settings app → Privacy & Security → Tracking → toggle LookOver off.
• Or globally: Settings → Privacy & Security → Tracking → turn off “Allow Apps to Request to Track,” which silently declines every app.

Note: Android users are not part of this program. We do not collect Android advertising IDs.

This measurement runs on your device and follows your tracking choice. We don't bypass that choice with server-side tracking, and we never share your ad-conversion data with Meta for anyone who hasn't tapped Allow.

In the app: measuring which ads work

We also work with an advertising partner, TrailIntel, using a data tool called Segment to route the measurements, so we can see which ads lead to installs and subscriptions. What we send is anonymous and never tied to you.

• What it sees: the screens you view and when you start a trial or subscription, including the plan and amount.
• What it never sees: your email, name, account ID, VIN, machines, service records, photos, or any advertising identifier.
• How it's controlled: turn it off anytime in the app under Settings → General → Ad Measurement, on either platform. On iOS it also requires tapping Allow on the tracking prompt, so declining tracking keeps it off too. On Android it collects no advertising ID.

On our website: measuring which ads work

When you visit our marketing website at lookover.app we use the same partner, TrailIntel, to understand which of our ads brought you there. It runs only in your browser on our public marketing pages. It does not run on the signed-in web companion where your garage lives.

• What it sees: the marketing pages you visit, the ad or link that referred you, general browser and device information, and your IP address.
• What it never sees: your account, machines, service records, photos, or reminders. You are not signed in on the marketing pages, so none of that data is there to collect.
• How to opt out: use your browser's privacy settings or any ad or tracker blocker. Blocking it has no effect on how the app or the web companion works.

Creator links: crediting the rider who sent you

Riders who make videos or run communities can share a LookOver link and earn a commission when the people they send subscribe. Our partner Insert Affiliate tracks which creator gets the credit.

• What it sees: a random ID for your install, the creator's link code if you arrived through one, and on Android the Play Store install referrer. On iOS, and only if you tap Allow on the tracking prompt, a one-time snapshot on first launch of your device model, OS version, screen size, memory size, language and region setting, time zone, and network type (Wi-Fi or cellular), so an install can be matched to the link you tapped. Like any server, it also sees your IP address.
• What gets credited: if a creator sent you, your subscription purchases are credited to them for 30 days after you tap their link. If you already pay for LookOver, no creator is ever credited.
• What it never sees: your email, name, advertising identifier (IDFA), location, machines, service records, photos, or GPS data.
• Your choices: on iOS, tap “Ask App Not to Track” and the device snapshot is never sent. The random install ID is still used on every device, and it is not linked to your email or name. On Android there is no separate switch: the install referrer only names a creator if you installed from their link. Either way, if you didn't arrive through a creator's link, nothing is credited to anyone.

Signing up as a creator on lookover.app/creators happens in a form run by Insert Affiliate, which holds your creator account (username, email, and password) and payout details under its own privacy policy.

Our website uses cookies to enhance your experience. These are small files stored on your device that help us:

• Remember your preferences
• Understand how you use our site
• Improve our website performance

Analytics: We use Google Analytics on both our marketing website and the signed-in web companion to see which pages and features get used, so we can improve them. It ties activity to a random analytics ID, not your account, and never sees your machines or service records. On our marketing pages only, we also use Trailintel to measure which ads bring people to the site (see the Advertising section).

You can refuse cookies in your browser settings, or block analytics entirely with any ad or tracker blocker. Blocking them has no effect on how the app or the web companion works, though some general website features may not behave normally without cookies.

The mobile app doesn't use cookies but uses similar technologies for analytics as described in the Third-Party Services section.