Privacy for the photo inspector

The inspector reads your selected file locally. It does not upload the image, its filename or its metadata.

Loading the website involves separate requests for its pages, scripts and sample files. Those boundaries are explained below.

Applies to the photo inspector and website measurement on vaultmax.app. Updated November 14, 2026.

Inspection and removal happen in memory.

When you choose a file, the tool reads its bytes in a browser worker and shows the supported fields in the page. It may create a local preview for supported image types. The inspector does not send the selected image, filename, field values or coordinates to a server. It does not use a map provider or request your device location.

Selected file contents and results are not written by this tool to cookies, local storage, IndexedDB, analytics or the page URL. If you choose Remove metadata, the browser rebuilds a separate JPEG or PNG from decoded pixels and inspects it in memory. Download writes the new file to the destination chosen by your browser. The original stays unchanged.

Clearing the workbench discards the tool’s selection, results and generated copy from the session. Canceling removal stops the local worker and returns to the existing inspection. Leaving or reloading the page also ends that page session. These actions do not securely wipe your device’s memory, delete your original file or change files kept by other apps.

A local read still starts on a website.

Your browser requests this site’s HTML, style sheet, scripts and any practice sample you choose. The tool uses locally served code and system fonts, without an outside font service, embedded map or advertising pixel.

The host and network still handle ordinary web requests and may process technical information such as IP addresses, request times and user-agent details under their own configuration. This page does not promise that hosting logs do not exist or specify a retention period that has not been verified.

Fictional sample files are downloaded as static assets when requested. Using a sample does not send one of your own photos. Your browser may cache site assets according to its settings and the server’s responses.

We count page views and App Store link clicks.

The website sends a fixed page identifier and, when you follow a download button, a fixed button identifier to a counter on vaultmax.app. We keep totals by UTC day in a rolling 400-day history. Older totals are cleared when the counter next receives an event. Refreshes and repeat clicks count again; these totals do not identify unique people.

This measurement does not save your IP address, user-agent string, full page URL, search terms, referrer, cookies, browser fingerprint or persistent visitor identifier. It never reads or sends inspector files, filenames, metadata, results, sample selections or free text. The counter request omits referral information. The hosting boundary described above still applies to ordinary server requests.

We honor Do Not Track and Global Privacy Control by skipping these website counts. Logged-in browsing, diagnostic traffic and known automated crawlers are excluded from the owner’s website report. This filtering cannot identify every automated visit.

Download links include an Apple campaign label for the page you chose. Apple uses its own privacy-protected reports to measure App Store product-page views, downloads and purchases associated with those links. Small results may be withheld. Website clicks are separate from confirmed Apple results, and this setup does not add analytics to the native Vault Max app.

Following a link changes the boundary.

Links to Apple documentation, the App Store and the existing Vault Max app site open those destinations only when you choose them. Those sites have their own privacy terms and may receive ordinary request and referral information. This inspector does not attach your filename, result values or selected image to those links.

The browser tool and Vault Max app have different roles. This page is not a replacement for the app’s privacy information or the policies of an app you use to send a photo.

Who serves the website?

Hostinger hosts this WordPress site. The public tool serves its code and practice images from vaultmax.app. We checked the hosted tool in a clean browser using fictional samples and selected local files. Inspection requests fetched code and sample assets from this site, and the tested flows did not send selected image bytes or metadata.

Have a question about a result?

Start with the inspector’s limits and our method. General support details are on the existing Vault Max help page. Avoid sending private images or secrets to explain a question about the tool.

This is a description of the included tool’s handling, not a claim of universal legal compliance, anonymity or protection from every form of identification.