Content Removal Policy

1. Requests covered

You may request deletion of your own content or report privacy violations, unauthorized likeness use, impersonation, trademark infringement, illegal or harmful material, or other breaches of the Acceptable Use Policy. This policy covers content, records, and access points controlled by Flux2.Cloud.

For copyright requests, provide the rights information described in the Copyright & Takedown Policy. For access, correction, personal information deletion, or account closure, see the Privacy Policy. Send any of these requests to support@flux2.cloud; we will apply the relevant process.

2. How to request removal

Use available deletion controls in the product or email us with “Content removal request” in the subject. Removing guest history from your browser does not immediately delete third-party copies or every server-side record; contact support for further action.

• Provide the specific URL, image link, or task ID and enough information to locate the content.
• Explain the action requested, your reason for removal or restriction, and the relevant rights or policy basis.
• Provide a contact email, your connection to the content or rights holder, and necessary evidence. Explain your authority if you act for someone else.

We may proportionately verify identity or authorization to prevent unauthorized deletion of your content. Share only information needed for the request. Do not send passwords, verification codes, full payment card information, or unrelated sensitive identity documents. If further identity evidence is needed, we will explain why and how to provide it.

3. Review, notice, and appeals

We review the grounds, evidence, risk, and applicable law. We may ask for missing information or restrict access while investigating a risk. Actions may include deletion, blocking, limiting sharing, account restrictions, or other proportionate measures. Timing depends on complexity and legal requirements; we do not promise completion of every request within 24 hours.

Where law and safety permit, we inform the requester and affected user of the outcome and main reasons. To appeal, reply to the original email with the task ID, your reasons, and further evidence. We will review and communicate the result. Legal complaint, court, and applicable copyright counter-notice routes remain available. Necessary request materials may be shared with affected parties as described in the Privacy Policy.

4. Scope of deletion and retention exceptions

When removal is warranted, we address active records, image objects, and access points under our control and allow relevant caches or backups to expire or be removed through their cleanup cycles. Limited records may need to be retained with restricted use for legal duties, transaction recordkeeping, security investigations, or disputes.

Browser caches, backups, upstream provider copies, and material others have downloaded or reposted on independent platforms may not be immediately or directly removable by us. We will explain the practical scope and, where appropriate, help direct requests to relevant providers. We cannot guarantee immediate, permanent removal of every copy worldwide. Before deleting your own content, save any copy you still need and are entitled to keep.

5. Billing, subscriptions, and updates

Content deletion does not itself cancel automatic renewal or issue a refund. Submit billing requests separately under the Refund & Cancellation Policy. Material policy updates follow the Terms of Service and do not limit applicable legal rights.