DrivePulse Privacy Policy

DrivePulse is a GPS driving utility for maps, live speed, trip recording, trip history, Street View access, and map measurement tools.

Effective: July 4, 2026 App: DrivePulse Package: com.drivepulse.gps

DrivePulse does not require an account and does not currently provide cloud sync. Saved trips, saved measurements, and app preferences are stored on your device.

Some app functionality uses third-party services such as Google Maps and, on Android, Google Mobile Ads, the Google User Messaging Platform, Firebase Analytics, Firebase Crashlytics, Firebase Remote Config, and Google Play Billing. Those services may process technical, usage, advertising, device, diagnostic, consent, billing, subscription, or location-related information as described below.

Information DrivePulse Uses

Location

Approximate and precise location may be used to show your current position, calculate live speed, record trip route points, and move map tools to your location.

Trip Data

Trips can include duration, distance, average speed, max speed, start/end coordinates, route points, and generated trip summary images.

Measurement Data

Saved distance, area, and radius measurements can include titles, selected units, calculated values, map points, and circle radius data.

Settings

DrivePulse stores preferences such as language, theme, speed unit, map style, and speed alert configuration.

Analytics Data

Android builds may use Firebase Analytics for app interactions, screen usage, feature usage, diagnostics, and device or app identifiers.

Crash And Diagnostic Data

Android release builds may use Firebase Crashlytics for crash reports, non-fatal error reports, app version, screen name, and limited technical diagnostics.

Advertising Data

Android builds may use Google Mobile Ads to display banner, native, interstitial, and app-open ads. The SDK may automatically collect or share IP address, app and ad interactions, diagnostic information, advertising identifiers, app-set identifiers, and other device or account identifiers for advertising, analytics, and fraud prevention.

Subscription And Purchase Data

Android builds may use Google Play Billing for premium subscriptions. DrivePulse may receive and store limited subscription entitlement details such as product ID, base plan, offer ID, purchase state, purchase token, acknowledgement state, expiry-related status, and whether premium access is active. DrivePulse does not receive your full payment card number or bank account details.

Consent And Privacy Choices

The Google User Messaging Platform may request, store, and communicate consent or privacy choices where required. These choices can affect whether personalized, non-personalized, or limited ads may be requested.

Remote Configuration

Firebase Remote Config is used to retrieve feature flags and configuration values. Firebase may use an app installation identifier and limited app or device information to deliver the applicable configuration to an app installation.

Shared Content

When you choose to share a trip summary image, the image is handled by the app or service you select from the system share sheet.

How Information Is Used

DrivePulse uses information to provide and improve app features, including:

Showing maps, traffic layers, current location, and Street View entry points.
Displaying live GPS speed, HUD mode, full-screen speed, and speed alerts.
Recording, saving, showing, deleting, and sharing trip summaries.
Creating, saving, editing, updating, and deleting distance, area, and radius measurements.
Remembering app preferences such as language, theme, map style, and units.
Understanding app usage and stability so DrivePulse can be improved.
Displaying, measuring, limiting, and protecting advertising where enabled.
Loading Google Play subscription details, processing premium purchases, checking active entitlement, and hiding ads for active premium subscribers.
Obtaining required advertising consent and applying applicable privacy choices.
Delivering feature flags and configuration without requiring an app update.

Location Permission

DrivePulse requests location permission because current location, speedometer, trip recording, and map tools depend on location. You can deny location permission and still pan maps or add measurement points manually.

If location permission or device location services are disabled, features that need current location or GPS speed may not work until they are enabled.

The current version is designed for foreground trip recording and does not declare Android background location permission.

Local Storage

Saved trips and saved measurements are stored locally in the app database on your device. DrivePulse does not currently upload saved trip history, saved measurement records, route titles, or saved route point lists to a DrivePulse cloud server.

Android automatic app backup is disabled for this version, so local DrivePulse app data is not backed up by Android's automatic app backup mechanism.

Analytics And Diagnostics

DrivePulse may use Firebase Analytics and Firebase Crashlytics on Android to understand which screens and features are used, monitor app behavior, diagnose crashes and non-fatal errors, and improve reliability. Analytics and diagnostics data may include app interactions, screen names, feature events, crash logs, diagnostics, app version, and device or app identifiers.

DrivePulse should not intentionally log precise trip routes, saved measurement points, saved measurement titles, start/end coordinates, speed values, or personal notes as analytics event parameters. If this changes in a future release, this policy and Play Store disclosures should be updated before release.

Firebase is provided by Google. You can learn more at Firebase Privacy and Security.

Advertising And Consent

Android builds may display ads provided through Google AdMob and the Google Mobile Ads SDK. Depending on the screen and configuration, these may include banner, native, interstitial, full-screen native, or app-open presentations. Ads may be enabled, disabled, or selected through remote configuration.

Google states that the Google Mobile Ads SDK automatically collects and shares IP address, user product interactions such as app launches, taps, and video views, diagnostic information, and device or account identifiers such as the Android advertising ID and app-set ID. Google uses this information for advertising, analytics, and fraud prevention. An IP address may be used to estimate a device's general location.

DrivePulse does not intentionally send precise GPS coordinates, recorded route points, saved measurement points, trip titles, or saved measurement titles to the Google Mobile Ads SDK as ad-request parameters.

