CuffPal
Last updated 7 August 2026
CuffPal has no account, no sign-in, and no server of its own. Every reading you log — the numbers you took on your own cuff — is written to your device and, if you allow it, to your own Apple Health data. Nothing is uploaded anywhere. We do not have a database of your blood pressure, because we never built one.
CuffPal is a log, not a monitor — it never measures your blood pressure itself. You take a reading on a real cuff and type the numbers in. Those readings are stored on your device. If you grant permission, CuffPal also reads and writes systolic, diastolic, and pulse values to Apple Health, so your history lives in Health alongside anything else you track. That sync happens entirely between your device and Apple's Health store; it does not pass through us or any server we run.
CuffPal requires an active subscription to use, after a seven-day free trial. That is a billing fact, not a data-collection one — it does not change anything above: your readings are still written only to your device and, if you allow it, to your own Apple Health data, whether or not your subscription is currently active. See the support page for exactly what happens to your data while a subscription has lapsed.
CuffPal Pro is an auto-renewable subscription, sold and billed by Apple through the App Store. We never see your payment details — not your card number, not your name, not your billing address. Apple processes the transaction and tells the app only whether your subscription is currently active.
CuffPal uses RevenueCat, a subscription-management service, to check and record that status. RevenueCat receives an anonymous, app-generated identifier (not your Apple ID or your name) and your purchase and subscription information — which plan, whether a trial is active, whether it renewed. It does not receive your blood pressure readings, your Health data, or anything else you log; CuffPal's billing layer and its reading log are separate code paths, and only the billing layer talks to RevenueCat. See Apple's privacy policy for how Apple itself handles the transaction, and RevenueCat's privacy policy for how it handles subscription data.
CuffPal contains no analytics SDK, no attribution or advertising library, no crash reporter, and no advertising of any kind. It does not use the advertising identifier and never shows the App Tracking Transparency prompt, because it has nothing to ask permission to track. Nothing about how you use the app — how often you open it, what you log, when you log it — is collected or sent anywhere.
The blood pressure and pulse values you enter are read from and written to Apple Health only with your explicit permission, granted through iOS's own Health permission screen. You can revoke that permission at any time in Settings → Privacy & Security → Health, and CuffPal will keep working as a local log. We never receive a copy of your Health data — the sync is between your device and Apple's HealthKit framework directly.
CuffPal is not directed at children and is not intended for anyone under 13. We do not knowingly collect information from children — in fact, we do not knowingly collect information from anyone, since nothing you enter leaves your device.
Under the GDPR, the UK GDPR and the CCPA you have rights to access, correct, export and erase personal data held about you. In CuffPal's case those rights are satisfied directly: your readings live on your device and in your own Apple Health data, under your control, and deleting the app removes CuffPal's copy of them. We hold no personal data of our own to disclose, sell, or share, and we have never sold or shared personal information.
If this policy changes, the date at the top changes with it, and the previous version is superseded. A change that adds a new data collector will be reflected here before it ships.
Questions about this policy or your privacy: gokhan.tosun1995@gmail.com.