Cookie and Advertising Disclosure

The current MVP does not set advertising cookies or load advertising scripts. This page describes what must change before ads are enabled.

Current MVP state

MetaRinse does not currently load AdSense, Auto ads, a CMP, or analytics. No decorative cookie banner is shown because there is no consent-controlled advertising system to govern.

Local browser state

The image cleaner uses in-memory state and temporary object URLs. It does not put files or metadata into cookies, localStorage, or IndexedDB. A future language preference may be stored only after the visitor explicitly chooses a language; it must not contain image-related information.

Advertising remains disabled

PUBLIC_ADS_ENABLED and PUBLIC_GOOGLE_CMP_ENABLED default to false, and no ad slot renders without a real client and slot configuration. Setting PUBLIC_GOOGLE_CMP_ENABLED to true does not install a CMP or represent consent; it must remain false until a certified integration actually controls ad loading. There are no fake blank ad boxes. The example ads.txt file contains instructions only.

Before future advertising

  • Receive AdSense approval and the real publisher ID.
  • Choose a Google-certified CMP for applicable regions.
  • Make consent state actually control ad loading.
  • Update Privacy and Cookies pages with final vendors and purposes.
  • Update CSP only for required documented hosts.
  • Publish the exact ads.txt seller line from the account.
  • Keep every ad away from upload, cleaning, navigation, and download controls.

Contact and legal review

Questions: metarinse@gmail.com. The final operator must review this disclosure for the deployed region and services.