Information we collect
The site does not create accounts, accept form submissions or collect email addresses. The page loads reviewed forecast and event data from same-origin JSON files. Vercel may process basic request data such as IP address, browser type, requested path and time to secure and deliver the site under its own terms.
Analytics
No analytics script is enabled in this build. If privacy-friendly aggregate analytics are added, this section will name the provider, the measurements collected, the purpose, retention period and any available opt-out before collection begins.
Cookies and local storage
The current preview does not set advertising, analytics or account cookies and does not store a visitor profile in local storage. Normal browser or hosting behavior outside the site’s code may still apply. Any future preference storage will be documented with its purpose and lifetime.
Advertising
Advertising is disabled. This build contains no visible advertising, Google AdSense script or ad request.
If Google advertising is enabled later, third-party vendors including Google may use cookies or similar technologies to serve and measure ads. Before that happens, this policy will link to the applicable ad-personalization choices and the site will implement required consent handling, including a Google-certified consent management platform where required for visitors in the EEA, United Kingdom and Switzerland.
Email alerts
Email alerts are not active and no email is collected. They will not launch until double opt-in confirmation, one-click unsubscribe, suppression handling, delivery deduplication and appropriate retention rules have been tested and documented.
External links
History and methodology pages link to external evidence, including OpenAI resources and public posts. Those destinations apply their own privacy terms. External requests occur only when a visitor chooses a link; the launch page does not silently embed those sources.
Data retention
The site retains its own public event evidence and forecast snapshots to make revisions auditable. These records describe public product events rather than visitor profiles. Retention for operational server logs, analytics or email records will be stated after the corresponding provider is selected.
Your choices
With the current feature set, there are no site accounts, marketing emails or advertising preferences to manage. Future controls will be available before the associated collection is enabled, and legally required access or deletion routes will be documented with a verified contact channel.
Changes and contact
Material policy changes will be dated and published before new collection begins. A verified public contact route is still required before launch and before any advertising review.