Privacy Policy

Who operates DriveBite

DriveBite is operated as a UK sole-trader business. The proprietor, Chris Frimley, is the data controller for the information described in this policy. Our service address is:

If you have a privacy question, request or complaint, the quickest way to reach us is through the feedback in the DriveBite app, which is also linked from our Support page. You can also email us at support@drivebite.co.uk.

Location and journey data

DriveBite is a journey utility, so it needs somewhere to search from. Here is what that involves.

• If you allow current location, DriveBite receives your latitude and longitude so it can provide Nearby or On Route. You can refuse this permission and enter a location instead.
• Custom searches, such as a postcode, town, city or destination, are used for geocoding (turning text into a place) and routing (working out the journey).
• Up to five recent destinations are stored locally in DriveBite app storage on your device, and expire after up to 365 days or until you clear them. DriveBite does not upload the recent-destination list as a stored history.
• Recent destinations are not put into analytics. Analytics never sees where you searched for or where you were going.

First-party analytics

Analytics is optional and off unless you explicitly allow it. If you allow it, DriveBite may store random visitor and session IDs and events such as:

• session start and activation
• Nearby and On Route searches
• restaurant views
• Directions clicks
• Order Ahead clicks
• feedback-submission events
• app version, page, usage context and limited campaign or referrer fields

Analytics does not include precise location, destination or search text, name, email address or feedback message content.

You can turn analytics off again inside the app. That stops future analytics and clears the local analytics identifiers on your device, but records already sent are not automatically erased by the toggle.

DriveBite does not sell analytics data to advertisers.

Feedback and reports

If you send feedback or report a problem, it may contain the bug or suggestion type, your free-text message, an optional contact email if you choose to give one, the page you were on, user-agent or device and browser information, and the app version.

Restaurant-data reports can include the restaurant, the problem type and the details you supply.

The contact email is optional. If you leave it out, we cannot reply to you personally, but your report still helps.

Providers and services currently used

DriveBite relies on a small number of providers to work. What each is used for:

• Supabase — backend data, the DriveBite routing function and first-party analytics.
• OSRM — road-routing calculations.
• Postcodes.io — postcode and place lookup.
• OpenStreetMap Nominatim — fallback place lookup.
• OpenFreeMap — map tiles for the in-app basemap on the packaged iOS and Android apps. OpenFreeMap serves map tiles built on OpenStreetMap data.
• Google Maps — the in-app basemap on the web version of DriveBite, and the handoff to external Directions.
• Restaurant operator websites and apps — the external Order Ahead handoff.

When you leave DriveBite for Google Maps or a restaurant service, that provider’s own privacy terms apply to what happens next.

Why DriveBite uses information

In plain terms, and deliberately kept cautious rather than legalese:

• Core app, location and routing: to provide the journey and location functionality you request and to operate the service.
• Analytics: only with your explicit choice to allow it.
• Feedback, reports and service security: our legitimate interests in responding to you, keeping restaurant and journey data accurate, preventing misuse and improving DriveBite.

This section is a plain-English summary, not legal advice. It describes how DriveBite handles information; it does not replace your rights under UK law.

How long information is kept

Not everything has a fixed keeping period, so where it does not, we use criteria instead:

• Recent destinations: stored locally on your device, kept for up to 365 days or until you clear them.
• Routing and geocoding caches:short-lived and operational, kept only to keep searches and routes working.
• Analytics: kept only while reasonably needed to understand and improve the service, then deleted or aggregated.
• Feedback and reports: kept while needed to investigate and respond, and for a reasonable follow-up period.
• Security and operational data: kept only as long as reasonably needed for reliability and abuse prevention.

If fixed retention schedules are adopted, this policy will be updated to say so.

Choices and rights

What you can choose, and what you are entitled to:

• Refuse the location permission and use a custom location instead.
• Allow or decline analytics, and change that choice later inside the app.
• Clear your recent destinations on your device at any time.
• Leave the contact email out of feedback if you would rather stay anonymous.

Under UK data-protection law you generally have rights to access your information, have it corrected or deleted, restrict or object to certain uses, and take your information with you where that applies. You can exercise these by getting in touch through the DriveBite app or our Support page.

If you are unhappy with how your information is handled, you can complain to the ICO, the UK’s data-protection regulator.

Children

DriveBite is designed as a journey utility for drivers and is not intended as a child-directed service. Our planned store target audience is 18 and over.

Changes to this policy

This policy was last updated on 27 September 2026. It may change as DriveBite, its providers or its features change. Material changes will be reflected here.