Privacy Policy

Last updated: 2026-09-30 · com.supertripper.app

1. Who we are

Super TripperPod is an app for Android and iPhone (iOS), developed independently by Guilherme Marzochi (individual developer), that connects smartphones to the TripperPod navigation display over Bluetooth Low Energy (BLE), with navigation through Google Maps or a built-in offline map.

Contact: suporte@marzochi.com.br

2. Data the app accesses on your device

The app accesses the following information on your device, solely so that it can work:

• Bluetooth: to find and connect to the TripperPod over BLE. No Bluetooth data is stored or sent to third parties.
• Notifications (Android): to read Google Maps notifications in real time and extract navigation data (distance, maneuver, estimated time). Notification content is not stored or sent to third parties (optional exceptions in sections 4.7 and 4.8).
• Location (GPS): used on the device for the compass and for navigation on the built-in map (position, heading and route calculation). Your location is not sent to or stored on our servers. To show the weather, approximate coordinates are sent to Open-Meteo (section 4.4).
• Phone state (Android, optional): used only to show the call icon on the display when your phone rings. No call data (number, contact, duration) is stored or sent.
• Local storage: the address of the last TripperPod, downloaded offline maps, recent destinations and preferences are saved only on your device.

3. Data the app does not collect

• Your GPS location or your trips on our servers. The approximate location shown in the developer's dashboard (country, state, city) comes exclusively from the IP address via GeoIP.
• Account information, email or password. Purchases are processed by Google Play or the App Store; the app never sees your card details.
• Your name, contacts, call data, photos or personal files.
• Any personally identifiable information.

4. Data sent over the internet

The app sends data to the developer's server and, where stated, to external services, in the situations below.

4.1 Audience and usage ping (automatic when the app opens)

Each time the app is opened, the following information is sent for anonymous user counting and product improvement:

• Anonymous session identifier (a UUID generated at each launch, not linked to any user or account).
• Anonymous device identifier (an irreversible SHA-256 hash of a device identifier, such as the Android ID, truncated to 16 characters; it cannot be used to identify the user or the device).
• App version, operating system version and device model (e.g. "Samsung SM-G991B").
• System locale and time zone.
• Approximate location derived from the IP address via GeoIP (country, state, city), without access to the device's GPS.
• Anonymous, aggregated usage statistics: how many routes were made with each navigation engine, how many times the app was opened, total distance travelled (odometer) and the current plan. No destinations, no trips, no coordinates.

This data is deleted automatically after 30 days of inactivity.

4.2 Address search (when you search online)

When you search with a connection, the text you type may be sent to geocoding services to return results: Photon (komoot, based on OpenStreetMap) and Nominatim (OpenStreetMap) for addresses, and Google Places for points of interest and businesses by name. To reduce this, the app first tries the local (offline) search and an on-device cache, and only uses online services when needed. House-number search in Brazil and search within an already downloaded region work offline, without sending anything.

4.3 Maps and routing graphs

Map images (tiles) are downloaded from OpenFreeMap, CARTO and OpenStreetMap. As with any online map, these services receive your IP address and know which area of the map is being displayed. Offline routing graphs are downloaded from our own server (grafos.marzochi.net), without sending your location.

4.4 Weather

To show the weather and forecast along the route, the app sends approximate coordinates to Open-Meteo (api.open-meteo.com). No identifier of yours is sent with these requests.

4.5 Purchase and subscription validation

When you buy a paid feature, the app sends the developer's server the anonymous device identifier and the purchase receipt issued by Google Play or the App Store, to confirm and unlock the feature. The server may query the store to validate the subscription. Per device, we only keep the entitlement status (e.g. "active subscription", "founder") and dates; never your card details or your Google or Apple account data, which are handled exclusively by the respective store.

4.6 Crash reports

When the app closes unexpectedly, a technical report is sent so the problem can be fixed: the error trace (stack trace), app and system version, device model and an installation identifier. No location and no routes.

