Maps4Garmin Privacy Policy
Maps4Garmin Privacy Policy:
Last Updated: May 4, 2026
Please note, you may use Google Translate to translate this document, but the ultimate authority comes from the English version of the document.
We may update this Privacy Policy from time to time. The 'Last Updated' date at the top of this policy indicates when it was last revised. For minor changes, we will update this page and revise the date. For material changes that affect how we collect, use, or share your personal data, we will provide additional notice through the app or other reasonable means before the changes take effect.
By using “Maps4Garmin”, an app on the Garmin Connect IQ Store, you agree to the following privacy policy.
Data we store:
The following information is collected and stored to help us understand how the app is used and to improve it:
- Zoom level, device type
- Number of app opens, date of app open (coarsened to date upon receipt), and # of successful and # of failed maps/radar images requested during app session
- Whether the user has purchased the app, or if they're a legacy user who inherited the weather radar features.
- Engagement with specific features and in-app announcements
- Whether the device has a touchscreen
- App version number
- Month of first app open (coarsened to month upon receipt; precise date/time is not retained)
- Language
- Whether or not GPS location was ascertained during the session
Error reporting via Garmin:
When Maps4Garmin encounters an error or crash on your device, Garmin's Connect IQ platform may capture diagnostic information about the error — including stack traces, device type, language, and app version — and make it available to us through Garmin's developer tools for the purpose of investigating and fixing bugs. This data is collected and retained by Garmin under their privacy practices, not by us. We access it through Garmin's tools but do not separately store it. For information on how Garmin handles this data, see Garmin's privacy policy at https://www.garmin.com/en-US/privacy/connect/.
Data transmitted but not stored:
Your IP address, HTTP request headers, map tile coordinates, and navigation start/end coordinates are transmitted to our servers in the course of providing the app's functionality. None of these are logged or stored on our servers.
IP addresses. Your IP address is transmitted to our servers as part of normal HTTP communication and is used to determine your country of origin for compliance with US export control regulations (e.g., to prevent use from embargoed regions). This determination is performed using a local geolocation library; your IP is not transmitted to any third party.
Data Retention:
The analytics data we retain contains no persistent identifiers and cannot be reasonably linked to any specific user or device. It is retained indefinitely for product improvement and historical analysis.
3rd Party Services:
Maps4Garmin uses the following third-party services to provide its functionality. Each service has its own privacy policy, which governs how they handle data they receive.
- XWeather. Maps4Garmin uses XWeather (operated by Vaisala Oyj) to provide weather radar tiles. When you view the radar, your watch sends a request to our servers, which then request the corresponding map tile from XWeather using the coordinates and zoom level of your map view. XWeather receives these coordinates but does not receive your IP address or device identifier. XWeather's privacy policy is available at https://www.xweather.com/privacy.
- Google Cloud. Maps4Garmin's backend runs on Google Cloud Functions. All requests from your watch pass through Google Cloud's infrastructure, which means your IP address is transmitted to Google in the course of normal HTTP communication. Google Cloud's privacy practices are described at https://cloud.google.com/terms/cloud-privacy-notice, and you can also see Google's privacy policy here: https://policies.google.com/privacy.
- Openrouteservice. Maps4Garmin uses openrouteservice to provide navigation. When you request a route, your watch sends your starting location (which is your current location) and destination to our servers, which then forward those coordinates to openrouteservice to generate driving directions. Openrouteservice receives precise location data (start and destination coordinates) but does not receive your IP address or any device identifier. If you do not want your location data shared with openrouteservice, do not use the navigation feature. Openrouteservice's privacy policy is available at https://openrouteservice.org/privacy-policy/.
- Google Sheets. Maps4Garmin temporarily stages analytics data (such as app opens, error reports, version info, and other non-location event data described in the "Data we Store" section) in Google Sheets before it is moved to our analytics database. Google Sheets is operated by Google. Google's privacy policy is available at https://policies.google.com/privacy.
- StadiaMaps. Most map tile requests are proxied through our servers, which forward only the tile coordinates to our map provider. However, for satellite imagery and certain specialty map styles, your device contacts StadiaMaps directly. In these cases, StadiaMaps receives your IP address and the geographic coordinates of the map view (which is often your location, since the map is centered on your location at startup). https://stadiamaps.com/privacy/privacy-policy/
Premium Feature Licensing (KiezelPay / kPay):
Maps4Garmin uses KiezelPay (also known as kPay) to manage premium feature licensing. The KiezelPay library in our app periodically transmits your Garmin device ID to KiezelPay's servers to verify license status. This occurs for all users, including those who have not purchased premium features.
If you choose to purchase premium features, you complete the transaction directly on KiezelPay's website, where they collect payment information and any required contact details.
KiezelPay acts as an independent data controller for your purchase data. After a purchase is completed, we have access to the following information about your transaction through KiezelPay's web interface:
- Your name and country
- Your Garmin device ID and device type
- Transaction reference number
- Date of purchase and refund status
- Payment method used (e.g. Apple Pay, credit card, PayPal)
- Total amount paid, tax paid, and any payment processing fees
- Timestamps for stages of your purchase flow (e.g. when the purchase was initiated, when payment processing began and completed)
We do not receive your payment card details or full billing address.
Legal basis (GDPR): legitimate interest in operating a licensing system and understanding our purchase flow for fraud prevention and service improvement; contract performance for processing purchase records and refunds.
The device ID transmission is a technical requirement of the licensing system; if you don't want this, don't use the app.
KiezelPay's privacy policy: https://s3.amazonaws.com/kiezelpay/agreements/Privacy-Policy.pdf
Children's Data:
This app is not directed at children under 13 (or under 16 in the European Union). We do not knowingly collect personal data from children. If you believe a child has used this app and you have concerns, please contact us.
Legal Basis (EU/UK Users): We process this data based on our legitimate interest (Article 6(1)(f) GDPR) in understanding how the app is used and improving its functionality. Because we do not collect persistent identifiers, this processing has minimal impact on individual privacy rights.
Your Rights (EU/UK Users):
Under GDPR, you have the right to: access your data, request correction, request deletion, restrict processing, data portability, object to processing, and lodge a complaint with your local data protection authority. To exercise any of these rights, email sirlancelot2604@outlook.com.
Important note on identification:
Because we do not collect persistent identifiers, we cannot identify which data in our analytics belongs to any specific user or device. Under Article 11 of the GDPR, when a controller cannot identify a data subject, certain individual rights (access, correction, deletion, portability) may not be technically possible to fulfill. If you can provide additional information that would allow us to identify your data, we will honor your request to the extent possible. You may also object to all processing of your data, in which case we will work with you to find an appropriate solution. To exercise these rights or ask questions, email sirlancelot2604@outlook.com.
All the data is submitted to us, and not to Garmin. Garmin has no responsibility or liability for the data Maps4Garmin collects.
LBS Provider follows CTIA’s Best Practices and Guidelines for Location-Based Services. If you want more information, please visit this link: https://www.ctia.org/the-wireless-industry/industry-commitments/best-practices-and-guidelines-for-location-based-services
As with any location based provider's service, there are location-based risks with using this app, including your location being intercepted/leaked. Please be aware of this while using this app.
LBS Provider follows CTIA’s Best Practices and Guidelines for Location-Based Services. If you want more information, please visit this link: https://www.ctia.org/the-wireless-industry/industry-commitments/best-practices-and-guidelines-for-location-based-services
As with any location based provider's service, there are location-based risks with using this app, including your location being intercepted/leaked. Please be aware of this while using this app.
Questions?
Email me at sirlancelot2604@outlook.com.
Email me at sirlancelot2604@outlook.com.
May 9, 2026 update: Add note that regardless of purchase status, deviceId is processed by Kiezelpay.
May 4, 2026 update: Add Kiezelpay information.
May 3, 2026 update: Add Stadiamaps information, and remove the statement about 24 hour IP retention in Google Cloud.
May 1, 2026 update: This policy was substantially revised on May 1, 2026 to more accurately reflect what data Maps4Garmin actually collects and retains. Key changes include: clarifying that timestamps are coarsened (dates only for app opens, month only for first app open), removing references to data fields no longer collected, adding a Data Retention section, expanding disclosures about third-party services, and adding GDPR-specific sections for EU/UK users (legal basis, rights, and Article 11 identification limits).