CleanCopy

Privacy Policy

Last updated: July 16, 2026

Your editor text stays in your browser. Cleaning is performed locally. CleanCopy does not send the source text, cleaned output, or clipboard contents to its servers.

Local browser data

Cleaning preferences are stored in your browser. Draft recovery is off by default. If you enable it, the current editor text is saved only in that browser’s local storage until you disable recovery or clear the data.

Optional feedback

If the feedback form is available and you submit it, CleanCopy stores the category, message, submission time, processing status, source label, and verified Firebase App Check application identifier. Do not include editor text or other sensitive information. Direct browser access to the feedback database is blocked.

Analytics measurement and optional cookies

CleanCopy loads Google Analytics on each visit using Consent Mode. Before consent, or after analytics cookies are declined, analytics storage remains denied and Google receives cookieless page-view and feature-usage signals for measurement and modeling. These signals may include the selected cleaning mode, action name, output character count, and standard device, browser, network, page, and request information. If you allow analytics cookies, Google Analytics may store identifiers that support fuller visit and returning-user measurement. Editor text, cleaned output, and clipboard contents are never included. You can change this choice using “Cookie settings” in the footer.

Hosting and security logs

Firebase Hosting and Google Cloud may process standard request metadata, such as IP address and user agent, to deliver and protect the service.

Third parties

The optional feedback service uses Firebase App Check, reCAPTCHA, Cloud Functions, and Firestore. Usage measurement uses Google Analytics with analytics storage controlled through Consent Mode. Their processing is governed by Google’s applicable terms and privacy documentation.

Contact

For a privacy request, use the feedback form without including sensitive editor content, or open an issue in the CleanCopy GitHub repository.