Embedded Files
Effective: 27 October 2026
This privacy policy describes which data the Android app “What Weather” (Google Play and Amazon Appstore, free and Pro versions) processes, for what purpose, and to whom it is disclosed.
1. Controller
Werner Kolov
An den Eschen 7
26129 Oldenburg
Germany
Email: playstore@kolov.com
2. Principles
The app does not require an account. It does not collect your name, phone number, contacts, photos or similar data.
The app contains no advertising, no analytics or tracking SDK and no crash-reporting service of its own.
Weather data is not requested from the weather services by your device directly but through our own server (the “backend”), hosted on Microsoft Azure. The weather services therefore do not see your device’s IP address. Exception: radar images (section 5).
Settings, saved locations and the local weather history are stored only on your device and are deleted when you uninstall the app.
3. Location and weather requests
Data: If you allow the app to access your location, your device’s coordinates are sent to the backend to retrieve weather data for that place. The app first rounds the coordinates to three decimal places (about 100 m). In Android you can also grant only approximate location, or deny location access and choose places manually; the selected place is then sent. With every request the app also sends technical information: app version, variant (e.g. Google/Amazon, free/Pro), language, selected units and the selected weather service. As with any internet connection, the server also receives your device’s IP address.
Disclosure: The backend forwards the coordinates as the app sends them (i.e. rounded to about 100 m), without IP address or device identifier, to the selected weather service. Depending on your settings this is: Deutscher Wetterdienst (via Bright Sky), NOAA/National Weather Service, AccuWeather, OpenWeatherMap, Meteosource, WeatherAPI.com, Visual Crossing or WeatherFlow. To determine the place name, the coordinates are sent to HERE. How these services use the coordinates is governed by their privacy policies (links in section 10).
Purpose and legal basis: Providing the weather data you request in the app (Art. 6(1)(b) GDPR). Location access is optional and can be revoked at any time in the Android settings; the app then works with manually selected locations.
Retention: We do not store your coordinates permanently or in logs. Only weather responses are cached for minutes to hours, rounded to about 1 km so that requests from the neighbourhood get the same response, and place names for a position (about 100 m) for one week. These caches contain neither IP address nor device identifier. The technical information is used only for anonymous counts aggregated per day (e.g. number of requests per app version or language); the individual counters are deleted after 30 hours at the latest, and the aggregated daily figures contain no personal data.
4. Location search
When you search for a place in the app, the search text and language are sent to the backend and from there to Amazon Web Services (Amazon Location Service) to obtain suggestions and place details. Legal basis: Art. 6(1)(b) GDPR.
5. Rain radar and maps
When you display the rain radar, the app requests the map area around your location from the backend. The background map comes from Google Maps (retrieved by the backend); it is cached for map areas rounded to about 1 km.
Radar images from LibreWXR (librewxr.net) are usually loaded by the app directly from its server to keep server costs low. LibreWXR thereby receives your device’s IP address and the requested map area, from which your approximate location can be derived. If a direct download is not possible, the backend loads the images on the app’s behalf.
If you enter your own API key for Rainbow.ai in the settings, radar images are retrieved from Rainbow.ai through the backend using this key.
Legal basis: Art. 6(1)(b) GDPR; for the direct download from LibreWXR additionally our legitimate interest in operating the service economically (Art. 6(1)(f) GDPR).
6. Personal weather stations (Pro version)
You can connect your own weather station from Netatmo, Weather Underground, WeatherFlow (Tempest), Davis WeatherLink or Ecowitt. To do so, you enter the credentials of the respective provider (e.g. API key, station ID, for Ecowitt also the station’s MAC address; for Netatmo you sign in directly with Netatmo and the app receives an access token).
These credentials are stored on your device and sent to the backend with every weather request, which uses them to retrieve your station’s measurements from the provider. The credentials are stored only on your device; neither the backend nor its logs store them. Use is optional and can be ended at any time in the settings; the data is then no longer transmitted. Legal basis: Art. 6(1)(b) GDPR.
7. Purchases and subscriptions
Purchases (Pro version, “Premium”, removing the button) are processed by Google Play or the Amazon Appstore. To manage purchases the app uses RevenueCat (RevenueCat, Inc., USA). This involves a randomly generated anonymous identifier (e.g. “$RCAnonymousID:…”), purchase receipts, device type, operating-system and app version, and the IP address. Neither the developer nor RevenueCat receives payment details; these are processed exclusively by Google or Amazon. Legal basis: Art. 6(1)(b) GDPR.
The anonymous identifier is shown in the Support section so that you can provide it with questions about purchases.
8. Support requests
If you use the support form in the app, your email address, your message and the additional information you selected are sent to the backend and forwarded from there to the developer by email. You can deselect each item of additional information before sending: current coordinates, app version, purchases and RevenueCat identifier, weather service, language and country, Android version, device model, manufacturer, brand and build ID.
Alternatively you can send an email with your own email app; on request, an app log can be attached, which you can review before sending.
The purpose is handling your request (Art. 6(1)(b) GDPR). Emails are deleted when they are no longer needed for handling the request, at the latest after 2 years.
9. Server logs
While operating the backend, Microsoft Azure (Application Insights) logs requests and errors in order to detect and fix problems. This may include time, called function, response time, error messages and the IP address. Coordinates and credentials are not logged. The legal basis is our legitimate interest in secure and stable operation (Art. 6(1)(f) GDPR). Logs are deleted automatically after 90 days.
Crash reports that you send to Google or Amazon via Android are processed by them under their own privacy policies; the developer only receives anonymised evaluations in the Play Console or the Amazon developer portal.
10. Recipients and transfers to third countries
Recipients of the data described in this policy are:
Microsoft (Azure, backend hosting, region West Europe (Netherlands)) – as processor
the weather, map and place services named in sections 3–6 and the providers of your own weather station
RevenueCat, Google (Google Play) or Amazon (Amazon Appstore)
Some of these providers are based in the USA or process data there (including Microsoft, Google, Amazon, RevenueCat, AccuWeather). Where the provider is certified, transfers are based on the EU-US Data Privacy Framework (Art. 45 GDPR), otherwise on standard contractual clauses (Art. 46(2)(c) GDPR) or, where necessary to provide the service you requested, on Art. 49(1)(b) GDPR.
How the recipients use the data is governed by their own privacy policies:
Microsoft (Azure): https://privacy.microsoft.com/privacystatement
Google (Google Play, Google Maps): https://policies.google.com/privacy
Amazon (Amazon Appstore): https://www.amazon.com/gp/help/customer/display.html?nodeId=468496
Amazon Web Services (Amazon Location Service): https://aws.amazon.com/privacy/
RevenueCat: https://www.revenuecat.com/privacy
Deutscher Wetterdienst: https://www.dwd.de/DE/service/datenschutz/datenschutz_node.html (retrieved via Bright Sky, https://brightsky.dev/)
NOAA/National Weather Service: https://www.weather.gov/privacy
AccuWeather: https://legal.accuweather.com/privacy-policy/
OpenWeatherMap: https://openweather.co.uk/privacy-policy
Meteosource: https://www.meteosource.com/personal-data-protection
WeatherAPI.com: https://www.weatherapi.com/privacy.aspx
Visual Crossing: https://www.visualcrossing.com/privacy/
WeatherFlow-Tempest: https://tempest.earth/privacy-policy/
LibreWXR: https://librewxr.net/ (no privacy policy published)
Rainbow.ai: https://rainbow.ai/privacy-policy
Weather Underground (The Weather Company): https://trust.weather.com/en-US/privacy/privacy-policy
Davis Instruments (WeatherLink): https://www.davisinstruments.com/policies/privacy-policy
11. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). Please contact the email address above.
Since the app works without an account, the developer cannot attribute most data to a person. For questions about purchases, the anonymous RevenueCat identifier from the Support section helps.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the member state of your residence.
12. Children
The app is rated for all ages but is not specifically directed at children. It does not require you to provide personal data. Children under 16 should only use the support form with their parents’ consent. If you become aware that a child has sent us data without such consent, please contact us and we will delete it.
13. Security
All connections between the app, the backend and the services named are encrypted (HTTPS). However, no one can guarantee complete security for transmission over the internet.
14. Changes
This privacy policy will be updated when the app or legal requirements change. The version published on this page applies.
Google Sites
Report abuse