Security

Sealed here. Unreadable from the office.

FULLFORCE LTD publishes the vault. It does not hold the keys. This page is a plain description of the design, not a certificate.

Updated 12 October 2026

How a file is sealed

Each vault has a random key. Your password wraps that key in the browser. Files are sealed with AES-256-GCM before they are written to private storage. File names are inside the encryption. While the vault is locked, the key is not kept in memory.

What the company cannot do

FULLFORCE LTD cannot read a document, reset a password, or rebuild an emergency code. A sealed backup is already encrypted before it is sent to an address you choose. Checkout goes to Stripe and does not include the file.

What this does not stop

Someone who knows the password can open the vault. A short PIN is easier to attack than a long password if the browser storage is copied. Malware on the computer can read what you can read. Clearing the browser can delete the vault. Device unlock, where the browser offers it, is a convenience on top of the password, not a copy stored by the company.

Reporting a problem

Write to the registered office on the contact page. Describe the issue without sending a document or a password. The guide explains how to run the vault and how a sealed file moves between computers.