Confidentiality · evidence
Encrypted documents
Associate evidence with a confidential file without publishing its contents. Your browser encrypts the file before sending it to Kicklinks. This page explains the workflow and its limits; using the tool remains subject to the current access conditions.
Contact KicklinksThree practical situations
How does this differ from Documents and images?
Standard Document and Image certificates are already private. In that workflow, Kicklinks receives the unencrypted contents for the intended processing and measures the fingerprint of the received file.
In the encrypted workflow, the contents are encrypted before upload. The plaintext, your password and the raw key are not sent. Metadata, including the file name, type, size and fingerprints, accompanies the encrypted file: keeping contents confidential does not mean sending no metadata.
How does the workflow work?
- Prepare the file and encrypt it in your browser using your password.
- Keep your password and recovery file; make several backup copies of the recovery file before uploading.
- The encrypted file, metadata and fingerprints are sent. Kicklinks measures the encrypted file’s fingerprint and records the certification information when certification is finalized.
- During the availability window, retrieve the encrypted file through the existing private download workflow. Decryption and fingerprint checks take place locally using your password and recovery file.
What the evidence establishes, and its limits
The fingerprint of the unencrypted contents is calculated in your browser and sent as a client declaration. The server has not examined those plaintext contents.
Kicklinks measures the encrypted file’s fingerprint from the bytes it receives. This allows the integrity of that encrypted file to be checked.
Certification records these fingerprints and the associated information. This record alone is not server-side cryptographic proof of the link between the plaintext and the encrypted file.
- The evidence does not validate the document’s meaning, truthfulness, author or signatory.
- It provides neither an absolute legal guarantee nor absolute confidentiality against every attack.
- The product’s use of the term ZK does not in itself establish a cryptographic zero-knowledge proof.
Retention, deletion and recovery
The encrypted file is available for private download for seven days from the first finalized certification. Retrying does not restart this window.
Downloads close at the end of those seven days. Physical purging runs separately; destruction at the exact second of expiry is not promised.
The owner can request early deletion of the encrypted file from their private workspace.
Revoking certification does not immediately delete the file or extend its availability window.
Encrypted files follow a dedicated purge process, separate from the standard file purge.
Evidence is retained after the file is deleted. It is not a backup from which the contents can be reconstructed.
Keep a copy of the encrypted file, your password and the recovery file. If the elements required for decryption are lost, Kicklinks cannot restore access to the contents.
This workflow is not a vault for long-term storage.
Access, cost and enquiries
Use requires an authenticated workspace, verified identity and compliance with the current access and credit conditions. ZK Labs exposure remains separate from this public presentation. Reading this page activates neither the lab nor the tool and does not guarantee eligibility.
No general price for this workflow or general commercial availability is established here. Contact Kicklinks to understand the conditions that apply to your situation before planning to use it.
