Privacy Policy - PWS Watch (HyperKode)

Last updated: May 16, 2026

This Privacy Policy describes how PWS Watch handles information when you use the dashboard, API, iOS app, watch app, widgets, admin tools, and related HyperKode services.

1) What PWS Watch does

PWS Watch helps you view personal weather station telemetry, recent trends, weather alerts, public forecast baselines, local calibration signals, and station-related assistant responses.

2) Information PWS Watch processes

A. Station and weather data

PWS Watch processes station identifiers, current observations, observation history, provider metadata, alert data, and forecast baselines from supported weather providers. Provider attribution may be shown in the product so you can see which sources are supported and which ones are active.

B. Anonymous client identifiers

The dashboard may create a stable anonymous clientId in browser local storage. This helps correlate usage, diagnose reliability, and support private aggregate metrics without requiring an account.

C. Optional email addresses

If you enter an email address, PWS Watch uses it to save station shortcuts, associate your tracked stations, and support soft station claims. Email is optional for viewing weather data.

Public station views do not show another user's email address. If a station is claimed by someone else, the UI should only show that the station is claimed.

D. Saved stations and claims

When you track or claim a station, PWS Watch stores that relationship. Claims are soft markers: one user can hold the current claim for a station, another user may reclaim it later, and claims do not block anyone from viewing or tracking the station.

E. Usage, diagnostics, and admin metrics

PWS Watch records operational events such as station views, API reads, saved-station actions, assistant usage, token usage, event-bus activity, and selected request context. These records are used for private operations, cost awareness, reliability, abuse prevention, and product improvement.

F. AI assistant interactions

If you use a PWS Watch assistant, your question and relevant page context may be processed by the configured AI provider to answer the question. Assistant usage may also be recorded in private aggregate metrics, including token counts, model, provider, prompt name, and status.

3) How email may be used

Email addresses are collected as optional contact identifiers for station features. HyperKode may use an email you provide to:

PWS Watch will not expose your email address to other public users. Entering an email does not by itself opt you into notifications or marketing. Future marketing, paid features, or monetization-related email use should include clear notice, consent where appropriate, and unsubscribe or preference controls.

4) What PWS Watch does not do

5) Third-party providers

PWS Watch may use weather, forecast, alert, cloud, database, billing, analytics, and AI providers to operate the service. Examples can include Weather.com PWS, Apple WeatherKit, Open-Meteo, National Weather Service, Google Cloud, and OpenAI, depending on current configuration.

6) Data retention

Browser settings and anonymous client identifiers remain on your device until you clear site data. Server-side operational records, saved stations, claims, and admin metrics are retained as needed for operations, reliability, cost management, and abuse prevention, unless deleted or changed as the service evolves.

7) Security

PWS Watch is designed to keep public weather access separate from private admin surfaces. Admin pages and admin APIs require an admin token. Public user-station APIs expose claim status without exposing another user's email address.

8) Your choices

9) Changes to this policy

HyperKode may update this policy as PWS Watch evolves. The "Last updated" date will be revised when the policy changes.

10) Contact

Developer: HyperKode (2026)
Website: https://hyperkode.com
Support: enrique.ortiz+pws@gmail.com