Version 1.4.0 · Effective November 8, 2026 · Last updated November 8, 2026

Read with the WagDev Privacy Policy, General Terms of Service and Data Security Standards.

Ears Up Privacy Policy Supplement

Effective Date: November 8, 2026 Last Updated: November 8, 2026

This Privacy Policy Supplement is specific to Ears Up. It adds to the WagDev Privacy Policy and our Data Security Standards. Where this supplement is more specific, it governs for Ears Up.

1. Summary

Ears Up is a single-user daytime-sleepiness check-in app. Your check-ins are stored on your device, and we never receive them. Everything you record (your check-ins, sleepiness ratings, notes and any reminder schedule) is stored in a database on your phone and is never sent to us or to any service we use. A device backup or an export you make can copy it elsewhere, under your control. There is no account, no login and no cloud sync. We do not run a server, we do not run analytics, and we do not have a copy of your check-ins anywhere.

Ears Up is available for iPhone and is coming to Android. A few limited flows of technical data leave your phone. None of them includes your check-ins:

2. Data Collection

2.1 What You Provide

All of the following is stored on your device, in a database inside the app:

We never receive, see or store any of this, 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 shows a single banner strip above the tab bar. It never covers your check-ins and never appears over a dialog.

When Ears Up requests an ad, the Google Mobile Ads SDK collects the following on Google's behalf, for ad delivery, frequency capping, measurement and fraud prevention. It never receives your check-ins, and ads are never chosen using your sleepiness data.

iPhone: non-personalized ads. On iPhone, Ears Up requests non-personalized ads only, and does not share your information for targeted advertising.

Android: personalized ads. On Android, Ears Up lets Google personalize ads. Each ad request sends Google your device's advertising ID, your IP address (from which Google estimates your general region), basic device information, and the identity of the app the ad appears in, which is Ears Up. Google can combine this with what it already knows about that advertising ID to choose ads. Ears Up never sends your check-ins, ratings, notes or anything else you record, and never tells Google anything about your sleepiness. Because the ad request names the app, Google can tell that the device uses a sleepiness check-in app, and could connect your advertising ID with that fact. Google's advertising policies restrict personalizing ads based on health conditions, but we do not control how Google uses this information. Some US state laws call this kind of ad personalization "sharing". You can stop it at any time (Section 5.2).

Consent in the EEA, the UK and Switzerland. If you are in the European Economic Area, the United Kingdom or Switzerland, Ears Up shows Google's consent form before it requests any ad. If you decline, Ears Up may still request a banner, but Google will serve only a limited ad: no personalization, and no use of cookies or device identifiers except, where enabled, to detect invalid traffic. Your IP address is still used to deliver it. Sometimes no ad is shown at all. Outside these regions, you are not shown a consent form.

Changing your choice. Open Settings and tap Privacy options to reopen the consent form at any time and change or withdraw your choice. A change applies from the next ad request. The row appears only where Google's consent tools require it, which today means the EEA, the UK and Switzerland.

Removing ads. Ears Up offers a one-time in-app purchase that removes advertising permanently. It grants nothing else; the Ears Up widgets are free for everyone. Once ads are removed, Ears Up stops requesting ads and the AdMob SDK collects nothing further.

Section 4.3 of the WagDev Privacy Policy gives the full AdMob disclosure. Google's handling of this data is governed by Google's privacy policy.

2.4 What Sentry Collects for Crash and Error Reporting

To find and fix bugs, Ears Up uses Sentry, a crash and error reporting service run by Functional Software, Inc. When the app crashes, hits an error or freezes, Sentry receives:

Sentry does not receive:

App stability sessions. Sentry also records a session each time you open and close Ears Up, so we can see how stable each release is. A session contains only the app version, device model and operating system version, the random installation ID, when the session started and how long it lasted, and whether it ended normally or in a crash.

IP address and approximate location. Sentry sees your IP address when a report arrives. We have set Sentry not to store it, but Sentry uses it on arrival to estimate an approximate location (city, region and country) and stores that estimate with error reports. We use it only to diagnose problems.

