Cookies and browser storage
Cookies are small pieces of information a website can store in your browser. Similar technologies include local storage and session storage. Their purpose matters, even when no cookie is used.
Sign-in
Keeps your MilePocket account session available while you use the website.
Saved drafts
Keeps unfinished vehicle setup in this browser so you can return to it.
Optional usage analytics
Helps us understand which account sections people use. Its collection is controlled by a choice in the account.
What the website stores
This inventory covers browser storage used by the MilePocket website. Persistent storage has no automatic expiry unless stated.
| Storage & purpose | Provider & location | Duration & removal |
|---|---|---|
| Sign-in sessionSession storage / IndexedDB Sign-in storage. The website selects current-tab session persistence. In both the Google and Apple tests, firebase:authUser:{apiKey}:[DEFAULT] appeared after login and survived a page reload. The SDK database was present before login. Technical detailsFirebase auth · sessionStorage / firebaseLocalStorageDb | Firebase / Googlemilepocket.com / this browser | In both tests, MilePocket sign-out removed the session key and it stayed absent after reload. The database remained; its entries were not inspected. Browser tab restoration remains unverified. |
| Firebase service metadataIndexedDB Firebase SDK service metadata. The database and store schema were observed before sign-in; no entries were read. Its consent category and exact stored content have not been verified. Technical detailsfirebase-heartbeat-database · IndexedDB | Firebase / Googlemilepocket.com / this browser | The database remained after MilePocket sign-out and reload in both tested flows. Entry lifetime and deletion conditions have not been verified. |
| Account setup draftLocal storage Your unfinished account and vehicle setup draft, independent of analytics. Technical detailsmilepocket.onboarding.v1.{uid} · localStorage | MilePocketmilepocket.com / this browser | No automatic expiry. It can remain after sign-out and reload. Completion removes the supported draft; clearing website data removes it from this browser. |
| Analytics browser identifierLocal storage Optional analytics browser identifier. Created only after you enable account usage analytics, or when your enabled choice is restored. Signing in alone is not consent. Technical detailsmilepocket-usage-installation · localStorage | MilePocketmilepocket.com / this browser | No automatic expiry. An existing identifier remains inactive when analytics is off and after sign-out. Clear website data to remove it. |
| Analytics choiceLocal storage Remembers enabled or disabled for this account in this browser. Technical detailsmilepocket-usage-choice-{uid} · localStorage | MilePocketmilepocket.com / this browser | No automatic expiry. Sign-out keeps the choice. Other accounts do not inherit it. |
| Pending analytics eventsLocal storage Pending optional analytics events, created only while collection is enabled. Technical detailsmilepocket-usage-queue-{uid} · localStorage | MilePocketmilepocket.com / this browser | Acknowledged events are removed. Turning analytics off, signing out or changing the active account clears its pending queue. A reload or crash may preserve it. Events older than 7 days are discarded when the queue is processed; a closed browser has no deletion timer. |
| Google sign-in cookiesCookies 23 cookie names and their attributes were observed on Google pages. 20 names were present before the MilePocket sign-in flow; 3 were first observed afterward. This does not establish which service created them or their exact individual purposes. Technical detailsGoogle cookies · provider pages | GoogleGoogle provider pages | The same 23 names remained after MilePocket sign-out; values were not compared. Observed Expires, domains, paths and flags are in cookie-inventory.csv / cookie-inventory.json. Max-Age was not captured. Cookie lifetime, token lifetime and server retention are separate. |
| Apple provider cookiesCookies Four names were observed on account.apple.com after the MilePocket Apple login/sign-out test and a separate provider-page visit: geo, dslang, site and cmrc_shld_mk_ck. There was no pre-OAuth provider-cookie baseline. These observations do not identify which cookies predated the flow or were created by it. Technical detailsApple cookies · provider pages | AppleApple provider pages | The inventory records the observed Domain, Path, Expires/session status, Secure, HttpOnly and SameSite. Max-Age, exact individual purposes and changes caused by sign-out were not verified. Cookies limited to the Apple authorization origin or other paths may be outside this observation. |
These are storage lifetimes, not the retention periods for trips, GPS routes, financial records or data already sent to a server. Clearing browser data does not delete your MilePocket account.
Other services your browser contacts
A network request can share connection information even when it sets no cookie.
Cloudflare
Delivers the website and account API. The live homepage and signed-out Account page also load Cloudflare Web Analytics, which uses no cookies or local storage for its analytics. Cloudflare documents 7 days of unsampled beacon data and access to statistics for the previous 6 months. That is not a deletion deadline for all Cloudflare logs.
Cloudflare documentationGoogle, Apple and Firebase
Google and Apple provide the sign-in method you select through Firebase. Both tested sign-in/reload/sign-out/reload flows removed the MilePocket session key at sign-out, while the SDK databases remained. Provider cookies are recorded separately below; the original Apple-cookie baseline and exact individual purposes remain unverified. Signing out of MilePocket does not sign you out of those providers.
Firebase sign-in documentationMaps
Opening an account map requests OpenStreetMap tiles for the viewed area. Opening a Google Maps link sends the selected location to Google. Map providers receive normal connection information; their browser-cache and cookie behavior still needs verification.
MilePocket Privacy PolicyServer retention is separate
Source sets receipt expiry at 8 days and device metadata expiry at 9 days. The enabled cleanup schedule runs daily at 04:20 America/New_York; expiry and a successful scheduled attempt do not prove each record was physically deleted. Daily aggregates older than the 90-day window are pruned during telemetry ingestion, not by a demonstrated deletion timer. Cloud Storage soft delete provides a 7-day recovery window after deletion; it is not the lifetime of all account data. Without new telemetry, older daily aggregates may remain longer.
Your choices
You can enable or disable optional account usage analytics in your account. Without a new or saved enabled choice, MilePocket creates no analytics identifier, queue or events and sends no optional account analytics. Turning it off stops collection, aborts pending requests and clears this account’s queue; it does not delete previously sent server data. A request already received by the server cannot be recalled. An existing browser identifier remains inactive until website data is cleared. The account choice does not control Cloudflare Web Analytics.
Change collection
Use the Optional analytics setting in your MilePocket account. This page does not change your saved preference.
Clear website data
Your browser's privacy settings can remove cookies and site storage. You may be signed out and lose unfinished drafts and saved choices.
Use more than one browser?
Manage each browser separately. Signing out of MilePocket does not sign you out of Google or Apple.
Updates and questions
We update this page when the website’s storage changes. Contact us if you have questions about an entry or your account analytics choice.
Trips, GPS routes, financial records, cloud sync and account deletion are covered by the Privacy Policy.
Read Privacy Policy