1. Document status and effective date
This policy is effective on 2026-07-31 and describes the current Stress Mate release offered in the Republic of Korea. It will be updated if the distributed build or its included SDKs change.
2. Operator
Stress Mate is operated by Oh Byung-gil (오병길). The operator is responsible for the app behavior described in this policy and for responding to privacy questions.
3. Scope
This policy applies to the Stress Mate iPhone app, its paired Apple Watch app, and the iPhone and Apple Watch widgets. Services provided by Apple or another business, including Apple Health, iCloud, the App Store, and apps selected in the system share sheet, are governed by their own policies.
Stress Mate is not a medical device or diagnostic service. Its body load and recovery information is intended for general wellness reference.
4. Data processed by the app
When the user grants Apple Health access, the app may read the following data on the device:
- heart rate, heart rate variability, resting heart rate, and walking heart rate average
- sleep, workouts, active energy, and step count
- respiratory rate, blood oxygen saturation, VO2 max, and body mass
- mindfulness minutes
Some health types are optional. When access is not granted, the app provides a more limited result without those signals.
The app may process information entered directly by the user, including mood, caffeine, alcohol, hydration, sunlight, breathing, meditation, symptoms, workouts, free-form notes, and breathing-session feedback.
The app may also generate or store on the device health ingestion state, raw and normalized signals, derived statistics, body load and recovery scores, trends and summaries, habit records, workout records and workout impact reports created from Apple Health workouts, notification settings, history and delivery diagnostics, sync reports, and current snapshots for Watch and widgets. The current app does not provide a Stress Mate account or sign-in.
On a shipping Release build running on a physical device, the iPhone app may collect coarse location, an app-installation device identifier, and product interaction such as app launches, sessions, and screen activity through Firebase Analytics. Firebase Crashlytics may collect crash stacks, relevant app state, device and operating-system information, installation identifiers, and other diagnostic data.
5. Purposes
Data is processed on the device to:
- calculate body load and recovery scores, trends, and health context
- establish personal baselines and assess signal completeness
- summarize workouts, breathing, mindfulness, and habit activity
- decide and suppress duplicate notifications according to user settings
- keep current state aligned across iPhone, paired Watch, and widgets
- produce a user-requested local summary export or delete local data
- diagnose app and delivery state on the device
- analyze non-Health app-use flows and improve product quality
- identify crash causes and improve app stability
Health data is not used for advertising or advertising personalization.
6. Storage and device-to-device transfer
App data is stored in the app container, App Group container, or UserDefaults on the user's devices. The iPhone app and widgets share limited snapshots through an App Group. The iPhone and paired Apple Watch may exchange current state, settings summaries, quick logs, breathing completions, feedback, and other functional payloads through Apple's WatchConnectivity framework.
The current release has no remote server or cloud-sync path operated by the Stress Mate operator. However, non-Health app-use information and crash diagnostics from the iPhone app may be sent to Google's Firebase services as described below.
7. Developer collection and third parties
AI features are optional. Personal insights and personal insight conversations are processed on-device. When the on-device model is unavailable, Gemini general questions are sent to Google only after the user separately starts that chat session and selects an app-authored preset. The request contains the fixed question, general instructions, and normalized Korean or English language, never personal Health or wellness data, saved insights, free text, prior conversations, or character identifiers.
General questions cover breathing, short breaks, bedtime routines, and general HRV explanations. Unpaid Gemini inputs and generated answers may be used to provide, improve, or develop Google products, services, and machine-learning technologies, and may be read or reviewed by humans. Firebase AI Logic and App Check process technical/request metadata and app attestation for routing, security, and abuse prevention. AI Monitoring is enabled; requests, responses, and request configuration may be recorded in Cloud Logging. Question and answer text is not included in Firebase Analytics events.
Shipping Release builds on physical devices include FirebaseCore, Firebase Analytics, and Firebase Crashlytics in the iPhone app. Firebase Analytics collects coarse location, an app-installation device identifier, and product interaction for non-Health app-use analytics. Firebase Crashlytics collects crash data, installation identifiers, and other diagnostics for app functionality and stability. This collection is mandatory and cannot be disabled in the app.
Health and wellness content is not sent to Firebase. The app does not set a Firebase user ID or send custom health events, Crashlytics custom keys, or wellness logs. Firebase is not linked in the iPhone widget, Apple Watch app, or Apple Watch widget.
Stress Mate has no advertising or user tracking. It does not combine collected data with third-party advertising data or provide it to a data broker. Google's Firebase privacy and security terms apply to Firebase processing.
Apple Health, WatchConnectivity, WidgetKit, notifications, and the share sheet are operating-system services. If the user selects another app or service in the share sheet, that provider may process the shared data under its own policy.
Gemini API terms · Firebase AI Logic data governance · Firebase privacy and security
8. Retention and deletion
Character conversations, optional personal insight context, and general-question replies may be saved locally on the device. Delete individual conversations from history or remove related local records using Delete local data in Settings. These records are not attached to subsequent Gemini requests. Deleting them in the app does not retract or delete requests or answers already processed by Google. Provider retention and deletion follow the applicable Google service terms and settings.
Stress Mate does not apply a single retention period to all app data. Data stored on the device is kept as follows.
- Detailed health records: the app cleans them up automatically when it reads, stores, and analyzes new Apple Health data. Health-ingestion records and copies of raw and normalized signals read from Apple Health are each deleted once they are more than 90 days older than the newest stored record of the same kind, regardless of health type. Detailed wellness signals used for analysis are deleted once their end time is more than 90 days before the analysis. Across all health types, the app keeps at most the 20,000 most recent raw signals, the 20,000 most recent normalized signals, and the 512 most recent ingestion records, so entries may be deleted before 90 days have passed. Signals created from habit records, including the automatic workout records described below, are excluded from this cleanup.
- Score history and hourly trend aggregates: the app cleans them up automatically when it analyzes and stores health data. Body load and recovery score history (including score history saved by earlier versions) is deleted once it is more than 113 days older than the newest stored score record. The newest record with a body load, which the app keeps showing when it cannot calculate a new score, stays regardless of age. Hourly trend aggregates are kept for this year and last year only: aggregates for hours before the first day of the previous year in the device calendar are deleted.
- Current-state items: derived statistics, sync reports, notification delivery diagnostics, current snapshots for Watch and widgets, and similar items are overwritten on each update. For personal insights, the app keeps only the latest result and the 32 most recent generation-attempt records; an insight attached to a saved character conversation is kept with that conversation. Turning off AI insights deletes the latest result and saved character conversations; the generation-attempt records used to check usage limits, which contain no content, remain.
- Other records: daily summaries, weekly, monthly, and yearly trend aggregates, habit records, breathing feedback, workout impact reports, notification history, and saved character conversations have no automatic deletion period. Habit records include entries the user makes directly and workout records the app creates automatically for each Apple Health workout it processes (activity type, start and end times, duration, active energy, average and peak heart rate, record source, and similar details). After the detailed health records are cleaned up, score history and hourly aggregates already created remain for the periods above, and summaries and period aggregates remain without a period.
Because the cleanup runs only when the app refreshes health data, records past their period may remain until the next refresh if the app has not refreshed for a while. Raw and normalized signal copies are measured against the newest stored record, so if no new Apple Health data arrives (for example, after all read access is turned off), they may remain regardless of age even when the app refreshes. Score history is also measured against the newest stored score record, so while the app keeps showing an earlier score because it cannot calculate a new one, records saved by earlier versions may remain. When data is deleted in Apple Health, the next time the app analyzes health data it deletes its copies of that data from the last 30 days. It deletes a workout impact report created from a deleted workout when the workout was in the last 30 days, no other record of the same workout remains, and the workout is still missing when the app checks again at least 72 hours later. When the app reads no data of a health type (for example, after read access for that type is turned off) or reads only part of it because of read limits (for example, frequently recorded heart rate, steps, or active energy), it does not delete that type's copies. The hourly trend aggregates of the last 30 days that held deleted data, and the weekly, monthly, and yearly aggregates of those hours, are calculated again from the remaining data. Older copies, score history and daily summaries already created, habit records (including automatic workout records), and other such records are not deleted with it.
Data without automatic deletion and copies that remain as described above may stay on the device until the user deletes them in the app or the app and its related containers are removed or replaced.
‘Delete local data’ clears or removes stored wellness summaries, HealthKit-derived records, health-sync state, notification history and diagnostics, habit logs, breathing feedback, and related local records. Notification settings and general preferences such as the theme may remain. The iPhone and its widgets clear current local wellness state immediately. The paired Watch and Watch widgets clear current wellness state and snapshots when they receive the deletion during the next sync.
Deleting local Stress Mate data does not delete data stored in Apple Health. Copies already shared with another app or service must be managed with that recipient. If HealthKit read permission remains available, a later refresh may create new local records from the signals the user still allows.
Deleting local data does not delete analytics or crash diagnostics already sent to Firebase. Firebase data retention and deletion follow the service's policies and operating settings. Related requests may be sent to the privacy contact below.
9. Export and sharing
At the user's request, the app creates a JSON summary containing its generation time and record counts for local data families. The current export does not contain raw HealthKit samples or the contents of habit entries.
The summary is handed to the iOS share sheet only when the user chooses to share it. The user selects the destination, and the destination's privacy policy applies to subsequent processing.
10. Permissions and choices
Enabling AI insights and starting Gemini general questions are separate choices. Enabling insights alone does not send a general question. Start general questions separately on each chat screen; closing the screen ends that session choice. General questions do not require personal health information.
Users can grant or withdraw access to individual health data types, notifications, and other system permissions in Apple Health and iOS Settings. Declining access may limit some scoring, trend, sync, or notification features.
The current release does not write mindfulness minutes to Apple Health. Its HealthKit authorization request is read-only and the app processes only the signals the user allows. Apple does not disclose individual read-access decisions to the app, so a completed permission request does not mean every listed health type was granted.
Users can request a local summary export or delete local data from app Settings. There is no server account for the user to delete. Firebase Analytics and Crashlytics collection is mandatory on shipping Release builds running on physical devices, and the app does not provide an opt-out control.
11. Children
Stress Mate is not designed specifically for children. The current app does not transmit user data to an operator server or create accounts. Parents and guardians should manage device access, Apple Health permissions, and family use of the app. Any age-consent requirement applicable in the Republic of Korea will be addressed.
12. Security
The app processes local data within Apple's app sandbox, App Group, HealthKit permissions, and device security controls. Users should protect their device with a passcode, install operating-system updates, and verify destinations before sharing. No storage method can guarantee absolute security.
13. Changes to this policy
If data types, purposes, servers, third-party SDKs, retention, deletion, or availability regions change, this policy and the App Store privacy answers will be reviewed together. Material changes will be communicated in the app or on the policy page, and the last-updated date above will be revised.
14. Contact
- Operator: Oh Byung-gil (오병길)
- Privacy contact: snowvil84@gmail.com
- Published policy URL: the canonical HTTPS address of this page
- Legal review: Oh Byung-gil (오병길) · 2026-07-31
The canonical published policy is the current HTTPS address of this page.