Terms of Use

Last updated: 2026-07-06

These terms describe how WeatherRecall can be used and what users should expect from the service. Historical weather interpretation involves uncertainty and source trade-offs; these terms help set clear boundaries while preserving openness for planning and research use.

Service scope

WeatherRecall provides historical weather analysis tools, summaries, and educational content. The platform is designed for planning support, research context, and weather literacy. It is not an emergency warning system and should not be used as a sole safety source for life-critical operations.

Data and interpretation limitations

• Data quality can vary by location, station coverage, and historical availability.
• Summaries are based on available measurements and calculated baselines.
• Users should verify critical decisions with official meteorological services.
• No warranty is provided for absolute completeness in every scenario.

Acceptable use

You may use WeatherRecall for personal, editorial, educational, and operational planning purposes. You may not abuse the service through scraping that degrades performance, automated credential attacks, or attempts to bypass fair-use controls. Any activity that harms platform stability or other users is prohibited.

API use

Where API functionality is available, usage must follow documented limits and fair-use principles. Large-scale production use should coordinate with the WeatherRecall team to prevent reliability issues and ensure correct interpretation of returned fields.

Intellectual and editorial integrity

WeatherRecall content may be cited with attribution. If you republish interpreted findings, include context and avoid presenting summary text as official governmental forecast guidance. Editorial integrity requires preserving uncertainty notes and methodological constraints.

Changes to terms

These terms may evolve with product capabilities, legal requirements, and quality standards. Significant updates are reflected in the last-updated date and can be tracked through the changelog.

For questions: [email protected]. Related pages: Privacy, Cookie Policy, Methodology.