Skip to privacy policy
Your information. Clearly explained.

Wheather Privacy Policy

Effective November 21, 2026

Wheather (“we” or “us”) is based in the United States. This policy covers the Wheather app, its widgets and weather service, and wheather.app. For privacy questions or requests, email support@wheather.app.

Privacy at a glance

Location permission is optional. Your saved-place list, personal views, preferences, and notification rules are stored on your device. Getting new weather sends selected coordinates to Wheather’s service, hosted by Supabase, which requests forecasts from Apple WeatherKit. Maps and place searches also contact providers described below.

Apple handles purchases. You do not create a separate Wheather account. The app has no advertising, advertising-tracking SDK, marketing-analytics SDK, or separate third-party crash-reporting SDK. We retain limited service-use and diagnostic records for access verification, forecasts, reliability, and abuse prevention.

Location and searches

Choosing Current Location requests location permission while you use the app. Wheather requests kilometer-level accuracy but does not round returned coordinates. Precise coordinates may be used when iOS supplies them and your settings allow it. The point obtains weather, identifies a place name/time zone through Apple, and centers maps. Wheather does not request Always permission or continuously track your movements in the background.

You can search for a place without device-location permission. Apple receives search text and may receive selected coordinates for reverse geocoding. Wheather locally saves the place’s name, coordinates, time zone, country when available, and an identifier. Fetching its weather still sends its coordinates to the weather service.

With Current Location selected and iOS widget-location authorization, a widget can request one location during an eligible refresh and reverse-geocode it through Apple. Saved-place widgets do not request device location. An available fallback may appear as Last location. Background weather and notification checks can use stored coordinates without requesting new device location. iOS controls background activity and refresh timing.

Weather and map providers

Forecast requests send selected coordinates, available country/time zone, language, Apple-signed access information, app version/build, request source, and a request identifier to Wheather’s Supabase-hosted service. It verifies access and sends coordinates and forecast options to Apple WeatherKit.

The weather function processes coordinates without saving them in its subscriber or usage database. It does not intentionally log request bodies, raw Apple proofs, or forecast responses. Infrastructure can separately process connection information and operational logs.

Depending on what you open, your device also contacts:

ProviderRequests handled
ApplePlace search, reverse geocoding, Apple Maps, location services, and purchases.
Iowa Environmental MesonetObserved radar and HRRR predicted-reflectivity catalogs and imagery.
NOAA / National Weather ServiceSupported radar, satellite, lightning, weather-warning, and forecast-map products.
NOAA Aviation Weather CenterVisibility observations for the viewed map area.
Environment and Climate Change CanadaSupported radar, wind, forecast, and air-quality products.
NASA GIBSSnow-cover imagery.

Direct providers receive connection information, including your IP address, and relevant search text, coordinates, map bounds/tiles, layer, or time. An area may be your location, a saved place, or elsewhere you explore. Apple receives the server connection for proxied WeatherKit requests; Supabase receives the device connection. Providers manage their own logs and retention.

See Apple’s privacy information, Supabase’s data-processing information, and source links in Settings → Weather & data sources.

On-device storage and backups

Local information includes saved/selected places, units, appearance, header metric, Home and Forecast layouts, map choices, notification rules, and welcome-screen completion. Wheather does not synchronize these preferences between devices through a Wheather account.

The app and widgets share selected-place information, relevant units, access status, and forecasts through an iOS App Group. Access information includes subscription product/tier, transaction identifiers, purchase/expiration dates, verification date, and environment. Protected shared files retain signed Apple app, subscription, and available renewal information for eligible widget refreshes.

The app’s forecast file holds six places and removes forecasts older than 24 hours when next read or updated. The separate shared widget cache holds six places without automatic age deletion. Older forecasts may remain until replaced, evicted, or removed with app data, including readings marked Earlier or Last location. Map imagery uses bounded local caches. Apple backups can include and restore app data, separately from this app/widget sharing.

Purchases and access

Apple StoreKit and the App Store handle purchases, renewals, billing, and restoration. Wheather does not receive payment-card/bank details, your Apple Account password, or Apple Account email through verification.

The first free month starts with first verified use and ends automatically without subscription signup. Verified Apple app identity recognizes the trial across reinstalls and devices. Continuing to open weather views afterward requires eligible subscription access.

Signed Apple information goes to Wheather’s service and is associated with a pseudonymous subscriber identifier. This is not anonymous: it links records over time. Apple can send signed subscription-status callbacks, such as renewal or revocation information. TestFlight/sandbox transactions are tests and can use different timing.

