Privacy Policy

1. Core privacy summary

The current version of this tool processes image cleanup entirely in your browser. Your selected image is not uploaded to a remote cleanup server, and you do not need to create an account to use the tool.

2. Image handling

When you choose an image, the file is read by your browser so the page can preview it, attempt visible-mark cleanup, and let you download a result. In the current v1 flow, this processing stays on your device.

• No image upload: the site does not send your selected image to a cleanup API in v1.
• No account requirement: the core tool works without sign-up or login.
• Visible-mark scope only: the tool targets visible Gemini-style corner marks and similar small overlays.

3. Temporary browser state

To make previews and downloads work, the current frontend may keep temporary in-memory state during your browser session. That can include object URLs for the source image, the cleaned result, and temporary selection state while you use the page.

• Current frontend behavior: the shipped frontend does not intentionally store selected images in localStorage, sessionStorage, or IndexedDB.
• Session lifetime: temporary state is expected to clear when you reset the tool, reload the page, or close the tab.

4. Site delivery and basic technical data

Even when image cleanup itself stays local, the site still has to be delivered to your browser. When that happens, the web server, hosting platform, CDN, or similar delivery layer may receive normal request information such as your IP address, user agent, referrer, and request time.

This kind of technical request data is separate from your image content. It is typically used to deliver pages, handle security, and maintain service stability.

5. Third-party requests

In the current shipped frontend, the main site assets needed for the core tool are served from the site itself. The current v1 cleanup flow does not require sending your selected image to Google or to a third-party cleanup provider.

If the delivery stack, embedded assets, analytics setup, or third-party integrations change later, this policy should be updated before those changes are enabled.

6. Cookies and analytics

The current shipped frontend does not require login cookies for the core cleanup flow and does not currently include Google Analytics 4 or another analytics script in the frontend code shipped with this site.

7. Sensitive content and your choices

Because the tool works on files you select yourself, you should only use it on content you are comfortable processing in your current browser environment and only on material you own or are allowed to modify.

8. Contact

For privacy requests or questions about this policy, use: 2296744453m@gmail.com.

For legal complaints or trademark-related notices, use: 2296744453m@gmail.com.

9. Policy updates

This policy may change if the product architecture, hosting setup, analytics setup, or feedback flow changes. When that happens, the updated version should be published on this page with a new updated date.