Weather Lens

Privacy, plainly.

Effective 18 October 2026

Weather Lens helps you understand the weather in your places. It has no advertising, requires no Weather Lens account, and does not sell personal information or use it for cross-company advertising tracking.

This policy covers the Weather Lens app and website, operated by Wayne Sang.

Locations and forecasts

The app uses your current location, when you give permission, or a place you select to provide forecasts and related features. You can use saved or searched places without granting access to your current location.

Apple WeatherKit and MapKit process location and search information to provide weather and place search. Ordinary forecast requests to our API use latitude and longitude rounded to two decimal places, along with relevant details such as country, language, time zone or search radius. Weather notification registration is different: it sends the selected place’s coordinates without this rounding, as described below.

Our API uses Open-Meteo, Environment and Climate Change Canada, and OpenStreetMap-based Overpass services for specialist forecasts, air quality, alerts and nearby places. Our Astronomy feature uses Geoapify for nearby-place discovery. Marine nearby-place discovery also uses Geoapify place and water-boundary map data. Nearby-place queries may be sent to Geoapify, overpass-api.de or the Private.coffee service at overpass.kumi.systems. Providers receive the requested area and relevant query details from our server; we do not forward your Apple transaction identifier or device IP address with those provider queries. NOAA supplies aurora data; matching that data to your location happens on our server.

Information on your device

Saved places, preferences and recent forecasts are stored locally. Cached forecasts may include coordinates. The app shares weather data with its widgets through local shared storage. Background forecast refreshes use the same services described above.

Purchases and Premium

Apple handles subscription purchases and billing. We do not receive your payment-card details or Apple Account password.

Our service processes signed Apple transaction information to verify Premium access. We also receive App Store Server Notifications from Apple about subscription events, such as renewals, expiry, billing recovery, refunds and revocations. We store subscription identifiers, product, status, expiry and verification timestamps to keep access up to date. Subscription records are stored using Upstash. These identifiers can link records to the same subscription even though they do not tell us your name or Apple Account email address.

Weather notifications

When you enable server-based weather notifications, the app sends the monitored place’s name, precise coordinates, country and time zone, your notification preferences, an Apple push-notification token and device registration information, and a subscription reference to our server. These records are associated with your device and subscription. We use them to check forecasts and supported official alerts while the app is closed, verify Premium access, deliver notifications and avoid duplicate messages.

The monitored place follows your selection when the app successfully updates the server. Current Location uses the last location sent by the app; this feature does not continuously track your location in the background. The notification service keeps the current monitored place and limited delivery state rather than a travel-history log.

We use Apple WeatherKit for precipitation forecasts and government-issued official alerts in supported regions, and Apple Push Notification service (APNs) to deliver messages. Official alert links open Apple’s alert detail page. Our notification service runs on Vercel and stores registration and limited delivery state in Upstash. We do not use this information for advertising or cross-company tracking.

Operational records

Our services are hosted on Vercel. Operational and security records can include IP addresses, request paths and parameters, approximate coordinates, user agents, timestamps, response times, status codes and errors. These records help us protect the service, diagnose problems and maintain reliability. Location and diagnostic request records may be associated with your IP address. Subscription records are associated with an Apple transaction identifier. This information is not exclusively anonymous.

The app contains no third-party analytics SDK and does not send custom screen-view or tap events. Apple may provide sales and download reports, and aggregated usage or diagnostic reports subject to its reporting and sharing settings.

This website

This website uses no advertising scripts, analytics scripts, sign-up forms or application cookies. Its images and fonts are served from the site itself. Vercel processes ordinary web requests and may retain operational and security metadata, including your IP address and the pages requested.

Support and feedback

If you choose to contact us, we receive your sender address, message and any attachments you send. We use Google Workspace to receive and respond to email. We use your message to respond and address your feedback; we have not connected a separate automated triage service. The app’s email actions prepare an editable draft with the app version and relevant app area; they do not automatically attach your location, logs or persistent identifiers. TestFlight feedback is handled through Apple.

Storage and retention

Information may be processed outside your country by our hosting, storage and data providers. Local forecasts and preferences remain until replaced or cleared. Shared server forecast caches are temporary. Operational records follow the applicable providers’ retention settings.

• Subscription records: we keep records while needed to manage access and billing recovery. Confirmed expired or revoked records have a 90-day retention period measured from their effective inactive date. Billing failures allow for Apple’s recovery period. If a terminal notification is missed, a fallback deadline removes the stored record 150 days after its last access-validity date. Renewals update that deadline; storage retention does not extend Premium access.
• Apple subscription-notification deduplication: identifiers and digests used to avoid processing the same subscription notification twice expire after 180 days.
• Weather notification registration: registration and current notification state expire after 30 days without a state write. App updates and ongoing notification processing can refresh this period, so it is not a fixed 30-day limit from enrollment. Successfully removing notification setup in the app removes the current registration.
• Weather notification duplicate prevention: hashed official-alert identifiers expire up to 48 hours after their last qualifying refresh. We do not keep full official bulletin text per subscriber for this purpose. Other limited delivery and duplicate-prevention records may remain after registration is removed and expire separately, generally within 30 days of their last update. Shared government bulletin history contains public weather information and is separate from personal registration.
• Operational logs: our forecast API’s configured Vercel runtime logs and observability events have a 30-day retention period. This does not mean all provider security records or backup copies are deleted at the same time.
• Provider records: Open-Meteo states that individual API logs are removed after 90 days; aggregate usage may remain. Private.coffee states that its Overpass request metadata may be retained for up to 48 hours. We have not established a fixed retention period for overpass-api.de.
• Support correspondence: we retain messages while needed to handle your request and relevant follow-up. You can contact us about deletion. A specific unresolved dispute, security matter or legal obligation may require longer retention.

Provider-managed backups and security records follow the providers’ own practices. Deleting our subscription record does not delete Apple’s purchase records, and a later purchase or restore can create a new record after verification.

Provider information

You can read more in Apple’s privacy policy, Open-Meteo’s terms and privacy policy, Vercel’s privacy policy, Upstash’s privacy policy, and Private.coffee’s Overpass privacy policy. Information about the other Overpass service is available at overpass-api.de. Astronomy and Marine place discovery is Powered by Geoapify; see Geoapify’s privacy policy for its handling of request records. Water-boundary map data also uses the © OpenMapTiles schema. Nearby-place data is © OpenStreetMap contributors.

Your choices

• Change or revoke location permission in iOS Settings.
• Remove saved places and clear cached weather through the app’s controls.
• Control weather alert types or remove notification setup in the app, and control notification permission in iOS Settings. Turning off device notification permission does not itself remove server registration. Switching delivery off or removing setup does not erase all subscription, duplicate-prevention or operational records; those follow their separate retention periods.
• Manage or cancel subscriptions in your Apple Account settings. Deleting the app does not cancel a subscription.
• Choose whether to send feedback and what to include.
• Contact us to ask about access, correction or deletion of information we hold. Some records may need to be retained for security or legal obligations.

Contact and updates

For privacy questions or requests, contact Wayne Sang at weatherlens@waynesang.com.

We will update this policy when our practices change and show the revision date on this page.