How Drive Zone handles your data

This is Drive Zone's full Privacy Policy for the app and website, including the limited processing used for public site access and contact routes.

Controller I Squared R Consulting LtdSupport support@drive-zone.appUpdated 7 October 2026

At a glance

The shortest useful summary before the full notice starts.

• Most operational data stays on the device unless you enable sync, request a DVLA-backed lookup, use Premium automatic DVLA refresh for saved vehicles, contact support, or use services provided through Google and Firebase.

• Cloud sync is optional and uses your iCloud account to keep supported records aligned across your devices.

• Vehicle lookup is on demand unless Premium automatic DVLA refresh is enabled for saved vehicles. The default refresh frequency is weekly, and you can change it in Vehicles settings.

• Optional diagnostics are offered as a separate choice at the end of onboarding. Google Firebase Analytics, Performance Monitoring and Crash reporting start selected, but none starts collecting until you tap Enable selected diagnostics & finish setup. Continue without diagnostics saves all three off. Existing users receive one dismissible choice; dismissing it saves all three off. You can change choices at any time in Privacy & Data. An ordinary policy or app update does not prompt again. A material change to a service’s purpose, recipient or data collected keeps that service off until you make a new choice. These choices are not UK GDPR consent. These diagnostic choices are independent of advertising choices. Firebase Remote Config uses a separate Firebase installation only while the user is advertising-eligible and UMP records the minimum permissions required for non-personalised advertising.

• Free users aged 13 or over may receive non-personalised Google adverts after agreeing to the basic device access required for them. Ages 13 to 17 receive teen ad treatment, never personalised adverts or an Apple tracking prompt. Personalised adverts for adults are optional and additionally require the relevant Google permissions, a verified or confirmed Apple adult declaration source, and Apple tracking authorisation. Declining personalisation or Apple tracking never requires Premium. New adults who decline basic ad access are offered Premium instead; zone monitoring and entry alerts pause until a choice is made. Existing free adults receive 30 days' notice before this access choice takes effect. Under-13 and unresolved-age users, and teenagers who decline basic ad access, retain free core access without Google adverts. Premium subscribers, active trial users and users in billing grace do not see adverts or receive advertising consent prompts.

Who controls Drive Zone

Contact details for privacy questions and legal notices.

Drive Zone is provided by I Squared R Consulting Ltd, which is the data controller for the personal data described in this notice.

If you have a privacy question, want to exercise your data protection rights, or need to contact us about this notice, use Help & Support > Start Help Wizard inside the app.

What this notice covers

The app does not require an account, and most live operational data is stored on your device unless you turn on an optional service.

• Using location, notifications and motion features in the app.

• Saving vehicles, zone settings, and journey history on your device.

• Optionally syncing supported records across your devices using iCloud and CloudKit.

• Looking up a vehicle registration through the DVLA lookup flow when you choose to do so, and periodically refreshing saved vehicle details if Premium automatic DVLA refresh is enabled.

• Validating Premium access, protecting backend requests with App Attest, and routing support notifications or user-requested Live Activity updates.

• Exporting a machine-readable ZIP package of the local data already stored on this device.

• Opening official payment or source links from inside the app.

• Showing non-personalised adverts to eligible free users aged 13 or over or, with separate permissions, personalised adverts to eligible adults after the applicable privacy choice, handling advertising privacy choices, requesting a privacy-preserving age range where available, and asking for Apple tracking permission only when adult personalised advertising is available.

Data Drive Zone uses

These are the main categories of personal data processed by the current implementation.

• Location data: current location, background location updates, location accuracy, and app-calculated zone entry points.

• Journey history: zone name or ID, date and time of entry, speed at entry, entry coordinates, payment status, and a vehicle snapshot used for the zone assessment.

• Vehicle information: registration number, nickname, make and model details, and DVLA-derived vehicle data if you choose to save it.

• Motion activity: whether the device reports walking, cycling, stationary, or automotive movement. This is used to improve driving-context filtering.

• Notification settings: whether alerts, badges and time-sensitive notifications are enabled.

• Local settings and preferences: visible zones, zone colours, mute and reminder preferences, payment link behaviour, map settings, and selected active vehicle.

• Cloud sync data when you enable that feature: synced copies of supported records stored in your Apple iCloud private database, plus the CloudKit record identifiers, zone metadata, per-record timestamps, and local encrypted sync-state files needed to keep your devices aligned.

