COOKIES AND DEVICE STORAGE POLICY
Last updated: 28 September 2026
This Policy explains how Via Originis uses cookies and similar technologies, including local browser storage, IndexedDB and service-worker caches.
1. WHAT THESE TECHNOLOGIES ARE
Cookies and browser storage technologies allow websites and web applications to remember information required for security, authentication, functionality and offline use.
Via Originis may use:
- cookies;
- localStorage;
- sessionStorage;
- IndexedDB;
- Cache Storage;
- service-worker caches.
2. STRICTLY NECESSARY AND FUNCTIONAL STORAGE
Via Originis currently uses browser storage primarily to provide functionality requested by the user.
Examples include:
Authentication and session
Used to:
- keep a user signed in;
- securely authenticate account requests;
- restore authentication sessions.
Authentication return information
Short-lived storage may remember where the user was before authentication so Via Originis can return the user to the correct route or purchase flow.
Route ownership
The device may temporarily cache information about routes owned by the signed-in account so access can remain reliable.
Route progress
Route state may be stored locally to support:
- walking progress;
- route continuation;
- discoveries;
- route start state.
Offline routes
IndexedDB and browser caches may store downloaded route files and map resources when the user chooses offline access.
PWA / Add to Home Screen preferences
Via Originis may remember that:
- an installation suggestion was dismissed;
- the suggestion should not immediately be shown again.
3. EXAMPLES OF CURRENT STORAGE
Current Via Originis browser storage includes functional items such as:
- authentication/session storage;
- short-lived authentication return information;
- local account snapshot information;
- route entitlement cache;
- route progress;
- offline route assets;
- map assets;
- application shell files;
- Add to Home Screen dismissal state.
Exact storage names may change when the product is updated.
4. OFFLINE STORAGE
When you choose to download a route for offline use, Via Originis may store:
- route content;
- route assets;
- map packages;
- map style resources;
- application files.
Some offline assets are stored at device level rather than directly against a user account.
This means some previously downloaded files may remain physically stored in the browser even after sign-out or account deletion until they are removed or evicted by the browser or operating system.
Their presence alone does not grant another account ownership of a paid route.
5. AUTHENTICATION STORAGE
Supabase authentication may use browser storage or cookies to maintain secure user sessions.
Authentication information is necessary for account access and purchased-route access.
Disabling required authentication storage may prevent account features from working.
6. ANALYTICS COOKIES
Via Originis does not currently use product analytics platforms such as:
- Google Analytics;
- Google Tag Manager;
- PostHog;
- Mixpanel;
- Plausible;
- Hotjar.
Accordingly, Via Originis does not currently place analytics cookies through those services.
7. ADVERTISING AND MARKETING COOKIES
Via Originis does not currently use:
- Meta Pixel;
- TikTok tracking;
- advertising cookies;
- cross-site behavioural advertising;
- remarketing cookies.
8. THIRD-PARTY SERVICES
Some external services used by Via Originis may receive ordinary technical request information when their services are accessed.
Examples may include authentication, payment, hosting or map-related service providers.
Their own cookies or processing practices may be governed by their respective privacy policies where applicable.
9. MANAGING STORAGE
You can control or remove cookies and stored website data through your browser or device settings.
Removing Via Originis storage may:
- sign you out;
- remove route progress;
- remove downloaded offline routes;
- require route content to be downloaded again;
- reset interface preferences.
10. CONSENT AND OPTIONAL TECHNOLOGIES
Via Originis currently uses browser storage primarily for required or user-requested functionality.
If Via Originis later introduces optional analytics, advertising, profiling or similar technologies requiring additional consent or user control, the website will be updated accordingly.
11. CHANGES
This Policy may be updated when Via Originis changes its technical systems or browser-storage practices.
The latest version will always show its most recent update date.
12. CONTACT
Questions about cookies or browser storage:
