Cookie Policy

1. What this policy covers

This policy explains cookies, local storage, pixels, SDKs and comparable technologies that store or access information on a device. It supplements the Privacy Policy. A cookie is a small text record placed by a website; local storage is browser storage associated with an origin.

2. Technologies currently used

• denialfight_consent_v5 — first-party local storage used to record necessary, preference and Google Analytics choices, policy version, timestamp and whether Global Privacy Control was detected. Retained until cleared or superseded.
• denialfight_device_id_v1 — persistent random first-party local-storage identifier used as the primary key for unique-device counting and to connect server-side page visits and funnel actions. It is created whenever the Service loads and is not controlled by optional cookie preferences.
• denialfight_analytics_session_v1 — first-party session-storage identifier used to group actions within the current browser session.
• df_analytics_visitor and df_analytics_session — HttpOnly first-party fallback cookies used by the server to connect the initial HTML request to the browser session before local storage can be read.
• Google Tag Manager and Google Analytics 4 — load with Consent Mode v2 defaults that deny analytics and all advertising storage. Before analytics consent, Google may receive limited cookieless consent and measurement signals. If analytics is accepted, Google Analytics may set first-party identifiers such as _ga and _ga_<container> to measure sessions and the conversion funnel.
• Interface preferences — first-party local storage or a functional cookie may remember optional display or workflow settings requested by the user.
• Server access and funnel records — every HTML document request is logged with IP address, approximate country, requested URL, referrer, timestamp and limited browser classification. Known crawlers and automation are filtered before reporting. These are first-party server records, not advertising cookies.

3. Strictly necessary category

Necessary technologies support security, routing, consent records, persistent device identification, server access logging and the document funnel. Server logging and the device/session identifiers are always active and cannot be switched off through the optional-cookie banner. You can block or delete browser storage in browser settings, which may create a new device ID and reduce journey continuity.

4. Preferences, analytics and advertising

• Preferences remember optional interface choices. They are off until selected unless strictly necessary to deliver a requested choice.
• DenialFight first-party server analytics always measures human visits, entry sources, requested-page journeys and document-funnel steps. A random device ID is stored to count unique devices. Session IP address and approximate country derived locally from it are retained in the access-restricted owner dashboard for generally up to 400 days. IP-based country estimates can be inaccurate. Full user-agent strings are not retained in analytics.
• Google Analytics 4 measures page views, engagement, PSEO content groups, quiz progress, document-upload completion, preview views, checkout starts and completed purchases. Event parameters exclude uploaded content, filenames, claim descriptions, email addresses and full IP addresses. Google Analytics storage is optional; all advertising consent signals remain denied.
• DenialFight does not sell or share personal information for behavioral advertising and does not enable Google advertising features.

5. Consent standard

Where consent is required, it must be freely given, specific, informed and expressed by a clear action. Continuing to browse is not treated as consent. Reject optional and Accept all are presented as real choices. Withdrawing consent is as easy as granting it. Under Google Consent Mode v2 Advanced Mode, the Google tag can load with analytics and advertising storage denied and send limited cookieless consent or measurement signals; analytics cookies and identifiers are enabled only after an affirmative analytics choice.

6. Global Privacy Control and browser signals

Where legally required, DenialFight treats a recognized Global Privacy Control signal as an opt-out of sale, sharing and targeted advertising. Because those activities are not currently used, the signal confirms the existing setting. Do Not Track is not uniformly defined; we do not conduct cross-site advertising tracking regardless of the signal.

7. Manage or withdraw choices

Use the Cookie settings button on every page. You may also delete site data in your browser. Withdrawal applies prospectively and does not make earlier lawful processing invalid. If policy purposes materially change, we will request a new choice.

8. Third parties

Google processes Google Analytics and Tag Manager signals under its applicable terms and privacy documentation, including how Google uses information from sites that use its services. Third-party sites reached through a link control their own technologies. DenialFight cannot delete a third party’s cookies. Review that provider’s privacy notice and controls before using an external site.

9. Updates and audit

We periodically audit pages and network behavior for new storage or trackers. If a new provider is activated, this inventory, retention period, purpose and recipient will be updated before or when required.

10. Contact

Questions or requests: privacy@denialfight.com. Effective August 3, 2026; last updated August 10, 2026.