• Support and rights-handling data when you contact Drive Zone: the message you send, any attachments you add, the request type, support-case status history, and support-notification delivery metadata linked to your installation.

• Service access and integrity data: an installation identifier, App Attest key, receipt and counter state, short-lived challenge or session metadata, pseudonymous routing scope, and security or rate-limit events used to protect Drive Zone services.

• Purchase and entitlement data: App Store subscription transaction identifiers, product ID, Premium entitlement state, expiry and renewal status, signed App Store metadata, and App Store Server Notification replay records used to provide and reconcile access. Optional Tip Jar purchases are separate repeatable consumable purchases processed by Apple. Drive Zone checks the verified StoreKit tip product ID and completion on your device to show a thank-you; it does not send tip transaction details to its backend or change Premium entitlement.

• Notification and Live Activity routing data: APNs device tokens, support push-channel state, Live Activity push tokens, active-session identifiers, and delivery history needed to start, update, end, or route a user-visible update.

• Help, feedback and rights-request data: self-service events used to improve support routing, and the minimum request, verification, timing and outcome records needed to handle or evidence a data-protection request.

• Analytics information, if Analytics is allowed: fixed names for the Drive Zone destinations you view; completion of onboarding, successful vehicle addition, map-search result selection, successful subscription purchase, and successful support-request creation; app version, Firebase identifiers, and coarse technical information. Drive Zone does not send advert events to Firebase Analytics and disables IDFV collection.

• Performance information, if Performance Monitoring is allowed: approved app-start and in-app workflow timings, coarse success or failure measurements, and redacted measurements for approved Drive Zone relay routes. Automatic app-start, screen and URLSession monitoring is disabled. Dynamic support case, message and attachment identifiers are replaced with placeholders.

• Crash information, if you save Crash reporting as allowed or explicitly send a locally held report: restricted crash stack traces, app and device details, Crashlytics installation identifiers and Firebase installation identifiers. Drive Zone does not add an app user ID, personal custom keys, app-authored diagnostic logs or Analytics breadcrumbs.

• Remote Config information after the minimum advertising permissions are granted: a separate advertising-only Firebase installation identifier, IP address, app details and configuration-fetch information needed to deliver advertising controls.

• Advertising age eligibility: on iOS 26 and later, Apple may share only a privacy-preserving age range and declaration-source category after a system request; if that result is unavailable or declined, or on iOS 18.4 to 25, Drive Zone asks only whether you are under 13, 13 to 17, 18 or over, or prefer not to say. The selected band is stored on this device. Drive Zone does not store an exact age, birth date, or Apple's range bounds.

• Advertising and consent information for confirmed free users: IP address, approximate location inferred by Google, device or app-scoped identifiers, local storage, adverts shown, advert interactions, consent choices, frequency-control information, reporting data, and information used for security and invalid-traffic prevention.

• Drive Zone does not add live location, journey-history entry events, zone or vehicle identifiers, registration numbers, vehicle details, search text or results, favourites, recent-place values, coordinates, permission states, support text or classifications, attachment filenames, transaction identifiers, prices, or user identifiers to Firebase or advertising events. Google and its advertising partners may still process the technical information described above under their own controls and terms.

How Drive Zone uses this data

We use only the data needed to run the features you choose to use.

• To detect likely entry into a charging zone and create an entry in your journey history.

• To estimate whether your active vehicle may be chargeable, exempt, compliant, or needs review against the zone rules bundled in the app.

• To show local alerts, badges, and reminder notifications.

• To save your selected vehicles, zone preferences, and local history between app launches.

• To sync supported records such as vehicles, entry history, achievements, settings, and zone override data across your own devices using iCloud if you enable cloud sync.

• To fetch DVLA-backed vehicle data when you ask for a registration lookup, and to refresh saved vehicle details periodically if Premium automatic DVLA refresh is enabled.

• To generate an export ZIP containing the vehicles, entry history, settings, zone preferences, current account state, and export metadata already stored on this device.

• To keep the sync and lookup services stable using short-lived challenges, time-limited refresh sessions, readiness checks, bounded caching, retry controls, and rate limiting.

• To validate Premium access, reconcile App Store transactions and server notifications, and recover the entitlement state attached to the current installation.

• To authenticate and protect backend requests with App Attest and pseudonymous installation or routing identifiers.

