Skip to content
CreatorPrivacyKit

The file and the browser leak different facts

CreatorPrivacyKit started with files: EXIF, GPS, C2PA. The browser is a second layer. A clean file can still be uploaded by a browser that is easy to recognize, and a careful browser does not remove coordinates already written into a JPEG.

Updated 23 September 2026

Do the file and the browser leak the same facts?

CreatorPrivacyKit started with files: EXIF, GPS, C2PA. The browser is a second layer. A clean file can still be uploaded by a browser that is easy to recognize, and a careful browser does not remove coordinates already written into a JPEG.

C2PA: Coalition for Content Provenance and Authenticity; C2PA specification 2.4

Last updated

What sits in the file

EXIF can hold camera details and time. GPS tags can hold where the camera was. C2PA is a signed claim, not a location log.

File records are a different layer: Metadata Cleaner. That work happens on the file bytes.

What sits in the browser

Canvas, WebGL, audio, fonts, screen, language, and time zone are readable from script without opening the file.

The grouped report is the browser privacy check. Those probes do not read your photo.

What to check before you post

If the worry is the place the photo was taken, inspect the file. If the worry is the browser being recognized later, inspect the browser.

Doing one and skipping the other leaves the other layer as it was.

Common questions

Does Metadata Cleaner change my fingerprint?
No. It edits the file you give it. It does not reconfigure the browser.
Does the fingerprint test upload my photo?
No. The browser tools do not take a file.