When you use EMOZ to protect your work, your files are never uploaded, stored, or transmitted to any server — not even ours. This is a deliberate design choice, not just a policy claim, and you can verify it yourself.

Instead of uploading your file, EMOZ computes a SHA-256 hash — a unique digital fingerprint — directly in your browser, on your own device. This happens entirely locally: your computer, smartphone, or tablet performs the calculation. Only the hash (a short string of characters) is sent to the blockchain to create your timestamp. The file itself never moves.

This applies to both the certificate creation process and the Hash Calculator at emoz.io/hash-calculator. The Hash Calculator is essentially a local web application: it runs entirely in your browser and nothing is sent anywhere. No file, no metadata, no data of any kind leaves your device.

Many services that offer file timestamping or verification require you to upload your file to their servers. This creates real risks — your files may be stored indefinitely, accessed by the service provider, exposed in a data breach, or subject to legal requests. This is particularly concerning for sensitive or confidential work: contracts, unreleased creative projects, business plans, personal documents.

With EMOZ, we cannot know what you timestamp. We only see the hash — and a hash alone reveals nothing about the content of the file.

This is not just a claim from us — it is fully auditable by you or any technical party you choose to engage.

To verify it yourself:

You will see no file upload request — because none happens. If a file were being uploaded, it would appear as a network request in that tab. There is no technical workaround to this: the browser's Network tab captures all outgoing data, and it cannot be bypassed silently.

Any independent technical expert can perform this same audit on your behalf in minutes.