1. In short
- A few strictly necessary cookies keep your session active and protect requests. The service cannot function without them, so there is no opt-out while you are signed in.
- Browser storage holds a small number of interface preferences and short-lived conveniences.
- An offline cache holds static files and an offline page so the app degrades gracefully on a poor connection.
- We do not track you across other websites and we do not sell or share this data for advertising.
2. Cookies and storage explained
A cookie is a small text file a site stores in your browser and reads on later requests. Local storage and session storage are similar browser stores a site reads and writes with scripts; session storage clears when you close the tab. An offline cache lets a background script serve previously downloaded files. We describe all of these together here.
3. Strictly necessary cookies
When you sign in, AmbTrack sets a small number of first-party cookies that keep you authenticated and protect state-changing requests against cross-site misuse. In production they are sent only over an encrypted connection and are restricted so other sites cannot read them. They last only as long as your session needs and are cleared when you sign out; expired sessions are also cleaned up on our servers. These cookies are essential — blocking them prevents you from signing in or staying signed in.
4. Browser storage
AmbTrack keeps a small amount of first-party data in your browser’s local and session storage to run the app for you — for example an interface preference such as light or dark theme, and short-lived values that let a screen render without an extra round-trip. Session-storage items are cleared when you close the tab. None of this is used to track you, and it is not shared with anyone. Additional minor keys may be added over time; they follow the same rule.
5. Offline cache
A background script caches static assets and an offline fallback page in your browser so the app shell can load on a weak connection. Signed-in and account-recovery pages are kept out of this cache. Uninstalling the app or clearing site data removes it.
6. Third-party items
- Bot-protection challenge. Sign-in and public forms use a challenge widget to block automated abuse. It may set its own cookie or storage entry to remember that a challenge was passed. It is used only for security, not for advertising or profiling.
- Maps. Dispatch tools embed a maps component to show locations and resolve addresses. It may set storage entries needed to render maps and handle input.
These providers act under contract and process only what their function requires (see the Privacy Policy, sections 9 and 10).
7. What we do not use
- No advertising or marketing cookies.
- No cross-site or cross-device tracking, and no data brokers.
- No third-party analytics that build a profile of you. Where we measure performance, we use aggregate, non-identifying counts.
- No “social” tracking pixels or share-button trackers.
8. Managing cookies and storage
- Your browser settings let you view and delete cookies and site data, and block them per site.
- Blocking the strictly necessary cookies will stop you from signing in or staying signed in.
- You can clear local and session storage from your browser’s site-data controls.
- Signing out clears the session cookies. Ending a session from your account settings revokes it on our servers as well.
- Uninstalling the installed app or clearing site data removes the offline cache.
9. Changes
If we add or change a cookie or storage item, we will update this page. A change that materially affects your privacy is notified with the Privacy Policy under its change process.
10. Contact
Questions about this notice: privacy@ambtrack.in.