EMOZ stores only the minimum information needed to provide its service, and always with user privacy as a priority:
EMOZ never stores the user’s file. In fact, the file is never uploaded: when a user drags a file into the EMOZ interface, it stays local in their browser. The only thing generated is the file’s fingerprint (SHA-256 hash), which is computed entirely within the user’s device. EMOZ has no technical means of knowing the file’s contents, nor of receiving or accessing it.
The data that EMOZ does store includes:
Verified email address of the user
Full legal name (used for the ownership certificate)
File fingerprint
File category selected by the user (e.g. code, photo, music, etc.)
Legal ownership declaration marked by the user
A random salt needed to verify ownership later
Blockchain transaction ID and the associated network (e.g. Polygon or testnet)
Payment data is not stored by EMOZ. All payment handling is outsourced to Paddle, a regulated payment provider that processes transactions, stores card data, collects applicable taxes (such as Spanish VAT), and forwards them to tax authorities. EMOZ does not have access to credit card numbers or any personal financial information.
In EMOZ’s payments table, only general and non-sensitive metadata is recorded:
Transaction ID
Checkout ID
Both are generated by Paddle. All legal and fiscal responsibilities related to payments are handled by Paddle.
All this data is hosted securely using Amazon Web Services (AWS), which provides industry-standard infrastructure and encryption protocols to ensure data protection and availability.