Cookie Policy

This Cookie Policy explains how DEBUNK uses cookies, local storage, SDK storage, and similar technologies on the web app.

Cookies and similar technologies can help keep you signed in, remember service state, measure usage, and connect web purchases or entitlements to your account.

DEBUNK uses essential session cookies and similar storage to keep authentication, account, security, and service state working.

These session cookies are necessary for requested service functionality and cannot be disabled from inside the app without affecting core features.

Firebase may use cookies or similar technologies for authentication, application infrastructure, and analytics.

RevenueCat may use similar technologies to support subscription entitlement and purchase flows.

DEBUNK does not intentionally set its own analytics cookies beyond provider functionality configured for the service.

DEBUNK does not intentionally set its own marketing cookies.

If marketing cookies are added later, this page and the cookie banner will be updated before they are used where consent is required.

Firebase and RevenueCat may set or read cookies or similar technologies when their SDKs or services are used.

Payment flows may also involve Stripe or app store pages that use their own cookies, policies, and consent tools.

DEBUNK needs a cookie banner for consent management before optional non-essential cookies are enabled or expanded.

Until that banner is implemented, DEBUNK should keep cookie use limited to essential service needs and provider functionality required to operate the app.

You can control cookies through your browser settings. Blocking cookies may prevent sign-in, account, payment, or debunk features from working correctly.

For questions about cookie use, contact info@ohmm.dev.