Protect who can open it.

EviMark proves the file. DeepEyes protects delivery to a confirmed recipient—while preserving the original proof for verification after decryption.

Discuss a DeepEyes Pilot →Understand EviMark First

The user experience

One recipient. One explicit trust decision.

DeepEyes never silently chooses a recipient identity or encryption key.

1Seal with EviMark

2Choose recipient

3Confirm identity and key

4Encrypt and send

5Recipient unlocks and verifies

Private delivery

The protected package is prepared for the selected recipient’s confirmed public key. Possession of the package alone should not reveal the file.

Proof remains intact

After decryption, the recipient can check the original EviMark to determine whether the file matches the sealed version.

Designed exit

The recipient saves the original file, proof package or complete evidence package locally. Vector5 is not positioned as permanent document custody.

Hybrid post-quantum strategy

Introduce stronger protection without discarding today’s trust infrastructure.

DeepEyes is designed to combine established cryptography with post-quantum key protection. Both layers must succeed before the confidential package is accepted. This creates a staged migration path while organisations continue using approved PKI, CA, timestamping, digital identity, HSM and key-management services.

Specific algorithms and assurance claims must match the tested product release and customer deployment policy.

Security design principles

Hybrid classical + post-quantum key establishment
Authenticated content encryption
Explicit recipient and key confirmation
Local recipient unlock where supported
EviMark verification after decryption
No silent key or recipient substitution

What DeepEyes does—and does not claim

Clear boundaries create stronger trust.

DeepEyes is designed to establish

The package was encrypted for a selected recipient key.
The protected package was not altered undetected.
The decrypted artifact can still be checked against EviMark.
The protection policy and cryptographic evidence can be inspected.

DeepEyes does not automatically establish

That a self-asserted recipient name is a legally verified identity.
That the statements inside the document are factually true.
That every receiving device is secure.
That long-term confidentiality is guaranteed without lifecycle management.

Have a confidential document exchange use case?

We can scope the recipient identity, key source, PQC policy, delivery flow and EviMark validation required for a controlled pilot.

Discuss DeepEyes →