MobiBubble
Cookie and storage notice
Last updated: 4 July 2026.
Current position
MobiBubble currently uses essential authentication cookies and limited local browser storage. We do not currently use advertising cookies, behavioural tracking pixels, or third-party behavioural analytics tags in the MobiBubble product surfaces.
First-party aggregate analytics
MobiBubble may collect privacy-conscious server-side product statistics, such as page/API request counts, booking flow events, response statuses, broad referrer origins, and browser family. This does not use analytics cookies, local storage identifiers, visitor IDs, device fingerprinting, or advertising networks.
Essential cookies
| Name | Purpose | Duration |
|---|---|---|
| mobi_bubble_refresh_token | Maintains signed-in sessions and rotates API refresh tokens. | Up to 30 days by default, or until logout/revocation. |
Local storage
The booking app may store a customer's first name, last name, phone, address line, and city in the browser on the same device so future bookings can be prefilled. This data is not used for advertising and can be cleared by clearing site data in the browser. A first-class app control to clear saved booking details is tracked as a pre-launch follow-up.
Error monitoring
MobiBubble may use Sentry for technical error monitoring when it is configured. This helps us understand frontend and backend errors, but is not used for advertising or behavioural profiling. We configure the product not to use Sentry session replay and not to send cookies, authentication headers, request bodies, or query strings in error reports.
Future analytics or marketing tools
If MobiBubble later adds advertising, marketing cookies, session replay, cross-site tracking, or analytics that identify or profile individual visitors, this notice will be updated and the product will add any consent controls required before those tools are enabled.
Contact
For privacy or storage questions, email support@mobibubble.uk.
