BoxMidfield← Back to BoxMidfield
PRIVACY & STORAGE

Cookies & Storage

How BoxMidfield uses essential browser storage, authentication storage and offline caching.

Last updated: 6 October 2026

1. Current position

The current BoxMidfield public build does not use advertising cookies, Google Analytics or third-party advertising SDKs. It does use storage and caching that are necessary for requested app features, account sessions, security and reliable PWA operation.

2. Essential technologies

Firebase authentication

Browser storage may be used to maintain a secure signed-in session and authentication state.

My Picks

Saved BoxMidfield views are stored locally on the device so they remain available between visits.

App/session state

Local or session storage may remember navigation, return routes, QA state or other requested app behaviour.

Service worker cache

The PWA stores versioned app files and an offline page so the interface can load reliably and update between releases.

3. Why consent is not currently requested for these items

The storage described above is used for functionality requested by the user, account/security operation or reliable delivery of the service. BoxMidfield does not currently use it to create advertising profiles or measure users for advertising.

4. Managing local data

You can remove locally stored BoxMidfield data through your browser or device site-data settings. Clearing it may sign you out, remove My Picks and require the PWA to download its files again.

5. Future analytics or advertising

If BoxMidfield introduces non-essential analytics, advertising or other technologies that require consent, they will not be enabled until this notice and the Privacy Policy are updated and an appropriate consent mechanism is available.

6. More information

See the Privacy Policy for account data, lawful bases, retention, transfers and your rights. For questions, use Contact & Support.