Cookies Policy

A cookie is a small piece of data stored on your device by your web browser when you visit a site. Local storage is a similar mechanism that lets a site keep data on your device between visits. We use both, and we describe each one below.

These are required for the service to function. They are loaded without asking, because Qamino cannot operate without them.

• Firebase Authentication tokens — keep you signed in across pages and reloads. Stored in browser storage by the Firebase SDK.
• Firestore persistent local cache — stores a copy of your trips and computed status on your device so that the app works offline-first and feels instant. Cleared if you delete your account or clear your browser storage.
• qamino_consent (localStorage) — remembers your cookie banner choice (accepted or declined) so we do not ask again at every visit.

These only load if you click "Accept" in the cookie banner. You can withdraw consent at any time using the "Cookie preferences" link in the footer.

• Zoho PageSense — product analytics. Helps us understand which features are used and where users get stuck. No personal identifier is set by us; PageSense uses cookies set by Zoho.
• Zoho SalesIQ — live chat widget. Loads with a "functional" cookie scope so you can talk to us. If you have consented to analytics, SalesIQ also collects session analytics. SalesIQ chat domain: qamino.io.

Qamino does not load Google Analytics, Google Tag Manager, Meta Pixel, TikTok Pixel, Mixpanel, Amplitude, Posthog, Hotjar, or any other third-party advertising or behavioral tracking script. If you see one in your browser tools that we have not listed here, please write to privacy@qamino.io — we want to know.

You can change your preference at any time using the "Cookie preferences" button at the bottom of every page. Choosing "Decline" removes the analytics and chat cookies on the next page load.

You can also clear cookies and local storage directly from your browser settings. Note that clearing the Firestore persistent cache will simply force the app to fetch your data again from the server on next sign-in — no data is lost.

If we add, remove, or change the cookies we use, we will update this page. The "Last updated" date at the top always reflects the current version.