Privacy Policy

What we collect and why

Account information

When you create an account we collect your email address🔒 and display name to identify you and deliver account-related communications.

Profile photo

If you upload a profile photo it is displayed to users you share trips with. Upload is optional.

Home location

If you save a home address, the text address🔒 and its coordinates🔒 are stored against your account and used as a default start or end point when planning trips. This is entirely optional and can be removed at any time via Settings.

Location data

FuelOracle uses location in two ways:

• Stored trip data: waypoints, route coordinates, and fuel stop locations you add when planning a trip are stored against your account to provide the planning service.🔒
• Device location: tapping "Use my location" asks for permission, then centres the map or finds nearby stations on your device. Nothing is sent to us for that. If you update your fuel level during a trip, or pour a jerry can into the car, your position is sent and stored on that trip so the rest of the plan can be recalculated from where you are. The same applies when the app saves the tank level it reads from your car (see Car Connectivity (OBD) below).

We do not collect background location. We do not track your movement over time.

Optional planning preferences

You may save optional preferences to personalise your planning experience. These are stored against your account and can be removed at any time via Settings. They are not shared with third parties.

Trip data

Trips you create - including waypoints, routes, fuel stops, dates and notes - are stored to provide the planning service. Not shared with third parties.

When you mark a fuel stop as completed, the actual price paid, litres filled, and odometer reading you enter or confirm are stored to track trip progress and calculate total costs.

Vehicle and garage data

Vehicles and caravans you add - including fuel economy, tank size, dimensions, and odometer readings - are stored to calculate fuel plans accurately. Not shared with third parties.

Car Connectivity (OBD)

On a paid plan in the iOS or Android app, you can pair your own Bluetooth OBD adapter (any plan can pair one inside the Car Connectivity Test, described below) so the app reads live values from your car: the odometer, fuel tank level, AdBlue level and use, engine oil temperature, tyre pressures, and the speed and fuel flow used to work out distance and fuel economy. The app also reads the car's VIN so it can tell your cars apart. It only reads. It does not read or clear fault codes.

What stays on your phone. Live readings are shown in the app and on CarPlay, and anything not listed below as sent is not sent to us. The adapters you have paired, the link between each adapter and a vehicle, and the full VIN also stay on your phone only. The VIN is held in the phone's secure storage (Keychain on iOS, Keystore on Android).

What is sent to us. Only these:

• Odometer: the car's odometer is saved to the vehicle in your Garage (at most once an hour while connected) and with the start, overnight and end of a trip. It is also offered as the starting figure when you log a fill-up or check-in, and you can change it before saving. When you hitch up or unhitch a caravan it is sent so the km the caravan was towed are counted.
• Tank level: the level is saved to the trip as its live fuel reading, with your phone's position at the time, as it is when you enter a fuel level yourself. A fill-up the app spots from a rise in the tank level is only logged if you confirm it.
• Trip summary: while a trip is running, the app saves a summary to the trip: the AdBlue level at the start and the latest level (with where and when it was read) and the litres used, the peak oil temperature with its time and place and the minutes it was over your alert, the lowest pressure of each tyre, the km driven while connected, and the trip's average fuel economy. It appears in the trip report and is used to learn how fast the vehicle uses AdBlue.
• Vehicle settings: the alert levels, tyre minimums, tank sizes and custom codes you choose to save for the car's readings are stored with the vehicle.
• VIN: the app sends the VIN to our server once, so it can be turned into a fingerprint. We do not store the VIN. We keep a keyed hash of your account ID and the VIN, and the last six characters, so a new phone can recognise the car. You can clear it from the vehicle in your Garage.
• Works with (optional): if you turn on "Share which codes work on my car", the app sends your car's make, model and year from the catalogue, the type of adapter, and which standard and community codes gave a valid reading. This is off until you choose it (the app asks once, and you can change your mind in the vehicle's Car Connectivity (OBD) section). It carries no VIN, location, vehicle ID or account ID, and is used to show other travellers which cars a code works on.
• This reading looks wrong (only when you send it): the sheet lists what will be sent before you tap Send. It includes the reading and what your dash shows (if you enter it), the code that was read (its request and formula, and its source if it came from the OBDb community library), the last few raw replies from the car (up to five), an optional note of up to 500 characters, your car's make, model and year, your adapter's name and type, and the app and phone software versions. It does not include your VIN (VIN-like text in a note is removed), your location or your email. The report is stored against your account, one per code and car model, and a copy goes to the error tracker described under Error reports so we can check the code and pass fixes to OBDb.
• Car Connectivity Test (optional upload): on any plan, including free, the Car Connectivity Test reads your car for about 90 seconds and shows which readings it shares. The results stay on your phone unless you choose "Improve the car database". That screen lists what will be sent before you send it: your car's make, model and year (and engine, if known), your adapter's name, type and protocol, the app and phone software versions, the codes the test tried with the car's raw replies and the values they gave (including the fuel level and odometer the car reported), which readings your car supports, and, if you enter them, the fuel level and odometer shown on your dash. It does not include your VIN, your location, a vehicle ID or your account ID. VIN-like text, and any reply that contains a VIN, is removed on your phone and again on our server before the upload is stored, and only the day it was sent is kept. An identical upload sent twice is stored once. We use uploads to check which codes work on each car, and they may be published to OBDb, the open community library of car codes, under its Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0) licence.

