Privacy Policy

FitForecast is an early beta (MVP). It has no user accounts and no FitForecast user database. Everything you set up is stored locally in your browser on your device. The only information that leaves your device is what is technically required to fetch a forecast.

• No user accounts, sign-in, or sign-up.
• No email addresses.
• No passwords or credentials.
• No server-side user database; no Supabase user records or tables are used by this MVP.
• No advertising trackers or advertising cookies.
• No Google Analytics, Meta Pixel, PostHog, or Sentry user analytics.
• No behavioral or session analytics.

The following are saved in your browser’s localStorage so the app can remember your setup between visits. They are not transmitted to a FitForecast server:

• First name (optional) — used only for your on-screen greeting.
• Clothing profile and preferences.
• Temperature preference (runs hot / neutral / runs cold).
• Style preference.
• Units preference (°F / °C).
• Location information, including the saved place name and its coordinates.
• Outfit history — a short, bounded list of recently shown outfit signatures used only to avoid repeating the same outfit. Limited to the current MVP implementation.

FitForecast may request your precise device location only after you choose the location feature and grant your browser’s location permission. It is a one-time request tied to that action.

• Latitude and longitude are obtained from your device at the moment you request it.
• Your location information is stored locally on your device.
• Coordinates may be transmitted to the weather and geocoding services required to produce a forecast.
• This MVP uses Open-Meteo (forecast and city search) and BigDataCloud (reverse geocoding).
• No FitForecast user account is created from this information.

FitForecast does not track your location continuously and does not collect location in the background.

The MVP relies on third-party services that are necessary for it to function:

• Open-Meteo — weather forecast and city search (geocoding).
• BigDataCloud — reverse geocoding (turning coordinates into a place name).
• Google Fonts — typography.
• Hosting and deployment infrastructure used to deliver the application.

As with any normal web request, contacting these services may expose technical information such as your IP address, browser user-agent, and request timing to that service. That is inherent to how the web works and is outside FitForecast’s control. Each service handles that information under its own privacy policy.

In production, technical errors are not transmitted to FitForecast. Any error details that may be captured remain local to your browser and are not used to build a profile of you.

Because FitForecast stores your preferences locally rather than in a FitForecast account or database, you are in control of removal. You can:

• Use “Clear My FitForecast Data” on the Profile screen, which removes all FitForecast keys from this browser and returns the app to the Welcome screen; or
• Clear this site’s data in your browser settings.

There is no backend deletion request process because there is no server-side user database to delete from.

FitForecast is not directed to children. Because the app can request device location, it should be used with adult supervision where local law requires it.

This is a beta product and this policy may change as the product changes. Questions about this policy can be directed to fitforecastnow@gmail.com.