Sentry is switched off in development and automated-test builds. Reports are deleted after 30 days. See Sentry's privacy policy.

2.5 Other Services

3. How Ears Up Uses Your Data

3.1 On Your Device

Your check-ins are used only to power the app on your device:

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

3.2 No Cross-Device Sync

Ears Up has no server or account, so your check-ins do not sync between devices. On a new device, you start fresh unless you import an export you made (Section 5.3). If you delete Ears Up, its data on that device is erased (Section 5.1).

4. Data Sharing

4.1 We Do Not Share Your Check-Ins

4.2 AdMob Receives Only Ad-Serving Data

AdMob receives only the data listed in Section 2.3. It never receives your ratings, notes, schedule or anything you create in the app.

4.3 Sentry Receives Only Diagnostic Data

Sentry receives only the data listed in Section 2.4. It receives no check-in data of any kind.

5. Your Privacy Controls

5.1 On-Device Controls

5.2 Advertising Controls

Ears Up works fully whatever you answer on the consent form.

5.3 Data Export

Ears Up offers a full export in Settings, then Your data, which you can keep somewhere safe and import on a new phone. Because your check-ins live on your device, we cannot recover them if your device is lost. On iPhone, iCloud and computer backups can include your Ears Up data. On Android, Google device backup does not include it, so use the export.

6. Data Retention

6.1 Your Check-Ins

Your check-ins stay on your device for as long as you keep Ears Up installed, or until you delete them. We set no time limit, because we never receive them.

6.2 Other Data

7. Age and Children

Ears Up is made for adults and is not directed to children. You must be at least 18 to use it. Ears Up has no accounts and does not ask your age. It does not mark its ad requests as child-directed, because it is not made for children. If you believe a child has used Ears Up, deleting the app removes all of its data from the device, and you can contact privacy@wag.dev.

8. Security

8.1 On Your Device

Your check-ins are stored in a database inside the app's private storage, protected by the phone's app sandbox. The app does not add its own encryption to that database. It relies on your phone's own encryption: iOS Data Protection when your iPhone has a passcode, and Android's device encryption.

8.2 Data in Transit

Data sent to AdMob, Sentry, Expo, the App Store and Google Play travels over encrypted connections.

9. Compliance Notes

9.1 Apple App Privacy Details

Ears Up's App Store privacy label declares:

Nothing is declared as used for tracking, so the App Store page has no "Data Used to Track You" section. "Linked to you" means linked to an identifier Google holds, not to any account with us: Ears Up has no accounts. No health data or user content is declared, because none leaves your device.

9.2 Google Play Data Safety

On Google Play, Ears Up declares Device or other IDs, Approximate location, App activity (App interactions) and Diagnostics as collected and shared, for advertising, analytics, fraud prevention and app functionality (Google's ad SDK, plus Sentry's installation ID, IP-derived location, breadcrumbs and diagnostics). Crash logs are collected by Sentry for app functionality and not shared. All of it is encrypted in transit. No health data or user content is declared, because none leaves your device.

9.3 Consumer Health Data (Washington, Nevada and Connecticut)

Some US state laws, such as Washington's My Health My Data Act, protect "consumer health data". Your check-ins are health data. On Android, the fact that a device uses Ears Up, sent with its advertising ID, could also be treated as health data. Here is exactly what happens:

9.4 Deletion Requests

We hold no copy of your check-ins and no account for you, so you delete your check-ins yourself, in the app or by deleting it (Section 5.1). We do hold crash reports in Sentry, which are deleted after 30 days and are not linked to your name or email. If you want them deleted sooner, email privacy@wag.dev and we will delete any reports we can match to an identifier you give us.

10. Changes to This Supplement

We will update the version and "Last Updated" date for every change. If we materially change how Ears Up collects or uses data, we will tell you in the app before the change takes effect, and we will not apply a new use to data collected earlier without your consent.

11. Privacy Contact

This supplement should be read together with the WagDev Privacy Policy and Data Security Standards.