Autogas Finder privacy policy
Beta version, updated: 4 November 2026.
1. Controller and contact
The data controller is Leszek Piszczyk, trading as QUALITY ASSURANCE SERVICES LESZEK PISZCZYK, ul. Dziewanny 21B/7, 44-102 Gliwice, Poland, tax ID 6391870546. Contact for app and privacy matters: kontakt@autogasfinder.app.
2. Browsing and data on your device
Browsing the map does not require a name, email address or account. The app contains no advertising, advertising profiling or advertising analytics. On your device we store settings, consents, favourites, selected route history, notes and trip costs, a local report queue and the community account token. The scope depends on the features you use. Local data can be removed in the app settings or by clearing app data. Uninstalling the app alone does not delete account data from the server.
3. Community account and reports
At the first action requiring the server, the app may create an account without a name, email address or password. The server generates a random access token and stores its SHA-256 hash, the account ID, creation and activity times, points and moderation status. The account is pseudonymous: reports can be linked to one identifier, so we do not treat them as fully anonymous data.
Information sent includes the location of the reported place or incident, content, time, report type, service rating and link to the account. If you share your location when reporting, your coordinates are sent to the server to calculate distance. The database stores the distance and on-site status, rather than those coordinates as a movement history. Some reports also send a direction or speed. Queries about nearby incidents include a search area or coordinates. We do not build a travel tracking log.
Report content, information about places and aggregated confirmations may be shown to other users. Do not put third-party personal data, vehicle registration numbers or sensitive data in comments.
4. Purposes, legal bases and retention
We process data necessary for accounts and reports to provide the selected service (Article 6(1)(b) GDPR). Security, abuse prevention and handling claims are based on the legitimate interests of the controller (Article 6(1)(f)). Access to GPS and the optional map depends on your consent; you can withdraw it in the app or device settings without affecting earlier lawful processing.
- The account remains until it is deleted; there is currently no automatic expiry date for an inactive account.
- Station reports, service information and votes on new places are retained for up to 400 days.
- Links between inactive incidents, their votes and the account are anonymised after 30 days.
- Speed-camera votes are deleted after 548 days; replaced votes lose their account link 30 days after closure.
- The report rate-limit log is deleted after 2 days. The salted IP hash used to limit registrations is retained for up to 48 hours.
- Retention is handled by server maintenance; deletion may occur during the next maintenance cycle. Backups rotate through 14 copies per database on a daily schedule. Data deleted from the active database may remain in access-restricted backups until that rotation expires. Restoring a backup requires deletion requests to be applied again.
- Support correspondence is retained while the issue is handled and for any defence against claims. The hosting provider may keep separate security logs; we do not state an unconfirmed retention period for those logs.
5. Providers and external connections
McProdukt hosts the website and community server; OVHcloud is the domain registrar. The controller is responsible for appropriate data processing agreements and processing scope with providers.
When Google Maps is enabled, the device connects to Google and sends, among other things, the IP address, device information, map area and coordinates used for route calculation in Google Routes. A public OSRM server may be used for fallback routes and receives route points. Opening directions in Google Maps or another navigation app passes the selected destination to that provider. Speech synthesis may use operating-system services. Provider policies: Google, OVHcloud, OSRM. External providers may process data outside the EEA under the terms in their documents and with appropriate safeguards. We do not sell user data.
Optional city or address dictation starts when you press the microphone button. Android requires microphone permission. Your system speech provider handles recognition; depending on your device and settings, audio may be sent to that provider. Autogas Finder receives the recognized text and inserts it into the selected search field. The microphone is released when dictation ends or is cancelled.
6. Account deletion and export
In the app, open Settings and select data export or Delete my account and data from the server. Deletion requires confirmation. The account, its token, reports and votes are deleted; added places and incidents may remain without a link to the account. This does not delete open data from public registers.
The external deletion request route is available on the account deletion page. Do not email your token. If you lose it, we have no email address assigned to the account with which to recover it. You can raise questions at kontakt@autogasfinder.app; we will determine an available verification method, without promising identification by name alone.
7. Your rights
You may request access, rectification, erasure, restriction of processing and data portability in the cases provided by law, object to processing based on legitimate interests and withdraw consent. We generally respond within one month; complex requests may require an extension under the GDPR. You may lodge a complaint with the President of the Polish Personal Data Protection Office: UODO.
8. Browser storage and changes
The app uses localStorage and cache storage. It does not set its own advertising cookies. Google mapping services have their own storage and privacy policies. We publish document changes with an update date. The information website does not load maps, analytics or advertising.
Accounts, saved routes, places and statistics
Optional accounts can synchronise favourites, the vehicle profile, saved route plans and places across your devices. Saved places contain a name, address, type and coordinates. They are private to your account and are included in account export and deletion. Plans contain selected start, destination, up to five waypoints and route preferences, rather than a GPS journey history or stored Google route geometry. Opening a plan calculates the road route again and may produce a different result. Deleting the account removes these saved data from the active database. A minimal version marker for deleted plans prevents an offline device from restoring them.
A shared link exposes its route points and preferences to anyone who receives it, but contains no password or account token. A complete local backup is different and must be kept private because it can contain account access.
Optional first-party counters store only a UTC day, platform, fixed event name and total count. No email, full URL, route points, visitor ID or IP address is stored in the counters table. There are no analytics cookies. Do Not Track and Global Privacy Control disable event submission. A short-lived salted IP digest in process memory limits abuse. Daily totals older than 90 days are removed during database maintenance or event recording. Independent hosting security logs are described above. Only the verified owner can read the aggregate dashboard. Account, route and place sync is available after sign-in. Optional counting depends on server configuration.