Privacy Policy

Last revised:November 23, 2026
App:Blood Pressure & Pulse Tracker
Package name:com.pt.blood.pressure.tool
Developer:RRL TRANSPORT
Contact:muzaffar.publisher@gmail.com

RRL TRANSPORT (“we,” “us,” or “our”) is responsible for determining how and why information is processed through Blood Pressure & Pulse Tracker (the “App”). This Privacy Policy explains the information involved when you use the App, the purposes for which it is handled, the services that support the App, and the controls available to you.

1The App and Its Intended Use

Blood Pressure & Pulse Tracker provides personal health record and activity features. You can record health information, review previous entries, and view records and trends for your own reference. The App also includes a pedometer, a camera-based heart rate estimation feature, and manual export of stored historical health records.

The App does not provide medical diagnosis, treatment, medical monitoring, or healthcare services. Health entries, activity information, estimated heart rate results, and related displays are intended for personal information and recordkeeping only. For medical advice, consult a qualified healthcare professional or medical institution.

The App is not intended for anyone under 13. Children under that age should not use the App or submit personal information.

2Personal Records and Information Processed on Your Device

Information you choose to enter

You may provide optional profile attributes, including your gender, age, and height. These details are voluntary and are not required to use the App’s core features.

The App allows you to enter and view records concerning:

Information you enter is used for local recordkeeping, display, tracking, and visualization. Optional profile details and health records are stored on your device. We do not provide these entries to advertising networks, analytics providers, or other third-party services.

Step-count information

The pedometer processes step-count information to display daily activity records and trends. Where the App reads step-count data available from your device, access is limited to the information needed for step tracking.

Step-count information is not shared with third parties and is not used for advertising or profiling.

Camera-based heart rate estimation

The heart rate feature requests camera access when you actively use that feature. Camera input is used only to detect pulse-related signals for estimating heart rate, and processing takes place on your device.

The feature does not record, save, or transmit photographs or videos. Camera data is not uploaded to a server or shared with third parties.

An estimate may be affected by the device, surrounding conditions, and how the feature is used. It is not intended for medical use or health monitoring. On some devices, the camera flash or LED may become warm during operation.

3Network Services, Advertising, and Operational Information

Some App functions require network connections or third-party services. These connections involve technical information that is separate from the personal and health entries described above.

Technical information and App activity

Information collected automatically by the App or its integrated services may include:

Although this information does not consist of your manually entered health records, identifiers and network information may identify a device, an App installation, or a user in some circumstances. We therefore do not describe all such information as anonymous.

Information is obtained through your interactions with the App and through automated processing by integrated services, including Firebase and AppsFlyer.

Depending on the service involved, technical and usage information supports:

Health records are not processed for medical purposes.

Advertising, attribution, analytics, and performance providers

The App integrates the following providers to support advertising, attribution, analytics, performance monitoring, and related functionality:

ProviderPrivacy policy
Google Firebase, including Firebase Cloud Messaging (FCM)Google Privacy Policy
AppsFlyerAppsFlyer Privacy Policy
AdMob (Google Ads)Google Privacy Policy
AppLovinAppLovin Privacy Policy
Pangle (TikTok for Business)Pangle Privacy Policy
Facebook (Meta Platforms)Meta Privacy Policy
MintegralMintegral Privacy Policy
Unity AdsUnity Privacy Policy
LiftoffLiftoff Privacy Policy

These SDKs may process advertising identifiers, device and system details, network information such as IP addresses, and App events or interactions for the purposes described above. The information processed by an individual provider depends on its role and the applicable integration.

Each provider handles information under its own privacy policy. The App does not give these providers access to locally stored personal entries or health records.

Firebase Cloud Messaging

The App uses Firebase Cloud Messaging (“FCM”), a Google Firebase service, to deliver App notifications.

FCM may process the registration token or App installation identifiers used to address notifications, together with the device, App, connection, and message-delivery information needed to provide that service. These technical identifiers are separate from your locally stored health records.