• To route support replies and start, update, or end Live Activities requested through an active driving session.

• To handle support, feedback and data-protection requests and retain the minimum evidence needed to demonstrate their outcome.

• To understand which fixed, named Drive Zone destinations are viewed and whether onboarding, vehicle addition, map-search selection, subscription purchase, or support-request creation succeeds, if Analytics is allowed.

• To measure approved app workflows and redacted Drive Zone relay performance if Performance Monitoring is allowed.

• To diagnose crashes through restricted Crashlytics fault reporting only after you save the reviewed choice without objecting, or when you explicitly send an unsent report, and to retrieve Boolean advertising switches through a separate Remote Config installation only while advertising permissions and eligibility remain valid.

• To display non-personalised adverts to eligible free users aged 13 or over only after purpose 1 consent, purposes 2, 7, 9 and 10 consent or legitimate interest, and Google vendor 755 consent. Users aged 13 to 17 receive teen ad treatment and no personalisation. Personalised adverts for adults additionally require purposes 3 and 4 consent, a verified or confirmed Apple adult declaration source, and Apple tracking authorisation. A refusal of basic ad access produces no Google advert request.

• To manage advertising privacy choices, control frequency, produce aggregated reports, protect advertising services, and detect invalid traffic.

When data leaves your device

Most data stays on the device unless you choose an action that needs an external service.

Most Drive Zone data is stored locally on your device in app storage or local settings.

Background location monitoring is intentionally used so Drive Zone can detect zone entry while the app is not open. The current implementation stores discrete entry events and supporting metadata, not route geometry or a continuous location trace.

If you turn on optional cloud sync, Drive Zone writes supported records from your device to your Apple iCloud private database using CloudKit. Drive Zone's own backend is not used for normal personal sync. Those synced records currently include vehicles, entry history, achievements, settings, and zone override data.

CloudKit and iCloud process the record identifiers, zone metadata, timestamps, and change-tracking information needed to keep your private iCloud database in sync. Drive Zone also keeps encrypted local sync-state files on your device.

Cloud sync does not copy the live location stream, motion or activity state, notification permission state, or device runtime and power state to iCloud.

When you ask Drive Zone to look up a vehicle, the app sends the registration number to Drive Zone's vehicle lookup service. If Premium automatic DVLA refresh is enabled for saved vehicles, the app may also periodically send saved registration numbers through the same service. The default automatic refresh frequency is weekly, and you can change it in Vehicles settings. The service then requests vehicle data from the DVLA Vehicle Enquiry Service API.

The lookup service is implemented as an always-on relay. In the current implementation it performs readiness probing, uses a bounded response cache with a TTL currently set to about one hour, applies retry and circuit-breaker behaviour, enforces rate limits, and uses short-lived auth or session artefacts to protect the service.

If you open an official payment page or another external source link, the destination site receives the information it normally receives from your browser or in-app web view under its own terms and privacy information.

When Drive Zone uses its backend, the service may process installation and App Attest integrity data, subscription entitlement and App Store notification data, support routing metadata, user-requested Live Activity channel or session data, and pseudonymised operational events. The backend is hosted by Render in Frankfurt and is not the normal storage location for personal iCloud sync payloads.

Drive Zone offers Google Firebase Analytics, Performance Monitoring and Crashlytics as optional diagnostics. All three start selected in the choice screen, but none activates until you explicitly enable selected diagnostics. Continue without diagnostics, or dismissal of the one-time existing-user choice, saves all three off. You can change choices in Privacy & Data at any time. Routine policy and app updates do not ask again. A material change to a service’s purpose, recipient or data collected keeps the affected service off pending a new choice. The choice is not UK GDPR consent. The local record stores each service state and purpose version, legal and PECR basis, time, privacy-notice version, app version and source. Unsent crash reports remain local until you choose to send or delete them. Diagnostic choices are independent of advertising choices and remain on the default Firebase installation. Remote Config uses a separate advertising-only Firebase installation only while the permissions required for non-personalised advertising remain valid. Withdrawing basic ad access deletes that installation without changing diagnostic choices; adult core access pauses after any applicable 30-day notice, while teenagers retain ad-free core access. Premium/trial/grace, under-13 and unresolved-age states disable advertising. Consent-authorised Remote Config may remain active for up to 12 hours while the relevant signals are unchanged; any signal change invalidates it immediately. If deletion cannot complete offline, all advertising remains disabled until cleanup succeeds. Drive Zone does not use Remote Config audiences, experiments, personalisation, Analytics properties or user-level targeting.

