Privacy Policy

Last updated: July 21, 2026.

Who we are

Conditions.Site ("we", "us") is operated by Beels Technologies, LLC. It generates historical weather, sun, and moon condition reports. Questions: support@conditions.site.

What we collect

• Your email address, to create your account and send one-time sign-in links.
• Report and scan history: report entries retain only a title containing incident date/time and location plus those same incident fields; they do not retain case name, notes, settings, report output, or a downloaded PDF. Scan entries retain their location, search mode/parameters, and cached scan result so they can be reviewed without rerunning.
• Usage metadata: counts and timestamps of reports generated, to enforce plan limits. We do not sell this.
• Subscription status from our payment processor (see below). We never see or store your full card details.
• Support and feedback details you choose to submit, which may include your message, issue category, app version, browser information, and the case date/location that was open when you submitted it.
• Report diagnostics used to improve source coverage: a timestamp, broad geographic region, coordinates rounded to a five-degree cell, a recency bucket rather than the exact incident date, source success/failure outcomes, approximate nearest-station distance and app version. These rows do not include your account email, but we do not promise that operational timestamps can never be correlated.
• Basic website analytics such as page views, referrer, coarse country and device/browser category through our cookieless Counterscale deployment.

We do not use third-party advertising trackers.

Payments

Subscriptions are processed by Lemon Squeezy, our Merchant of Record. Your payment details are entered on and handled by Lemon Squeezy under their privacy policy; we receive subscription/customer identifiers, status, period dates, your account email, and a customer-portal link. We also keep a random checkout identifier while an issued checkout URL remains usable so account deletion cannot race a purchase.

Data sources

To build a report we query public weather, geocoding, elevation, and imagery services (e.g. Open-Meteo/ERA5, NOAA/AviationWeather.gov, ECCC GeoMet, GeoSphere Austria, SMHI, NASA, OpenStreetMap/Nominatim). The location and time you enter are sent to those services to retrieve data for that point. Successful public Nominatim geocoding responses may be kept in a shared cache for up to 30 days to reduce repeat provider requests; cache keys are hashed and are not stored with your account identity.

How we store it

Account, history, and usage data are stored in Cloudflare's infrastructure. Sign-in sessions use a signed, http-only cookie plus a revocable server-side session record. Sign-in links are single-use and expire in 15 minutes. Authorized service operators may access account metadata, history titles, feedback, diagnostics and stored records when reasonably necessary to operate, secure or support the service; this data is not public and is not sold.

Retention

Saved history remains until you delete an item/account, subject to a 250-item and 50 MB per-account cap. Automated cleanup retains de-identified diagnostics for up to 90 days; feedback and metered usage for up to two years; completed or expired operation records for one to seven days; rate-limit buckets for up to 48 hours; and processed billing deliveries for up to 90 days. An unconsumed checkout record remains through the checkout URL's 30-minute validity plus a 10-minute webhook safety interval; expired or consumed records are removed by the next daily cleanup. Subscription state/cursors remain while the account exists to prevent delayed billing events from changing access incorrectly. A keyed, non-email deletion digest may remain for up to 90 days after account deletion. Prior payment-provider subscription identifiers paired only with that keyed digest (not the raw email) may be retained as a durable suppression list solely to prevent late annual-plan events from attaching old billing identity to a future account generation. Upstream providers and Cloudflare may retain request/security logs under their own policies.

Your choices

• Access / export: your saved reports are visible in the app's History.
• Deletion: use Settings → Delete account to erase email-linked application data, saved History, feedback, usage, entitlements, sessions, and sign-in tokens. A paid subscription must be cancelled first, at the provider, because a subscription that can still charge you must not outlive the account. Once it is cancelled you can delete immediately, without waiting for the period you already paid for to run out; deleting early forfeits the rest of that period, and resuming the subscription afterwards will not restore the account. Deletion also waits while an issued checkout can still be used or its webhook safety interval / a verified billing update is in flight. When billing is configured, the deletion request sends the account email to Lemon Squeezy to verify that no matching live subscription was missed; contact support@conditions.site if you need help.
• Cancellation: manage or cancel your subscription anytime from the customer portal.

Changes

We may update this policy; material changes will be reflected by the "last updated" date above.

Terms of Service → · Report Methodology →