Service records and retention

The service retains verified app/transaction identifiers; subscription status, tier, environment, expiry/revocation; trial timing; first/last use; usage counts; and diagnostics including request outcomes, source, version/build, timing, duration, and error category. Administrative restrictions and abuse-review flags protect service availability. Keyed hashes of network identifiers support rate limiting; the usage database does not store raw IP addresses.

These records serve access verification, delivery, reliability, support, and security, rather than advertising. Saved-place lists, personal views, notification rules, search history, raw forecast coordinates, and forecast bodies are not stored in this database.

Configured retention is:

  • 30 days: detailed request diagnostics and Apple subscription callback events.
  • 90 days: daily usage detail and administrative audits.
  • About two days: keyed network/subscriber rate-limit buckets.
  • Rolling 30 calendar days: abuse-review flags.
  • No fixed automatic expiry: subscriber, trial, access and entitlement/revocation records, transaction associations, and cumulative counts. These remain until administrative removal or an applicable verified deletion request is handled, subject to necessary security or legal retention.

Detailed cleanup is scheduled daily, so removal may occur at the next run. Abuse flags have a separate scheduled cleanup. Global monthly usage totals may remain without individual subscriber identifiers. Hosting logs/backups follow provider retention settings and may persist beyond deletion from live records. Local preferences and access proofs remain until changed, replaced, cleared, or removed with app data.

Notifications

In Settings → Weather notifications, add, edit, disable, or remove rules and choose their places, conditions, thresholds, windows, and timing where available. Rules stay on-device. Forecast checks use the requests above; the app evaluates forecasts and schedules notifications locally, without uploading rules to a weather-notification push server.

Removing/disabling a rule cancels its pending notification. Delivered notifications can remain until dismissed. Turning notification permission off in iOS does not erase rules. Checking and delivery depend on forecasts, service access, and iOS scheduling.

Website and support

The website uses Brizy. Hosting/delivery infrastructure receives ordinary request information such as IP address, URL, timing, and browser/device information to deliver and protect the site. Provider logs and platform cookies/storage follow applicable settings and Brizy’s privacy practices.

The interactive preview uses labeled sample readings. It requests no device location or live weather and sends no demo choices to Wheather’s weather backend. We have added no custom advertising pixels, analytics integrations, registration, or contact forms. Manage website storage/cookies in your browser. External links lead to services with their own policies.

Support receives the email address, message, and attachments you choose to send. The app’s email link automatically attaches no location, subscriber information, or logs. We use Supabase for email-related services and use correspondence to respond to and follow up on your request. Email storage is subject to provider settings and applicable security/legal requirements. Please do not send passwords or payment-card details.

Controls and deletion

  • Change location/Precise Location in iOS Settings → Privacy & Security → Location Services → Wheather. Saved places work with device-location access off. Widget permission is While Using the App or Widgets, where available.
  • Remove places in Settings → Manage saved locations. Removing the selected place returns to Current Location and may request permission. Earlier cached weather can remain.
  • Edit views through Customize Home View and Customize Forecast View; manage rules in Weather notifications. Remove widgets if no longer wanted.
  • Use Delete App, rather than Offload App, to remove local data managed by iOS. Manage backups separately through Apple settings.
  • Manage/cancel subscriptions through Apple. App deletion does not cancel billing or automatically delete Wheather service records or Apple purchase records.

Permission loss clears the ineligible last-current-place cache; disabling Precise Location clears it when marked precise. Older app/widget forecasts can remain.

Email support@wheather.app for access, correction, or deletion requests. We may verify your request and retain limited information for applicable security, fraud-prevention, or legal requirements. Providers separately manage previously received information and backups.

Security, processing locations, and rights

The weather database is configured in US East, United States. Edge functions, hosting, delivery networks, email, and other providers can process requests elsewhere. Wheather uses HTTPS, protected local access/forecast files, and restricted database access. No system guarantees absolute security.

Depending on applicable law, you may have rights to access, correct, delete, restrict/object to processing, or receive eligible information in a portable format. Where processing relies on consent, you can withdraw it for future processing. Rights have conditions and exceptions. Contact support to exercise rights or raise concerns. You may also complain to a relevant authority or use an applicable statutory appeal process. Requests are handled within legally required periods. Parents/guardians can contact us about information concerning their child.

Changes and contact

Updates appear at wheather.app/privacy-policy with a revised effective date. Additional notice will be provided where legally required.

Wheather · United States support@wheather.app