Sealed Courier
Hand a file directly to a specific recipient — quantum-resistant (ML-KEM-1024) encryption, no public web hosting, no third party holding the bytes. Both sender and recipient need the local Synergent Agent running.
What Sealed Courier does and doesn't hide
It hides: the payload bytes (ML-KEM-1024 + AES-256-GCM, post-quantum confidential), and proves the sender's identity to the recipient (FALCON-1024 + ML-DSA-87 dual signatures).
It does NOT hide: the recipient's identity, the sender's identity, the timestamp, or the approximate payload size. Delivery JSON is metadata-leaky by design — anyone with the file knows who sent it to whom and when. If that's a problem, layer onion routing on top.
No delivery confirmation or expiration. Once handed off, the encrypted blob travels however you choose to move it. The cryptography doesn't enforce a TTL — that's storage policy.