For eligible free users aged 13 or over, Drive Zone uses Google Mobile Ads and Google User Messaging Platform to manage advertising choices and request non-personalised adverts. Non-personalised serving requires purpose 1 consent, purposes 2, 7, 9 and 10 consent or legitimate interest, and Google vendor 755 consent. Ages 13 to 17 receive teen ad treatment and no personalised adverts or Apple tracking request. Adult personalised serving additionally requires purposes 3 and 4 consent, a verified or confirmed Apple adult declaration source, and Apple App Tracking Transparency authorisation. Self-declared, guardian-declared and iOS 18.4 to 25 adult declarations do not permit personalisation. Declining personalisation or Apple tracking keeps non-personalised free access available when basic ad access is granted. After a completed adult refusal or withdrawal of basic ad access, free adult core access pauses after any applicable 30-day notice and the app offers Premium; no Google advert is requested. Teenagers who refuse retain ad-free core access. Unknown or incomplete consent, under-13 or unresolved age, unresolved entitlement, and pending advertising-data cleanup prevent advert requests.

Non-personalised adverts are not selected from past behaviour, but Google may still use identifiers or local storage for frequency control, aggregated reporting, fraud prevention, security and delivery after basic ad access is granted. Google's publisher first-party identifier and personalisation are disabled for non-personalised serving. Drive Zone does not enable programmatic limited ads, mediation, consent syncing, Firebase-to-AdMob reporting or Analytics-to-AdMob sharing. An eligible request does not guarantee that an advert is available; no-fill or offline conditions do not by themselves pause access after a valid free-tier choice.

Premium subscribers, active trial users and users in billing grace are excluded from advertising and advertising consent prompts. Drive Zone also treats unresolved or failed entitlement checks as ineligible for adverts.

Lawful bases

These are the bases we rely on under UK data protection law.

• Performance of a service you ask us to provide: for example, saving your vehicles and history, showing zone information, carrying out a vehicle lookup when you request one, and refreshing saved vehicle details if Premium automatic DVLA refresh is enabled.

• Performance of a service and legitimate interests: to validate and reconcile Premium entitlements, route requested support or Live Activity updates, recover service access, and keep those flows reliable.

• Legitimate interests: to improve and protect Drive Zone using restricted Analytics, approved custom Performance Monitoring, restricted Crashlytics fault detection, service protection, short-lived caching and rate limiting. The controller has assessed restricted Analytics and custom Performance Monitoring under the PECR statistical-purpose exception and restricted Crashlytics under the technical-fault exception. Advertising-related storage and access requires the separate basic advertising choice described above. Remote Config storage and access remains gated by the permissions required for non-personalised advertising.

• Legitimate interests and legal obligations: to use App Attest, installation integrity records, pseudonymous operational events, support history and the minimum rights-request evidence needed for security, abuse prevention, legal compliance and accountability.

• Consent: to serve personalised adverts and use tracking technologies where consent is required. Apple tracking permission is also required before Drive Zone permits personalised adverts that use IDFA.

• Legal obligations and legitimate interests: to present and retain advertising privacy choices and meet privacy, platform, security and advertising-compliance requirements.

• Analytics, Performance Monitoring and Crash reporting: legitimate interests for their restricted purposes, with a right to object before activation and at any time later. All three start selected, but saving the review is required before any optional telemetry can activate. Saving records review and no objection; it is not consent.

• Legal obligations: where we need to comply with applicable law, regulation, or lawful requests.

iOS permission prompts still matter. Drive Zone only accesses location, motion activity, or notifications after you allow those permissions through Apple's operating system controls.

Sharing

Drive Zone keeps sharing limited.

• If you enable cloud sync, Apple processes the synced records and CloudKit metadata needed to keep your private iCloud database aligned across your devices.

• DVLA lookup requests are shared with Drive Zone's vehicle lookup service and then with DVLA when you choose to perform a vehicle lookup, and when Premium automatic DVLA refresh periodically checks saved vehicles while enabled.

• Support and rights-request messages are processed through Drive Zone support tooling and the support delivery channels needed to show replies in-app on your linked installation.

• Render hosts the Drive Zone backend and database in Frankfurt for vehicle lookup, installation integrity, entitlement, support, notification-routing and Live Activity services.

• Apple and iOS may also process data needed to provide iCloud, CloudKit, Sign in with Apple, Apple account recovery, iCloud Keychain, App Attest, subscription and optional Tip Jar purchases, App Store transaction validation, APNs notifications, Live Activity updates, device permissions, and other platform features under Apple's own terms and privacy information.

• Apple Mail or iCloud Mail may process support correspondence and rights requests sent to the Drive Zone support mailbox.

• We do not sell your personal data. Google and its eligible advertising partners process the advertising, consent, analytics, crash, performance and remote-configuration information described in this notice. The available partner list and choices are shown through Google's published privacy message where required.

• Google services use global infrastructure and information may be processed outside the UK. Google Ireland Limited is the recorded contracting entity for the reviewed UK Analytics and advertising arrangements. The recorded safeguards are the UK Extension to the EU-US Data Privacy Framework where applicable and contractual safeguards, including the UK International Data Transfer Addendum and standard contractual clauses, where required.

Retention and deletion

Local data and service-side records are kept for different reasons depending on the feature you use.

• Saved vehicles remain on your device until you edit or delete them, or remove the app.

• Journey history remains on your device until you clear it, delete entries, or remove the app.

• Zone preferences stay in local settings until you change them or remove the app.

• If you enable cloud sync, synced records remain in your Apple iCloud private database until they are replaced, deleted, or removed through your device actions, including Delete Synced iCloud Data in the app.

• Operational events used to secure and monitor the backend services are retained for up to 365 days and use pseudonymised client and registration fingerprints rather than raw IP addresses or raw registration numbers.

• Support correspondence, attachments, and related support-case records are retained for up to 24 months after the last interaction unless they are needed longer for an active dispute, claim, or legal obligation.

• Installation and App Attest integrity records are kept while the installation uses Drive Zone backend services and for the minimum operational period needed to secure or reconcile those services.

• Subscription entitlement and App Store notification records are kept while needed to provide, recover or reconcile Premium access and related transaction state.

• Support push-channel records follow the related support-case retention period. Live Activity channel, token and session data is kept until the session completes or operational cleanup removes it.

• Help and self-service feedback linked to a support case follows the support-case retention period. Rights and deletion request evidence is retained for three years using the minimum personal data necessary.

• The vehicle lookup service uses short-lived cache entries, readiness state, and rate-limiting data to keep the relay stable. It is not intended to act as a general customer profile database.

• Export My Data creates a ZIP package from the data already available on this device and excludes raw auth tokens, Keychain-protected encryption material, and other credentials.

• Analytics event and user-level data is configured for a 2-month retention period. The period does not restart when a user returns. Aggregated reports may remain available for longer because Google Analytics does not apply this setting to standard aggregated reporting.

• Firebase documents that Crashlytics keeps crash stack traces, associated identifiers and related crash information for 90 days before removal begins.

• Firebase documents that Performance Monitoring keeps IP-associated events for 30 days and installation-associated and de-identified performance information for 60 days before removal begins.

• Advertising and consent information is retained under the applicable Google service settings and terms. The separate advertising Firebase installation is deleted after withdrawal of basic ad access or loss of eligibility. A versioned hash of relevant UMP/TCF state and the last successful Remote Config server-fetch time are stored locally; raw consent strings and Remote Config values are not duplicated by Drive Zone. Authorised Remote Config may be used for no more than 12 hours while signals remain unchanged.

If you want us to deal with a personal data request relating to data processed by Drive Zone infrastructure, or with deletion, correction, restriction, or another issue the export does not cover, submit it in Help & Support > Start Help Wizard.

Apple account recovery, iCloud Keychain, and your iCloud account are part of the trust boundary for cross-device sync access.

Your privacy choices

Controls available in Drive Zone and iOS.

• The optional-diagnostics draft selects Analytics, Performance Monitoring and Crash reporting. The draft itself causes no processing: all services stay off until you review and save the complete versioned choice set. You can switch off or object to any service before saving or at any time later. Switching Analytics off also resets its app data on this iPhone, but switching off does not automatically erase information already retained by Google.

• When crash-report submission is off, unsent reports stay local. Drive Zone offers an explicit send or delete choice; enabling another Firebase service does not submit them.

• Where Google requires a continuing privacy-options entry point, you can open Advertising privacy options in Privacy & data controls to review or change your advertising choices.

