Last updated: August 21, 2026
Strap Zone ("the App") is designed to prioritize your privacy. The App connects directly to your Bluetooth Heart Rate hardware and processes data locally on your device.
We do not collect, store, or transmit your personal health data to Strap Zone servers. Heart-rate and workout data are processed and stored locally unless you choose an export described below.
The phrase "your health data stays on your device" refers to exact heart-rate samples, BPM values, workout history, and GPS routes. It does not mean that the App has no analytics, purchase processing, or optional support communication. The table below separates those flows.
| Data | Collected or created | Leaves the device | Processor and purpose | Control and retention |
|---|---|---|---|---|
| Exact heart rate, BPM, zones, and workout history | Yes, from the connected sensor and your workout settings | No, unless you explicitly export a file or write a workout to Apple Health or Health Connect | Processed locally by Strap Zone for live display, alerts, and workout history | Stored on the device. Individual workout records can be deleted in the App. Removing the App or its local data removes the local copy. |
| Precise GPS route, distance, and pace | Only when GPS Recording is enabled for an active workout | No to Strap Zone servers. Route points leave the App only through an export you choose | Processed locally for route, distance, pace, files, and optional system health export | GPS can be disabled. Local workout deletion removes the local route. Exported copies follow the destination's rules. |
| Bluetooth sensor name and identifier | Used while scanning, connecting, and remembering the selected sensor | Not included in product analytics | Processed locally to connect the App to your heart-rate sensor | Bluetooth permission can be revoked in system settings. Local App data can be removed from the device. |
| Product analytics and diagnostics | Release builds may record app-flow events, platform, store, coarse buckets, feature flags, sanitized error codes, and an installation identifier. Firebase may derive coarse technical location from network context. | Yes | Firebase Analytics, to measure onboarding, connection, purchase, workout, review-prompt, and export flows | No account or email is attached by Strap Zone. Retention follows the Firebase project configuration. Contact us about an access or deletion request. |
| Optional website analytics | Only after you allow analytics: page views and clicks from strapzone.app to App Store or Google Play. Google Analytics also processes limited browser, device, referrer, session, and approximate region information. | Yes, only after consent | Google Analytics, to understand which public pages help visitors reach the correct store listing. Strap Zone sends the page path without its query string, the referring origin, content locale, content variant, and selected store. | Your choice is stored locally in the browser. Google Analytics cookies are created only after you allow analytics. You can change the choice below at any time. |
| Purchase and entitlement information | When prices, purchases, subscriptions, or restores are requested | Yes | Apple App Store or Google Play processes payment. RevenueCat processes product, receipt, transaction, anonymous app-user, and entitlement data. | Purchase records follow store and RevenueCat retention requirements. Contact the store for payment records and us for a RevenueCat-related privacy request. |
| Optional feedback and reply email | Only when you submit feedback. A reply email is optional in the Settings form. Current in-app submissions include locale and platform, and the server adds the request user agent. The payload supports an appVersion field, but the two current in-app call sites do not send it. | Yes | Strap Zone's feedback endpoint and Resend process the message so support can read and reply | Do not include health data in feedback. Contact us to request deletion of a support message where legally and operationally possible. |
The website does not load Google Analytics until you actively allow it. Continuing without analytics does not restrict the website, support pages, downloads, or links to App Store and Google Play. Website analytics do not include heart-rate samples, workouts, GPS routes, Bluetooth sensor details, feedback text, email addresses, purchase records, or an account identifier.
The consent choice is stored in your browser's local storage. If analytics are allowed, Google Analytics may
set first-party _ga cookies. Disabling analytics stops new Strap Zone website events and removes
those first-party analytics cookies where the browser permits it.
Current choice: No choice saved
When GPS Recording is enabled in Settings, the App records your location during active workouts to include route data in workout exports. GPS data is stored locally and is not transmitted to Strap Zone servers. If you explicitly enable route export to Apple Health or Health Connect, qualifying workout route points are written to that system health store. You can disable GPS recording or health route export at any time in Settings. Location is only collected while a workout is actively running.
The App requires Bluetooth permissions to scan for and connect to your heart rate monitor. This connection is direct between your phone and your strap.
Health export is optional and off by default. If you enable it, the App may write a completed workout and the data types you select—heart rate, distance, estimated active calories, and route—to Apple Health on iOS or Health Connect on Android. Strap Zone does not import health records created by other apps and does not request health history or background-read access on Android.
You control each system permission and may revoke it in device settings. Permission denial never prevents a workout from being saved locally. Turning export off stops future automatic exports and does not remove records already written. When the App offers deletion from the system health store, it targets only records created by Strap Zone. Uninstalling Strap Zone may not remove records already exported.
Apple Health and Health Connect store and process exported data under your device, account, backup, and sync settings and under Apple or Google's applicable privacy terms. Health data is never used by Strap Zone for advertising or shared with data brokers.
The App uses Firebase Analytics in release builds to understand onboarding, purchase, workout, review prompt, and export flows. Analytics may include a random analytics installation/session identifier and limited technical context such as platform, store, app flow step, and sanitized error codes. Analytics events do not include heart-rate samples, exact BPM values, GPS coordinates, routes, Bluetooth device names or identifiers, account details, email addresses, or raw error messages.
Analytics are used only to improve the product and diagnose where users get stuck. Your heart-rate and GPS route data stay on your device unless you choose to export them to a file or supported system health store.
Strap Zone does not add exact GPS coordinates or routes to analytics events. Firebase may derive a coarse region from network or device context; that is separate from the precise workout route recorded locally.
On strapzone.app, Google Analytics is optional and remains off until consent. It measures public page views and store-link clicks using the limited website fields listed in the table above. This website flow is separate from Firebase Analytics inside release builds of the App.
RevenueCat supports App Store and Google Play product, purchase, restore, and entitlement handling. Strap Zone does not provide RevenueCat with your name or email as an account identity. Apple, Google, Firebase, RevenueCat, and Resend process their respective data under their own privacy terms.
Strap Zone does not require an account. You can delete individual local workouts in the App and remove local App data through the operating system. Deleting a local workout does not automatically delete a copy that you previously exported to a file, Apple Health, Health Connect, or another service.
For analytics, entitlement, or support-message questions and deletion requests, email wojciech.zieba@gmail.com. Include only the minimum information needed to locate the data, such as an applicable transaction reference. Because analytics identifiers are not attached to a Strap Zone account, some records may not be identifiable from an email address alone. Store transaction records may need to be handled by Apple or Google and may be retained for legal or financial obligations.
App Store Privacy and Google Play Data Safety use standardized categories that may group installation identifiers, coarse technical location, purchases, product interaction, fitness, and diagnostics more broadly than this policy's data-flow descriptions. Those store disclosures should be read together with this policy. If a store disclosure and the App's actual behavior appear inconsistent, contact us so the declaration can be reviewed.
If you have any questions about this Privacy Policy, please contact us at wojciech.zieba@gmail.com.