Where required, DrivePulse uses Google's User Messaging Platform to request and apply consent or privacy choices before requesting ads. The available choices and resulting ad treatment depend on your region, Google's consent message configuration, applicable law, and whether Google permits ads to be requested. Ads may be personalized, non-personalized, or limited.

You can reset or delete the Android advertising ID using your device's advertising privacy controls. Learn more from Google Mobile Ads data disclosure and Google advertising technologies.

Subscriptions And Google Play Billing

Android builds may offer DrivePulse Premium subscriptions through Google Play Billing. Subscription products, prices, trial availability, billing period, taxes, purchase confirmation, renewal, cancellation, and refunds are handled by Google Play and shown in the Google Play purchase flow before purchase.

DrivePulse uses Google Play Billing to query available subscription plans, start purchases, acknowledge purchases where required, restore purchases, and check whether a premium subscription is active. The app may store the last known premium entitlement state locally so it can decide whether to show ads or premium purchase options during startup.

Purchase-related information can include product ID, base plan ID, offer ID, purchase token, purchase state, acknowledgement state, purchase time, auto-renewing or entitlement state, and limited order or account information provided through Google Play Billing. DrivePulse does not collect or store full payment card numbers, bank account numbers, or Google account passwords.

You can manage or cancel subscriptions through Google Play subscription settings: https://play.google.com/store/account/subscriptions. Google Play's privacy practices are described in Google's Privacy Policy.

Remote Configuration

Android builds use Firebase Remote Config to retrieve feature availability, advertising configuration, onboarding behavior, update behavior, and other operational settings. The app keeps a local fallback and may cache the last successful configuration on the device. Remote Config uses an installation identifier to fetch configuration for an app installation. Remote configuration values do not contain your saved trips, route points, measurements, titles, or precise location.

Third-Party Services

DrivePulse uses third-party services to provide app functionality:

Google Maps Platform: Used for maps, map styling, traffic display, Street View, and map-related interactions. Google may process technical and location-related information according to Google's privacy practices.
Firebase Analytics on Android: Used for usage analytics and app improvement as described above.
Firebase Crashlytics on Android: Used for crash reporting, non-fatal error reporting, diagnostics, and app reliability improvements.
Firebase Remote Config on Android: Used to retrieve and cache feature flags, operational settings, advertising configuration, and rollout controls.
Google AdMob and Google Mobile Ads on Android: Used to request, display, measure, and protect advertisements, and to support advertising analytics and fraud prevention.
Google User Messaging Platform on Android: Used to obtain and apply advertising consent and privacy choices where required.
Google Play Billing on Android: Used to show subscription products, process premium subscription purchases, restore purchases, and check active premium access.

Google's Privacy Policy is available at https://policies.google.com/privacy.

Data Sharing

DrivePulse does not sell your personal data. DrivePulse does not currently provide a DrivePulse backend, account sync, or cloud backup for saved trips and measurements.

Data may be collected, processed, or shared by service providers such as Google Maps Platform, Firebase Analytics, Firebase Crashlytics, Firebase Remote Config, Google AdMob, Google Mobile Ads, and the Google User Messaging Platform to provide maps, analytics, diagnostics, configuration, advertising, consent management, fraud prevention, and related app functionality.

If you manually share a trip summary image or other content through your device share sheet, that is a user-initiated action and the selected receiving app controls its own handling of the shared content.

Security

DrivePulse keeps app-created trip and measurement records on your device in the current version. Network services such as Google Maps and Firebase use their own transport security practices. No method of electronic storage or transmission is completely secure.

Data Deletion

You can delete saved trips from the trip history screens and delete saved measurements from the saved measurements screen. You can also remove local DrivePulse data by clearing app storage or uninstalling the app from your device.

Because DrivePulse does not currently use DrivePulse accounts or cloud sync, deleting local app data removes the local records controlled by the app on that device.

Clearing app data or uninstalling DrivePulse does not necessarily delete information already processed by third-party service providers. Their retention and deletion practices are governed by their respective policies. You may reset or delete your Android advertising ID through your device settings.

Children's Privacy

DrivePulse is not directed to children under 13. The app is intended for driving, travel, map utility, and measurement use. If you believe a child has provided personal information through the app, please contact us.

Current Release Scope

The current release may include:

Live map, traffic map, current location, map styles, and Street View access.
GPS speedometer with KM/H and MPH support, full-screen speed, HUD mode, and speed alerts.
Trip recording, trip history, trip analytics, trip detail, deletion, and summary image sharing.
Distance, area, and radius measurement tools with saved measurement support.
Settings for language, theme, speed units, and default map style.
Android Firebase Analytics for usage analytics and app improvement.
Android Firebase Crashlytics for crash and non-fatal error diagnostics.
Android Firebase Remote Config for feature flags and operational configuration.
Android Google AdMob and Google Mobile Ads for advertising.
Android Google User Messaging Platform for applicable advertising consent choices.
Android Google Play Billing for premium subscription products, purchase flow, purchase restore, and premium entitlement checks.

Changes To This Policy

This Privacy Policy may be updated when DrivePulse adds or changes features such as cloud sync, account login, subscriptions, new advertising providers, background trip recording, cloud storage, or expanded analytics. Updates will be posted on this page with a revised effective date.

Contact

If you have questions about this Privacy Policy or DrivePulse privacy practices, contact:

Email: vishalbhimporwala@gmail.com

Play Store Data Safety declarations must match the app behavior and third-party SDKs in the release build. Review your final build before submitting updates to Google Play.