Notification purposes include reminders feature updates, and summaries. Your user-entered profile details and health records are not uploaded to FCM as part of notification delivery.

Notification controls are described in Section 4. Google’s handling of information is explained in the Google Privacy Policy.

Cloudflare configuration storage and delivery

The App uses Cloudflare-hosted storage and related infrastructure to store and distribute cloud configuration parameters.

Configuration parameters control certain non-essential client behaviors, such as interface presentation, content display rules, operational parameters, service settings, and feature rollout.

When the App retrieves configuration parameters, Cloudflare may receive information necessary to handle the network request. This can include the requesting IP address, request headers, device network information, and the time of the request.

The configuration parameters do not contain your user-entered personal information or health records. The App does not upload those private entries through this function. The service distributes App configuration; it does not synchronize or back up user records to the cloud.

Cloudflare processes the technical information associated with these requests under its Privacy Policy.

MediaStack news content

The App requests news content from MediaStack through network API calls. To respond, MediaStack may receive technical request information, such as an IP address or request headers.

Providing news content does not require access to your user-entered profile details or health records, and the App does not provide those entries to MediaStack.

For details, see the MediaStack Privacy Policy.

4Device Permissions and Background Operations

Permissions and system access are used for the functions described below. Their availability and the way Android presents them may vary by device and operating system version.

Camera access - android.permission.CAMERA

The App requests camera permission only when you choose to use the camera-based heart rate estimation feature. Camera input is processed on your device solely to estimate pulse-related signals. No photos or videos are recorded, stored, transmitted, or shared with third parties.

Any estimate is provided for personal reference only, has no intended medical purpose, and should not be relied upon for diagnosis, treatment, or medical monitoring. Results may be affected by your device, environmental conditions, and how the feature is used. For medical assessment or advice, consult a qualified healthcare professional or medical institution.

Camera permission is optional. You may decline the request or revoke permission later through your device settings. Without camera permission, this feature will be unavailable; Other features that do not require camera access remain available.

Physical Activity Permission - android.permission.ACTIVITY_RECOGNITION

The App accesses step-count information from your device to support the pedometer and display daily activity records and trends. This information is used only for personal activity recordkeeping and is not used for advertising, profiling, or sharing with third parties.

Step counts and related trends are provided for general reference. Their accuracy and completeness may vary depending on your device, system settings, and usage conditions.

Any permission required to access step-count information is optional. You may decline the request or revoke permission through your device settings. Without the required permission, step counting and related activity records may be unavailable or limited. Other features that do not require this access remain available.

Notification Permission - android.permission.POST_NOTIFICATIONS

The App requests notification permission where required by Android to display health-record reminders, feature updates, and summaries. Firebase Cloud Messaging (FCM) supports notification delivery as described in Section 3.

Granting this permission is optional. You may decline the request or withdraw permission at any time through your device’s notification settings. You can also manage notification preferences through the available settings within the App. If notifications are disabled, you may no longer receive these reminders, updates, or summaries; features that do not depend on notifications remain available.

Foreground Service

The App uses Android’s FOREGROUND_SERVICE permission to support ongoing operations associated with the following features:

Historical health-record export — FOREGROUND_SERVICE_DATA_SYNC, with the dataSync foreground service type.
When you manually initiate an export of historical health data, a foreground service supports the processing needed to complete that export while Android manages the App’s execution. Its use is limited to the export operation and the time needed to complete it.

The Android term dataSync identifies the service type. Its use for export does not mean that your health records are synchronized with a remote server. The App does not provide cloud synchronization of those records.

Pedometer — FOREGROUND_SERVICE_HEALTH, with the health foreground service type.
A health foreground service supports ongoing step counting when the pedometer is active, including when the App’s interface is not in the foreground. It is used for activity tracking and does not provide medical monitoring.

Foreground services are subject to Android’s operating requirements and system controls, including the applicable ongoing status notification or service indication. Foreground service permissions do not, by themselves, authorize access to additional health information; any separate permission required for step-count access remains subject to the relevant Android controls.

