Plain-English privacy

The server never meets your file.

MetadataView is a static browser tool. You select a file; JavaScript in this tab reads it. There is no account, upload route, cloud bucket, or file history.

01

How files are processed

Supported files are read from browser memory. Parsing runs in a Web Worker when practical. Image cleanup uses browser image decoding and Canvas re-encoding. C2PA verification loads the official WebAssembly library only on its tool page.

No selected file or extracted metadata is sent to a MetadataView server.

02

What stays in memory

The selected file and result live only in the current page session. We do not put them in localStorage, a URL, IndexedDB, or a cookie. Refresh or close the tab and that state disappears.

Temporary Object URLs created for downloads are revoked after use. Workers terminate when a task finishes or the page unmounts.

03

Analytics

This MVP ships without analytics. If privacy-preserving traffic measurement is added later, it will not receive uploaded files, file bytes, metadata values, prompts, filenames, or local paths.

04

Cookies and future ads

The MVP does not require an account or first-party session cookie. Future third-party advertising may use its own cookies under its own policy, but browser isolation does not grant an ad script access to the file input or parsed result.

05

The honest limit

Local processing protects the transfer path. It does not make the visible content anonymous, prove metadata is true, or detect malicious files. Do not open files you do not trust merely because the parser is local.