Skip to content
DOCDocumentation

Know what each tool does.Keep the keys.

A practical guide to Cypra: sealing files in your browser, sharing them by link, managing keys and recording who may read what on Robinhood Chain. Start here, then open the tools.

What Cypra does

Cypra puts encryption, sharing and access records in one Terminal. Files and notes are sealed with AES-256-GCM in your browser before they go anywhere. You decide who gets the key, and if you want a public trail, you write it on Robinhood Chain: the file's hash, the addresses you allowed and when you changed your mind.

Start in three moves

  1. 01Seal something. Open the Vault, type a note or pick a file, choose a passphrase you can remember and press Seal. Download the .cypra file.
  2. 02Send it. Secure Share makes a link whose key lives after the #. Send the link, or the file plus a passphrase you share another way.
  3. 03Record access, if you need proof. Connect a wallet, anchor the sealed file's hash and grant the reader's address. Anyone can check it later in Onchain Records.

Which tool for which job

  • Vault: seal and open text or files under a passphrase (PBKDF2, 600,000 rounds) or a 256-bit key.
  • Secure Share: a link for one reader, with expiry and an optional one-time read when site storage is on.
  • Key Management: generate keys, see fingerprints, export wrapped backups, re-seal a file under a new key.
  • Access Permissions: anchor, grant, revoke and retire records on Robinhood Chain from your wallet.
  • Onchain Records: look up a record by number, owner or file, and check whether an address holds a grant.
  • Market, Credits and Developer API: token facts from chain, and the plans that are not built yet, labelled as such.

See the Toolkit for direct links, and How protection works for what each layer does and does not cover.

Where your data and keys live

Sealing, opening, key generation and hashing run in the browser tab. The site never receives your plaintext, your passphrase or your key. Share storage, when it is on, receives sealed bytes only, and deletes them at expiry or on first read if you chose that.

Keys you generate live in the tab's memory until you close it. Export a wrapped copy to keep one. There is no reset and no recovery: a lost passphrase or key means the sealed data stays sealed.

Local encryption does not protect a device that is already compromised, and it does not hide metadata such as file size or the addresses you grant on chain.

On-chain records

The CypraGrantBook contract on Robinhood Chain stores a ciphertext hash, an optional label hash, the owner address and the grants. It has no owner, no admin key, no fee and no upgrade path. It cannot decrypt anything and cannot stop anyone from opening a file they hold the key for: it is a public statement of your decisions, with a block and a time attached.

Until the contract is deployed, Access Permissions and Onchain Records run in a clearly marked practice mode that keeps signed actions in your browser.

$CYPRA

The plan is for $CYPRA to pay for service credits such as hosted storage, API calls and premium features. None of that is active and no tool reads your balance. $CYPRA is a utility token still being planned: it gives no ownership, no share of revenue and no promised return. See the token page.

Read results with care

A grant on chain is a record, not a lock. A clean result in Onchain Records means the chain says what it says; it does not prove who wrote a file. The risks page and the terms spell out the limits, and the FAQ covers the usual questions.