◩ clearcutt.

Clearcutt Privacy Policy

How Clearcutt handles local images, Google sign-in, reviews, payment references, model downloads and membership data.

Photos and edits

Selected photos, masks and edits remain in browser memory; they are not uploaded to the payment backend. Clearing the editor or closing the tab discards the editing session. Downloads are stored where your browser saves files. Model files may remain in browser cache. Closing a tab is not a guarantee of forensic memory erasure.

Accounts and payments

Firebase provides Google sign-in and can remember the login until you sign out or clear browser data. Cloudflare D1 stores the validated account ID, verified Google email, order and payment references, plan, expiry and webhook identifiers. These records restore membership and prevent duplicate payment processing. Razorpay hosts payment entry; Clearcutt does not store card numbers, CVVs, banking passwords or UPI credentials.

Third-party connections and performance analytics

GitHub Pages and Cloudflare serve the website, Google/Firebase provide authentication, and Razorpay handles payments. Model requests go to Hugging Face and its CDNs; the runtime downloads from jsDelivr. Those providers receive ordinary network metadata, such as IP addresses and request headers. Cloudflare Web Analytics currently injects a cookie-free performance beacon. It sends the page URL, referrer and browser performance measurements such as loading, paint and layout-shift timings to Cloudflare; it does not receive your selected photo, mask or edits. Cloudflare states that the beacon does not use cookies or browser storage and that source IP addresses received during request handling are discarded at the nearest data centre rather than stored in its core analytics databases or logs.

Retention and requests

Account and payment metadata currently remain in the backend; an automatic deletion schedule and self-service deletion are not implemented. Payment records may need retention for support and applicable obligations. See Contact for the current support channel. Never post private account or payment information in a public issue. This policy describes the implementation reviewed on 14 November 2026 and will be updated when practices change.

Public reviews

Signed-in users may submit one display name, rating and written review. Reviews are stored with the Firebase account ID and published immediately. Public responses do not expose account IDs or email addresses. Administrators may remove abusive or irrelevant content; deleting a review removes the saved review. Moderation decisions are logged for accountability.

Contact for privacy requests

Email yxsingh2@gmail.com to request correction or deletion of your account information. Identify the Google account concerned; Clearcutt may need to verify account ownership. Do not send passwords or payment instrument credentials. Financial records that must be retained may be excluded from deletion.

Open the free background remover →