Supported image and short-video bytes are processed in the browser with local code, bundled models, WebAssembly, canvas, and browser media APIs. The media is not uploaded to ReForge or Aliyun.
Product-specific privacy policy
Cleanmark for Gemini
This policy explains how Cleanmark handles generated image and short-video downloads, local cleanup, Chrome permissions, locally saved settings, ReForge product services, limited operational events, Reviews, and conditional account features.
Cleanmark runs on Gemini, Google AI Studio, and Google Labs Flow and activates around explicit download actions. It does not request access to all websites or read unrelated browsing history.
Product configuration, operational events, Reviews, and any account action you choose can contact ReForge or Aliyun. Those requests do not include media bytes, prompts, chat content, or complete media URLs.
1. What Cleanmark does
Cleanmark works with supported downloads from Gemini, Google AI Studio, and Google Labs Flow. When you click a normal download control, the extension may identify the source media request, fetch the corresponding bytes from the supported page or Google media host, detect a supported visible watermark, process it locally, apply your export settings, and create a download.
User clicks Download
Supported Google media is read
Detection and cleanup run locally
Quality gate checks the result
Cleaned or original file is saved
If detection confidence is low, the quality gate rejects the processed output, or local video processing fails, Cleanmark is designed to keep or restore the original file rather than silently save a damaged replacement.
2. Media, page, and download data
2.1 Supported media bytes
- Cleanmark can read image or video bytes associated with a download you initiate on a supported Google page.
-
Source bytes may come from the current page, a same-page
blob:URL, an imagedata:URL, or an allow-listed Google or Googleusercontent HTTPS host. - Image pixels and supported video frames are processed in browser memory. Bundled ONNX models and ONNX Runtime WebAssembly are loaded from the extension package.
- Cleanmark does not send those image bytes, video bytes, frames, or manually selected local files to ReForge, Aliyun, or an AI cleanup service.
2.2 Download and tab metadata
- The extension may use a download URL, MIME type, filename, download ID, originating tab ID, and recent pending filename to identify a supported Flow download and apply your chosen filename or Downloads subfolder.
- The popup checks the active tab URL to tell you whether the current page is Gemini, AI Studio, or Flow.
- This metadata is used for the immediate download workflow and is not assembled into a browsing-history profile.
2.3 Page content Cleanmark does not collect
- Cleanmark does not intentionally read or transmit your prompts, chat messages, generated text, form fields, private messages, bookmarks, cookies, or passwords entered into Google pages.
- It does not request the Chrome history, cookies, bookmarks, webRequest, identity, clipboard, or all-sites permissions.
- If account controls are enabled in the future, credentials entered into Cleanmark’s own account form are handled as described in Section 6 and are separate from page content.
2.4 Manual Cleanup
When you choose or drop a PNG, JPEG, or WebP into Manual Cleanup, the file is read into local browser memory and canvas. The before preview, processed canvas, brush edits, and exported result remain on the device. Cleanmark does not upload that file.
3. Data stored locally
| Local data | Purpose | Storage and removal |
|---|---|---|
| Enable switches, output format, canvas preset, custom dimensions, folder, language | Remember the export and interface settings you selected | chrome.storage.local until changed, cleared, or extension data is removed |
| Total, daily, image, and video cleanup counts; installation time | Show your local success counters and control when a Review prompt may appear | chrome.storage.local until cleared or extension data is removed |
| Latest result state, media type, time, reason, dimensions, progress, configuration key, match score | Show recent status and support local diagnostics | chrome.storage.local; replaced by later results or removed with extension data |
| SDK installation UUID, install time, device ID, encrypted product configuration cache, Review state | Product configuration, feature access, operational event continuity, and Review eligibility | chrome.storage.local until cleared or extension data is removed |
| Authentication token, account email, product ID, timestamp, cached subscription state | Used only if account controls are enabled and you sign in or complete payment auto-login | chrome.storage.local; logout clears auth, cached user data, and cached product configuration |
Cleanmark uses local storage rather than Chrome Sync for its own settings and counters. Uninstalling normally removes extension-local storage, subject to Chrome’s platform behavior and any browser backup or enterprise policy outside our control.
4. Network requests and service providers
4.1 Google pages and media infrastructure
- The extension may request the source media from the supported Google page or Google media host to complete the download and local processing you requested.
- These requests may use your existing Google session credentials and are processed by Google under Google’s own terms and privacy practices.
- Cleanmark does not operate or control Google’s retention of the original generated content or request logs.
4.2 ReForge product API
-
https://api.reforgeextensions.comprovides product configuration, announcements, feature-access configuration, account services, subscription state, checkout, customer portal, and payment-success auto-login support. - Configuration requests can involve product ID, extension ID, extension version, installation or device identifiers, and cached configuration state.
- The current product configuration is free and does not require an account for local cleanup. Conditional account and payment behavior is described in Section 6.
- Cleanmark does not call the SDK’s AI generation method and does not send media, prompts, or generated content to the ReForge API.
4.3 Aliyun Log Service operational events
When operational logging is enabled in the bundled SDK, limited events are sent to a product-specific Aliyun Log Service endpoint. The audited build can send:
- installation and extension update events, including a previous version on update;
- user-triggered cleanup success, failure, or skipped results with fields such as media type, output format, local configuration key, renderer mode, processing duration, and reason category;
- user-triggered setting changes and manual exports;
- Review prompt shown, dismissed, rating, store redirect, and optional low-rating reason.
Automatic event fields can include event time, category, operation, anonymous installation UUID, install time, extension version, operating-system type, browser type, language, product ID, plan category, and account email if you are signed in. The event payload does not include media bytes, prompts, chats, generated text, page body text, or complete media URLs.
4.4 Chrome Web Store Reviews
- After at least five successful cleanups and three days since installation, opening the popup may show a Review prompt.
- A four- or five-star choice can open the Chrome Web Store review page for this extension.
- A one- to three-star choice can ask for an optional explanation. If submitted, the star count and reason of up to 500 characters are sent as an operational event. The SDK does not keep the reason in local Review state.
4.5 Website and support providers
- Visiting this privacy page may cause website hosting, DNS, TLS, caching, and security providers such as Cloudflare to process standard request metadata.
- If you email support, our email routing and mailbox providers process your address, message, attachments, and routing metadata so we can respond.
5. Chrome permissions
| Permission or host | Why it is requested | Data boundary |
|---|---|---|
storage |
Save settings, counters, latest result, SDK state, and conditional account state | Local browser storage; no Chrome Sync used by Cleanmark’s own state helpers |
downloads |
Apply filenames and folders and safely replace supported Flow video downloads | Uses download URL, MIME, filename, ID, and originating tab context; does not scan file contents from download history |
alarms |
Run one daily local counter-maintenance task | No webpage content is read by the alarm |
tabs |
Identify a supported active page, open extension or Gemini pages, and contact the originating Flow tab | Uses active URL and tab ID for the feature; does not build unrelated browsing history |
| Gemini, AI Studio, and Google Labs Flow | Run the explicit download detection and local processing bridge | Limited to the listed Google products rather than all websites |
| Google media hosts | Read the source media selected for download | Media is processed locally and is not forwarded to ReForge or Aliyun |
| ReForge API | Product configuration, Reviews support, and conditional account/payment services | Does not receive image or video bytes from the cleanup pipeline |
6. Conditional account and payment features
Cleanmark’s current product configuration is free, and the normal local cleanup workflow does not require an account. The audited code includes account and subscription controls that remain hidden unless ReForge product configuration marks the product as paid.
If those controls are enabled and you explicitly use them:
- email and password are submitted over HTTPS to the ReForge API for login; the audited extension code does not write the password to extension storage;
- email, one-time code, challenge ID, device ID, and product ID can be submitted for passwordless login;
- email can be submitted to request a password reset or create a checkout session;
- authentication token, account email, product ID, timestamp, device ID, and cached subscription state can be kept in local extension storage;
- checkout and customer-portal pages open in a normal browser tab and may be handled by ReForge and its configured payment provider under their applicable policies.
Logging out clears the locally stored authentication state, cached user information, and cached product configuration. Review state and anonymous install identity remain until extension storage is cleared.
7. Retention
- Local settings, counters, result status, SDK identifiers, and Review state remain until replaced, reset, cleared, or removed with extension data.
- Conditional authentication state remains until logout, storage clearing, or extension removal.
- Temporary media buffers, decoded frames, canvas pixels, and object URLs are intended to exist only while processing, previewing, or exporting the requested media.
- Server-side configuration, account, security, payment, and operational logs are retained only as reasonably necessary to provide the service, prevent abuse, resolve incidents, handle support, meet legal obligations, or maintain aggregate operational records. The extension code does not define a fixed provider retention period.
- Support email records may be retained for up to 24 months after the last support interaction unless a longer period is necessary for an unresolved dispute or legal obligation.
8. Chrome Web Store Limited Use
Cleanmark’s use of information received from Google APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
- Data is used only to provide or improve the user-facing Cleanmark workflow.
- We do not sell extension user data.
- We do not use extension user data for personalized advertising, retargeting, data brokerage, credit evaluation, lending, or unrelated profiling.
- Human access is limited to support, security, abuse prevention, legal compliance, or actions you explicitly request and is not used to inspect generated media as part of the normal local cleanup workflow.
9. Security and data minimization
- Network requests use HTTPS/TLS.
- Media URLs are restricted to local blob or image data URLs and allow-listed Google or Googleusercontent HTTPS hosts.
- Downloads subfolders and filenames are normalized to remove path traversal and invalid characters.
- Web-accessible models, WASM, and the Reviews icon are exposed only to the supported Google products rather than all websites.
- Operational event transmission is non-blocking and does not control whether local media processing succeeds.
No security measure can guarantee absolute protection. We review the extension’s permissions, hosts, dependency behavior, and data flow and aim to minimize each category of data used.
10. Your choices and controls
- Turn Cleanmark protection or video cleanup off from the popup or Settings.
- Change output format, canvas preset, folder, dimensions, and language at any time.
- Use the original file when the quality fallback activates, or use Manual Cleanup for a local second pass.
- Decline or dismiss the Review prompt.
- Log out if conditional account features are enabled and you have signed in.
- Disable or uninstall the extension and clear its site or extension storage through Chrome.
- Contact [email protected] to request access, correction, or deletion of support or account data that ReForge controls, subject to applicable law and necessary security verification.
11. Children
Cleanmark is not directed to children under 13, and we do not knowingly collect personal information from children through this extension. Contact us if you believe a child has provided account or support information so we can review the request.
12. International processing
ReForge, website infrastructure providers, email providers, Aliyun, Google, and any configured payment provider may process the limited service data described above in countries other than your own, subject to their infrastructure and applicable law.
13. Changes to this policy
We may update this policy if Cleanmark’s permissions, supported Google products, media pipeline, operational events, account features, service providers, or legal obligations change. The updated date at the top of this page will be revised when the policy changes.
14. Contact
ReForge Extensions controls the Cleanmark-specific product services described in this policy. Questions, privacy requests, or support requests can be sent to [email protected].
Product page: https://reforgeextensions.com/extension/cleanmark-for-gemini
Static review URL: https://reforgeextensions.com/privacy/cleanmark-for-gemini/