poiPrivacy Policy
No registration or profile
poi does not ask you to register, provide a name or email address, or create a profile. It uses a technical Firebase identifier so the app can authenticate requests, apply usage limits and recognise an active subscription. This identifier is not shown as a user account in the app.
Route data
Routes you import or build are stored on your device. They can include route points, elevation and distance data, waypoints, titles and place data; local routes are excluded from device backup. When you request routing, place search or save a route to the service, route geometry and the technical identifier are sent to our server. Server-side route records can include route geometry, a route name, distance, ascent and update time. We also keep technical quota, region and subscription-entitlement records.
Technical recovery data
The app uses a recovery UUID and, on Android, Android ID as technical recovery keys. The server stores only SHA-256 hashes of these values bound to the technical identifier; it does not store the raw values. These keys help prevent a reinstall from receiving a fresh usage quota.
Providers and transfers
- Google Firebase provides authentication and Firestore storage.
- Routing and place-search services process the route geometry and search requests needed for results.
- RevenueCat processes subscription entitlement information. Apple or Google process payment through their store; we do not receive payment-card information.
- OpenStreetMap and OpenFreeMap data support map and surface information. Attribution is shown in the app.
Providers may process data outside the European Economic Area. Where that happens, the transfer uses safeguards required by applicable data-protection law.
Analytics and consent
Firebase Analytics is enabled only after you choose to share usage data. The app does not use advertising identifiers, advertising use, Google signals or an analytics user ID. Usage events do not include route geometry, route titles or the technical identifier. Detailed analytics event data is retained for two months.
You can change this choice in app settings. Turning sharing off disables collection and resets local analytics data. It does not delete aggregate reports that Google may already have created.
Why we process data
We process technical identifiers and route data to provide poi. We process limited data for support, security, fraud prevention and service improvement where this is in our legitimate interests. Analytics is processed with consent. We may retain or disclose data where necessary to comply with a legal obligation.
Retention and your rights
We keep data only as long as needed for these purposes, including legal obligations and disputes. Local routes remain on your device until you remove them. Depending on where you live, you may have rights to access, correct, erase, restrict, object to, or receive a copy of personal data. For a request, see Data deletion. You may also complain to the Polish President of the Personal Data Protection Office (UODO); see UODO’s complaint guidance.
Changes
We may update this policy when poi changes. The current version is published on this page.