No Trace Share
Clean a File
Menu
No Trace Share / Metadata Glossary
PLAIN-ENGLISH METADATA GUIDE

What can this metadata actually reveal?

No Trace Share gives a short explanation beside each finding. This glossary goes further so you can understand what a field means before deciding whether to keep, replace or remove it.

Quick index

AI Traces

AI Traces are explicit records embedded in a file that may describe AI generation or editing, such as prompts, generation parameters, workflow fields, generator names or AI-related provenance actions. No Trace Share inspects supported embedded records; it does not look at the pixels and guess whether an image is AI-generated.

These records can reveal how an asset was created, which tools were used, or parts of a generation workflow. Some multi-tool workflows can retain traces from more than one stage.

Content Credentials / C2PA

Content Credentials are provenance records designed to describe origin and editing history. They can contain manifests, actions, software names, identifiers, authors, certificate text and ingredient relationships.

Their presence alone does not prove that visible media was generated by AI. No Trace Share reports supported records but does not certify signature validity, trust or authenticity.

GPS & location metadata

Latitude and longitude can reveal where a photo was captured. Depending on accuracy, that may expose a home, workplace, school, hotel, medical facility or another location the sender never intended to disclose.

Related location metadata can include altitude, direction, speed, destination coordinates and named places. Even when each field seems harmless by itself, several fields together can provide substantially more context.

Identity and ownership

Author, artist, owner, credit, source, contact and copyright fields can identify a person or organization connected with a file. Some are deliberately added for attribution; others may be inherited automatically from software or templates.

No Trace Share treats these as information the user should consciously choose to share rather than assume is invisible.

Device information and identifiers

Camera or phone models reveal the device family used. Serial numbers, unique image IDs, host names and manufacturer-specific blocks can go further and may help correlate multiple files with the same equipment or workflow.

A model name alone does not identify a person, but device information can become more revealing when combined with dates, locations, account names or repeated files.

Dates, times and history

Capture, modification, digitization and GPS timestamps can reveal when a file was created or processed. Time-zone offsets may add geographic context. Repeated files can expose routines, travel dates or a sequence of events.

Not every date refers to the visible content. For example, a color-profile creation date belongs to the profile itself rather than necessarily to the photo.

Software and workflow metadata

Software fields can identify applications, exporters, generators or services used to create or modify a file. Editing history can reveal more than one step of a workflow.

This information may be useful for provenance, but it can also contribute to correlation or reveal tools a user did not intend to disclose.

Descriptions, comments and rights

Titles, captions, descriptions, comments, keywords and rights fields can contain names, places, client information, project details or other text that is not visible when someone simply looks at the image or document.

Some rights metadata is intentionally public. No Trace Share exposes it so the user can make that decision knowingly.

Hidden data and identifiers

Files may carry document IDs, custom metadata, embedded thumbnails, trailing bytes or application-specific structures. These can help link files, preserve previews, or carry information outside the visible content.

No Trace Share removes supported structures where safe and clearly reports known retained structures or format limitations.

Color profiles

An ICC color profile helps software display colors correctly. The useful color-transform data can sit beside profile metadata such as software identifiers, manufacturer, model, creator, profile ID, creation date, description and copyright/provider text.

Automatic Clean sanitizes supported JPEG, PNG, WebP and compatible HEIF/HEIC profiles: it keeps the validated color transform while neutralizing supported identifying profile metadata. It does not replace those values with a No Trace Share identifier.

When a copy can be safely created and checked but its profile cannot be sanitized, No Trace Share retains the original profile and flags its remaining metadata for review. You can also remove the whole profile, which may change color-managed appearance. HEIF/HEIC supports validated RGB and Gray matrix/TRC ICC profiles in supported still-image container layouts. Other color-profile structures can require review or an explicit choice when a copy cannot be safely created. Green marks these as technical findings; it does not guarantee that a preserved profile contains no identifiers. Retained transform data is not certified anonymous.

READY TO CHECK A FILE?

Inspect first. Decide with context.

Your selected files stay on your device while supported inspection and cleaning run in the browser.

Open the cleaner