United Kingdom browser storage
Cookie Policy
Effective: 10 October 2026 · Version 2026-10-10
1. What cookies and browser storage are
Cookies are small text files placed on a device by a website. Browser storage, such as local storage, allows a site to save small pieces of information in the browser without using a cookie. Similar technologies can support authentication, security, preferences, analytics, and advertising.
2. What Trukfox currently uses
| Item | Type and purpose | Duration |
|---|---|---|
authToken | Essential local storage. Holds the signed authentication token so a user can remain signed in and access the correct company panel. | Until sign-out, invalidation handling or manual browser clearing. An expired bearer cannot access the server; a separate verified driver offline allowance can authorize prepared local work. |
currentUser | Essential local storage. Holds limited current-user and company-display information to support navigation and branding. The server verifies the account while connected; a valid session can use permitted cached information offline. | Until sign-out, invalidation handling or manual browser clearing. |
| Encrypted offline workspace and changes tray | IndexedDB storage, scoped to the account and company. Holds permitted cached records, prepared protected paperwork, queued changes, selected evidence, signed driver offline allowances, an encrypted prior identity for queue recovery and non-extractable encryption keys. | Driver access is bounded by a signed allowance, normally seven days and configurable from one to 30 days. Other permitted workspace reads require a valid session and are limited to 24 hours. Encrypted bytes may remain until eviction, sign-out or site-data clearing. Pending work remains until sync, discard or clearing. Work older than 30 days requires review and is not automatically erased. |
| Public offline app shell | Service-worker Cache Storage for public HTML, scripts and styles. Company API responses, authentication requests and private files are excluded. | Until a newer app-shell version replaces it or site data is cleared. |
| Native background delivery queue | Encrypted app-device storage, separate from browser storage, protected with a Keychain or Keystore key. Holds pending changes, selected evidence, a scoped authentication token, the driver offline allowance, renewed session metadata and delivery receipts. | Pending changes remain until synced or cleared through the app. Sign-out clears the native queue; receipt history is bounded, with receipts older than 30 days pruned on subsequent successful delivery. Browser site-data clearing alone does not clear a separate native queue. |
trukfoxLegalRegion | Functional local storage. Remembers whether you selected the UK or US legal library so the same region follows you between legal pages. | Until you choose another region or clear browser site data. |
| Server security logs | Not a browser cookie. Request and security information may be logged to protect and troubleshoot the Service. | Kept only as reasonably needed. |
authToken and currentUser are used only to provide and secure the authenticated service explicitly requested by the user. The legal-region preference is set only after a region is selected and remembers that requested choice. We rely on the applicable PECR exemption for these limited uses rather than optional consent. Blocking or clearing authentication storage prevents signed-in company-panel use; clearing the legal preference resets the library to UK.
Authentication items are necessary to provide and secure the signed-in product. The legal-region item remembers your requested choice. Blocking or clearing authentication storage prevents signed-in company-panel use; clearing the legal preference resets the library to UK.
3. Analytics and advertising
As of the effective date, Trukfox does not use third-party advertising cookies, cross-site behavioural tracking, or optional analytics cookies. If that changes, this Policy will be updated and an appropriate consent control will be provided before non-essential cookies are used where required by law.
We will not place or access non-exempt cookies or similar technologies on a UK user’s device until any consent required by PECR has been obtained through a clear affirmative choice. Withdrawing consent will be as easy as giving it. We will reassess new statistical, security, and preference technologies against PECR as amended by the Data (Use and Access) Act 2025 before deployment.
Trukfox does not currently “sell” or “share” personal information through cookies for cross-context behavioural advertising and does not use cookies for targeted advertising. If that changes, we will provide any state-law notice, opt-out, and Global Privacy Control response required at that time.
4. Third-party page resources
Public pages may request fonts from Google and images from an image-hosting service. When a browser requests these resources, the provider receives technical information such as IP address, browser details, and request time. Chart and map-display software are bundled locally. HERE map backgrounds, routing and geocoding use the Trukfox backend; submitted addresses and tile coordinates identifying the viewed area reach HERE.
The optional AI assistant does not use advertising or tracking cookies. The company administrator’s Settings → Platform assistant setting controls eligible prompt sharing with OpenAI when the service operator has configured AI. It starts disabled. See the Privacy Policy for that data flow and provider retention.
Provider links used during mailbox setup, including Google, Microsoft, and Yahoo, open external websites. Trukfox does not control cookies placed by those external websites.
5. Managing storage
You can clear Trukfox local storage using browser privacy or site-data controls. Doing so signs you out. Most browsers also let you block cookies and storage, but essential platform features may stop working.
Clearing all Trukfox site data removes browser offline records and the cached public app shell. Use the app's sign-out control to clear its browser records and native background queue; unsynced changes are lost when cleared. Session or signed-allowance expiry and the 30-day review limit restrict use and replay without automatically erasing saved bytes.
On a shared device, always use the Trukfox Sign out button and consider clearing browser site data. Do not allow a browser to save business passwords on a device you do not control.
6. Changes and contact
We may update this Policy when our storage technology or providers change. Questions may be sent to privacy@trukfox.com.