Manual city forecasts are the current default.

Browser and location data currently processed

• World-server choice, reactions and SOLO RUN: removed after a 90-day absolute expiry while the app is open, or on the next visit if it was closed
• Interface language: stored in an HttpOnly locale cookie for up to one year
• Automatic location: while disabled, Geolocation calls, coordinate or cell transfers and location-triggered AI calls are all zero
• Any earlier location display result is removed by the one-hour expiry timer or the delete-data control

Weather provider

OpenWeather processes public city forecasts. It receives a reduced cell centre only if the separately approved location feature is enabled. Always prioritise official local sources for severe weather and emergency guidance.

Direct sponsorship readiness

No external advertising or analytics SDK is connected. A tracking-free text sponsorship path is prepared for approved public-city pages, with zero active campaigns today. Allow, decline and the neutral 16+ choice stay on this device for 180 days, yield to GPC and can be deleted at any time.

PayPal payment readiness

PayPal Sandbox and Live payments are both disabled. There are currently zero orders, approvals, webhook mutations or payment-access cookies. If approved, PayPal processes payment details; we are designed to keep only an HMAC digest of a random access token, SHA-256 key digests of order/capture identifiers, amount, currency, state and expiry in Upstash for the approved term. On approval return, same-tab sessionStorage keeps only a validated order reference and absolute expiry for up to 15 minutes so the URL can be cleaned and a refresh can recover. This is neither encryption nor anonymisation.

Translation beta feedback

For posts awaiting native review, a visitor may choose only Natural, Awkward, Unclear or Risky/Offensive. By default nothing is sent to a server or stored in the browser. After a click, a code containing only the public post ID, market, language and enum verdict can be sent through the OS share sheet or copied manually. An external feedback page opens only after provider review and explicit configuration.

Incomplete before launch

The operator identity and privacy contact, deployment countries and log retention, legal bases, international transfers and vendor contracts are not final. Automatic location, advertising and multiplayer remain launch-blocked until those details are completed and reviewed; this page is not a claim of complete legal compliance.

Purposes and legal bases

Public city forecasts need no personal account. Language, server choice and SOLO RUN are device conveniences requested by the user. Regional legal bases and consent text for location, advertising and multiplayer are not final, so those features remain disabled.

Processors and international transfers

OpenWeather supplies public city weather; configured batch jobs may use OpenAI, Anthropic or xAI for public city copy. Upstash and hosting depend on deployment. Processing countries, subprocessors, DPAs and retention are not final, so transfers of personal location or advertising data have not begun.

User rights and location withdrawal

The delete control below removes browser storage and service cookies. If location is later approved, browser permission withdrawal, suspension and deletion of the one-hour result will be available together. Personal-data features will not launch until an operator and rights-request contact are published.

Children

The service is designed for a general 16+ audience and does not collect birth dates, schools or addresses. Even after location is approved, a neutral device-only 16+ check comes first; under-16 or no-answer choices block location permission and API calls. Advertising remains off pending separate approval.

Safeguards and incidents

Controls include minimisation, HMAC-based abuse protection, enforced expiry, security headers and kill switches. An incident procedure exists, but the responsible officer and external contacts remain launch blockers until the operator is final.

Redress, effective date and changes

The applicable supervisory and dispute-resolution routes will be named after the operator and launch countries are final. This document is dated 16 July 2026; later versions will record their date and material changes.

Delete my data

Delete this browser's location result and age-band choice, server choice, reactions, local progress, ad preferences and service cookies in one action.