Retyc Blog

Opening the link, unlocking the transfer, decrypting the files, saving them: on the recipient's side, everything happens in the browser. What it does at each step, and why Chrome and Firefox don't offer you the same thing.

Through Anthropic's Cyber Verification Portal, we had Retyc pentested by Claude, on our development environment.

A post-quantum key pair per transfer, 8 MB chunks encrypted one by one in a Web Worker, an API that refuses classic keys. What the browser does between the moment you drop a file and the moment the last byte leaves, with the code to show for it.

Drop a file, type an address, click "Send". Consumer file transfer services have become a reflex at work. Without end-to-end encryption, they see everything that goes through them. Five professional situations to understand what that means.

Retyc embeds no AI. But your agent can drive Retyc: the command-line client exposes an MCP server that runs on your machine. What it enables, how to install it, what the agent sees and does not see, and the limits to know before using it.

"It's between two professional addresses, so it's secure." This is the most widespread belief about email, and it is wrong. The real journey of an attachment, explained without jargon, and what to do instead.

Almost every file sharing service is "encrypted". Yet in most cases, the service can read your documents. A jargon-free explanation, examples from 2026, and a single question to ask: who can read my files in plaintext?