What DailyGeo collects and why.

This privacy policy applies to dailygeo.app and the DailyGeo web application. It explains the categories of personal data we process to run the product, prevent abuse, measure usage, and fulfill subscriptions.

DailyGeo is built around daily puzzle gameplay, account sign-in, optional paid subscriptions, and ad-supported access for non-subscribers. This policy is written for that MVP scope and should be read together with the terms and ad disclosure pages.

We collect account data you provide directly, such as your email address and authentication identifiers returned by supported login providers. If you purchase a subscription, we also store subscription status, Stripe customer references, and billing event metadata needed to keep entitlements in sync.

We collect gameplay and product telemetry generated by your use of the app. That includes puzzle mode, guesses submitted, solve state, streak progress, hint unlocks, archive access, share actions, consent preferences, and ad interaction events such as rewarded-video completions.

Like most hosted web applications, we and our infrastructure providers may also process technical request data such as IP address, browser details, device metadata, timestamps, and security logs for reliability, fraud prevention, debugging, and error monitoring.

We use data to authenticate users, persist puzzle progress, score guesses, maintain streaks, suppress ads for subscribers, process subscriptions, enforce rate limits, diagnose service issues, and investigate application errors reported through Sentry.

We also use Google Analytics 4 for aggregate product analytics and use ad-measurement data to understand product performance, monitor ad frequency limits, and evaluate whether the free tier remains sustainable. We do not expose exact puzzle answer coordinates to clients before a solve.

DailyGeo uses an ad-supported free tier. Where required by law, we request ad consent before serving personalized advertising. Users who decline personalization should receive contextual or otherwise limited ad treatment when supported by the ad stack.

Consent choices and related audit details are stored so the application can honor your selection and demonstrate when the setting was changed.

We share data with service providers only as needed to operate the product. That includes Supabase for authentication and application data, Vercel for hosting and delivery, Stripe for subscription billing, Google Analytics for aggregate usage reporting, Sentry for error monitoring, and Google advertising services for consent and ad delivery when enabled.

We may disclose information when reasonably necessary to comply with law, enforce the terms, protect users, or investigate abuse of the service.

We retain account, gameplay, and subscription records for as long as they are needed to operate the service, maintain streak and billing integrity, resolve disputes, and satisfy legal obligations. We may keep de-identified or aggregated analytics longer.

You can manage account access through supported login providers and can update ad-consent choices from the app when that control is available. Before launch, the operator should add a public support contact for privacy requests, corrections, and deletion inquiries.