Taxometer · Privacy Policy
Local records, online maps, Google Drive, SumUp and your privacy choices.
Effective October 3, 2026
Scope and contact
Taxometer is developed by Oleksii Burdeniuk, Kraków, Poland. Privacy contact: burdeniuk.oleksiy@gmail.com. This policy covers the app. The website has its own privacy policy. Core features require no developer account; connecting Google Drive or using SumUp is optional.
Trips, tariffs, settings, payment results and optional driver, company, vehicle and licence details are stored on your device. The developer does not operate a backend receiving your trip history. No advertising, behavioural tracking or analytics SDK is used by the current app. Online services described below still receive data when you use their features.
Location and records
After permission and a user-started metered trip, precise GPS positions, timestamps, speed and accuracy support distance, time and fare estimates, including while the screen is locked or another app is open. Recording is tied to an active trip; pausing or finishing ends trip recording. Location is not used for advertising. Revoke access in system settings to prevent further access. GPS metering requires the relevant permissions; fixed-price records without GPS metering can be used where available.
Records can contain route points, pickup/drop-off addresses, dates, duration, distance, tariff, totals, discounts, tips and payment references. Optional profile fields include name, telephone, email, business address, tax identifier, driver identifier, licence details, vehicle registration and VIN. Settings and bounded address/route caches stay local. Active-trip widgets or Live Activities may display summaries on your lock screen; control visibility in system settings.
Network services
Online address search/reverse lookup sends search text and/or selected precise coordinates to Photon (photon.komoot.io). Route calculation sends pickup, destination and stop coordinates to Valhalla (valhalla1.openstreetmap.de) or OSRM (routing.openstreetmap.de). Map tiles, fonts and sprites are requested from OpenFreeMap and reveal network information and the viewed map area. Automatic trip address lookup uses the operating system’s Apple/Google geocoder; the web version uses OpenStreetMap Nominatim. These providers receive request/network information, including IP addresses where applicable; their policies govern logs and retention. The developer does not control those public services or guarantee their availability.
Connecting Google Drive authorises access using the drive.file scope and stores your account email and upload settings locally. Connecting enables automatic receipt upload; you can disable it. Receipt PDFs in your Google account can include addresses, trip dates, totals and the optional profile details included in the document. PDFs do not include the raw GPS track. Uploads are private by default. Creating a receipt QR/link sets that file to anyone-with-the-link access: anyone receiving or forwarding the link can read it. Review the PDF before sharing; remove public access or delete the file in Google Drive when needed.
Choosing card payment opens the separate SumUp app. Taxometer passes amount, currency, a trip/payment reference and callback information. SumUp handles merchant authentication, payment authorisation and card data under its own terms. Taxometer receives the returned payment outcome and, when available, a transaction reference, and stores these locally. The developer does not receive full card numbers, security codes or banking credentials. No trip route or profile is passed in the SumUp payment request.
Exported receipts and shared files go to the recipients/services you choose. If you email support, the developer receives your address and the content you send, using an email provider. Send only information needed for the request; redact passenger details and payment identifiers where possible. Do not send passwords or card data.
Purposes and legal bases
Data is used to deliver the functions you request, maintain local records, provide optional cloud export and payment handoff, and answer support requests. For personal data handled by the developer, responding to service requests relies on performance of the service, necessary troubleshooting on legitimate interests, and required recordkeeping on legal obligations; optional device access is subject to permission. OS permission is not a universal legal basis for processing another person’s data. If you use the app professionally, you are responsible for the lawful basis, notices and security of passenger, employee and business data you enter or share.
Local records remain until deleted, app storage is cleared or the app is uninstalled; exports and system backups may remain separately. Disconnecting Google Drive stops app access/upload settings but does not delete uploaded files or necessarily revoke the Google authorisation: manage both in your Google account. Delete cloud PDFs and revoke public links separately. SumUp keeps its own transaction records. Support correspondence is retained only while needed to resolve requests and satisfy applicable legal obligations; unnecessary attachments are removed. Providers set their own retention periods.
Where applicable, you may request access, correction, erasure, restriction, portability, or object to processing; consent can be withdrawn without affecting prior lawful processing. Contact the developer for data held by the developer and the relevant provider for provider-held data. You can complain to your local supervisory authority, including Poland’s UODO. Google, SumUp and other providers may process data outside your country/EEA under their published safeguards; consult their policies. Local storage does not eliminate device, backup or sharing risks.
Protect your device, cloud account and receipt links; no system is completely secure. The app is not directed at children. Do not include personal data you have no right to process. Changes will be published here with an updated date; material new processing or permissions require appropriate information before use. Contact us with questions about this policy.
Provider information
These links explain the external services’ own processing. Their policies do not replace this policy. Using a provider is limited to the feature you request; the developer does not sell personal data.
Oleksii Burdeniuk · Kraków, Poland · burdeniuk.oleksiy@gmail.com
Email the developer