Last updated: September 1, 2026
Mindware Stress Coach is designed to work without an account or service operated by the app owner.
Data the app handles
The app can store stress, energy, and sleep ratings; selected stress signals and supports; optional journal notes; practice completions; favorites; program start date; and reminder settings. These records are stored in the application’s local sandbox on the device.
The app does not include an account, app-operated wellbeing-data backend, cloud synchronization, or a separate app-analytics or crash-reporting service. It does not sell data or automatically send wellbeing entries to the project owner or another person. RevenueCat provides the limited network service used to validate purchases and synchronize the ad-free entitlement.
Advertising and purchases
The free mobile version may show Google AdMob banner ads on the Today and Practice library screens. Ads are never shown during an exercise, guided-audio session, check-in, journal entry, onboarding, or safety screen. The app requests contextual, non-personalized ads and does not send stress ratings, sleep or energy ratings, journal text, practice history, favorites, reminders, or other locally entered wellbeing data to Google.
The Google Mobile Ads SDK may automatically collect and share the device’s IP address (which can indicate approximate location), app and ad interactions, diagnostic information, and device or account identifiers for advertising, ad measurement, analytics, security, and fraud-prevention purposes. Data sent by the SDK is encrypted in transit. The Android build prevents access to the Android advertising ID and Privacy Sandbox ad-ID, attribution, and topics permissions, but Google documents that other identifiers, such as an app-set ID, may still be used. Depending on location, Google’s User Messaging Platform asks for required privacy choices before the ads SDK starts; users can later reopen Ad privacy choices in More when that option is required.
Users can make a one-time app-store purchase to remove ads permanently. If the app is accepted into Google Play Pass, members receive the same remove-ads entitlement through Play Pass. The app store processes payment and purchase-account information; the app never receives payment-card details.
RevenueCat processes purchase history, product and entitlement status, store transaction information, app and device metadata needed for its SDK, and a randomly generated anonymous App User ID. It uses that information to validate and restore the purchase from the applicable app-store account, keep entitlement status current, prevent fraud, and provide aggregate purchase analytics. Because the app has no account or login, it does not promise that a purchase made through one app store will transfer to a different platform’s store account. The app does not send names, email addresses, advertising IDs, journal text, stress or sleep ratings, practice activity, or other locally entered wellbeing data to RevenueCat. RevenueCat data is encrypted in transit. A small local entitlement flag is also cached so the app can respect an existing purchase when the network is temporarily unavailable. The app refreshes RevenueCat when it starts or returns to the foreground so refunds, revocations, restorations, and Play Pass changes can take effect.
Device services
- If the user enables a reminder, the operating system receives the time and text needed to schedule a local notification.
- If the user chooses Export my data, the mobile app creates a temporary readable JSON file in its cache and passes that file to the operating-system share sheet. The user chooses whether and where to send it, and the app requests deletion of its temporary cache copy after the share sheet closes. The web version instead downloads the JSON file through the browser.
- If the user opens a research, safety, phone, text, or crisis link, the operating system or browser handles that request. Those services have their own privacy practices.
- The operating system may include app data in a device backup depending on the user’s platform and backup settings. Local storage is protected by the device and is not separately end-to-end encrypted by this app.
The app does not request microphone, camera, contacts, precise location, or health-record access. The Android build prevents access to the Android advertising ID. Bundled audio plays offline. Links are handed to another installed app, such as the browser, phone, text, or email app, which uses its own permissions and privacy practices.
Control and deletion
Users can delete individual check-ins, export a copy of their data, or choose Erase all local data in the More tab. Uninstalling the app ordinarily removes its local sandbox, subject to the platform’s backup and restore behavior.
Ad privacy choices can be reviewed from More when required in the user’s region. Android users can also reset or delete advertising identifiers in system settings. Purchase history is controlled by the applicable app-store account and is not erased by deleting local wellbeing data. A user may contact [email protected] to request deletion of the anonymous RevenueCat customer record associated with the app, subject to records that the app store, RevenueCat, or the developer must retain for legal, security, fraud-prevention, or transaction-integrity purposes.
Children and clinical information
The app is a general wellness tool and is not intentionally designed to collect information from children through an online service. It is not a medical record system and should not be used as the sole location for information needed in an emergency or for clinical care.
Contact and changes
Privacy and support questions can be sent to [email protected]. Additional developer information is available at mindware.mobi.
This policy will be updated if accounts, synchronization, a developer-operated backend, or additional analytics, advertising, or network services are added.