Privacy Policy

account_circle 1. Who is responsible for your data

The data controller is FillRadar. For privacy questions, rights requests, complaints or account deletion, email support@fillradar.co.uk.

database 2. Data we process

• Account data: your email address, Firebase user ID, sign-in provider and authentication or security records. If you choose Google sign-in, Google may supply basic profile information permitted by you, such as an account identifier, email, display name or profile photo.
• Location and searches: your approximate or precise device location when you grant Android location permission, and a postcode, town, route start or destination you submit. Device location is accessed only while FillRadar is open and in use. We use it to return nearby or on-route forecourts, position the map and save the last foreground area for home-screen widgets. FillRadar does not request background location access.
• Route allowance: for signed-in users, we keep the Firebase user ID, the date and non-readable hashes of route searches used that day to enforce the free daily allowance.
• Saved choices: saved forecourt identifiers, vehicle fuel type, tank or battery capacity, fuel or electric efficiency, charging connectors, an optional vehicle name you type, and theme stored on your device. While you are signed in, your vehicles are also stored on our Firebase server against your Firebase user ID, so the same garage appears when you sign in on another device; signing out leaves them on that device, and deleting your account deletes them. Signed-in route users may also store route endpoints, route preferences, station identifiers and price-alert settings on our Firebase server. Signed-in users with saved forecourts also have the weekly insights we send them stored against their Firebase user ID: short statements about those forecourts and the ones around them, kept for six months; deleting your account deletes them.
• LPG reports you submit: no LPG price feed exists in the UK, so any LPG price shown in the app was typed in by a driver or added from another published source and shown with its date. When you report a price, mark a site as unavailable, or confirm somebody else's report, we store the site identifier, the price or status, the time and your Firebase user ID. The price itself, its age and the number of confirmations are shown to other users; your identity is not, unless you choose to show your name (see Showing your name below). When you report that a forecourt sells LPG, we store the forecourt identifier, the time and your Firebase user ID; the forecourt then appears on the LPG map credited to FillRadar drivers, never to you by name. When you suggest an LPG place that is not on the map, we store what you entered (its name, the position of the pin, and any address, postcode, phone number, opening hours and price) in our list of LPG places without your account, and keep a separate record of your Firebase user ID, the time and the name of the place so we can limit how many places one account suggests a day. The place appears on the map only after FillRadar has checked it by phone or in person, and is never credited to you by name.
• Boat fuel reports you submit: when you report a diesel or petrol price at a boat fuel point, say which duty declaration a diesel price was quoted under, mark a product as unavailable, or confirm somebody else's report, we store the site identifier, the product, the declaration, the price or status, the time and your Firebase user ID. As with LPG, the price, its age and the number of confirmations are shown to other users; your identity is not, unless you choose to show your name.
• Report checks: to keep LPG and boat fuel prices honest, when you report or confirm we check whether your email address is confirmed or you signed in with Google, how long your account has existed, and whether it has been restricted. With each report we store whether it was shown at once or held until another driver confirmed it, and why. When reports look like abuse (an account reaching its daily limit, several new accounts reporting the same site, or one site's price changing back and forth) the reports and the Firebase user IDs behind them are flagged for an administrator to review.
• Contribution points: when a price, availability report or confirmation of yours reaches the map, or FillRadar keeps a forecourt or place you added, your account earns points. We store, against your Firebase user ID, a running total, a count of each kind, and a list of what earned them (the kind, the time, the layer and the site identifier), so points can be taken back if the report is withdrawn or reversed. Your profile shows your total, your level, how many of each you have done, a weekly chart of the last twelve weeks, and how your total compares with other contributors as a percentage. Nobody else sees your points, and there is no public table of contributors.
• Showing your name: in Contributions in your profile you can turn on "Show my name on cards". It is off unless you turn it on. While it is on, the prices and availability reports you send, and the prices you confirm, are shown to other users as reported or confirmed by the part of your account email address before the @ (without any +tag), instead of "a driver". We store that name and your choice against your account. Turning it off takes your name off the cards within about ten minutes; deleting your account removes it, your points and the list behind them.
• Notification and plan data: a Firebase Cloud Messaging device token, route-alert delivery records and a server-controlled Free or Premium entitlement used to enforce feature limits.
• Technical and security data: IP address, device or app integrity information and request diagnostics processed by Firebase, Google Play Integrity and our cloud functions to operate and protect the service.
• Anonymous usage counts: when a search resolves to a town, when you plan a route, or when you load an area of the map, we add one to a monthly tally for that town or for a coarse map cell of roughly a kilometre. Alongside the count we record which fuel or charging view was open, the hour of the day, whether a station or charger was saved and which chain or charging network it belongs to, and, for a route, only how long it was as a broad band: under 10 miles, 10 to 30, 30 to 100, or over 100. These tallies are not linked to your account, device or session. We do not keep the text you typed, your precise position, which particular station you saved, the time to the minute, or a route's start and destination as a pair; each end of a route is counted separately. They tell us only where and when the app is busy and which drivers use it, which If a search for LPG, boat fuel or a charger finds nothing within a short distance, that map cell is counted as well, which shows where supply is missing. Separately, for each forecourt, charger, LPG or boat fuel point we count per month how many times its card was opened, directions to it were requested, or it was saved. These place counts belong to the place: they hold no account, device or time finer than the month. They tell us only where and when the app is busy, which drivers use it and which places they head for, which helps us decide where to promote it and may be shared with fuel retailers, charging networks or suppliers as totals.
• App usage counts: each time the map is on screen we count, per day, which fuel, charging, LPG or boat fuel view it showed and how long it stayed on screen, rounded into broad bands from under 10 seconds to over 10 minutes. We also count, per day, the steps of getting started: whether the welcome pages were finished or skipped, whether location and notification permissions were allowed, the first saved place, first alert and first sign-in on a device, and widgets added or removed; how often the charging time and cost calculator was used; how many notifications of each kind were sent, accepted by Firebase for delivery and opened; and how many “tell me when one is free” alerts were set, found a free charger (and after how many minutes) or ran out. Per month, we count the saving a comparison of two forecourts showed on one fill, as a band. These counts hold no account, device identifier, position or station. Whether a “first” step has already been counted is remembered on your device only, so that it is counted once.
• Account activity: when you are signed in, the app tells our server once a day that the account was used. Against your Firebase user ID we store the date the account was created, the dates on which it was used (the most recent 120) and the version of the app. We use this only to count how many accounts are active each day, week and month, and how many come back after a day, a week and a month. Only totals and percentages are taken from it, never the record of any one account. Administrator and test accounts are left out of these figures. You can avoid it by using the app without signing in, and it is deleted with your account.
• Website analytics & cookies: when you visit our website (fillradar.co.uk), if you accept analytics cookies via our consent banner, Google Analytics 4 (GA4) collects anonymized technical data (including anonymized IP, device and browser type, approximate location, page views, session duration, and referring URLs). This data is aggregated and used exclusively to monitor site performance and improve user experience. If you decline, no Google Analytics cookies or scripts are loaded. Separately, our pages load Vercel Web Analytics, which counts page views and referrers without cookies and does not follow you across other sites, whether or not you accept cookies; we rely on our legitimate interest in understanding how the website is used. Our fonts and images are served from our own domain, not from Google.
• Demo video: nothing is loaded from YouTube until you press play on the demo video on our home page. When you do, the video is served from YouTube's privacy-enhanced domain (youtube-nocookie.com) and Google may process your data under its own privacy policy.
• Optional app diagnostics: if you choose “Help improve FillRadar” in the Android app, Firebase Analytics records coarse actions such as which app section was viewed, whether a fuel or charger card was opened, whether a search succeeded, which welcome pages and tabs were viewed, whether a comparison showed a saving, a widget was set up, a notification was opened or the charging calculator was used; Crashlytics receives crash and stability diagnostics; and Firebase Performance Monitoring measures app start, screen rendering and network performance. We do not add precise location, search text, addresses, station identifiers, account identifiers, email addresses or the Android advertising ID to these events.

gavel 3. Why we use data and our lawful bases

• To provide searches, maps, accounts and saved features you request: performance of our contract with you, or steps taken at your request before entering a contract.
• To check LPG and boat fuel reports, hold back or remove inaccurate ones and restrict accounts that submit false data: our legitimate interests in keeping the prices other drivers rely on accurate. Holding a report until somebody confirms it is automatic; restricting an account is decided by a person.
• To count contribution points and show you your own: our legitimate interests in thanking and encouraging the drivers who keep prices accurate. Showing your name on cards: your consent, which you give and withdraw with the setting in your profile.
• To secure the service, prevent abuse, diagnose failures and control cloud costs: our legitimate interests in operating a safe and reliable service.
• To see where, when and by which kind of driver the app is used, which chains are popular, and to plan where and when to promote it: our legitimate interests. These counts are aggregated at the moment they are recorded and hold nothing that identifies you.
• To measure how the app is used and kept, to improve it and to report figures about the service to investors, prospective investors and partners: our legitimate interests in running, developing and funding the service. Account activity is limited to the dates the app was used and its version; everything else is counted without identifying anyone. You may object to account activity being recorded by contacting support@fillradar.co.uk.
• To process website analytics via Google Analytics on fillradar.co.uk: your consent provided via our cookie banner. You can withdraw or decline consent at any time.
• To receive optional Firebase Analytics, Crashlytics and Performance Monitoring data in the app: your consent. These services remain disabled until you allow them, and you may withdraw that choice in Profile at any time.
• To access device location: only while FillRadar is open and after Android grants the foreground permission you choose. FillRadar does not request location when the app is closed or not in use. You can search by postcode or place instead.

We do not make decisions about you using solely automated processing that produces legal or similarly significant effects.

pin_drop 4. How location and caching work

Location or a geocoded search centre is sent to our Firebase server to request forecourts within the selected area. FillRadar does not request or access your device location in the background. Home-screen widgets use the last foreground location saved on your device. Refreshing a widget may request current station or charging-price data for that saved area, but it does not retrieve a new device location. Route searches send the start and destination to our server and Google Maps Platform to calculate driving geometry and the alternative routes Google offers. Route geometry and resolved place labels may be held in a shared server cache for up to 24 hours. We do not store the readable start or destination in your daily allowance record; it contains route hashes and is linked to your account solely to enforce the allowance. If you save a route, its readable endpoints and the station identifiers within the selected corridor remain associated with your account until you delete the route or account.

cloud_sync 5. Service providers and data sources

• Google Firebase and Google Cloud: authentication, app-integrity checks, server functions, protected storage, plan enforcement and Firebase Cloud Messaging notifications; and, only with your consent, Firebase Analytics, Crashlytics and Performance Monitoring.
• Investors and partners: we may share totals and percentages about the service, such as the number of accounts, active accounts, how many keep using the app, map views, notifications sent and opened, and drivers' reports. These figures never identify anyone, and a group of fewer than 10 is not reported.
• Google Analytics (Google LLC): website measurement and analytics on fillradar.co.uk, operated with anonymized IPs and loaded only after consent.
• Vercel: hosts fillradar.co.uk and provides cookieless website analytics.
• Google Maps Platform: maps, geocoding of places you submit, resolving which town a coarse map cell of roughly a kilometre sits in, and calculation of requested driving routes.
• Google and Meta: only if you choose their sign-in method; their handling of your account is governed by their own privacy terms.
• postcodes.io (Ideal Postcodes Ltd): when you move the pin in the form for suggesting a new LPG place, the app sends the pin's coordinates from your phone to postcodes.io to look up its postcode. Like any web request, it also reaches them with your device's IP address. No account or device identifier is sent. Not used in Northern Ireland.
• UK Government Fuel Finder: forecourt, brand, amenity and reported fuel-price data, including which forecourts declare an LPG pump. FillRadar does not send Fuel Finder your account identity.
• Open Charge Map: charging point locations, connector details and community-reported tariffs, licensed under CC BY-SA 4.0.
• UK Government greenhouse gas conversion factors (Department for Energy Security and Net Zero, 2026): the kilograms of CO₂ per litre of petrol, diesel and HVO behind the emissions shown for a drive to a forecourt and in comparisons. The published figures are built into the app; nothing about you is sent to DESNZ. Contains public sector information licensed under the Open Government Licence v3.0.

These providers may process data outside the UK. Where required, transfers are protected by the provider's contractual safeguards and applicable UK data-transfer mechanisms.

history 6. Retention

• Account information is kept while your account exists. After we initiate deletion, Firebase states that authentication data is removed from live and backup systems within 180 days; logged authentication IP addresses are generally kept for a few weeks. You have the right to request deletion of your account and personal data at any time — step-by-step instructions can be found on our Account Deletion page.
• Saved forecourts, preferences, cached map data and the last foreground location remain on your device until they are replaced, you remove them, clear app data or uninstall the app.
• Shared forecourt and search caches are refreshed or replaced according to operational cache rules. Security and request logs are retained according to the relevant cloud provider's documented schedules and only as long as reasonably necessary.
• Account activity records are kept while the account exists, hold at most the 120 most recent days on which it was used, and are deleted with the account. App usage counts and daily summaries built from them are kept for up to 400 days.
• Shared route geometry is cached for up to 24 hours. Daily route-allowance records are operational records that may be deleted after they are no longer needed for limits, security or dispute handling.
• Saved routes and their alert preferences are retained while your account exists or until you delete them. Device notification tokens are retained until they expire, are rejected by Firebase, or are deleted with the associated account data.
• Anonymous town, map-cell, route-length and per-place tallies are kept for about 13 months and then deleted automatically. Because they identify no one, they cannot be traced to you or removed on request.
• Website analytics records in Google Analytics are retained in accordance with standard GA4 data-retention settings (14 months).
• Optional Firebase Analytics, Crashlytics and Performance Monitoring records follow the retention controls and operational schedules configured for our Firebase project and are retained only for product analysis, stability and performance diagnosis.
• LPG reports are kept as a record of what was claimed about a site and when. If you delete your account, your identifier is removed from them and the reports themselves remain, because other drivers rely on the price and its date; your confirmations of other people's reports are deleted outright. Boat fuel reports and confirmations are treated the same way. Records that an account is restricted from reporting, and alerts raised for review, are kept while they are needed to protect the service. If you believe your account was restricted in error, contact us and we will review it. Your suggestions of new LPG places are kept the same way. Your contribution points, the list of what earned them and your name choice are kept while your account exists and are deleted with it.
• If you contact us, correspondence may be retained as needed to answer the request, resolve disputes and meet legal obligations.

tune 7. Cookies, your choices and rights

Website Cookies: When visiting our website, we use essential storage for your preferences and optional Google Analytics cookies for audience measurement. Vercel Web Analytics uses no cookies. You can accept or decline analytics cookies at any time via the on-screen banner, or reset your choice by clearing your browser's local storage.

Mobile App Controls: In the Android app, you may deny or revoke location permission, use the app as a guest, remove saved forecourts, disable notifications, turn optional app diagnostics on or off under “App Analytics & Diagnostics” in Profile > Privacy & Data, or sign out. Turning diagnostics off stops future collection, resets local Analytics data and deletes unsent crash reports.

Depending on the circumstances, UK data-protection law gives you rights to be informed, access, correct, erase, restrict or port your data, and to object to processing based on legitimate interests. You may also complain to us and to the Information Commissioner's Office (ICO).

child_care 8. Children

FillRadar is not directed to children under 13 and we do not knowingly collect their personal data. A parent or guardian should contact us if they believe a child has created an account.

lock 9. Security and changes

We use HTTPS, Firebase access controls, Secret Manager and app-integrity checks. No system is completely secure. We may update this policy when the app, providers or law changes; the revised date will appear here. Material changes will be highlighted in the app where reasonably practicable.

mail 10. Contact

For privacy questions, rights requests or complaints, email support@fillradar.co.uk. See how to delete your FillRadar account and data.