Full Privacy Policy - Version 8 - August 2026 - Driverr Technologies Ltd - Company No. 17184545
Download full Privacy Policy (PDF)Previous version: June 2026 (v7)
What changed in this version:
Welcome to Driverr. This Privacy Policy explains how Driverr Technologies Ltd ('Driverr', 'we', 'us' or 'our') collects, uses, stores and protects your personal data when you use our mobile application and related services (collectively, the 'Service').
Driverr Technologies Ltd is registered in England and Wales with company number 17184545. We are registered with the Information Commissioner's Office (ICO) as a data controller.
By using Driverr, you agree to the collection and use of information in accordance with this Privacy Policy. If you do not agree with any part of this policy, please do not use our Service.
The data controller responsible for your personal data is:
When you create a Driverr account, we collect:
When you use the app, we collect data you voluntarily enter:
Driverr uses your device's GPS location for the following purposes:
Location data is processed in real-time on your device. Your GPS coordinates are passed to Open-Meteo solely to retrieve relevant weather data - they do not store or retain your coordinates. We do not track your location continuously or in the background. Location data is not stored on our servers beyond what is explicitly logged in your shift records. Push notification tokens are stored locally on your device and used only to deliver shift end reminders and PCO renewal alerts. We do not use push notification tokens for marketing purposes.
If you sign in with Google OAuth, we receive from Google:
We do not receive your Google password. Google authentication is handled securely by Supabase Auth and Google's OAuth 2.0 system.
When you use the Service, we may automatically collect:
Push notification token - stored locally on device - used only to deliver shift reminders and PCO renewal alerts If you use the native iOS or Android app, a separate device push token is stored to enable notification delivery via Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM), used only for the same purposes: shift reminders and PCO renewal alerts.
Your personal data is stored on Supabase, a cloud database service hosted in the European Union (Ireland - West EU region). This means your data is stored within the UK GDPR jurisdiction and is subject to EU data protection standards. Receipt images and financial documents are stored in Supabase Storage in the same West EU Ireland region.
In the event of a personal data breach likely to result in a risk to your rights and freedoms, we will notify the ICO within 72 hours. We will also notify affected users without undue delay where the breach is likely to result in a high risk to their rights.
We retain your personal data for as long as your account is active. When you delete your account, we permanently delete all your personal data within 24 hours including all shift records, ride records, expense records, EV charging records, your driver profile and your authentication account. Deletion request audit records are retained for 90 days for legal compliance purposes. Receipt images stored in Supabase Storage are also permanently deleted within 24 hours of account deletion.
To exercise any of these rights, contact us at hello@driverr.app. We will respond within 30 days.
If you are located in the EU, your data is protected by GDPR. Our data storage in Ireland means your data remains within the EU. All rights in Section 6 apply to EU users.
We do not sell your personal data. California residents have additional CCPA rights including the right to know what data we collect, the right to delete it, and the right to opt out of data sales (we do not sell data). Contact hello@driverr.app to exercise California privacy rights.
Your data is protected under PIPEDA. You have the right to access your personal information and challenge its accuracy. Contact hello@driverr.app to exercise these rights.
UK GDPR compliance meets or exceeds data protection standards in most countries globally. Contact hello@driverr.app with any questions about your local data protection rights.
Database and authentication provider. Data stored in West EU Ireland. Privacy policy at supabase.com/privacy Supabase Storage is also used to store receipt images uploaded by drivers. All stored data is subject to Row Level Security ensuring drivers can only access their own data.
We use Transport for London's API to display live tube and rail disruption status. This feature is only active for drivers in London. No personal data is shared with TfL.
We use Open-Meteo's weather API to display current weather conditions based on your GPS location. Your coordinates are sent to Open-Meteo only to retrieve relevant weather data - they do not store or retain your coordinates. No personal identifying information is shared with Open-Meteo.
We use Ticketmaster's API to import local events for your registered city. No personal data is shared with Ticketmaster.
Stripe - stripe.com - Payment processor for Pro subscriptions. When you subscribe to Driverr Pro your payment is processed by Stripe Inc. Stripe collects and processes your payment method details including card number, expiry date and billing address. We never store your full card details on our servers - Stripe handles all payment data under PCI DSS Level 1 compliance, the highest level of payment security. Stripe stores a secure payment token linked to your account to process recurring subscription payments. You can manage, update or cancel your subscription at any time through the Stripe Customer Portal accessible from More - Account - Manage subscription. Stripe's privacy policy applies to all payment data - stripe.com/privacy. Stripe is certified to the EU-US Data Privacy Framework. Legal basis for processing: contract performance. If you request a refund, we review your account and usage data (subscription dates, feature usage) to assess the request. Refund decisions and processing are handled manually by Driverr. See our Refund Policy at driverr.app/refunds for eligibility and timing.
When our B2B partner network launches, additional data processing will occur. This Privacy Policy will be updated and all users notified before the B2B network goes live.
When you contact support@driverr.app, your message may be processed by an AI system to help classify your query and draft a response. This uses Google Workspace to receive and store the email, and Anthropic's Claude AI model to read the message content and generate a suggested response. All AI-drafted responses are reviewed by a human (the founder) before being sent - the AI never sends a response automatically. Certain topics (refunds, complaints, account deletion, legal matters, and anything the AI is not confident about) are always escalated for manual handling and are never processed or responded to by AI. Anthropic processes this content solely to generate the response and does not use it to train its models. Anthropic's privacy policy applies: anthropic.com/privacy. Google Workspace acts as our email processor for support@driverr.app; Google's privacy policy applies: workspace.google.com/privacy.
Driverr uses browser localStorage to store strictly necessary data locally on your device including theme preference, saved home location, navigation preference, notification preference, onboarding status, driver preferences, shift data cache, active shift state, weekly target and authentication session token.
We do not use advertising cookies or third-party tracking cookies. See our full Cookie Policy at driverr.app/cookies.
Driverr is intended for licensed professional drivers aged 18 and over. We do not knowingly collect data from anyone under 18. Contact hello@driverr.app immediately if you believe we have collected data from a minor.
Driverr uses automated processing to provide direction recommendations, surge predictions, weather-based demand signals and earnings analysis. These are guidance tools only and do not constitute legally significant automated decisions. You are free to disregard any recommendation the app makes.
We will notify you of significant changes by email to your registered address and by in-app notice at least 14 days before changes take effect. The version number and date at the top of this policy indicate when it was last updated.