Privacy Policy

BullMeteo is a Bitcoin Market Weather and daily Forecast Game at bullmeteo.com. This page describes confirmed technical processing. It does not claim a legal basis that has not been approved and does not make an absolute compliance claim.

Privacy contact

For privacy questions or requests, email [email protected].

Account and authentication data

When you create an account, BullMeteo processes a user ID, email address, display name, password hash and salt, account timestamps, and hashed session records with session metadata. The raw session token stays in the browser cookie; BullMeteo stores its SHA-256 hash server-side.

Forecast and game data

BullMeteo stores your forecasts, forecast-time evidence, settled results, XP, level, streaks, achievements, and the timestamps needed to operate and audit the daily game. This preserves the exact forecast submitted before the server-authoritative deadline.

Notifications

Account notifications can contain result, achievement, and progress updates together with their read state. Notification details are private to the signed-in account.

BullMeteo is partly a public forecasting product. Depending on your activity, your display name, stable public profile URL, level and XP, forecast counts, accuracy, current and best streak, forecast distribution, achievements, recent settled results, and leaderboard position may be visible without signing in.

Public result pages and their Open Graph sharing previews may also identify your display name and forecasting outcome. Your email, password information, sessions, notifications, account controls, and P7 Personal Forecast Intelligence remain private.

Signup already explains that a display name and forecasting performance may be public while the email address remains private.

Server and security logs

The nginx reverse proxy processes request metadata including host, remote IP address, request path, HTTP status, referrer, User-Agent, and upstream details. These logs support security, abuse prevention, troubleshooting, and service operation. Reverse-proxy logs are size-bounded and rotated; BullMeteo does not describe that bound as a fixed number of retention days.

PostgreSQL statement and duration logging is disabled in the verified production configuration. Short-lived rate-limit buckets exist only in application memory. Visitor addresses selected for rate limiting are immediately hashed and are not persisted by the application.

Security measures

• Passwords are stored as salted password hashes, not plaintext.
• Sessions use random browser tokens and server-side token hashes.
• The production session cookie is HttpOnly, Secure, SameSite=Lax, host-only, and restricted to the site root.
• PostgreSQL has no published host port, and the web container is reached through Docker networks and nginx-proxy.
• BullMeteo trusts Cloudflare’s visitor-IP header only when the separately authenticated proxy header is valid. It does not trust X-Forwarded-For for rate-limit identity.

These measures reduce risk but are not a promise that every security incident is impossible.

Cloudflare

Production traffic passes through Cloudflare before reaching BullMeteo. Cloudflare receives the visitor IP, request URL and path, request headers, cookies, and request body in transit. Network Error Logging (NEL) and Report-To headers are active. No Cloudflare cookie was observed during normal anonymous requests, although security or challenge cookies may appear conditionally when protection features are triggered. Cloudflare retention and transfer details have not yet been confirmed for this draft.

Hosting

The production application and PostgreSQL database run on a ZAP-Hosting VPS in Germany according to operator information, using Docker and nginx-proxy. This draft does not assign speculative legal roles to the provider.

CoinGecko

BullMeteo requests Bitcoin market data from CoinGecko server-to-server. BullMeteo does not send your account identity, forecast identity, session, or browser IP address to CoinGecko, and the browser does not call CoinGecko for BullMeteo market data.

Let’s Encrypt

Let’s Encrypt and ACME are used for certificate issuance. BullMeteo currently has no runtime email, analytics, advertising, or external error-monitoring provider.

Cookies

BullMeteo currently uses strictly necessary storage only. Details of the first-party session cookie and conditional Cloudflare security cookies appear in the Cookie Notice. BullMeteo currently uses no analytics, advertising, or marketing cookies.

Retention

• The session cookie has a 30-day lifetime.
• Expired database session rows are purged through protected settlement maintenance.
• Account data, notifications, forecasts, and results are currently retained while the account exists, subject to the deletion behavior below.
• Anonymous settled forecasts may remain after deletion to preserve historical Crowd and Engine-vs-Crowd integrity.
• Rate-limit buckets and market-data caches are short-lived according to their operational cache/window policies.
• Docker and reverse-proxy logs are size-bounded rather than retained for a guaranteed number of days.

Backups

Access-restricted, compressed database backups are created daily at 03:20 UTC and retained for up to 30 days under the configured rolling policy. They are stored locally on the VPS and can contain account and personal data. Deleted information can therefore remain in an older backup until that backup expires. Pruning runs only after a successful replacement backup. There is no confirmed off-site copy or application-level backup encryption.

Your account controls

Signed-in users can edit their display name, sign out of the current session, sign out all devices, download a JSON account export, and permanently delete the account. BullMeteo does not currently provide email-address changes, password changes, password recovery, or a per-session device list.

Deletion and anonymization

Account deletion removes the personal account identity, email, password data, sessions, notifications, private account records, open or unsettled forecasts, public profile, P7 insights, and leaderboard membership. Settled forecasts may remain in anonymized form, without a link to the deleted user, so historical aggregate results remain internally consistent.

A retained public result URL may continue to show the result under “Deleted forecaster.” Older backups can retain deleted information until the rolling 30-day backup retention expires. Search engines, social platforms, and other external caches may take additional time to refresh previews that were created before deletion; BullMeteo cannot promise immediate removal from those third-party caches.

Your rights

Depending on the applicable law and circumstances, you may have rights concerning access, correction, deletion, restriction, portability, objection, or a complaint to a competent supervisory authority. The applicable scope depends on the governing law and circumstances. Controller identity and service-address details are not published in this release. Privacy requests can be sent to [email protected]. The built-in export and deletion controls remain available from your account.

Changes to this policy

This notice will be updated when BullMeteo’s processing, service providers, retention practices, or optional technologies change. Material additions such as analytics, advertising, or other non-essential storage require a fresh technical and privacy review before deployment.