# Encryption and browser lock — Orvi 0.2.0 ## Saved Orvi records Preferences, bookmarks, saved history, session-restoration records and cleanup metadata are stored in authenticated AES-256-GCM envelopes. Each write uses a fresh 96-bit nonce and a 128-bit authentication tag. Record names are authenticated so one record cannot be substituted for another. Writes use an atomic rename; a damaged ciphertext fails closed. A random 256-bit vault key is protected by Windows DPAPI CurrentUser. No plaintext storage fallback is available. The Windows helper receives data only through stdin and returns it only to the main process; it does not log keys, change execution policy, elevate, or send data over the network. Existing JSON records are encrypted, read back and authenticated before the old JSON and its temporary file are removed. Ordinary deletion cannot guarantee removal of historical disk sectors, backups or files held elsewhere. ## PIN or encryption key Enable Browser lock in Settings > Security. Choose a PIN of at least six digits or an encryption key/passphrase of at least 16 characters. A longer key is stronger than a short PIN. When enabled, the vault key is wrapped using AES-256-GCM under a key derived with scrypt (N=32768, r=8, p=1, random 128-bit salt), then additionally protected by Windows DPAPI. The previous automatic-unlock wrapper is removed. Unlock is required before saved records or website contexts load, including launches from external links and additional windows. Failed attempts are serialized and delayed; delays survive normal application restarts. This UI limit is not an offline-attack guarantee. A random 256-bit recovery key is displayed once during setup. It has a separate authenticated key wrapper. Changing/recovering the lock rotates that recovery key. There is no online reset or Orvi-held master key. Recovery also requires access to the original Windows DPAPI identity; losing Windows encryption credentials can make data unrecoverable. Lock using the toolbar or Ctrl+Shift+L. Lock closes tabs, cancels unfinished downloads, stops workers/connections, clears transient browser data and removes the active vault key from its Buffer. Unlocked records and UI data are discarded. Locked sessions open on a fresh tab after unlocking. Automatic lock supports 1/5/15/30/60 minutes of Windows input inactivity and Windows lock/suspend events. Windows process suspension timing and memory zeroization outside that Buffer require platform verification. ## Website storage Private browsing contexts are memory-backed by default. They do not use a persistent Chromium website profile. Saving sign-ins or site exceptions requires Windows EFS on the dedicated WebsiteData directory. Orvi encrypts and checks existing files, rejects links, and verifies encryption inheritance with a probe before opening the persistent profile. On unsupported Windows editions, filesystems, policy restrictions or verification failure, persistence is refused. An older saved profile can be removed through an explicit in-app prompt before switching to private sessions. EFS protects website file contents with the Windows identity. The Orvi PIN/key separately protects Orvi records; it is not a replacement for Windows file encryption and does not independently password-wrap Chromium databases. Filenames remain visible. Other applications running as the same Windows user, a compromised computer, administrator access and live process memory are outside this protection model. EFS keys need Windows-supported backup/recovery procedures. ## Network encryption HTTPS-only is enabled by default. HTTP GET/HEAD requests are upgraded before sending; unencrypted submissions and ws:// connections are blocked. Normal certificate validation remains enabled. Users can explicitly disable HTTPS-only through a warning; those connections are then not guaranteed encrypted. Search engines and websites receive the data users submit. This is not a VPN or anonymity service. DNS, routing metadata and operating-system network activity are not covered by a blanket all-traffic encryption claim. ## Exclusions and verification Downloaded files stay where users save them and are not encrypted by the Orvi vault. Windows temporary files, memory/pagefiles, dumps, backups, filesystem metadata and third-party records are outside an application-only encryption guarantee. Use Windows device encryption/BitLocker for broader device protection. AES-GCM, scrypt, migration, locked access, retry delays and recovery behavior have automated tests. Actual Windows DPAPI, EFS, process startup, lock/suspend and complete browser-storage behavior still require Windows validation. No complete-encryption or production security certification is claimed.