Health Data Statement
Step count and Health Connect data processing based on separate consent.
Health Data Statement
Step count and Health Connect data processing (iOS / HealthKit currently inactive)
⚠️ GOVERNING LANGUAGE NOTICE This document is an English translation of the Hungarian Health Data Statement (HE-001). In case of any discrepancy between the Hungarian and English versions, the Hungarian version shall prevail. Hungarian version: https://cashleticsapp.com/legal.php?slug=egeszsegugyi-adat&lang=hu |
| Data Controller | Mózer Ferenc (sole trader / egyéni vállalkozó) 6044 Kecskemét, Hetény-Belsőnyír 268/2., Hungary |
| Effective date | 5 July 2026 |
| Version | v1.5 | 2026 |
| GDPR reference | Art. 9(2)(a) — explicit consent for special category data |
| Related documents | AT-001-EN, ROPA-001, DPIA-001, HJ-001-EN, HE-001 (HU) |
| Governing language | Hungarian (HE-001) — this EN version is a translation |
1. Why Is Step Count Special Category Data?
⚠️ SPECIAL CATEGORY DATA — GDPR ARTICLE 9 Step count qualifies as health data under GDPR Article 9 and European Data Protection Board guidance, as it can indirectly reveal information about a person's physical condition and health status. Processing is only lawful with explicit consent — implied or general consent is NOT sufficient. |
The Cashletics application can access step count data from the following sources — exclusively based on the user's decision:
Android: Health Connect API (primary source) or device sensor (fallback)
iOS: HealthKit API — currently inactive; to be updated before the iOS launch
2. What Data We Collect and Why
| Data | Exactly what | Purpose | What we do NOT collect |
|---|---|---|---|
| Step count | Daily aggregate step count (integer) | Activity tracking, gamified reward calculation | Raw GPS data, route, location |
Data minimisation: the application stores only aggregated daily data — per-minute, per-hour, or raw sensor data is NOT retained.
3. Legal Basis for Processing
| Legal basis | GDPR Art. 9(2)(a) |
| Explanation | Explicit consent of the data subject to processing their special category data |
| Requirements | Explicit (not implied), informed, freely given, unambiguous |
| When obtained | When the step count feature is enabled — consent flow step 2 (HJ-001-EN) |
| Form | Separate checkbox confirmation in the app, optional (not mandatory) |
| Revocable? | Yes — at any time, without retroactive effect (GDPR Art. 7(3)) |
4. In-App Consent Text (to be implemented)
The following text is displayed to the user when they first request step count access. Exact wording and UI layout: HJ-001-EN.
CONSENT STATEMENT — In-app text (to be implemented) You are granting Cashletics permission to access your daily step count data via Health Connect (Android). What we use: • Daily aggregate step count • Purpose: activity tracking and gamified reward calculation What we do NOT use: • GPS location, routes, or raw sensor data • Your data is NOT shared with advertisers This consent is optional — the application is fully usable without step count data. You can withdraw at any time: App > Settings > Health Data. Full statement: Health Data Statement (HE-001-EN) |
5. Data Flow and Storage
| Step | Description | Where it happens |
|---|---|---|
| 1. Source | Health Connect API or device sensor | On the user's device |
| 2. Aggregation | Daily total calculated (raw data discarded) | On the user's device |
| 3. Storage | Aggregated daily data uploaded | Cloud Firestore (Google LLC, EU-US DPF) |
| 4. Use | Activity display, reward calculation, statistics | Within the application |
| 5. Deletion | Upon consent withdrawal or account deletion | Permanently from Firestore |
Retention period: until consent withdrawal, but no longer than 90 days from the last synchronisation. Upon account deletion, all health data is immediately and permanently erased.
6. Prohibited Uses
Under the Google Play Health Permissions Policy and GDPR Article 9, health data (step count) may only be used for permitted purposes. The following are expressly prohibited:
Advertising purposes — data is NOT shared with AdMob or any other advertiser
Transfer to third parties without notification
Use for credit, insurance, or employment decisions
Publication on the public leaderboard
Storage of raw sensor data
7. Android — Health Connect Details
| Parameter | Value |
|---|---|
| API | Android Health Connect (androidx.health.connect) |
| Permission request method | Health Connect system dialog — user grants via Android system UI |
| Withdrawal method (1) | Cashletics > Settings > Health Data > Disable |
| Withdrawal method (2) | Android Settings > Health Connect > Cashletics > Remove permissions |
| Play Console declaration | Health Connect API usage declaration required — GPS-001 |
| Play Data Safety type | "Health info" and "Fitness info" — optional, user-shared |
| Permissions requested | READ_STEPS; READ_HEALTH_DATA_HISTORY; ACTIVITY_RECOGNITION. READ_HEALTH_DATA_HISTORY is used for weekly/monthly/yearly aggregated step totals; ACTIVITY_RECOGNITION supports Android activity/step-count permission handling. The app still does not process GPS, routes, heart rate, workout type or other health data. |
8. iOS — HealthKit Details (currently inactive)
iOS / HealthKit currently inactive; to be updated before iOS launch HealthKit integration details to be added before App Store submission. Structure is identical to the Android section; only API-specific details differ. |
| Parameter | Android equivalent | iOS value |
|---|---|---|
| API | Health Connect | iOS / HealthKit currently inactive |
| Permissions requested | READ_STEPS; READ_HEALTH_DATA_HISTORY; ACTIVITY_RECOGNITION. READ_HEALTH_DATA_HISTORY is used for weekly/monthly/yearly aggregated step totals; ACTIVITY_RECOGNITION supports Android activity/step-count permission handling. The app still does not process GPS, routes, heart rate, workout type or other health data. | iOS / HealthKit currently inactive |
| Info.plist key | — | iOS / HealthKit currently inactive |
| Withdrawal method | Android settings | iOS / HealthKit currently inactive |
| App Store declaration | Play Console Health declaration | iOS / HealthKit currently inactive |
9. Your Rights Regarding Health Data
| Right | How to exercise |
|---|---|
| Withdrawal (GDPR Art. 7(3)) | App > Settings > Health Data > Disable — takes effect immediately |
| Erasure (GDPR Art. 17) | privacy@cashleticsapp.com — executed within 30 days |
| Access (GDPR Art. 15) | privacy@cashleticsapp.com — response within 30 days |
| Restriction (GDPR Art. 18) | privacy@cashleticsapp.com |
| Portability (GDPR Art. 20) | privacy@cashleticsapp.com — JSON format |
| Complaint (GDPR Art. 77) | NAIH: www.naih.hu | ugyfelszolgalat@naih.hu |
Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal. After withdrawal, the step count feature stops, and already stored aggregated data is deleted within 30 days.
10. Cross-Reference — Synchronised Documents
Health data processing appears in the following documents — all must be consistent with each other:
| Document | Relevant section / row | Synchronised element |
|---|---|---|
| AT-001-EN | Section 6 | Health data standalone section, retention, legal basis |
| AT-001 (HU) | Section 6 | Same content in Hungarian |
| ROPA-001 | Health data row | GDPR Art. 9 flag, 90-day retention |
| DPIA-001 | Risk assessment | Special category data risk analysis |
| HJ-001-EN | Consent flow step 2 | In-app text and UI flow |
| GPS-001 | Health info declaration | Play Console Data Safety form |
| HE-001 (HU) | Full document | Hungarian source version |
⚠️ GOVERNING LANGUAGE NOTICE This document is an English translation of the Hungarian Health Data Statement (HE-001). In case of any discrepancy between the Hungarian and English versions, the Hungarian version shall prevail. Hungarian version: https://cashleticsapp.com/legal.php?slug=egeszsegugyi-adat&lang=hu |
Publication addendum
v1.5a supplement — Android Health permissions:
The current Android permission set remains unchanged in the source code: READ_STEPS, READ_HEALTH_DATA_HISTORY and ACTIVITY_RECOGNITION. These are used only for reading step count, historical aggregated step totals, and Android activity-recognition support. Cashletics does not request or process location data, GPS routes, heart rate, workout type, or other health data.
Next review: 5 July 2027.