Skip to main content
Inheribase employs four distinct layers of protection to ensure your digital legacy remains private and secure — from the moment you upload a file to the moment your heirs receive it. Each layer operates independently, so the failure of any single component cannot compromise your data.

​
1. Zero-knowledge architecture

Inheribase uses a zero-knowledge architecture, meaning we have no technical ability to access, read, or share your files. This is not a policy — it is a constraint built into how the system works. Your files are encrypted using keys derived from credentials that only you control. Inheribase employees cannot view your files, passwords, or keys at any point in the lifecycle of your vault.
Even under a valid legal order, Inheribase can only produce encrypted blobs — we do not hold decryption keys.

​
2. End-to-end encryption

All data stored in Inheribase is protected with AES-256-GCM encryption — the standard used by governments and financial institutions worldwide. Encryption and decryption happen exclusively on your device; the network and our servers never see plaintext.
1

Local encryption

Your files are encrypted on your device before transmission. The encrypted blob is the only thing that ever leaves your machine.
2

Secure transport

Only the encrypted blob travels over the network, wrapped in TLS 1.3. Even a network-level attacker sees nothing meaningful.
3

Encrypted storage

Our servers store only the encrypted, unreadable blob. There is no server-side key, no master password, and no administrative override.
4

Local decryption

Decryption occurs only on your authorized devices — or on your heirs’ devices after a verified release. No intermediate party ever handles plaintext.

​
3. Cryptographic data integrity (SHA-256)

When you entrust files to a digital inheritance platform, you need mathematical proof that the file your heir receives in 20 years is identical to the file you sealed today. Inheribase provides this guarantee through SHA-256 verification. The integrity chain works as follows:
  • Your browser computes a SHA-256 hash of the original file before encryption.
  • After submission, our servers independently verify the hash to confirm no transmission corruption occurred.
  • The verified hash is anchored on Base Mainnet, creating a tamper-proof, permanent record.
  • When heirs download the file, their local client re-verifies the hash — proving absolute authenticity without trusting any intermediary.

​
4. Data permanence: owned, not rented

Traditional cloud storage operates on a rental model. If you stop paying, your data is deleted. Inheribase ensures your estate is owned, not rented, by storing your encrypted files on Arweave — a permanent, decentralized data network. Once your data is written to Arweave, it cannot be deleted or modified. The permanence model works in three stages:
  • Instant temporary cache: Files are placed in a high-speed cache immediately after upload, giving you instant confirmation.
  • Arweave settlement: The encrypted blob is settled onto the Arweave blockweave. Once confirmed, the record is permanent and immutable.
  • Sustainable endowment: A portion of your fee is contributed to the Arweave Storage Endowment, covering the cost of maintaining your data for a minimum of 200 years.
Even if Inheribase ceases to exist as an organization, your encrypted data remains retrievable from Arweave and can be decrypted by your guardians using open-source tools — with no dependency on our infrastructure.