Cookie and Similar Technologies Policy
Version 1.1 · Effective 10 October 2026 · Last updated 10 October 2026
1. What this covers
This policy explains the cookies and similar technologies we use on the DriveBuddy website, web app and mobile app (iOS and Android), what they're for, and how you can control them. It sits alongside our Privacy Policy, which explains what we do with personal information more generally.
"Cookies and similar technologies" covers:
- cookies in your browser
- local storage and session storage in your browser
- information our mobile app stores on your phone, such as sign-in tokens and settings
- software tools (SDKs) built into the app that store or read information on your device
The same principles apply everywhere. We only use what's strictly necessary without asking you. Everything else needs your choice first.
2. The short version
We use these technologies to keep you signed in, to keep payments secure, and, only if you allow it, to understand how DriveBuddy is used so we can improve it. We don't use advertising cookies or your phone's advertising ID, we don't track you across other companies' websites or apps, and we don't share your data with advertisers.
3. What we use
3.1 Website and web app
Strictly necessary. These make the service work. Without them you can't sign in or pay, so they can't be switched off.
| Set by | Purpose | Roughly how long |
|---|---|---|
| DriveBuddy / Supabase | Keeping you signed in and maintaining your session | Session, and up to 1 year where you choose to stay signed in |
| DriveBuddy | Remembering security and login state | Session |
| Stripe | Processing payments and detecting fraud | Up to 1 year |
Stripe sets cookies on pages with payment functionality as part of its fraud prevention. That's a security function, not advertising.
Analytics. These help us understand how DriveBuddy is used: which features people reach, where they get stuck, what breaks. They are off until you accept them.
| Set by | Purpose | Roughly how long |
|---|---|---|
| PostHog | Product analytics: usage, feature adoption, errors | Up to 1 year |
Our analytics run in the European Union and are first-party only. We use them to improve DriveBuddy itself, not to track you across other websites or apps, and we don't build advertising profiles.
Preferences.
| Set by | Purpose | Roughly how long |
|---|---|---|
| DriveBuddy | Remembering your settings and display choices | Up to 1 year |
3.2 Mobile app
The DriveBuddy mobile app doesn't use browser cookies. It does store information on your phone and uses a small number of software tools.
Strictly necessary. These can't be switched off while you use the app.
| Set by | Purpose | Roughly how long |
|---|---|---|
| DriveBuddy / Supabase | Keeping you signed in. Sign-in tokens are held in your phone's secure storage (iOS Keychain, Android Keystore) | Until you sign out, or delete the app or your account |
| DriveBuddy | Security and session state | Session |
| Stripe | Processing payments and detecting fraud. Stripe's software in the app may read basic device information while you pay | While you use payment screens; after that, Stripe's own policy applies |
| Expo | Checking for and delivering app updates. Expo receives your app version and basic device details | Each time the app checks for an update |
Analytics. The mobile app doesn't currently run any analytics. If we add them, we'll ask for your choice first and update this policy before they go live.
Features you switch on.
| Set by | Purpose | Roughly how long |
|---|---|---|
| Expo, Apple and Google notification services | Delivering booking reminders and updates to your phone, using a device token | Until you turn notifications off or sign out |
| DriveBuddy | Remembering your settings in the app | Until you delete the app or your account |
Notifications, location sharing and photo or camera access only work if you allow them in your phone's own settings. Location sharing is off by default.
3.3 What we don't use
No advertising cookies or advertising IDs. No third-party tracking pixels. No social media trackers. No crash reporting SDKs. No device fingerprinting. If we add anything in these categories, we'll update this policy and ask for your consent where the law requires it, before it goes live.
4. Your choices
Website and web app. Our cookie banner lets you accept or reject non-essential cookies when you first visit. You can change your mind at any time using the cookie settings link in the footer. Your browser also lets you block or delete cookies. Blocking all cookies will stop you signing in, and blocking Stripe's cookies may stop payments working.
Mobile app. The app doesn't currently run analytics, so there's no analytics choice to make. Notifications, location and photo access can be switched off in your phone's settings. Signing out removes your sign-in from your phone, and so does deleting the app. You can also delete your account.
Everywhere. Strictly necessary items can't be turned off, because the service doesn't work without them.
5. Learners under 18
For learners under 18 we collect less analytics data as standard. Section 9 of our Privacy Policy explains what else is different.
6. Changes to this policy
We'll update this policy when our use of these technologies changes. Every version has a number and a date.
| Version | Date | Change |
|---|---|---|
| 1.1 | 10 Oct 2026 | Extended to cover the mobile app; added mobile storage, Stripe app software and notification tokens; the app currently runs no analytics; contact address aligned with the Privacy Policy |
| 1.0 | 28 Aug 2026 | First published version |
7. Contact
Questions about this policy: support@drivebuddy.uk.
To complain about how we've handled your data, email the same address with "Data protection complaint" in the subject line. We'll acknowledge within 30 days. You can also complain to the Information Commissioner's Office at ico.org.uk.