AI Metadata Cleaner

Legal information

Last updated: 6 November 2026

Privacy Policy

This policy explains how information may be handled when you visit AI Metadata Cleaning. It distinguishes the website currently available from file-processing and account features that are still being developed.

1. Who this policy applies to

This Privacy Policy applies to visitors of the AI Metadata Cleaning website and describes the information associated with using the website in its current development stage.

The legal name of the individual or entity operating this project, its registered business address, and its privacy contact details have not yet been confirmed for publication. These details must be added before the service is opened to the public.

2. Current status of the service

AI Metadata Cleaning is currently being developed. The present website provides product information and navigation. It does not currently provide a functioning file-upload or metadata-cleaning service.

User registration, customer accounts, paid subscriptions, public API access, and MCP integrations are also not active.

This distinction matters. We do not claim to receive, inspect, clean, store, or delete uploaded files through features that have not yet been implemented.

3. Information that may be processed when you visit

Visiting a website can generate ordinary technical information needed to deliver pages and maintain the hosting infrastructure. Depending on the eventual hosting configuration, this information may include:

  • Your IP address.
  • The date and time of a request.
  • The page or resource requested.
  • Your browser type and version.
  • Your operating system and device information.
  • Referring page information, where provided by your browser.
  • Technical error and diagnostic information.

These details are commonly available in web-server or infrastructure logs. The exact information collected, the purposes for processing it, the hosting provider responsible, and the retention period must be verified against the production configuration before launch.

4. Information submitted directly by visitors

The current application does not provide an account-registration form, customer dashboard, file-upload form, or subscription checkout.

As a result, the current application does not have an operational account profile or file-submission database through which it collects those categories of information.

Any contact form or dedicated privacy-request channel introduced in the future will be documented here, including what information it requests and how that information is handled.

5. Files and embedded metadata

Digital files can contain information that is not immediately visible when someone opens or views them. Depending on the format, examples include:

  • EXIF camera and capture information.
  • GPS coordinates and location information.
  • IPTC author, copyright, and description fields.
  • XMP properties and editing information.
  • Document author and software properties.
  • Video container and stream metadata.
  • Other format-specific embedded information.

The current website does not accept files for inspection or processing. We therefore do not currently receive file contents or embedded metadata through an upload feature.

Before uploads are enabled, this policy must be updated to explain whether file inspection takes place in the browser or on a server, what information is read, whether original files leave the device, whether temporary copies are created, which service providers can access them, and exactly when they are deleted.

6. How information may be used

Technical request information may be used by the infrastructure delivering the website for purposes such as:

  • Delivering the requested pages and website resources.
  • Diagnosing server errors and availability problems.
  • Protecting the infrastructure against abusive traffic.
  • Investigating technical or security incidents.
  • Maintaining the reliability of the website.

Any additional purposes, such as analytics, customer support, account administration, or file-processing operations, must be described here before the corresponding functionality is activated.

7. Cookies and similar technologies

We use Google Tag Manager to understand how visitors use the site, such as which pages are visited. Tags configured in the container may set cookies (for example _ga and related Google Analytics cookies) and send information such as page views, page URL, referrer, browser type, and approximate location to Google.

The file-cleaning tools themselves run entirely in your browser and do not send your files or their contents to us or to Google.

You can opt out of Google Analytics across all websites using Google's official opt-out browser add-on, or block tracking with a browser extension or your browser's tracking protection settings.

See our separate Cookie Policy for the service-specific explanation of the cookies in use.

8. Service providers and sharing

Delivering a website may require infrastructure providers to process technical request information. The identity, role, processing location, and contractual arrangements of the providers used by the production service have not yet been finalized in this project.

Before public launch, we will identify relevant providers and explain the information they process and why they need it.

If future features introduce payment companies, email services, authentication systems, object storage, analytics, or file-processing services, their relevant privacy roles will be documented before those features are activated.

9. International data transfers

The production hosting location and the locations of any third-party processors have not yet been finalized. We cannot therefore provide a reliable list of countries in which production information may be processed.

Before launch, the operator must identify relevant international transfers and disclose the safeguards or transfer arrangements required by the applicable privacy laws.

10. Data retention and deletion

There is currently no active file-upload storage system, customer account database, or file-cleaning job history in this application. We therefore cannot give a file-retention period for an upload feature that is not operational.

Technical log retention depends on the production hosting and infrastructure configuration. That configuration must be reviewed and a specific retention period disclosed before the website launches publicly.

When file processing is introduced, the retention policy must explain the treatment of original uploads, temporary working files, cleaned outputs, downloadable copies, processing records, and backups. Deletion statements will only be made after the relevant deletion mechanisms have been implemented and tested.

11. Information security

Uploaded files can contain personal and confidential information, including precise location data. The handling of those files requires appropriate technical and organizational safeguards.

Security controls for future file processing will need to address access restrictions, file validation, isolation of processing tasks, resource limits, protected storage, secure downloads, and deletion.

Those controls are development requirements, not a claim that a finished production file-processing system is already operating. No website can guarantee that information transmitted or stored online is completely free from security risk.

12. Privacy rights and requests

Depending on your location and the privacy laws that apply, you may have rights relating to personal information. These can include requesting access, correction, deletion, restriction of processing, or information about how data is used.

The rights available to you and the response requirements depend on the relevant law and the circumstances of the processing.

A dedicated privacy contact address and the identity of the responsible data controller or operator must be published before this policy is treated as the final public privacy notice. These details have not yet been supplied for this project.

13. Children and the website

The website is a technical product intended for people who need information about file metadata and privacy. It is not designed as a service directed specifically at children.

Because account creation and file uploads are not currently active, the application does not presently operate a child-user account or file-submission system.

Any age restrictions and related safeguards for future features will be reviewed before those features become available.

14. Changes to this policy

This policy will need to change as the product moves from a development website to an operational service. For example, enabling file uploads, accounts, analytics, payments, or API access may introduce information processing that does not exist today.

We will update the policy to describe material changes accurately rather than leave outdated statements about how the service works. The date at the beginning of the policy indicates the latest recorded revision.

15. Operator and privacy contact

The legal operating name, business address, applicable jurisdiction, and privacy contact email have not yet been confirmed for publication.

These details are required before the service accepts personal information through accounts, uploads, payments, or other interactive features. This development version must not be treated as a complete legal disclosure until those details and the actual production data flows have been verified.