Version 1.3.1 · Last updated 2026-10-15

Ears Up - Privacy Policy Supplement

Effective Date: October 15, 2026 Last Updated: October 15, 2026

This Privacy Policy Supplement is specific to Ears Up and supplements WagDev LLC's general Privacy Policy and Data Security Standards.

1. Summary

Ears Up is a single-user daytime-sleepiness self-check-in app. Your check-in content is stored only on your device. Everything you record — your check-ins, sleepiness ratings, notes, and any reminder schedule you set — is stored locally on your device in an encrypted database and never leaves it. There is no account, no login, and no cloud. We do not operate a server, we do not run analytics on your check-in content, and we do not have a copy of your check-in data anywhere.

Two narrow outbound data flows leave your device, disclosed in detail below. Neither one receives your check-in content:

2. Data Collection

2.1 What You Provide

All of the following is stored exclusively on your device in an encrypted local SQLite database (SQLCipher):

We never see, transmit, or store any of this check-in content on our infrastructure, and it is never shared with AdMob or any advertiser.

2.2 What Ears Up Does Not Collect

2.3 Advertising: What AdMob Collects on Google's Behalf

Ears Up is supported by advertising. You see a single banner strip anchored above the tab bar. It never covers your check-in content and never appears over a dialog or modal.

When Ears Up requests an ad, the embedded Google Mobile Ads SDK collects the following on Google's behalf, for ad serving, measurement and fraud prevention (not your check-in content):

Consent in the EEA, the UK and Switzerland. If you are in the European Economic Area, the United Kingdom or Switzerland, Ears Up presents Google's User Messaging Platform consent form before it requests a single ad, and nothing is requested from AdMob until you have answered it. The form is shown even when the ads that follow will be non-personalized: serving any ad at all still involves storing or reading information on your device, so choosing non-personalized narrows what is used rather than skipping the question. If you refuse consent, Ears Up does not request an ad at all and simply shows no banner. If you are outside these regions, you are never shown a consent form.

Changing or withdrawing your consent. Your first answer is not binding on you. Open Settings and tap Privacy options to bring the same consent form back up at any time, change any choice, or withdraw your consent altogether. A withdrawal takes effect on the next ad request. The Privacy options row is there only if you were shown a consent form to begin with, so it does not appear for users outside the EEA, the UK and Switzerland.

Ad personalization. On Android, ads may be personalized, subject to your consent answer and to your system Ad ID settings. Ears Up never asks for tracking permission on iOS. There is no App Tracking Transparency prompt, so the advertising identifier stays unavailable to the ad SDK and your ads on iOS are non-personalized. Nothing you do can change that, and there is nothing for you to decline.

Removing ads. Ears Up offers a one-time in-app purchase that removes advertising permanently. On iOS it also unlocks the Ears Up home screen and Lock Screen widgets. There is no Ears Up widget on Android, so on Android the purchase buys ad removal and nothing else. Ears Up has no account, so the purchase is tied to your App Store or Google Play account rather than to anything we hold: if you reinstall, or move to a new device, use Restore purchase in Settings to bring it back. Once ads are removed, Ears Up stops requesting ads and the AdMob SDK collects nothing further.

The full disclosure of AdMob data practices appears in Section 4.3 ("Advertising in Some Apps") of the WagDev Privacy Policy, which is incorporated here by reference. Your AdMob data is governed by Google's privacy policy.

2.4 What Sentry Collects for Crash and Error Reporting

To diagnose and fix bugs, Ears Up integrates Sentry — a crash and error reporting service operated by Functional Software, Inc. (d/b/a Sentry). When the app encounters a runtime error or crash, the Sentry SDK transmits:

What Sentry does not receive from Ears Up:

App stability sessions. Separately from error reports, the Sentry SDK records an anonymous session each time you open and close Ears Up, so we can measure how stable each release is and whether the app is being used at all. A session contains only: the app version, the device model and operating system version, when the session started and how long it lasted, and whether it ended normally or in a crash. Sessions carry no advertising identifier, no IP address, no location, and none of your check-in content, and are never linked to your identity (Ears Up has none to link them to) or used to track you across apps or websites.

