Skip to main content

Decryption: encryption in reverse

When you ask for your file, here’s how it safely comes back together.

Thanasis Karavasilis avatar
Written by Thanasis Karavasilis
Updated over a week ago

Once your file is encrypted and stored in the Hivenet network, it’s locked up tight. But what happens when you want to access it again?

That’s where decryption comes in—essentially the upload process, but in reverse.

Let’s break it down.

Step-by-step: how decryption works

  1. Your user key (generated from your passphrase)
    This unlocks your read key

  2. The read key
    This decrypts the block key used to link the pieces of your file

  3. The block key
    This identifies the individual encrypted chunks that make up your file

  4. Each chunk is retrieved and decrypted
    Using the block key for that chunk

  5. Chunks are reassembled into your original file
    Just like putting puzzle pieces back in order—securely, privately, and only for you

What this means for you:

  • Only you can unlock the full file—because only you have the passphrase

  • Hivenet can’t see or access your data

  • The system is built to be secure, resilient, and transparent

Even if someone got access to parts of your data, they wouldn’t have enough information—or the keys—to make any sense of it.

Up next: how we keep your files intact even when some pieces go missing.


Did this answer your question?