Battery optimization exemption

For ongoing pedometer operation, the App requests Android’s battery optimization exemption through REQUEST_IGNORE_BATTERY_OPTIMIZATIONS.

The purpose is to reduce interruptions to active step counting caused by system power-saving restrictions. This access does not provide additional access to personal or health information and is not used to expand the purposes for which step data is processed.

The system presents the exemption request for your decision. You can decline it or change the setting later through your device’s battery optimization settings. Without the exemption, Android may restrict background execution and interrupt step tracking. Other device or system restrictions may still affect operation even when an exemption is granted.

5Disclosure, Storage, Retention, and Protection

When information reaches other organizations

Your user-entered profile details and health records remain on your device and are not shared by us with third-party services.

Technical and usage information may be processed by the providers identified in Section 3 for their disclosed operational, analytics, performance, advertising, attribution, fraud-prevention, configuration-delivery, notification, or news-content purposes.

We do not sell user data.

Storage and retention

Personal entries and health records are stored locally. The App does not provide cloud synchronization.

You can remove locally stored information through the available deletion controls or by clearing the App’s storage in Android settings. Uninstalling the App ordinarily removes its local health records, optional profile details, cached information, and settings.

Files you manually export outside the App’s own storage may remain in the location where you saved them until you delete those files.

Third-party providers maintain the information they process under their own storage and retention practices. Uninstalling the App does not necessarily delete information previously processed by those providers.

Security measures

We use reasonable safeguards intended to reduce the risk of unauthorized access to information handled by the App. Third-party providers are responsible for protecting information within their own services under their respective security practices.

No storage system or transmission method can guarantee complete security. The safeguards described here should not be understood as a promise that every security incident can be prevented.

International Data Transfers

For users in the EEA or UK, information processed through services such as Firebase or advertising partners may be transferred outside those regions.

Where required by applicable law, these transfers must be covered by appropriate safeguards, such as Standard Contractual Clauses.

6Access, Correction, Deletion, Export, and Permission Choices

Viewing and correcting records

You can access your stored health information through the App’s record displays.

If you need assistance understanding the available controls, contact muzaffar.publisher@gmail.com. Because your personal entries and health records are stored locally, contacting us does not give us remote access to those records.

Deleting local information

You can delete locally stored data using the App’s available deletion controls.

You can also uninstall the App:

The storage effects of uninstalling, including the separate treatment of exported files and third-party information, are explained in Section 5.

Exporting records

The App allows you to export stored data manually. Historical health-record exports may use the temporary foreground service described in Section 4.

Withdrawing device permissions and system access

You can review or revoke permissions, including camera access and any applicable step-count permission, through your device’s App permission settings. You can manage notifications through system notification settings or the available controls within the App.

The pedometer’s battery optimization exemption can be withdrawn through your device’s battery settings. Android also provides system controls for managing active services and App execution.

Withdrawing access may prevent the associated feature from operating or may interrupt an ongoing operation. Revoking a permission does not, by itself, erase information already stored; use the deletion options above to remove local records.

Where your Android version provides advertising identifier controls, you can manage those controls through the device’s privacy or advertising settings.

Information held by service providers

For information already processed by an analytics, advertising, or other third-party provider, consult that provider’s privacy policy for its applicable data-request procedures.

You may also contact us at muzaffar.publisher@gmail.com for assistance submitting a request. A provider’s retention and request procedures continue to apply independently of whether the App remains installed.

7Children

The App is not intended for children under 13. If you are under 13, do not use the App or provide any personal information through it.

8Changes to This Policy

We may revise this Privacy Policy periodically. An updated policy will be made available through the App or its store listing, and the revision date will identify the updated version.

9Contact Details

For privacy questions, concerns about information handling, or assistance with the controls described in this policy, contact:

Developer: RRL TRANSPORT
Email: muzaffar.publisher@gmail.com