Everything above that is saved against your account, including trip summaries, odometer readings, VIN details and wrong-reading reports, is removed when you delete your account. Works-with reports and Car Connectivity Test uploads have no account ID, so they are not removed when you delete your account. You can stop sharing them, and stop the app reading from your car, at any time by turning off the setting or unpairing the adapter.

Subscription and billing

If you buy a paid plan, your plan status and tier are stored against your account. Payments are processed by Apple in the iOS app, by Google in the Android app, and by Stripe on the web. FuelOracle never receives your payment card details. We store a subscription reference identifier to verify your entitlement.

Public share links

If you share a trip via a public link, view counts are tracked. Viewer IP addresses are never stored in identifiable form. Email addresses you enter to send share links are used once to deliver the email and are not stored.

Push notifications

If you turn on notifications, a push token that identifies your phone or browser to Apple, Google or your browser vendor is stored against your account, along with which platform it is for and your device's time zone, so reminders arrive at the right local time and quiet hours are honoured. The token is removed when you turn notifications off, sign out on that device, or delete your account, and when the device reports it can no longer receive them.

On Android, Google's Firebase messaging library also creates an identifier for the app installation so that Google can deliver notifications to it.

Passkeys

If you register a passkey, only the public credential is stored. Your private key never leaves your device.

Login IP addresses

When you sign in, the IP address of the login attempt is recorded against your account for security purposes. Login records are retained for 7 days and then automatically purged. No IP address data is shared with third parties. IP-based threat detection is handled entirely on our own infrastructure.

Server logs

Standard web server logs may record your IP address (IPv4 or IPv6), the address you requested, and the browser or app version your device reports, for operational and security purposes. These logs are kept for up to 30 days and then deleted.

Error reports

If the app or website hits an error it can send a report to a server we run ourselves in Sydney. A report contains the error message, the technical trace of where it happened, the app version, your device model and operating system version, and a short list of recent app actions. We remove trip details, locations, email addresses and search text before a report leaves your device, and we do not store your IP address with it. Reports are kept for 30 days, are used only to fix faults, and are not shared with anyone.

AI assistants

On a paid plan you can connect an AI assistant, such as Claude or ChatGPT, to your FuelOracle account. Nothing is connected unless you approve it on the FuelOracle connection screen, which names the app and what it will be able to do.

A connected assistant can read and change your FuelOracle data within those permissions: trips and their fuel plans, vehicles and caravans, fuel prices and places you look up, and your account preferences. This includes the car readings saved to your trips and vehicles, such as odometer figures and the trip summary described under Car Connectivity (OBD). It cannot see or change your password, email address, passkeys, billing or payment details, and it cannot delete your account. What the assistant receives is handled by the company that runs it under its own privacy policy (for Claude, Anthropic; for ChatGPT, OpenAI). FuelOracle does not receive your conversations with the assistant.

