CardioSnap — Privacy Policy

Last updated: April 9, 2026

Introduction

Welcome to CardioSnap, developed by Evgenii Pestrev ("we", "us"). This Privacy Policy explains what information we process when you use our iOS application and related services ("Service"), why we process it, and how you can exercise your rights.

By using the Service, you agree to this Privacy Policy. If you do not agree, please do not use the Service.

What We Process

We designed CardioSnap with privacy in mind. Your health data is stored locally on your device. We do not permanently store your blood pressure readings, pulse data, or photos on our servers, and we do not build user profiles.

1) Health & Measurement Data

• Blood pressure readings (systolic, diastolic) and pulse values are stored locally on your device using SwiftData. We do not have access to this data unless you use the AI insight feature.
• When you request an AI-generated health insight, the relevant reading data is transmitted from your device through our secure proxy server to an AI provider for analysis. We do not retain your health data after processing is completed (beyond transient, short-lived caching strictly required to operate the Service).
• Our proxy server acts solely as a relay — it forwards your request to the AI provider and returns the result to your device.

2) OCR Scans (Tonometer Photos)

• When you use the OCR feature to scan your tonometer screen, the image is processed entirely on your deviceusing Apple's Vision framework. The photo is not transmitted to our servers or any third party.

3) Apple Health (HealthKit) Data

• If you grant permission, CardioSnap can read and write blood pressure and heart rate data from/to Apple Health. This data remains on your device and within Apple's ecosystem. We do not transmit HealthKit data to our servers or third parties, except when you explicitly request an AI insight for a specific reading.

4) Family Monitoring Data (CloudKit)

• If you use the Family Monitoring feature, blood pressure data is shared between the observed person and the observer via Apple iCloud (CloudKit Shared Zones). This data is transmitted and stored entirely within Apple's iCloud infrastructure. We do not operate any third-party servers for this feature and do not have access to the shared data.

5) Purchase & Subscription Data

• For subscriptions and purchases, we rely on Apple (App Store) and RevenueCat.
• Data involved may include purchase receipts, subscription status, product identifiers, country/currency, and anonymous app user identifiers needed to validate entitlements.