Skip to main content

Cookie Policy

Last updated: September 18, 2026

This document is a technical overview of everything this site and console currently store in your browser or send to a third party on your behalf — including cookies, other local storage (localStorage), and third-party requests — and why. We do not use any analytics or advertising technology. "Marketing" gates exactly one thing today, an interactive map in the admin console (see the table); if we add another use in the future, this table and the cookie preferences (available from the footer) will be updated.

Most of what's listed below is your browser's localStorage, not an HTTP cookie — the exceptions are two first-party cookie mechanisms (a small cookie that hands your language choice off between the public site and admin sign-in, and a sign-in session cookie that our authentication provider may split into a few numbered cookies for a larger session) and a third-party map-tile request that isn't storage at all (see the table).

Necessary storage cannot be turned off, because the site or console could not function correctly without it — for example, you would not be able to sign in to the admin console, or we would not remember that you've seen this notice.

NameProviderSurfaceTypePurposeCategoryLifetimePartyConsent required?
gl-taxi.cookie-noticeGL-TAXIPublic sitelocalStorageRemembers that you've seen this cookie notice and your preferences choice.NecessaryUntil you clear it, or this policy's version changesFirst-partyNo — necessary for the requested service
admin.langGL-TAXILogin / dashboardlocalStorageRemembers the admin console's last-selected language before your profile loads.NecessaryUntil cleared or changedFirst-partyNo — necessary for the requested service
admin.activeTenantGL-TAXILogin / dashboardlocalStorageRemembers which tenant company you're currently managing in the admin console.NecessaryUntil cleared or you switch tenantsFirst-partyNo — necessary for the requested service
admin.sidebar.collapsedGL-TAXILogin / dashboardlocalStorageRemembers whether the console's sidebar is collapsed.NecessaryUntil clearedFirst-partyNo — necessary for the requested service
sb-<project-ref>-auth-token(.0, .1, …)SupabaseLogin / dashboardHTTP cookieKeeps you signed in to the admin console (managed by our authentication provider, Supabase). For a larger session, this may be split across a few numbered cookies sharing the same name.NecessaryUp to 30 days, or until sign-outFirst-party (processed by Supabase)No — necessary for the requested service
gl-taxi.localeGL-TAXIPublic site / loginHTTP cookieCarries your selected language from the public site to admin sign-in, and back, so the two stay in sync.NecessaryOne year, refreshed on each visit to the public siteFirst-partyNo — necessary for the requested service
tile.openstreetmap.orgOpenStreetMap FoundationLogin / dashboardThird-party network request (no storage)Renders an interactive map of a ride/reservation/delivery's pickup and drop-off in the admin console's order details view, by requesting map tile images from OpenStreetMap for the coordinates involved. Only requested after an admin accepts the "Marketing" category — see the consent column.MarketingNot stored — a live request made only while the order details view with a map is openThird-partyYes — only after accepting "Marketing"

Controller and contact

The GL-TAXI platform is operated by:

Legal name
Hashlab s. r. o.
Registered address
Juraja Sklenára 100/29, 052 01 Spišské Tomášovce
Company registration number
52575420
VAT ID
SK2121069203
Commercial register entry
Mestský súd Košice, oddiel Sro, vložka č. 46939/V
Privacy contact
informacie@lovepix.sk
Contents

1. Analytics and marketing technologies

GL-TAXI does not use any analytics script (e.g. Google Analytics), advertising pixel, or ad-tech vendor of any kind — none exists in the product's code, and "Analytics" remains fully inert. "Marketing" gates one real thing: the admin console's order-detail map (see "Embedded third-party services" below), because it discloses a customer's coordinates to a third party.

2. Error monitoring (Sentry)

We use Sentry to catch application errors. It is configured to not collect cookies or user information, and only activates on an error or performance event — we found no persistent identifier it writes to your browser's storage.

3. Embedded third-party services

The admin console's order details view can show an interactive map of a pickup/drop-off, rendered from OpenStreetMap tiles — this only loads after an admin accepts the "Marketing" cookie category (see the table); until then, a placeholder is shown instead and no request is made. The dispatch board's live fleet map uses the same tile provider to show driver positions and is treated as necessary to operate that screen, so it is not gated the same way. Map tile rendering (Google Maps on Android, Apple Maps on iOS) and Stripe's payment UI in the mobile app may separately set their own storage under those providers' own policies — refer to their respective privacy policies.

4. How to change your choice

Use "Cookie settings" in the footer to reopen this preferences panel at any time — it works even after you've already dismissed the first-run notice. "Necessary" storage cannot be turned off; "Analytics" has nothing behind it yet; "Marketing" controls whether the admin console's order-detail map loads (see the table).