1. Purpose of this disclaimer
AI Metadata Cleaning is being developed as a toolkit for inspecting and removing supported metadata from digital files. This disclaimer explains what metadata removal can and cannot establish, why results may vary between file formats, and what visitors should consider before relying on a processed file.
The information on this website is intended to explain technical concepts and the planned product. It should not be treated as a guarantee that every file, metadata field or privacy risk can be handled by a single cleaning operation.
Read this document together with our Terms of Service, Privacy Policy and Acceptable Use Policy.
2. Current development status
As of 6 November 2026, AI Metadata Cleaning is a pre-launch project. The website presents information about planned metadata-cleaning tools, but operational file uploads and metadata-processing features are not yet available.
Image, video, PDF and camera RAW processing are development objectives. Their actual support, processing methods, size limits and verification capabilities will need to be tested before they are presented as available services.
A page describing a planned feature does not mean that the feature has passed technical testing or is ready for production. Visitors should not rely on the current website as a working file-cleaning service.
3. Understanding digital file metadata
Metadata is information associated with a digital file. Some metadata describes how, when or where a file was created. Other fields identify an author, editing application, device, document properties or other characteristics.
Depending on the format and software used, metadata may be stored in different places within a file. Examples include:
- EXIF information associated with digital photographs and camera capture details.
- GPS coordinates that may reveal where a photograph was captured.
- IPTC fields containing descriptions, author information and copyright details.
- XMP properties containing descriptive and editing-related information.
- PDF document properties and embedded metadata streams.
- Video container and stream information, including format-dependent technical properties.
These categories are not interchangeable. A method that handles EXIF information in a JPEG image may not handle metadata inside a PDF, video container or camera RAW file.
4. Metadata removal is not the same as anonymization
Removing supported metadata can reduce information stored inside a file, but it does not automatically make the file anonymous.
Information identifying a person may remain visible in the content itself. Examples include:
- Faces, name badges, vehicle registration plates and identifying documents visible in photographs.
- Addresses, account numbers or signatures visible in scanned documents.
- Spoken names, street signs or location details in video and audio content.
- Distinctive backgrounds and other details that may help identify a person or location.
- Copies of the original file or information stored in separate files and backups.
A file without supported EXIF or GPS fields may still contain identifying information. Metadata cleaning should therefore be considered one part of a broader privacy review rather than a guarantee of anonymity.
5. EXIF and GPS removal limitations
EXIF metadata can contain camera model information, capture settings, timestamps, orientation details and, where recorded, GPS coordinates.
GPS metadata deserves particular attention because location coordinates can reveal a place associated with a photograph. However, not every image contains GPS information, and not every application stores location data in the same way.
A photograph may also contain related information in XMP fields, embedded thumbnails, application-specific blocks or other format-dependent structures.
A claim that GPS information has been removed should be based on the actual output inspection method and the file format being handled. Checking one metadata field is not proof that all location-related information has disappeared.
6. Supported file formats and compatibility
Metadata behavior differs across JPEG, PNG, WebP, HEIC, TIFF, video formats, PDF documents and camera RAW files. Even files with the same extension may contain different metadata structures depending on the application or device that created them.
The future cleaning tools will publish their tested format support and relevant restrictions. A file extension alone should not be treated as proof that a file is valid or supported.
Compatibility may depend on:
- The actual file format and its internal structure.
- The metadata standard and fields present in the file.
- The software or device used to create or edit the file.
- The file size, dimensions and processing requirements.
- Encryption, corruption or other format restrictions.
- The availability of a safe method for rewriting the file.
Unsupported or malformed files may not be processable. Format-specific limitations will need to be explained rather than hidden behind a generic successful result.
7. Re-encoding and changes to file quality
Some metadata-cleaning methods rewrite or re-encode a file. This can change more than the metadata.
Depending on the file format and processing method, re-encoding may affect:
- Image quality, compression and color representation.
- Video or audio encoding parameters.
- File size and internal structure.
- Embedded profiles, thumbnails or auxiliary information.
- Features that depend on the original file representation.
A method that preserves the visible appearance of an image does not necessarily preserve every underlying technical property. Where output quality or file fidelity matters, the result should be checked against the original.
8. PDF documents and digital signatures
PDF files may contain document properties, embedded XMP information, attachments, annotations, embedded objects and other internal structures.
Editing or rewriting a signed PDF can invalidate its digital signature or change the document in a way that affects signature validation.
A metadata-cleaning operation should not be assumed to preserve the validity of a digital signature. Anyone who depends on a signed document should verify the result using appropriate PDF signature-validation software.
Some PDFs also contain visible personal or confidential information. Removing document properties does not remove information displayed on the pages.
9. Video and camera RAW processing
Video files
Video files can contain metadata at container, stream and track levels. Depending on the format, relevant information may include recording dates, device information, location fields, software details or technical encoding properties.
Rewriting a video container or stream can introduce compatibility or quality changes. A video that plays successfully is not necessarily a video from which all identifying metadata has been removed.
Camera RAW files
Camera RAW formats vary between manufacturers and camera models. They can contain proprietary structures, previews, embedded thumbnails, capture information and other metadata.
Preserving RAW image data while changing metadata requires format-specific handling and testing. A general image re-encoding method should not be assumed to preserve a RAW file correctly.
10. Output verification and inspection
A trustworthy metadata-cleaning workflow should inspect the generated output rather than rely only on the fact that a processing operation completed.
Future verification features are intended to check supported metadata fields after processing and communicate the result accurately.
Verification still has technical limits. Two metadata inspection tools may interpret a file differently, and a parser may not recognize every proprietary or uncommon metadata structure.
Consequently, a successful inspection of supported fields should not be described as absolute proof that every possible identifying element has been eliminated.
11. No security or malware certification
A metadata cleaner is not automatically a malware scanner, antivirus product, file-integrity certification system or security audit service.
Metadata removal does not establish that a file is safe to open, execute, download, distribute or send to another person.
File validation and secure processing are important requirements for the planned service, but visitors should use appropriate security software and handling procedures when working with files from untrusted sources.
Do not use a successful metadata-cleaning result as evidence that the file contains no malicious content.
12. Keep an original copy of important files
Files may be important for personal, legal, professional or archival reasons. Before applying a metadata-cleaning operation to an important file, retain a separate original copy.
A cleaned output may differ from the source because of format conversion, metadata rewriting, compression, unsupported fields or processing errors.
Do not rely on a processed copy as the only copy of an important document, photograph, recording or archive.
13. Third-party software and services
Future versions of the product may use third-party software or infrastructure to process files, deliver downloads or provide supporting functionality.
The behavior of an external library, operating system, browser or file-format implementation can affect processing results. The project will need to test its supported workflows and review the relevant provider documentation before making specific compatibility claims.
External services may have their own terms and privacy practices. See the Privacy Policy for the project status and information-handling details.
14. No professional advice
Explanations about EXIF, GPS metadata, digital privacy, file formats and metadata removal are general technical information. They are not legal advice, cybersecurity certification, forensic advice or professional assurance that a particular file is safe to disclose.
If a file is subject to legal, regulatory, contractual, evidentiary or professional requirements, seek advice from a qualified person who can assess the specific circumstances.
15. Website information and availability
Product descriptions, planned features, technical explanations and availability information may change during development.
Although we aim to provide useful and accurate information, the website may contain incomplete descriptions, technical errors or material that becomes outdated as the product evolves.
The website is not a guarantee that a particular feature will be available on a specific date or support every file format.
The conditions for accessing the website are explained further in the Terms of Service.
16. Limitation of liability
To the extent permitted by applicable law, information on this website is provided without a guarantee that it will always be complete, uninterrupted, error-free or suitable for every particular purpose.
Nothing in this disclaimer is intended to remove consumer rights or exclude liability where applicable law does not permit that exclusion.
The enforceability and final wording of any liability limitation must be reviewed after the legal identity of the operator and the applicable jurisdiction have been established.
17. Changes to this disclaimer
This document may be revised as the image, video, PDF and camera RAW tools are implemented and tested. New processing methods or supported metadata categories may introduce additional limitations that need to be explained.
Material changes will be reflected in an updated revision date. Visitors should review the current version when relying on information about a particular feature.
18. Related product and legal information
Explore the metadata-cleaning tools overview for the product areas currently under development.
The Acceptable Use Policy explains restrictions on misuse of the planned tools. The Privacy Policy explains the current state of information handling, while the Terms of Service describe the conditions for using the website.
The Cookie Policy describes website cookies and similar browser technologies.