AI Metadata Cleaner

Legal information

Last updated: 6 November 2026

Acceptable Use Policy

This policy explains the activities that will be permitted and prohibited when using AI Metadata Cleaning. It addresses responsible use of file metadata tools, future uploads, automated processing and developer services.

1. Purpose and scope

AI Metadata Cleaning is being developed as a toolkit for inspecting and removing supported metadata from digital files. This Acceptable Use Policy establishes the conduct expected from people who visit the website and, when available, use its processing and developer features.

These rules are intended to protect visitors, file owners, the infrastructure supporting the product and people whose information may be contained in digital files.

This policy should be read with the Terms of Service and Privacy Policy.

2. Current service availability

As of 6 November 2026, the product is still under development. The website currently provides informational pages and does not offer operational file uploads, metadata processing, registered accounts, public API access or MCP tools.

The restrictions in this policy describe the standards intended for the current website and the future services. They do not mean that file processing or account enforcement systems are already operational.

Before these services launch, the applicable rules will be reviewed against the actual features, technical safeguards and available enforcement procedures.

3. General responsibilities

Anyone using the website is expected to act lawfully, respect the rights of others and avoid conduct that interferes with the availability or security of the service.

In particular, you must not:

  • Use the website to violate applicable laws or regulations.
  • Interfere with another person or organization using the service.
  • Attempt to access systems, accounts, data or resources without authorization.
  • Misrepresent your identity, ownership or permission to handle a file.
  • Circumvent technical restrictions or security protections.
  • Disrupt the normal operation of the website or its infrastructure.

4. Rules for future file uploads

File upload and metadata-cleaning functionality is not currently available. When it is introduced, users will be responsible for ensuring that they are legally entitled to submit the files they choose to process.

You must not submit a file when doing so would violate another person or organization rights, confidentiality obligations, intellectual property rights or applicable privacy requirements.

Files must be submitted with appropriate authority

Before using a future cleaning tool, you should have ownership of the file or permission from the relevant rights holder. Possessing a copy of a photograph, document or video does not automatically give you permission to disregard another person rights or contractual restrictions.

Prohibited file submissions

Subject to applicable law and the actual technical capabilities of the service, the following activities will be prohibited:

  • Submitting files obtained through unauthorized access.
  • Using the service to conceal evidence of illegal activity.
  • Processing files to facilitate fraud, identity theft or deception.
  • Submitting content that infringes copyright or other intellectual property rights without authorization.
  • Using the service to facilitate harassment, stalking or unauthorized disclosure of personal information.
  • Attempting to distribute malicious software or harmful files through the service.

5. Malware and harmful files

A future metadata-cleaning service will need to accept files from different devices and applications. Uploaded files must therefore be treated as untrusted input.

You must not attempt to use the service to store, transmit, distribute or deliver malware or other harmful software.

Prohibited examples include:

  • Files intended to execute malicious code on another system.
  • Trojanized or deliberately harmful documents.
  • Files intended to exploit vulnerabilities in processing tools.
  • Files designed to exhaust processing resources or crash workers.
  • Files intended to compromise another user device or account.

Changing file metadata does not make malicious content safe or authorized. Users must not treat a metadata cleaner as a malware removal or file-security certification service.

6. Privacy and personal information

Digital images, videos and documents can contain personal information, including location coordinates, author details, identification information and other information about individuals.

You must have an appropriate legal basis or authorization when handling personal information belonging to another person.

You must not use the future service to:

  • Remove identifying information to facilitate stalking or abuse.
  • Process personal documents without appropriate authority.
  • Expose confidential information belonging to another person.
  • Circumvent privacy restrictions or contractual protections.
  • Use file processing to facilitate discrimination, intimidation or harassment.

Metadata removal can reduce certain forms of information disclosure, but it does not make every file anonymous or remove all personal information from its visible content.

For information about how the project intends to handle personal information, see the Privacy Policy.

7. Copyright and intellectual property

You must respect copyright, trademarks, confidential information and other intellectual property rights when using the service.

The future tools must not be used as part of a process intended to disguise unauthorized copying, misrepresent authorship, falsify ownership information or remove attribution in violation of another person rights.

For example, removing an author or copyright field does not transfer ownership of a photograph, document or other protected work.

You remain responsible for obtaining any permissions needed to handle and distribute the files you submit.

8. Prohibited security activity

The security of the application and its processing infrastructure is important. You must not attempt to compromise or interfere with those systems.

