How Wandrio’s website and browser-based service use cookies and similar technologies, and how users can manage their choices.
| Controller | Wandrio Oy, Business ID 3546427-8 |
| Data protection contact | support@wandrio.net |
| Scope | Wandrio’s public website and browser-based Wandrio service; the processing of personal data in the mobile application is described in the Privacy Notice |
| Updated | 18 August 2026 |
| Version and status | 1.0 |
| Key principle. Wandrio uses cookies and similar technologies without consent only where they are strictly necessary for the service to function. Optional analytics or other non-essential tracking is enabled only after the user has made a choice where consent is required by law. |
1. What are cookies and similar technologies?
A cookie is a small data record stored in the browser. In addition to cookies, Wandrio’s browser-based service may use local browser storage, such as localStorage, sessionStorage and IndexedDB, as well as session and device identifiers. In this notice, these are collectively referred to as technologies.
Technologies may be session-based, in which case they are removed when the session or browser is closed, or persistent, in which case they remain for a defined period or until the user removes them. First-party technologies are set by the Wandrio service. Third-party technologies are set by an external service integrated into Wandrio.
2. What these technologies are used for
| Category | Purpose | Consent |
| Strictly necessary | Sign-in and session management, security, load management, delivery of a page or feature requested by the user, and storage of the user’s cookie choice. | Consent is not requested because the technology is necessary to provide the service requested by the user. |
| Functional | Language, user interface settings, map state, onboarding state, caches and other remembered choices that make the service easier to use. | Consent is requested if the purpose is not necessary for a feature requested by the user. |
| Analytics | Measuring service usage, views, features, platform and application version, and improving the service. | Used only after consent where the measurement stores information on, or reads information from, the user’s device and is not necessary. |
| Third-party mapping technology | Loading Mapbox maps and map features, and possible technical telemetry from Mapbox. | The map is loaded when the user requests a map feature. Non-essential telemetry is allowed only in accordance with the user’s choice and applicable law. |
| Marketing | Targeted advertising or tracking a user across different services. | Wandrio does not currently use advertising tracking technologies. If introduced, prior consent will be requested. |
3. Technology categories used by Wandrio
| Technology or provider | Data and purpose | Typical retention |
| Firebase Authentication / Wandrio session | Sign-in and session identifiers that keep the user signed in and allow protected requests to be associated with the correct user. | For the duration of the session or until the user signs out, clears browser data or the session expires. |
| Storage of cookie choices | The user’s acceptance, rejection and category-specific choices, so the request is not shown again unnecessarily and the choice can be demonstrated. | For the period defined by the selected consent tool, or until the user changes the choice or clears browser data. |
| Wandrio localStorage and settings storage | For example language, application version, onboarding state, user interface choices, map or route state and notification settings. | For the session or persistently, until the data is replaced, the user clears browser data or the account is deleted. |
| Wandrio IndexedDB and local caches | Local caches of activity, route, map, tile, view and feed data to improve performance and continue a feature requested by the user. | Until the cache expires or is replaced, the user clears browser data or the account is deleted. |
| Wandrio’s own usage event measurement | Event name, view, time, platform, application version and properties limited to the relevant feature. An event from a signed-in user may be linked to the account through the server session. | Storage on the user’s device only as permitted by consent or necessity; server-side retention is defined in the Privacy Notice and analytics settings. |
| Mapbox | Request, network, device and usage parameters required to deliver map tiles and map features, and possible telemetry in accordance with Mapbox’s practices. | For the period defined by Mapbox. Current details are provided in the technology-specific list in the consent interface and in Mapbox’s privacy documentation. |
| Google Cloud/Firebase hosting and security | Technical request, IP address, security and error data used to deliver, protect and troubleshoot the service. | As described in Wandrio’s Privacy Notice; ordinary service logs are generally retained for 30 days. |
The exact names, providers and maximum durations of the technologies are shown in Cookie Settings. The list is updated when technologies are added to or removed from the service.
4. Giving and withdrawing consent
When a user visits Wandrio’s web service, they may accept all optional technologies, reject them or make category-specific choices. Rejecting is as easy as accepting, and optional categories are not preselected. Strictly necessary technologies remain active even when optional technologies are rejected.
Users may change their choices at any time through the Cookie Settings link on the site. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal. Rejecting optional analytics does not prevent use of Wandrio’s core features.
5. Browser and device settings
Users may remove cookies, localStorage data and IndexedDB databases through their browser settings. Blocking or removing browser data may sign the user out, reset settings to their defaults, remove local caches and prevent some features from working. A general browser cookie block may not withdraw consent previously given to the service, so the choice should also be changed in Wandrio’s Cookie Settings.
6. Personal data and third parties
If information collected through a technology can be linked to a user, it is personal data. The processing of personal data, recipients, international transfers, retention periods and user rights are described in Wandrio’s Privacy Notice. Third parties, such as Mapbox and sign-in providers, may also process data in accordance with their own privacy practices when acting as independent controllers.
7. Changes to this notice and contact details
Wandrio updates this notice when the purpose, provider or retention period of a technology changes. The current version and update date are published on Wandrio’s website. Questions concerning cookies, consent or the processing of personal data may be sent to support@wandrio.net.
8. Legal sources
1. Traficom’s National Cyber Security Centre Finland: Cookies — consent, strictly necessary cookies and information requirements in Finland
2. EU General Data Protection Regulation — processing of personal data and transparency
3. European Data Protection Board: Guidelines on consent — freely given, specific, informed and unambiguous consent