Skip to content

Cookie and local storage policy

Last updated: November 2026

1. Introduction

This policy explains how PZO (mobile app and web dashboard) uses local storage technologies in your browser and on your mobile device. Unlike many websites, PZO does not use traditional HTTP cookies for its operation. We instead use storage mechanisms built into the browser and the phone: localStorage, sessionStorage, IndexedDB and, in the app, the phone's secure keychain and files saved on the device.

2. Storage technologies used

2.1 localStorage

localStorage is a client-side storage technology that allows data to be kept in your browser. PZO uses localStorage to:

Stored dataPurposeDuration
Authentication token (JWT) — on the dashboard; in the app, it is kept in the phone's secure keychain (iOS Keychain / Android Keystore)Maintain your login sessionUntil sign-out or token expiration
User profile dataDisplay your name, role, and organization without a server requestUntil sign-out
Interface preferencesRemember your settings (layer visibility, units, notifications)Persistent
Selected vehicle identifierFind the vehicle associated with the operator at the next openingPersistent
pzo_cookie_consentRemember your choice for the cookie consent banner (accepted / declined)Persistent until manually cleared
mapbox.eventData (Mapbox)Anonymous identifier used by Mapbox to count map loads; sent to MapboxSet by Mapbox

Except for the Mapbox identifier, this data stays on your device and is not transmitted to third parties. It is essential to the operation of the service and cannot be disabled without preventing the use of the application.

2.2 IndexedDB

IndexedDB is a browser-integrated database that allows larger amounts of data to be stored. Only the PZO mobile app uses IndexedDB (the web dashboard creates none), to:

DatabasePurposeDuration
pzo-tile-cacheCopy of map elements already displayed (including styles, fonts, icons and aerial imagery) and of vehicle 3D models, to show them again without network and save satellite data30 days for map elements (sooner if storage runs low), 1 year for 3D models, even after sign-out. An expired copy is no longer used; an automatic cleanup deletes it while the app is open
pzo-dbData not yet received by the server, mostly data created without network (including GPS positions, reports and points of interest with their photos, loaded/empty status, trip start and end), waiting to be sentUntil sent to the server, or until you sign out of the app yourself
pzo-offline-assetsCopy of PDF maps, documents and photos (reports, points of interest) received or opened in the app, to view them without networkUntil you sign out of the app yourself or use "Clear all" (Settings > Offline storage); above 200 MB, the least recently viewed are removed
pzo-voice-clipsName and type of vehicles that have already been nearby (the name may be their driver's), as text and short audio recordings, to speak them in voice alertsUntil you sign out of the app yourself
pzo-memoireLatest version received of what the app displays (layers and maps, reports, points of interest, SOPFEU zones, fires, notifications), to find it again on restart without networkUntil you sign out of the app yourself
pzo-sentry-hors-ligneApp error reports that occurred without network, waiting to be sentUntil sent

These databases mainly help operators in remote areas, where the network is weak or goes through satellite: what is already on the device is not downloaded again, and what is created without network waits for it to return before being sent.

3. Third-party services

3.1 Mapbox

PZO uses the mapping services of Mapbox Inc. to display maps. When you view the map, your browser downloads map tiles, fonts, and icons from Mapbox servers. Mapbox may receive the geographic coordinates of the displayed map area (not your exact GPS position) as well as your IP address. For more information, see the Mapbox privacy policy.

3.2 Stripe

Payments are processed by Stripe Inc. During payment, Stripe may set technical cookies necessary to secure the transaction and prevent fraud. These cookies are managed directly by Stripe and are subject to the Stripe privacy policy.

3.3 Sentry (error reports)

PZO uses Sentry to automatically receive application crash reports. When an error occurs, your browser sends a technical trace (source file, line, error message) and may include your internal identifier, your IP address and, if you are signed in to the dashboard, your email address. Sentry operates from the European Union and sets no cookies in your browser. No functional data (GPS position, photos, passwords) is transmitted. For more information, see the Sentry privacy policy.

4. Tracking and advertising cookies

PZO does not use any tracking, behavioral analytics, or advertising cookies. We do not use third-party analytics services such as Google Analytics. We do not track your browsing activity outside of our services.

5. Managing local storage

You can delete locally stored data at any time:

  • On a web browser: via your browser settings, in the "Site data" or "Storage" section, delete the data associated with pzo-fleet.com
  • On the mobile app: via the app settings, use the sign-out option (it clears most local data; your preferences and map copies stay on the device) or uninstall and reinstall the app

Note: data not yet sent to the server (including positions, reports and photos) is lost if you sign out or uninstall the app before it is sent. What the server has already received remains intact and will be reloaded at your next sign-in, except for a free account without sign-up, which cannot be reopened.

6. Changes to this policy

We may update this policy to reflect changes in our local storage practices. The date of the last update is shown at the top of this page.

7. Contact us

For any question relating to this policy, please contact us:

Email : contact@pzo-fleet.com
Website : pzo-fleet.com

See also our Privacy policy, our Terms of service, and our Legal notice.