Multi-Recipient Sharing in Vaulternal: How Per-Recipient Encrypted Keys Work

Most cloud storage treats sharing like a digital room: you invite a few people in, and they all see the same thing using the same access permissions. But what happens if you need different people to get access to the same file, but only under very different conditions? That is where Vaulternal is a zero-knowledge encrypted file vault platform that specializes in conditional file delivery with per-recipient encryption keys changes the game. Instead of one shared lock, it creates unique locks for every person you choose.

The Logic Behind Per-Recipient Encryption

In a standard shared folder, the system usually encrypts a file once and then shares the decryption key with a group. If one person's account is compromised, the file is exposed for everyone. Vaulternal handles this differently. It uses asymmetric encryption principles to ensure that each single recipient is treated as a unique entity. When you share a file with three different people, the platform doesn't just send a link. It essentially creates three separate encrypted versions of that file, each locked with the specific public key of the recipient. This means the recipient only needs their own private key to get the data. If Recipient A manages to steal Recipient B's access link, it won't matter because Recipient A doesn't have Recipient B's private key. This architecture ensures that access is not just about "who has the link," but "who has the correct key."

How Conditional Access Continuity Works

Sharing isn't just about who gets the file, but *when* they get it. This is what the platform calls conditional access continuity. You can set specific triggers that must be met before the per-recipient key is released. This is incredibly useful for scenarios where you might be temporarily unreachable, such as during a long international expedition or a scheduled medical procedure where you won't have phone access for a few weeks. There are several ways to trigger this release:

• Inactivity Triggers: The file is released to a trusted contact if you haven't checked into your account for a set period. For example, if you're on a remote sabbatical and don't log in for 30 days, your partner could automatically receive the documents they need.
• Time-Based Triggers: You can schedule a file to be accessible on a specific future date. Think of it as a digital time-capsule or a birthday note sent to a friend months in advance.
• Manual Release: You can trigger the delivery yourself but set a cancellation window to ensure the process is intentional.
• On-Chain Signals: Because the system uses Polygon is a layer-2 scaling solution for Ethereum used by Vaulternal for on-chain metadata anchoring , it can trigger delivery based on wallet activity on a public blockchain.

Distributed Infrastructure and Security

Because this system deals with sensitive keys, it doesn't rely on a single corporate server that could be hacked or go bankrupt. Instead, it uses a distributed stack. The actual file data is stored using Arweave is a decentralized protocol for permanent data storage for permanence and IPFS is the InterPlanetary File System, a peer-to-peer hypermedia protocol for efficient distribution. On top of this, the platform uses client-side AES-256 encryption (specifically AES-256-GCM). This means the encryption happens on your device before the file ever touches the internet. The files are chunked and integrity-hashed, ensuring that not a single bit of data is altered during the process. Since it is a zero-knowledge architecture, the team at Vaulternal has no way to see your files or reset your password. If you lose your keys, the data is gone-unless you've set up a recovery trigger.

Practical Scenarios for Multi-Recipient Sharing

When do you actually use per-recipient encrypted keys? It's mostly for situations where you need to delegate access without giving away your master password or compromising your entire vault. Imagine you are a project lead transitioning a role to a new manager. You can set up a folder with all the critical project credentials and technical docs. Instead of emailing them in a risky PDF, you use Vaulternal. You encrypt the folder for the new manager and set a manual release trigger. If the handover happens on Monday, you hit the trigger. If the transition is delayed, the files stay locked and secure. Another scenario involves a planned handover for a contractor offboarding. You can give them access to the final deliverables they need, but set a time-based trigger so their access expires or is only granted at the moment of the final payment confirmation. By using separate keys for each contractor, you ensure that Contractor A cannot peek into the files meant for Contractor B.

Recovering Your Own Vault

One of the most clever uses of the per-recipient system is account recovery. Usually, zero-knowledge vaults are terrifying because if you lose your key, you're locked out forever. Vaulternal solves this by treating the master key as just another file that can be shared. You can encrypt your own master recovery key and assign it to a trusted contact. You then set an inactivity trigger. If you don't log in for, say, 60 days, the system delivers your master key to that trusted person. They can then use it to help you get back into your account. This creates a safety net that doesn't require you to trust a company with your password, but rather trusts a human you actually know. For more technical details on how the chunks and hashes are handled, you can check out the architecture page at vaulternal.com/en/architecture/.

Next Steps for New Users

If you're just getting started at vaulternal.com, don't just upload files and forget them. Start by mapping out who needs what and when.

• For Freelancers: Set up project-specific folders with manual release triggers tied to your final invoice dates.
• For Remote Workers: Establish an inactivity trigger (e.g., 30 days) that grants a partner or colleague access to your emergency contact list and critical project docs.
• For Security Conscious Users: Immediately set up the recovery trigger to a trusted contact so you aren't one lost password away from losing your entire vault.

If you encounter issues with file uploads, ensure your internet connection is stable, as the client-side chunking and hashing process requires a consistent stream to properly anchor the data on the distributed network.