Cookie and browser-storage policy

The web source uses Vercel Web Analytics for aggregate page-view measurement. It does not use third-party cookies, and query parameters are removed before page-view events are sent. The source contains no Google Analytics, Meta Pixel, Hotjar, Microsoft Clarity, tag manager or advertising pixel. Optional trackers must not be added without a fresh audit, clear notice and any required prior consent.

Supabase browser authentication storage uses the configured ASIS customer/driver/admin key to keep a signed-in session. It is strictly necessary for authentication. `asis:language` and the legacy `asis:customer-language` key in localStorage store the chosen English/Albanian interface preference. For a guest booking, `asis:guest-contact` in localStorage keeps the submitted name and phone while navigating booking steps or reloading. During booking, sessionStorage temporarily keeps `asis:pending-booking` (the selected pickup, destination, route distance and duration) until the ride is created or becomes terminal. Native apps use OS secure storage for sessions and push tokens. Exact key lifetimes depend on session expiry, sign-out, browser clearing and OS storage behaviour.

Google Maps is loaded when map/location functionality is used and receives map, place, geocoding and routing requests. Firebase/Expo are used only after a user enables notifications. These are not classified here as advertising trackers.

Vercel Web Analytics does not use third-party cookies, so it does not require a cookie-storage consent control. You can clear browser storage in browser settings, sign out to end the application session, and change language in the interface. If optional tracking that requires consent is introduced, ASIS TAXI must add equally prominent Accept all, Reject all and Manage preferences controls before it loads.