Privacy Policy

Last updated: October 20, 2026

App: Honest Stress Tracker
Developer / data controller: Mikhail Kostin, Poland

Honest Stress Tracker helps you record stress and notice patterns. It is a personal reflection tool, not a diagnostic or emergency service.

1. Your journal

Your stress scores, context, emotions, notes, and custom metric information are stored in the app’s local storage on your device. Honest Stress Tracker does not upload this journal content to Firebase. No account and no cloud journal sync are provided in this version.

Local storage does not by itself exclude data from operating-system backups; backup and restore depend on your device and release configuration. Honest Stress Tracker does not add its own encryption layer to journal storage.

You can edit check-ins, export or import a CSV, and delete all check-ins in Settings. Exporting a CSV shares the file with the destination you choose; that destination’s privacy practices apply. Deleting check-ins in Honest Stress Tracker does not delete copies you exported or existing device backups.

2. Accounts, payments, and subscriptions

This version of Honest Stress Tracker does not create accounts, does not offer in-app purchases or subscriptions, and does not use RevenueCat or other purchase SDKs.

3. Usage analytics

On configured iOS builds, Google Analytics for Firebase may run when Share usage analytics is on. The choice defaults to on. You set it during onboarding and can change it anytime in Settings. Collection stays blocked until your saved preference loads, then follows that preference. Android and web builds do not send usage analytics in this version.

When enabled, Google Analytics for Firebase processes installation and session identifiers, event timestamps, device and app information, and SDK-derived technical metadata. The app sends fixed events about onboarding, check-in activity, selected main screens, and reminder enable or disable actions. Firebase may also collect automatic lifecycle and session events. This is usage measurement, not anonymous measurement.

The app never sends journal answers, scores, emotions, context labels, notes, metric names or definitions, journal dates or IDs, entry counts, reminder times, insight results, CSV contents, or raw errors to analytics. Visits to the Get Help screen are not explicitly logged as screen events.

Advertising consent and advertising personalization are disabled. The iOS build excludes advertising-ID support and disables vendor-ID collection. Honest Stress Tracker does not set an analytics user ID, link Google Ads accounts, or enable Google Signals. No App Tracking Transparency permission is requested. Honest Stress Tracker does not show ads and does not use IDFA for advertising.

Turning Share usage analytics off disables further collection and resets local Analytics data on the device. That does not erase data already processed by Google. Deleting local journal entries also does not erase previously uploaded usage analytics. Analytics event data is configured for two-month retention; aggregate reports can have different retention behavior.

Google’s Firebase privacy information: https://firebase.google.com/support/privacy

4. Crash reports

On configured iOS builds, Firebase Crashlytics may run when Share crash reports is on. The choice defaults to on. You set it during onboarding and can change it anytime in Settings. Collection stays blocked until your saved preference loads, then follows that preference. Android and web builds do not send crash reports in this version.

When enabled, Firebase Crashlytics processes native crash stack traces, installation identifiers, crash timestamps, and technical device and app information. Honest Stress Tracker does not attach journal answers, notes, metric configuration, user identifiers, custom logs, or raw JavaScript exceptions. Automatic JavaScript and unhandled-promise reporting are disabled. Native diagnostic reports are technical data, not anonymous or guaranteed personal-data-free.

Turning Share crash reports off disables further collection and deletes unsent reports still on the device. Previously uploaded crash reports are not automatically deleted by that switch or by journal deletion. Crashlytics has its own retention behavior; the Analytics two-month setting does not control crash-report retention.

Firebase may attach automatic Analytics breadcrumbs containing the fixed usage events to native crash reports when both services are enabled.

5. Optional audience survey

After onboarding, configured iOS builds may invite you to answer two optional, fixed-choice questions about what brought you to the app and what you would like help with when usage analytics is on. Answers are sent only when you tap Send answers. Skipping sends no answers. The survey has no free-text field and is separate from your journal.

We also collect survey invitation and start events, without answers, to understand participation. Survey events include a survey version. The selected option identifiers are sent to Google Analytics for Firebase in an audience_survey_submitted event to help the developer decide what to build next. Firebase technical and installation/session metadata and the analytics retention rules above also apply to this event. Survey events may appear in automatic Analytics crash breadcrumbs. Only the invitation’s dismissed or submitted status is saved in local app settings; deleting journal entries does not delete submitted survey responses.

6. External links and support

Privacy, support, and crisis-resource links open external websites. Those organizations have their own privacy practices. Honest Stress Tracker does not monitor your safety or contact emergency services for you.

7. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of personal information. In the app you can:

To ask about analytics or crash data associated with the app, email us using the address below.

8. Contact

For privacy and support questions, contact:
support@kostin.app
Mikhail Kostin, Poland

9. Changes to this policy

We may update this policy when the app or legal requirements change. We will publish the updated version on this page and revise the “Last updated” date.