Sentry crash and performance reporting is gated off entirely in development and end-to-end test builds, so it only operates in released production builds. Sentry data is retained per Sentry's data retention policy and governed by Sentry's privacy policy. The full disclosure of how WagDev uses Sentry across apps appears in Section 4.2 ("Service Providers") of the WagDev Privacy Policy.

3. How Ears Up Uses Your Data

3.1 Local Use Only

Your check-in data is used solely to power the app's features on your device:

No remote processing, no machine learning on your content, no human review.

3.2 No Cross-Device Sync

Because Ears Up does not have a server or an account, your check-in data does not sync between devices. If you install Ears Up on a second device, you will start fresh on that device. If you delete and reinstall Ears Up on the same device, your local data will be erased (see Section 5 below).

4. Data Sharing

4.1 We Do Not Share Your Check-In Data

4.2 AdMob Receives Only Ad-Serving Data

AdMob receives only the data categories listed in Section 2.3 above. It does not receive your check-in ratings, notes, schedule, or any content you create in the app.

4.3 Sentry Receives Only Diagnostic Data

Sentry receives only the data categories listed in Section 2.4 above. Our SDK configuration disables PII collection, performance traces, and session replay. Anonymous app-stability sessions are enabled and are described in Section 2.4: they carry no identifiers, no IP address, and no check-in content. Sentry receives no check-in data of any kind.

5. Your Privacy Controls

5.1 On-Device Controls

Because all of your check-in data is local to your device, you have direct control:

5.2 Advertising Controls

The app remains fully functional whatever you answer on the consent form.

5.3 Data Export

Ears Up does not currently offer a built-in data export. Because your check-in data lives only on your device, you cannot lose it to a server outage — but you also cannot retrieve it if your device is lost. Back up your device using its native backup system (iCloud Backup, Google One Backup) to preserve your Ears Up data.

6. Data Retention

6.1 As Long As You Have the App

Your check-in data is retained on your device for as long as you have Ears Up installed and your device's storage permits. We do not impose any time-based retention limits because we never receive your check-in data.

6.2 After Uninstall

Uninstalling Ears Up removes the app's encrypted SQLite database from your device. Because we never received your check-in data, there is nothing for us to delete on our side. Ad-related data already collected by AdMob remains subject to Google's retention practices, which you can review and manage at adssettings.google.com.

7. Children's Privacy

Ears Up is not directed to children under 13 and we do not knowingly collect any personal information from children under 13. Because Ears Up has no account system and collects no personal identifiers of its own, there is no profile to create. AdMob is configured with "treat as child-directed" set to No, meaning Ears Up is not designated as a child-directed app under COPPA. Parents who believe their child under 13 is using Ears Up should uninstall the app, which removes all local data.

8. Security

8.1 On-Device Security

Your Ears Up check-in data is stored in an encrypted local database using SQLCipher (via expo-sqlite), layered on top of Apple's and Google's standard application sandboxing. We also rely on:

Because Ears Up has no network sync of your check-in content, there are no transit-layer security concerns for that content.

8.2 AdMob and Sentry Security

Data sent to AdMob is encrypted in transit using TLS by the Google Mobile Ads SDK. Crash reports sent to Sentry are likewise encrypted in transit using TLS.

9. Compliance Notes

9.1 Apple App Privacy Details

The following data types are declared in Ears Up's App Store privacy nutrition labels, consistent with the app's iOS privacy manifest:

No data from your check-in content is declared, because no check-in content is collected off your device.

9.2 Google Play Data Safety

The Google Play Data Safety section declares the AdMob categories above (device or other IDs, app activity / advertising data, and approximate location for advertising) plus the Sentry diagnostics categories, a "Data is encrypted in transit" affirmation, and a "Users can request data deletion" affirmation pointing to the uninstall path in Section 5.1. Sentry crash data is declared as Diagnostics → Crash logs, not linked to a user.

10. Changes to This Supplement

If we materially change how Ears Up collects or uses data, we will bump the version of this document and update the Last Updated date. Continued use of Ears Up after a change indicates acceptance of the revised supplement.

11. Privacy Contact

For Ears Up privacy questions:

For urgent privacy concerns:

This Privacy Policy Supplement should be read together with WagDev LLC's general Privacy Policy and Data Security Standards for a complete understanding of our privacy practices.