For each request an assistant makes we record which app made it, which operation it ran, whether it succeeded, how long it took and the network address it came from (normally the assistant provider's servers). We do not store what the assistant sent or what we returned. These records are kept for 90 days and are used for security and to fix faults.

We tell you by email, in the app and by push notification whenever a new assistant is connected. You can disconnect any assistant at any time in Settings under AI assistant access, which deletes its access at once. Every connection also ends when you change or reset your password, turn assistant access off, or delete your account.

Usage analytics

This website and the web app (fueloracle.app) use our own self-hosted copy of Umami to see how they are used. The iOS and Android apps include no analytics. Error reports are described below.

Umami records the pages you view, where you came from, what you click or search for on the blog, your browser and device type, your approximate location from your IP address (the address itself is not stored) and how fast pages load. On this website a sample of visits also records where people click and how far they scroll, for heatmaps. Codes, tokens and searches are removed from web addresses before anything is sent.

In the web app, while you are signed in, Umami also records your account ID and plan, and the amount of any plan you buy, on the web, in the App Store or on Google Play.

There is no third-party tracking and there are no third-party cookies. Analytics data stays on our own servers and is never shared or sold.

What we do NOT collect

• Payment card numbers or banking information - payments are processed by Apple (iOS app), Google (Android app) or Stripe (web) and we never have access to your card details
• Background or continuous device location - the iOS and Android apps only access location when you explicitly tap a button, and only in the foreground
• Your car's full VIN - it stays on your phone, and we keep only a keyed fingerprint and the last six characters
• A running log of your car's readings - only the figures listed under Car Connectivity (OBD) are sent, and fault codes are never read
• Advertising or marketing data
• Data from third-party advertising networks, third-party tracking or third-party cookies

Data sharing

Your data is not sold, shared or disclosed to third parties except:

• Fuel price data is fetched from Australian state government APIs to provide pricing information.
• Route calculations are performed on our servers using a self-hosted OSRM (Open Source Routing Machine) instance. No routing data is sent to third-party services.
• Address search uses Geoapify (geoapify.com), a commercial geolocation service. Queries are sent from our servers to Geoapify's API - your search terms and coordinates may be processed by Geoapify. No personally identifiable information is included beyond the location text or coordinates you enter. Geoapify's privacy policy is available at geoapify.com/privacy-policy.
• Map tiles are served from our own infrastructure using tileserver-gl with OpenStreetMap data. No map tile requests are sent to third-party services. OpenStreetMap data is © OpenStreetMap contributors, available under the Open Database Licence (ODbL).
• Google Places API is used to enrich fuel station details (name, phone, hours). Requests are made from our servers.
• Purchases made in the iOS and Android apps are managed through RevenueCat (revenuecat.com). Your FuelOracle account identifier and your App Store or Google Play purchase receipts are shared with RevenueCat solely to verify and manage your plan status. RevenueCat's privacy policy is available at revenuecat.com/privacy.
• Purchases made on the web are processed by Stripe (stripe.com). Your email address and payment details go to Stripe directly; we store only the Stripe customer and subscription identifiers. Stripe's privacy policy is available at stripe.com/au/privacy.
• Push notifications to the iOS and Android apps are delivered through Expo (expo.dev), which passes them to Apple or Google. Expo receives your device's push token and the text of each notification, which can include the name of a trip. Expo's privacy policy is available at expo.dev/privacy. Notifications to the web app go directly to your browser vendor.
• If you connect an AI assistant, the data it reads from your account goes to the company that runs that assistant (for Claude, Anthropic; for ChatGPT, OpenAI) and is handled under that company's privacy policy. Only assistants you approve can connect, and you can disconnect them at any time.
• If the Android app stops responding or closes unexpectedly, Google Play may collect a crash or performance report from your device. We read those reports through Expo (expo.dev), which builds and submits the apps for us, so Expo can access them too. The reports are diagnostics produced by Google, not information the app sends us, and they are not linked to your FuelOracle account. Expo's privacy policy is available at expo.dev/privacy.

Data retention

Your account data is retained until you delete your account. On deletion, all your trips, vehicles, passkeys and profile data are permanently removed. Invite tokens you created that have been used are anonymised. Readings from your car that are saved against your account, including "This reading looks wrong" reports, go when you delete your account. Records of AI assistant requests are kept for 90 days, server logs for up to 30 days and error reports for 30 days.

Your rights

You can:

• Export your trip data as PDF or GPX at any time
• Delete your account and all associated data via Settings → Danger Zone
• Update or remove your home location and profile photo at any time
• Revoke any active share links at any time
• Turn push notifications off, or choose which kinds you receive and when, in Settings

Security

• Passwords are hashed using a memory-hard algorithm resistant to brute force
• All connections use HTTPS/TLS
• Account lockout protects against repeated failed login attempts

Contact

For privacy enquiries contact: privacy@fueloracle.com.au. For help with FuelOracle, including a connected AI assistant: support@fueloracle.com.au.

Changes

This policy may be updated from time to time. Continued use of the app after changes constitutes acceptance of the updated policy.

🔒 Fields marked with a padlock are encrypted at rest. Encrypted data cannot be read without the server's encryption key, protecting your information in the event of unauthorised database access.