Weather Sage Privacy Policy

Effective October 4, 2026 · Updated 2026-10-13

Gulfstream Software Consulting LLC provides the Weather Sage website and weather service used by the mobile app. This policy explains how they process information when you visit the website or request weather, radar, astronomy, weather news, or AI outdoor activity forecasts. Your device platform and app store have their own privacy policies.

Information processed

• Location: The service receives the latitude and longitude supplied by the app, such as a location you select or a device location you permit the app to use. Weather and outdoor forecasts use a nearby geographic cell; astronomy requests use the supplied coordinates. Radar tile requests identify a map area.
• Network and service information: Our hosting provider processes your IP address and request information to deliver and secure the service. IP addresses are used for request limits. Operational logs can include request routes, approximate weather cells, response status, timing, and errors.
• Access credentials: Protected features use short-lived access tokens. The service processes tokens and authentication credentials to authorize requests and prevent abuse. Tokens expire after 15 minutes.
• Device registration: If the app registers for future notification features, we store a random installation identifier, a hashed private registration credential, a Firebase messaging token and platform, separate weather-alert and individual-message preferences, subscribed location names and coordinates, and registration/update dates in Cloudflare D1. Current-location coordinates replace the previous position rather than retaining a coordinate history. Delivery records contain notification identifiers, category, message content, status, retries, and timestamps; queued location references do not store coordinate history. You can change preferences or unregister using the app’s Notifications settings. These records persist until removed by the operator. Device notification permission is separate from each application opt-in. Messages are sent only for opted-in categories and require a valid push token.
• Usage statistics: We store aggregate daily and all-time counts of requests, errors, cache activity, and upstream calls. These counters do not contain individual locations, IP addresses, or access tokens.
• Website analytics and advertising data: The public landing page uses Meta Pixel. When you visit it, Meta may receive information such as the page visited, IP address, browser and device information, and identifiers stored in or read from cookies or similar technologies. Weather Sage records a page-view event through the pixel to measure visits and support advertising measurement.

How information is used

Information is used to deliver forecasts and map tiles, generate outdoor activity guidance, cache responses, measure reliability, limit abusive traffic, and measure the effectiveness of marketing for the public website. The API and mobile app do not provide user accounts or include the Meta Pixel; it runs on the public landing page.

Service providers and AI forecasts

• IFTTT: Receives the random installation identifier and registration creation time through a webhook when a new installation registers. Registration credentials, Firebase tokens, and locations are not included.
• Meta: Provides Meta Pixel on the public landing page and processes page-view, network, browser, device, cookie, and similar identifier data for analytics and advertising measurement under Meta’s applicable terms and privacy policy.
• Firebase Cloud Messaging: Receives your messaging token and notification content to deliver messages to your app installation.
• Cloudflare: Hosts the API and processes network requests, cached responses, security controls, operational logs, and aggregate statistics.
• LibreWXR alert service: Receives exact coordinates to retrieve alerts for your viewed or subscribed locations.
• Official weather news: NWS receives shared forecast-cell coordinates to identify offices, zones, and alerts. NHC and SPC provide shared public feeds without user location. News articles and forecast snapshots are stored by geographic cell in Cloudflare D1; cells unused for seven days and expired stories are removed in bounded background batches. Weather Sage Forecast news is generated using rules, without sending news-generation data to OpenAI.
• OpenWeather: Receives the geographic cell and forecast options needed to obtain weather data. For weather notifications using an unnamed current location, its reverse-geocoding service receives the subscribed coordinates to find a nearby city or area name.
• LibreWXR radar server: Receives tile coordinates, radar timestamps, and rendering options needed to provide radar imagery.
• MET Norway: Receives coordinates, date, and time offset for astronomy calculations.
• OpenAI: When you request an AI outdoor forecast, receives the approximate forecast cell, hourly weather data, units, and activity categories. We do not include your IP address or mobile access token in the AI prompt. We disable response storage with the API’s store: false setting. This does not disable OpenAI’s abuse monitoring. OpenAI states that API data is not used to train its models unless the API customer opts in, and that abuse-monitoring data may generally be retained for up to 30 days, with exceptions. See OpenAI’s API data controls.

Service providers may process data in countries other than your own under their applicable terms and privacy practices.

Retention and security

Weather, radar, astronomy, and generated forecasts are cached temporarily and may be shared between requests for the same area. Cache lifetimes vary by feature, and stale responses can be retained to handle upstream outages. Operational log retention follows the hosting configuration and provider policies. Aggregate statistics have no automatic expiration in the current service.

API keys remain on the server. Access controls protect restricted features and the statistics dashboard. Prefer sending mobile access tokens in authorization headers; tokens placed in URLs can appear in network or platform logs.

Your choices and requests

You can change location permissions in your device settings and stop sending device location by disabling that permission. Requests for locations you select still send the selected coordinates. Avoid requesting the AI outdoor forecast if you do not want the associated approximate location and weather data sent to OpenAI. You can limit Meta Pixel data through browser privacy or content-blocking settings and the advertising and privacy controls available from Meta.

Depending on your location, you may have rights to request access, correction, or deletion of personal information, or to raise a concern with a privacy authority. Contact us to discuss a request. Aggregate statistics do not identify individual users, so we may be unable to associate those counters with you.

Changes and contact

We will update this page when these practices change and revise the date above.