Prohibited activities include:

  • Unauthorized vulnerability exploitation or access attempts.
  • Credential theft, phishing or password attacks.
  • Attempting to access another user data.
  • Circumventing authentication, permissions or usage limits.
  • Introducing malicious payloads into processing requests.
  • Interfering with the availability of the website or API.

Security research must not involve unauthorized access, disruption or exposure of personal information. An authorized testing process, if introduced, will have its own defined scope and conditions.

9. Automated access and resource abuse

Automated access can place substantial demands on a website and its processing infrastructure. Future usage limits and automated access conditions will be published with the relevant service.

You must not use scripts, bots or automation to:

  • Generate requests designed to overload the service.
  • Evade documented request or processing limits.
  • Create excessive or deceptive account activity.
  • Obtain free usage beyond permitted limits through abuse.
  • Circumvent rate limits or technical protections.
  • Interfere with other users access to the service.

Normal browsing and reasonable automated use permitted by the published service documentation will remain distinguishable from abusive traffic.

10. API and MCP usage rules

A public REST API and Model Context Protocol (MCP) integration are planned but are not currently available.

When these developer services are released, their documentation will define authentication requirements, permitted operations, request limits and usage restrictions.

Future API and MCP users must not:

  • Share, sell or expose API credentials without authorization.
  • Attempt to bypass API authentication or permission checks.
  • Use another customer credentials or account without permission.
  • Circumvent request limits, plan allowances or processing quotas.
  • Use integrations to facilitate prohibited file submissions.
  • Misrepresent automated processing results to other people.

Separate developer terms may be published when API access becomes operational.

11. Account and subscription misuse

User accounts, paid plans and subscriptions have not yet been introduced.

When accounts become available, users will be expected to protect their login credentials and provide accurate information where required for account operation or billing.

Future account restrictions may apply to activities such as:

  • Sharing paid account access in violation of plan conditions.
  • Using fraudulent payment methods.
  • Abusing introductory or promotional allowances.
  • Creating accounts to evade a previous service restriction.
  • Using another person account without permission.

Any account-specific enforcement process will be documented in the applicable account and subscription terms.

12. Automated decisions and file-cleaning results

A future cleaning tool may analyze file formats and metadata fields to determine which operations can be applied.

You must not knowingly misrepresent the output of such a tool, claim that a file was verified when it was not, or present an incomplete metadata-removal result as a guarantee that all identifying information has been removed.

The intended product will distinguish supported metadata, partially processed files, unsupported formats and results that cannot be verified.

Technical limitations are explained further in the Terms of Service and will be covered in more detail by the separate Disclaimer when that page is published.

13. Reporting suspected misuse

If you become aware of activity that appears to violate this policy, compromise the service or misuse another person information, the matter should be reported through an official contact channel.

A dedicated abuse-reporting email and response procedure have not yet been established for this project. These must be published before the upload service, user accounts or developer integrations are activated.

A report should include only the information reasonably needed to explain the concern. Do not send passwords, payment credentials or unrelated confidential files.

14. Enforcement and restrictions

Where the service becomes operational, reasonable action may be taken to protect its users and infrastructure when there is credible evidence of prohibited activity.

Depending on the circumstances and the actual service capabilities, possible responses may include:

  • Rejecting an unsupported or harmful processing request.
  • Applying technical request restrictions.
  • Temporarily limiting access while a security concern is investigated.
  • Suspending an affected account where justified.
  • Taking action required by law or a valid legal request.

Any enforcement measures must be proportionate to the issue, consistent with applicable law and supported by the relevant operational procedures.

These are the intended enforcement standards. An active moderation or account-enforcement system is not currently part of the pre-launch website.

15. Changes to this policy

This Acceptable Use Policy may be revised as image processing, video cleaning, PDF handling, RAW file support, API access and MCP integrations are developed.

New restrictions may be needed when technical features introduce different security or misuse risks. Changes should be reflected in the published policy with an updated revision date.

16. Contact and operator information

The legal operator name, registered business address and official abuse-reporting contact have not yet been confirmed for publication.

These details must be completed before this policy is treated as the final public agreement for file uploads, customer accounts or developer services.

17. Related policies and product information

Read the Privacy Policy for information about personal data and the Terms of Service for the general conditions of using the website.

The Cookie Policy explains website cookies and related technologies. You can also visit the metadata-cleaning tools overview to learn about the product features under development.