Barometric Pressure Tracker — Privacy Policy
Effective Date: November 13, 2026
This Privacy Policy covers Barometric Pressure Tracker, both the Android app on Google Play (package com.patzerllc.BarometricPressureTracker) and the iOS app of the same name on the Apple App Store for iPhone and iPad (together, “the App”). Both are developed and published by Mobile Card Games & Travel Apps, LLC. It explains what data the App collects, how it is used, and how your privacy is protected. Where the Android and iOS versions differ, the difference is called out explicitly.
1. Data We Collect
The App is designed so that your personal data stays on your devices — and, on iPhone and iPad, in your own iCloud account:
- Symptom log entries: Health-related entries you choose to log (see the Health Data section below). Stored on your device and, on iPhone and iPad, synced end-to-end encrypted through your own iCloud account.
- Your location (with your permission): Used to fetch the local pressure forecast and to tag a symptom entry with where you were when you logged it. On Android, the coordinates are rounded to a grid of about 11 km before a forecast request leaves your device (see the Location section).
- Live barometer readings (with your permission): The App can read your device's built-in barometer via the motion sensor permission (iOS) for an optional real-time pressure view. On Android the App reads the pressure sensor directly; Android requires no permission for it. These readings are processed on your device.
- Saved locations and settings: Places you track and your app preferences. On iPhone and iPad, saved places sync end-to-end encrypted through your own iCloud account.
- Purchase information: Transaction records for the subscription, managed by Apple (iOS) or Google Play (Android) and RevenueCat.
The App does not collect your name, email address, advertising identifiers, or photos, and it contains no third-party analytics or advertising SDKs. The Android version removes the Android advertising-ID permission, so it cannot read one.
2. Health Data
The App includes an optional symptom log for tracking how pressure changes affect you (for example headaches, migraines, joint pain, or sinus pressure). Each entry you log can include: the symptom type, a severity rating (1–10), the start date and time, an optional freeform note, whether you took medication (a simple yes/no toggle — no medication name or dose is captured), the barometric pressure reading at the time, and a snapshot of your location name and coordinates at the time of logging.
- On your devices and in your own iCloud: On iPhone and iPad (version 1.11 and later), symptom entries are saved in an on-device database (SwiftData) that Apple’s CloudKit syncs through the private database of your own iCloud account, so they appear on each iPhone and iPad signed in to that Apple Account. Everything you enter — symptom, severity, times, note, medication toggle, pressure readings, and location — is end-to-end encrypted with keys kept in your iCloud Keychain, so neither we nor Apple can read it. If you aren’t signed in to iCloud, or you turn off iCloud for the App, entries stay on that device only. Earlier versions kept entries on the device only. There is no upload to any server we operate. On Android, symptom entries are kept in the App's private storage and are excluded from Android backup and device-to-device transfer.
- We cannot see it: Your symptom log is never sent to Mobile Card Games & Travel Apps LLC or to any third party. Its iCloud copy lives in your private iCloud database, which only your Apple Account can access, and its contents are end-to-end encrypted. As the App itself says on the log form: entries stay on your devices and your own iCloud, and we never see or share them.
- Reports you export (Android): If you choose to export a report, the App creates a CSV file and a PDF of your symptom entries on your device and hands them to the app you pick in the share sheet. Where they go from there is your choice; we never receive them.
- Never sold or shared: Your health data is not sold, shared, or used for advertising or marketing.
The App does not use Apple HealthKit, and the Android version does not use Health Connect.
3. Consumer Health Data
Some laws treat information about your health that an app handles — “consumer health data” — with special care. In plain terms, here is where this App stands:
- What health data the App handles: the symptom entries you log — symptom type, severity, time, optional note, a medication yes/no toggle, the pressure reading, and the location snapshot attached to the entry.
- Where it lives: on your devices, in a local database, and — on iPhone and iPad — end-to-end encrypted in the private database of your own iCloud account. It is never uploaded to us, and it is never sold, shared, or used for advertising.
- Processing in transit: on iPhone and iPad, your symptom entries travel only between your devices and your own iCloud account, end-to-end encrypted; none of your symptom data is sent to us or to any other party. The only other related network request sends location coordinates to fetch pressure and weather data (on iPhone and iPad directly to Apple WeatherKit; on Android, rounded coordinates through our weather server, see the Location section); no symptom information is included. On Android, a report leaves your device only if you export it and send it somewhere yourself.
- Your choices: delete any symptom entry in the App (on iPhone and iPad the deletion also reaches your other devices and your iCloud copy), turn off iCloud for the App to keep entries on one device, or uninstall the App to delete everything on that device. For questions or to exercise any right over health data, contact us at the email below.
4. Location
Location is used while the App is open, in two ways:
- Weather and pressure lookups (iPhone and iPad): The coordinates of your current or saved location are sent to Apple WeatherKit to retrieve pressure and forecast data. This is Apple's own weather service, and the coordinates are processed by Apple under Apple's privacy policy. No server we operate is in this path.
- Weather and pressure lookups (Android): Before anything leaves your device, the App rounds the coordinates of your current or saved location to 0.1° (roughly 11 km) and sends only those rounded coordinates, with your device language and the App version, over an encrypted connection to a weather server operated by Mobile Card Games & Travel Apps, LLC. The server uses them only to retrieve pressure data from Apple Weather (Apple WeatherKit) and return it to the App. It does not store your coordinates with any identifier, build a location history, or link requests to you; its own logs record only the 0.1° grid square and whether the answer came from its cache, never your IP address. It briefly caches the weather data for each grid square without any information about who asked. Like any web service it receives your IP address to answer the request, and our hosting provider (Google Cloud) processes it to deliver the request; the IP address is used only transiently to deliver the response and to limit abuse. Apple receives only the rounded grid coordinates from our server, never your device's IP address or identity. To keep forecasts and alerts current, the Android App also refreshes the forecast for your selected location in the background about every 6 hours, in the same rounded way; it does not use your location in the background.
- Symptom entry tagging: The location attached to a symptom log entry is stored alongside that entry — on your device and, on iPhone and iPad, end-to-end encrypted in your own iCloud account. It is never sent to us or anyone else.
- Place names and search (Android): To show the name of your current location, or to find a place you type in, the App may use your device's built-in geocoding service, which may process your coordinates or search text under your device provider's privacy policy.
You can deny location permission and instead track pressure for locations you enter manually.
5. Third-Party Data Sharing
On iPhone and iPad, the App shares data with only two parties, and neither can read your health data. The Android version works with the parties marked (Android) instead, and none of them receives your health data either:
- Apple: WeatherKit receives location coordinates to return pressure and weather data, and Apple processes your subscription payment (iOS). We never see your payment card details. On iPhone and iPad, iCloud stores your synced symptom log and saved places in your private iCloud database with their contents end-to-end encrypted, so Apple can’t read them. On Android, Apple Weather receives only the rounded grid coordinates from our weather server. Weather data is provided by Apple Weather. Data sources.
- RevenueCat (revenuecat.com): Manages subscription purchases. RevenueCat receives purchase/transaction tokens and a random anonymous app-user ID — never your name, email, or any symptom data. On Android, RevenueCat receives an automatically generated anonymous App User ID, basic device and app technical information, purchase history, Google purchase tokens, and subscription status — never your name, email address, symptom entries, or precise location. See the RevenueCat Privacy Policy.
- Our weather server (Android): Operated by us, as described in the Location section.
- Google Play (Android; Google Privacy Policy): Processes subscription payments through Google Play Billing; we never see your payment card details. Google Play also shows the in-app rating card and, when the App suggests one of our other apps, that app's install sheet.
- Our website (Android): The App occasionally downloads a small configuration file from mobilegames.cloud that decides whether to suggest another of our apps. The request contains no personal data.
We do not sell, rent, or share your data with any other third parties. There is no Firebase, no analytics SDK, and no ad network in this App.
6. Data Storage and Retention
- On your devices and in your iCloud: Your symptom log and saved locations live in a local database on your device; on iPhone and iPad they also sync, end-to-end encrypted, through the private database of your own iCloud account, which we cannot access. Your pressure-alert schedule stays on each device. Small app preferences are synced across your devices via Apple iCloud key-value storage tied to your Apple ID (iOS); we cannot access them. On Android, symptom entries, saved locations, cached forecasts, and settings are kept in the App's private storage, and there is no iCloud sync.
- Android backup: Android cloud backup and device-to-device transfer are limited to the App's cross-promotion preferences (a random install ID used only on your device, a session count, and whether one of our other apps has already been suggested). Your symptom entries, locations, forecasts, and settings are excluded from backup.
- On our servers: We do not operate servers that store your data. On Android, our weather server caches weather data per grid square, without any information about who asked.
- Notifications: Pressure-change alerts are scheduled locally on your device — there is no remote push server. On Android they are re-armed after your phone restarts.
- Widget (Android): The home-screen widget shows the latest pressure from the forecast the App has already saved on your device.
- Deletion: You can delete individual symptom entries in the App at any time; on iPhone and iPad the deletion syncs to your other devices and your iCloud copy. Uninstalling the App removes the data stored on that device. Your iCloud copy stays available to your other devices, so delete your entries in the App first if you want them gone from iCloud too.
7. Data Security
On iPhone and iPad, your symptom log leaves your device only to sync with your own iCloud account, and everything you enter is end-to-end encrypted before it leaves, so only your devices can read it. On Android, your symptom log never leaves your device unless you export a report yourself. The App’s other network traffic — WeatherKit weather lookups and App Store purchase processing — travels over encrypted HTTPS connections operated by Apple and RevenueCat (iOS). On Android, requests to our weather server, Google Play and RevenueCat purchase processing, and the configuration download from our website also use encrypted HTTPS, and coordinates are rounded on your device before they are sent.
8. Your Rights
You have the right to:
- Delete any symptom entry, saved location, or alert in the App at any time.
- Remove all App data from a device by uninstalling the App (on iPhone and iPad, delete your entries in the App first to remove the iCloud copy as well).
- Deny location or motion-sensor permissions; the App will still work for manually chosen locations. On Android, you can deny or revoke location and notification permissions at any time in Android Settings.
- Manage or cancel your subscription in your Apple ID settings (iOS) or in Google Play under Payments & subscriptions (Android).
Depending on where you live, privacy laws such as the European Union's General Data Protection Regulation (GDPR) and the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA) give you rights over your personal data, including the rights to know, access, correct, and delete it. Because we do not hold your data on servers we operate, there is typically nothing for us to access or delete on request — your data lives on your devices and, on iPhone and iPad, in your own iCloud account, where you control it. Where the App does process data in transit, or a third-party service described above collects data, you may contact us at the email below to exercise your rights, and we will respond as required by applicable law.
9. Children's Privacy
The App is not directed at children under 13, and we do not knowingly collect data from children under 13. In some regions, including the European Union, a higher minimum age applies to consent for data processing; the same statement applies there — we do not knowingly collect data from anyone under the applicable age.
10. Data Breach Notification
In the unlikely event of a data breach affecting user data on any system we operate, we will notify affected users as required by applicable law.
11. Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be reflected by updating the "Effective Date" at the top of this page.
12. Contact Us
If you have questions about this Privacy Policy or your data, please contact us at:
v5cqpsj4e3u4@opayq.com