Privacy Policy

Weather

This Privacy Policy explains how Weather ("we," "us," or "this App") collects, uses, and protects your information when you use our Android application.

1. Information We Collect

1.1 Information Collected by the App Itself

Weather is primarily a local weather forecast client. Unless explicitly described in this Privacy Policy (such as requesting forecasts, city search, geocoding, radar, or alerts from third-party providers), core preferences and cached weather data are processed on your device. It does not require you to register or sign in, and it does not upload personally identifiable information to our servers for an account system. Specifically:

• We do not require your name, mailing address, national ID number, or similar information as mandatory collection items;
• Saved cities, coordinates, display preferences, units, language, notification settings, weather-source choices, widget configuration, and cached forecast responses are primarily stored on your device (in the app's private storage / local database);
• Operations such as viewing forecasts, managing locations, updating widgets, showing local notifications, and calculating in-app alerts are processed primarily on your device; we do not operate a user-account backend or cloud service to store your city list or forecast history.

If you use the system "Share" feature or an optional companion integration to send weather content to another app, the data flow is governed by the system and the other app's policies. This App accesses such data only to the extent needed to perform the action you chose.

1.2 Information Related to Third-Party Services

This App does not integrate advertising SDKs (such as AdMob), and we do not use the Advertising ID to show personalized ads in the App. We do not operate a user-account backend or cloud service for storing users' personal account data. This App uses the following third-party services, which may collect certain information:

The Firebase-related data above is processed under Google's privacy policy. For more information, see: https://policies.google.com/privacy

General note: Data collected through Firebase is used primarily for analytics and app improvement. Google processes such data in accordance with its privacy policy. We do not upload your saved cities, forecast history, or weather preferences through Firebase.

Important: We do not provide a user account system, and we do not operate our own servers for storing users' personal data. Data processed by Firebase is subject to Google's data retention and security practices; retention periods follow Google's rules.

2. Permissions Requested by the App

To provide the corresponding features, this App declares or may use the following permissions (subject to your device system and the final merged application manifest):

Permission	Purpose
android.permission.INTERNET	Used to download forecasts, air quality, radar-related content, geocoding, city search, and weather alerts from third-party providers, and for Firebase Analytics / Crashlytics network transmission. Not used to provide an account, cloud backup, or an in-app advertising network.
android.permission.ACCESS_NETWORK_STATE	Used to check network connectivity before refresh attempts, Firebase SDK operations, and to avoid unnecessary failed requests.
android.permission.ACCESS_COARSE_LOCATION android.permission.ACCESS_FINE_LOCATION	Optional. Used while the App is in the foreground to determine your current place for the current-location city. You may deny these permissions and still use the App by searching for cities manually. Coordinates are stored locally and sent to weather/geocoding APIs only as needed for forecasts.
android.permission.POST_NOTIFICATIONS	Optional (requested as required by the system on Android 13 and above). Used for weather update progress, alert notifications, daily summaries, precipitation notices, and outing reminders when you enable those features.
android.permission.RECEIVE_BOOT_COMPLETED	Used after device reboot to reschedule background forecast refresh and reminder schedules that you enabled. These jobs use saved city coordinates, not continuous GPS tracking.
android.permission.WAKE_LOCK (merged via libraries such as WorkManager)	Used by system / WorkManager components to keep short work windows alive so scheduled refreshes can complete reliably.
android.permission.FOREGROUND_SERVICE (merged via WorkManager; used by weather refresh workers)	Present in the final App package. Used for expedited / foreground weather-refresh work (WorkManager), typically together with a visible notification while the task runs. This App does not use a foreground service for background location tracking.

Note: This App requests only the permissions needed for its features. You may manage or revoke some permissions in system settings; revocation may affect related features (for example, inability to set the current-location city or to show notifications).

3. Widgets, Background Updates, and Other On-Device Features

This App provides home screen widgets that display weather for your saved cities using data already stored or refreshed on your device. Widget updates do not require background location permission.

If you enable background updates, the App schedules periodic tasks to refresh forecasts for your default / saved cities, update widgets, and optionally show alerts. Those tasks use the coordinates already saved for each city.

This App does not provide cloud sync, online social feeds, or personalized advertising recommendations. The App uses Firebase Analytics and Crashlytics as described in Section 1.2.

4. How We Use Information

We use related information only for the following purposes:

• To provide and improve this App's forecasts, radar, air quality, alerts, widgets, and related weather features;
• To resolve place names and timezones for cities you add or for optional device location;
• To deliver local notifications and reminders you enable;
• To keep preferences and cached weather data available between sessions on your device;
• To optionally send a weather summary to Gadgetbridge when you enable that setting;
• To analyze aggregated app usage and diagnose crashes through Firebase Analytics and Crashlytics, in order to improve stability and product quality.

5. Data Sharing and Disclosure

We do not sell, trade, rent, or share personal information for advertising purposes. Technical request data may be transmitted to the third-party providers described in this Policy solely to provide the requested weather, search, geocoding, radar, air quality, or alert services, or for analytics and crash reporting. Data processing or disclosure may occur only in the following circumstances:

• Weather / search / geocoding / alert services: technical request data (such as coordinates or a search query) needed for the feature you used is handled by the corresponding provider under its privacy policy;
• Google Firebase: analytics events and crash diagnostic data are processed by Google under Google's privacy policy, as described in section 1.2;
• Sharing initiated by you: when you use system share or optional Gadgetbridge integration, the data is received by the destination you choose;
• Legal requirements: where required by law, or upon a lawful request by a court or other competent authority, we may disclose necessary information as required.

6. Data Security

We take the security of your information seriously. Data related to this App's core weather and management features is processed primarily on your device. When requesting forecasts, search results, geocoding, radar, or alerts from third parties, or when Firebase Analytics / Crashlytics transmissions occur, network transmission typically uses secure protocols such as HTTPS/TLS. We will not sell your data or use it in ways inconsistent with this Policy. We do not operate a user-account backend or cloud service for storing your city list or forecast history.

Please note: if Android Auto Backup is enabled on your device, some app data may be included in device backups according to system rules. That visibility results from your device / account backup settings, not from upload by us to a separate weather-account service.

7. Children's Privacy

This App is not directed to children under the age of 13, and we do not knowingly collect personal information from children under 13. If you believe there is a related issue, please contact us.

8. Changes to This Policy

We may update this Privacy Policy from time to time. The updated version will be posted on this page (or the same in-app link), and the "Last updated" date will be revised. For material changes, we will provide notice in an appropriate manner as required by applicable law. We encourage you to review this Policy periodically.

9. Your Rights

To the extent permitted by applicable law, you may have the right to know about, access, correct, delete, or restrict processing of information related to you. Because this App is primarily local, you can usually manage local data through in-app features such as deleting saved cities, or by clearing app storage / uninstalling the app in system settings. You may also revoke location or notification permissions in system settings. You may uninstall this App at any time to stop using it; after uninstall, data in the app's private directory is deleted according to system rules, but device backups may retain copies until expired or deleted by you or the backup provider.

Because we do not store your city list or forecast history on our servers as a cloud account, there is no server-side request for access, correction, or deletion of that local content from "our cloud." For information processed by third-party weather or search providers during a request, please see their privacy policies.

10. Contact Us