Privacy Policy
What MetaRinse processes locally, what ordinary web hosting may receive, and which services are disabled in the MVP.
Plain-language summary
Image processing data
The cleaner reads files only after you choose or paste them. It uses browser memory, local object URLs, a worker when supported, and canvas encoding. Image bytes, base64, blob URLs, thumbnails, filenames, metadata values, hashes, dimensions tied to a file, GPS, and camera models are not sent through fetch, XHR, forms, beacons, analytics, error reporting, or third-party SDKs.
- No account or database.
- No image persistence in localStorage or IndexedDB.
- Object URLs are revoked when items are removed, results are cleared, or the page closes.
- No third-party error-reporting SDK.
Ordinary website requests
The hosting provider may process ordinary request information such as IP address, request time, requested path, user agent, and security logs when your browser loads site files. Those requests do not include the images you select in the cleaner. Cloudflare hosting disclosures must be reviewed against the final account configuration.
Analytics
Cloudflare Web Analytics is disabled in the current MVP configuration. If enabled later, this policy must be updated first. No future analytics event may include filenames, metadata, GPS, camera details, hashes, previews, or exact file sizes.
Advertising and consent
Google AdSense, manual ad slots, Auto ads, and the Google CMP are disabled. The current build flags and dormant component scaffold are not a consent platform: they do not collect, store, or enforce a visitor’s choice. Before advertising is enabled, the owner must supply a real publisher ID, integrate a certified CMP where required so consent actually governs loading, update this policy and the Content Security Policy, and publish the authorized ads.txt entry.
Your choices and contact
Clearing the cleaner or closing the page removes the in-memory working session. For privacy questions, contact metarinse@gmail.com.