ThermoWeather Privacy Policy
Version scope. The optional privacy controls described below apply to version 1.0.17 and later. Version 1.0.16 and earlier did not offer separate analytics and crash-report controls; their previous behaviour is identified below. Updating this page does not add controls to an older installed app.
ThermoWeather (the “app”, “we”) shows weather forecasts and brings together temperature values from external BLE sensors and manual entry. The iPhone itself does not measure room-air or body temperature in degrees, and the app is not a medical device. The app is designed to collect as little as possible and to keep the most sensitive data on your device entirely.
1. Data that never leaves your device
Microphone recordings. The acoustic thermometer plays a short chirp and records its reflection. The recording is analysed on-device and discarded immediately; it is never uploaded or shared. The microphone is used only when you explicitly start a measurement.
Manual body-temperature values. If you enter body temperature manually, the value is handled only in current-session memory. It is not written to the app’s local database or app-container backup and is never sent to our servers, Firebase Analytics, Google AdMob, Adapty, or any other third party.
Local ambient-temperature log. External Bluetooth sensor readings and manual room-air entries are stored locally. A manual body-temperature entry remains available only until the app is closed. We operate no user-measurement servers and cannot see these values.
2. Data shared with services
Location. With your permission, coordinates (coarsened to forecast-level precision) are sent to WeatherAPI.com to fetch your local forecast. We keep no movement history. You may pick a city manually instead, in which case no location access is needed.
Forecast and weather map. WeatherAPI.com receives the forecast coordinates or selected city, weather request parameters and IP address. For weather map layers (precipitation, temperature, wind and pressure), WeatherAPI Maps receives tile indices, zoom level, selected layer and forecast hour, IP address and technical request headers. Tile indices identify the area being viewed. See the WeatherAPI.com Privacy Policy.
Geomagnetic activity. When you open the geomagnetic activity screen, the app requests the global planetary Kp index from NOAA Space Weather Prediction Center. Requests disclose your IP address and technical request headers to NOAA; they do not include your location, sensor readings or room measurements. The app caches the response locally. See the NOAA Privacy Policy.
U.S. official warnings. When the selected place is in the United States or a U.S. territory, the app requests active warnings for that place from the U.S. National Weather Service (api.weather.gov, part of NOAA). The request contains the place's coordinates rounded to 0.01° (about 1 km, because warnings are issued per county or zone), your IP address and technical request headers including the app's contact address; it does not include sensor readings or room measurements. Places outside the U.S. are never sent. The app caches the response locally. See the NOAA Privacy Policy.
Regional cyclone and tsunami bulletins. When you open these source screens or select the corresponding event layer on the map, the app requests the current tropical cyclone summary from NOAA NHC/CPHC and public CAP bulletins from NOAA tsunami warning centers (NTWC or PTWC). The warnings map checks both centers. These requests disclose your IP address and technical request headers, but do not include your location, sensor readings or room measurements. The cyclone map also downloads the official forecast cone and track files (KMZ/KML) from www.nhc.noaa.gov, using links in the cyclone summary. These requests likewise disclose IP addresses and technical headers, but do not contain the selected place's coordinates or indoor measurements. Responses and forecast graphics are cached locally. The sources have regional coverage; their records are not a determination of danger at your selected place. Opening an official bulletin link also makes a request to that source. See the NOAA Privacy Policy.
Earthquakes. When you open the Observations tab of the hazards screen or select the earthquake layer on the map, the app requests recent earthquakes near the selected place from the U.S. Geological Survey (USGS). The request contains that place's coordinates rounded to 0.1° (about 11 km), plus your IP address and technical request headers; it does not include sensor readings or room measurements. While the earthquake layer is shown, the app also requests earthquakes in the part of the map you are viewing; that request contains the edges of the visible area rounded outward to a grid of 1° to 15°, not your location. The app stores the response for the selected place on the device; responses for map areas are kept only in memory while the app is running. See the USGS privacy policy.
Base map. When you open or pan the map, the app requests images directly from OpenStreetMap Foundation servers. These requests disclose the IP address, tile indices and zoom level (the viewed area), and technical headers including the app name. They do not contain sensor readings or your temperature log. Denying location access does not hide the IP address or viewed area from map providers. See the OpenStreetMap Foundation Privacy Policy.
Map cache. Viewed tiles are stored in the device's cache directory to reduce repeated network requests. The operating system may clear this cache; it is removed when the app is deleted. We do not receive a copy of it.
3. Analytics and advertising
Product analytics (1.0.17 and later). “Usage analytics” is off by default. Only if you enable it, Google Analytics for Firebase processes app interactions, session events, app-instance identifiers and technical device information to help us understand feature use and improve the app. Reports may be aggregated, but underlying events are not necessarily anonymous. Our custom-event filter rejects temperature values, body categories, exact coordinates, user notes and sensor names. Weather usage events may include the country returned by the weather provider, not forecast coordinates.
Crash diagnostics (1.0.17 and later). “Crash reports” is a separate, off-by-default choice. Only if you enable it, Firebase Crashlytics receives crashes and handled errors, stack traces, app and operating-system versions, device information and installation identifiers to diagnose failures. Custom diagnostic fields are restricted to technical states; we do not intentionally attach readings, coordinates, sensor names, notes, email addresses or advertising identifiers. Handled-error messages are sanitised; uncaught crash messages can contain runtime error details.
Configuration and experiments. Firebase Remote Config uses installation identifiers to deliver configuration values, including onboarding and subscription variants. In the current implementation, fetching settings and assigning a variant can occur independently of the optional analytics choice. Sending our interaction and experiment-exposure events for measurement requires “Usage analytics” in 1.0.17 and later. Configuration delivery and measuring an experiment are distinct purposes; an analytics refusal is not permission to collect experiment events. See Firebase privacy information.
Subscriptions. Adapty processes subscription and transaction information, profile or installation identifiers, paywall interactions and technical device data to validate purchases, restore access and analyse subscription performance. In 1.0.17 and later, optional paywall-view logging requires “Usage analytics”. Purchase validation, restoration and the service's internal transaction records continue without that choice. The app disables Adapty IDFA/GAID and IP-address collection options and external analytics integrations; these settings do not disable all internal subscription processing. Apple handles payment details; we do not receive card numbers. See Adapty End-Users Privacy Policy.
Advertising. Google AdMob may process IP-derived approximate location, device identifiers, ad interactions and diagnostics to serve and measure ads and prevent fraud. Personalisation depends on your choices and applicable requirements. Where required, Google UMP presents advertising privacy choices; requests are gated on its permission to request ads. If you decline personalisation, limited or non-personalised ads may still involve data processing, or ads may be unavailable. Tracking permission is requested through Apple's App Tracking Transparency prompt. Plus removes in-app ads. Subscription processing continues; optional analytics and diagnostics follow your separate choices in 1.0.17 and later. Advertising choices and ATT do not grant permission for these optional streams. See Google Privacy Policy and AdMob data disclosures.
4. Legal bases (GDPR)
For 1.0.17 and later, we rely on your consent (Art. 6(1)(a)) for optional usage analytics and crash-report sharing. You can decline or withdraw each choice independently, without losing app features or Plus. We do not switch these optional streams to “legitimate interests” when you decline.
Core features you request, such as forecasts and purchase validation, rely on contract performance where applicable (Art. 6(1)(b)); required billing and record-keeping may rely on legal obligations (Art. 6(1)(c)). Advertising and tracking use separate consent where required. Delivering configuration does not by itself establish that participation in an A/B experiment is necessary to provide the app.
Earlier versions. In 1.0.16 and earlier, analytics services initialised at startup and release builds enabled crash reporting without separate in-app switches. The earlier notice described crash/usage statistics under legitimate interests (Art. 6(1)(f)). The new choices do not apply retroactively; you can contact us about earlier processing using the rights described in section 6.
5. Retention and deletion
On your device. Microphone samples are discarded after analysis. Manual body-temperature values last only for the current session. Ambient readings remain until you delete them or delete the app. App deletion removes its local data and cache; offloading the app may preserve data, and operating-system backups are managed through your Apple settings.
Analytics and configuration. Identifiable event and user data are subject to the Google Analytics property's retention settings; expiration and any reset on new activity follow those settings. Aggregated reporting can be retained separately. See Google Analytics retention controls. Remote Config installation identifiers remain until deletion is requested; Firebase describes removal from live and backup systems within 180 days after that request.
Crash reports. Firebase states that crash traces and associated identifiers are retained for 90 days before removal from live and backup systems begins. This is not a promise that all backup copies disappear on day 90.
Subscription records. Records are retained as needed to validate and restore entitlements, resolve billing disputes, prevent fraud and meet legal obligations. Adapty retention follows our service terms and applicable law; eligible data can be deleted on our instruction. Deleting app data does not cancel your Apple subscription or erase purchase records that Apple must retain.
Advertising and provider logs. Google advertising data and weather/map request logs follow the providers' retention policies, including service operation, security and legal needs. See Google retention information and the WeatherAPI and OpenStreetMap policies linked above. We do not control independent provider logs or promise their immediate removal when the app is uninstalled.
Support correspondence. We retain messages for handling your request and any related follow-up, dispute or legal obligation. We delete or anonymise identifiable information when it is no longer needed for those purposes.
6. Your choices and rights
Advertising choices can be reopened in app Settings → “Privacy settings” when the provider requires that option. Tracking permission can be changed in iOS Settings → Privacy & Security → Tracking. Location, microphone and Bluetooth permissions can be revoked in iOS Settings. You can choose a city manually without location permission.
In 1.0.17 and later, open Settings → Privacy → “Your privacy choices” to change “Usage analytics” and “Crash reports”. Both start off; “Continue without sharing” leaves them off. The initial choice also applies after updating from an older version if you have not yet made a choice. The app and Plus work when you decline.
Turning a choice off stops future optional sharing. Events that occur while usage analytics is off are not saved by the app for later replay. Withdrawal does not automatically erase information already received by providers; their retention rules in section 5 and deletion-request rights still apply. It does not cancel a subscription or stop core weather, map, configuration and purchase requests. Advertising choices and iOS permissions are managed separately.
You may object to processing or request access, correction, restriction, portability or deletion, where applicable, by emailing tgstartup@icloud.com. Withdrawal does not affect processing that was lawful before withdrawal.
We respond within one month, subject to lawful extensions, and explain any request we cannot fulfil. We may need limited information to locate an app installation or purchase; do not send passwords, card details or health readings. We do not require you to create an account to submit a request. Where possible, we instruct our processors to delete identified records and explain any legal retention exceptions. Uninstalling alone does not submit such a request. You may also complain to your local data protection authority.
7. Protection and international processing
We require third parties receiving personal data through our app to protect it at least as strongly as this policy and Apple's applicable privacy requirements. Providers acting on our behalf must limit processing to authorised purposes and apply appropriate confidentiality and security measures. We remain responsible for selecting and configuring the services used by our app; linking a provider policy does not waive that responsibility.
Services may process data outside your country. Where required, international transfers must use recognised safeguards, such as an adequacy decision or standard contractual clauses. Provider policies describe their locations and safeguards. Connections to the listed services use HTTPS; no method of storage or transmission can be guaranteed completely secure.
These legal pages are hosted on GitHub Pages. Opening them sends a web request to GitHub, which processes technical information such as your IP address to operate and secure its service. See the GitHub General Privacy Statement. We do not add analytics, advertising, cookies or third-party scripts to these pages. Copies viewed on Google Drive are served by Google under its privacy policy. No account or app installation is required to read these web pages.
8. Children
The app is not directed at children under 13 and we do not knowingly collect their data.
9. Changes and contact
Material changes update the date above and, where appropriate, are announced in the app.
Privacy contact and developer: tgstartup, tgstartup@icloud.com.