• Android: reports are sent through Firebase Crashlytics (Google), subject to Google's privacy policy.
• iPhone: reports go to our own server, with the same kind of technical data.

4.7 Maneuver icon recognition

When the app finds a Google Maps maneuver arrow it does not yet recognise, it may send only the icon image (no text, no location) to our server, to improve recognition in future versions. You can turn this off at any time in Settings › Navigation, in the privacy section, with the "Help improve icon recognition" switch.

4.8 Support diagnostics (only with a code)

If you are being helped by support and type a code they give you into the app, the app captures up to 5 Google Maps navigation notifications over 24 hours and sends them to our server, only to analyse your case. Without the code, none of this happens.

4.9 Help request (voluntary)

When you use the "Report a problem" option in the app, the following is sent: the problem description, the Bluetooth connection status, the last navigation instruction received, the app version and the device model. Sending is always started by you and never happens automatically.

Data sent to the developer's server is stored securely on our own server located in Brazil.

5. Waze Mode (Android, beta)

In Waze Mode, the app receives turn, distance and speed-camera data from a modified, compatible build of Waze that you install yourself, through a local broadcast inside your phone. Nothing related to Waze Mode is sent to our server. The permission to remove apps is used only when you tap "Uninstall Waze" in the Waze card.

6. Permissions requested (Android)

• BLUETOOTH_SCAN / BLUETOOTH_CONNECT: to find and connect to the TripperPod over BLE.
• ACCESS_FINE_LOCATION: for the compass and navigation on the built-in map (position and heading). Used on the device; we do not transmit your location.
• BIND_NOTIFICATION_LISTENER_SERVICE: to read Google Maps notifications and obtain navigation data in real time.
• READ_PHONE_STATE (optional): only to show the call icon on the display when your phone rings. It is an optional step of the initial setup; no call data is stored or sent.
• REQUEST_DELETE_PACKAGES: used only when you tap "Uninstall Waze" in the Waze card.
• FOREGROUND_SERVICE: to keep the BLE connection and navigation running in the background.
• POST_NOTIFICATIONS: to show the connection status notification in the system bar.
• BILLING: to offer and validate purchases and subscriptions through Google Play.
• INTERNET: for the transmissions described in section 4.

On iPhone, the system asks for the equivalent authorisations (such as Bluetooth and location), for the same purposes.

7. Third-party services

Super TripperPod does not include analytics, advertising or tracking SDKs (such as Google Analytics, Facebook SDK, etc.) and is completely ad-free. The only third-party SDK that sends data is Firebase Crashlytics, used on Android for crash reports only.

Each service is subject to its own privacy policy.

The app reads notifications generated by Google Maps, but has no affiliation, partnership or official integration with Google LLC. Google Maps is used by the user independently.

8. Security

Technical data is sent to the developer's server over HTTPS with token authentication. No personal data is transmitted. Bluetooth communication with the TripperPod uses PIN authentication according to the device's protocol.

9. Data retention

Anonymous audience data (launch ping) is deleted automatically 30 days after the session's last activity. Crash reports, maneuver icons, support diagnostics and help requests are kept for as long as needed for analysis and may be deleted by the developer at any time. No personal data is retained.

10. Your rights (LGPD and GDPR)

You have the rights provided by Brazil's General Data Protection Law (LGPD, Law No. 13,709/2018) and, if you are in the European Union, by the General Data Protection Regulation (GDPR), including confirmation, access, correction and deletion of data. Since the app does not collect personally identifiable data, in most cases there is no data linked to you; even so, any request can be made by email to suporte@marzochi.com.br.

11. Children

Super TripperPod is intended for adult motorcyclists and is not directed at children under 13. We do not collect data from children.

12. Changes to this policy

This policy may be updated as the app evolves. Updates will be published on this page with the revision date updated. Continued use of the app after changes means you accept the new version.

13. Contact

For privacy questions or requests: suporte@marzochi.com.br

See also the Terms of Use.