• You can review Apple tracking permission in iOS Settings. If you choose Ask App Not to Track, Drive Zone does not permit personalised adverts that use IDFA.

• Switching off or objecting to Analytics, Performance Monitoring or Crash reporting stops future collection for that service immediately. Narrowing advertising permission removes loaded adverts and prevents a more personalised mode for the rest of the app session. Refusing or withdrawing basic ad access pauses adult free-tier core access after any applicable 30-day notice and offers Premium; teenagers retain free core access without Google adverts. A later free choice may require a fresh app launch before Google ads can resume. Privacy controls, subscription management, support, data export and deletion remain available. Withdrawal or objection does not automatically erase information already lawfully retained by Google for legal, security, fraud-prevention or service-integrity reasons.

• To ask about deletion or another data-protection right that the in-app controls do not cover, use Help & Support > Start Help Wizard.

Your rights

UK data protection law gives you rights over your personal data.

• You may have the right to request access to your personal data.

• You may have the right to ask for correction, deletion, restriction, or objection in appropriate cases.

• You can export a machine-readable copy of supported on-device data from inside the app, and you can use Help & Support > Start Help Wizard if you need help with a broader request.

• You can submit a request in-app through Help & Support > Start Help Wizard.

• You also have the right to complain to the Information Commissioner's Office if you are unhappy with how your data has been handled.

Children

Whether this app is designed for children.

Drive Zone is a general-audience aid for UK vehicle users and drivers, including possible 17-year-old learners. On iOS 26 and later, Drive Zone requests Apple's privacy-preserving Declared Age Range; if it is unavailable or declined, and on iOS 18.4 to 25, the app asks for a coarse age band without an identity document or birth date. Under-13 and unresolved-age users receive no Google adverts or Apple tracking prompt. Eligible 13-to-17-year-olds may receive only non-personalised Google adverts after valid basic ad-storage permission, with teen ad treatment and no Apple tracking prompt. Teenagers who refuse retain free ad-free core access. Eligible adults may receive non-personalised adverts after basic permission; personalised advertising requires a verified or confirmed Apple adult source, the complete Google consent matrix and Apple tracking authorisation. Drive Zone stores only the selected age band and declaration-source category, never an exact age, birth date or Apple's range bounds.

Changes to this notice

How we review and update this privacy information.

We may update this notice as the app changes. The current dated Privacy Policy is available through links in the app and on the Drive Zone website. This version was last updated on 7 October 2026.

Website-specific additions

The public website adds limited public-site and hosting-side processing beyond the app.

• When you visit the website, standard web requests and security logs may process limited technical data such as IP address, browser or device details, requested paths, timestamps, and related hosting diagnostics needed for delivery, reliability, and abuse prevention. These records are kept only for the provider and operational periods needed to deliver, secure and troubleshoot the website.

• The website publishes legal information, contact details, App Store links, and a fleet enquiry form for organisation contacts.

• If you submit the fleet enquiry form, the website sends the contact details, organisation details, fleet size range, role, and message you provide to Drive Zone support tooling so we can review and respond to the enquiry.

• Fleet enquiries are processed to take steps towards a possible organisation service and for the legitimate interest of reviewing and responding to the request. Render hosts the support record in Frankfurt, and Apple Mail or iCloud Mail may process an email reply. The enquiry follows the support-case retention period of up to 24 months after the last interaction unless it is needed longer for an active dispute, claim, or legal obligation.

• The public website uses Google Analytics 4 only after you accept website analytics. We rely on your consent for analytics cookies and associated personal-data processing, to improve website content and navigation and understand marketing effectiveness. This website choice is separate from app diagnostics and advertising choices. No website Google Analytics request is made before acceptance or after rejection. You can withdraw through Cookies & settings in the footer of every page. See Cookies and analytics for collected events, retention and controls.

If you are using the website and do not have access to the app, you can contact I Squared R Consulting Ltd by email at support@drive-zone.app or by post at Ground Floor, 11 Manvers Street, Bath, BA1 1JQ.

Website hosting and regional delivery

Website hosting and optional analytics have different processing arrangements.

Website hosting and the fleet support service are provided in the EEA. Optional Google Analytics processing can involve international transfers, including to the United States, under the applicable Google processing terms and UK transfer safeguards; website hosting location does not mean all analytics processing stays in the EEA.

Optional analytics cookies