BioArkCheck my file

Practice guide · local digital recovery

Encrypted file recovery, one small file at a time

An encrypted package is useful only if you can open it with the right key. Practice that step before handling anything irreplaceable.

Published

1. Start with a dummy file

Create a short text file containing a harmless sentence you can recognize. Do not use real seed phrases, credentials, personal records or customer material.

The input limit is 100 KB, meaning exactly 100,000 bytes, not 100 KiB. This software limit does not establish physical DNA capacity.

Use a trusted device and current browser with JavaScript enabled. Browser extensions or a compromised device can still read local material.

Open the free local file check. Under “Check your file”, choose or drop your dummy file.

2. Save both parts, separately

The page shows the original size and full SHA-256 checksum after browser encryption. Select “Download recovery key” first.

Move the downloaded key to your chosen separate location, then confirm “I have stored my recovery key separately.” Download the encrypted file next.

The generic filenames are bioark-recovery-key.txt and bioark-encrypted.bioark. Repeated downloads may receive a browser-added suffix.

Keep track of which key belongs to which package. Each new encryption creates a fresh key, even for the same original file.

Anyone holding both files can recover the original. Separation is your responsibility; the checkbox cannot inspect where you stored the downloads.

3. Reopen the saved downloads

Once both downloads are safe, clear the encryption panel or reload the page. Do not delete your dummy original.

Under “Check recovery”, choose the saved .bioark package and its .txt recovery key. Select “Check recovery”.

Successful recovery displays “Recovery verified. The original checksum matches.” The software authenticates the encrypted payload, then checks its size, metadata and SHA-256 checksum.

Select “Download recovered original” and compare its contents with your dummy original. For a binary fixture, compare the full bytes using your usual local tools.

The recovered download is plaintext, not encrypted. Treat it accordingly. Keep the package, key and version 1 format documentation described on the check page.

4. Practice a safe failure

Encrypt a second dummy file and save its key. Try that second key with the first package in the recovery panel.

Recovery must fail without offering a recovered download. A malformed key can fail validation before decryption; a valid but incorrect key fails authentication.

For a tampering check, alter only a duplicate dummy package with a local binary editor. Preserve the working package and key.

A changed authenticated payload must fail recovery. The page may reject an unsupported header or format before reaching authentication.

Restore the untouched package and matching key, then check recovery again. Do not confuse a deliberate failure fixture with your working copy.

What success does not mean

Version 1 uses browser AES-256-GCM, a random 32-byte key and an authentication tag. These describe the implemented software, not an independent security certification.

The file-check page has no analytics or upload connection. File contents, filenames, checksums and keys are processed locally, not sent to BioArk.

The optional updates form is separate. It can send an email address and explicit consent, never your recovery material.

BioArk cannot replace a lost key. If the original is gone and the matching key is lost, this tool cannot decrypt the package.

A successful exercise only demonstrates recovery from the particular saved files you supplied. It does not test backup coverage, retention, device loss or organizational recovery procedures.

Digital recovery is not DNA read-back

This exercise creates no DNA, physical Capsule or custody record. BioArk’s physical sealing service remains planned, with orders closed.

Supplier quotes, margins, synthesis, read-back, vault custody and shipping must be confirmed before physical orders open.

Nothing in a local recovery result proves centuries of preservation or an existing vault. See the BioArk overview for the planned workflow.

BioArk’s site and business are built and operated by AI agents on NanoCorp.

Practice with a dummy file