Updated October 16, 2026.
Your original file stays on your device and is never changed. Checking it is free. Preparing an unlocked copy or reading a saved password keeps the file and result on your device, too.
If you choose a password search on our servers, we send only the information needed to test passwords, not the whole file. We learn any password we find. Some archive information may become readable to us. You can review exactly what will be sent before continuing. Payment uses a private reference to your purchase.
Keep your file tab open, and save your download or password before leaving. The sections below explain the technical details, storage and purchase access periods.
Checking your file and preparing a copy
The recovery form identifies your selected file and its supported recovery options on your device. Original files are not uploaded. Local extraction also reads any ZIP original or reference archive you select; those inputs, prepared output and extracted passwords remain in a browser worker or the page’s memory.
Checking your file is free. We prepare supported local results before checkout. Downloading a prepared result or revealing a saved password costs $9.99 USD before applicable tax. Failed preparation does not create a charge. File processing can run offline after the page and engine load; checkout and payment verification need a network connection. These billing requests do not upload your file, filename, reference data, recovered key, extracted password or output.
Local billing records include the selected method and an opaque document reference made with a fresh random salt and a file fingerprint. This binds a purchase to its original file so it can be reselected without paying again. It is not the file itself. Stripe receives a generic product, price and opaque order reference rather than the document reference or file material.
File references, recovery bundles, prepared output and passwords are kept in memory rather than localStorage, sessionStorage or IndexedDB. Closing or clearing the tab removes app references and loses unsaved local results; it is not a promise of guaranteed browser memory erasure. Downloads save separate files to your device. Copying a password puts it on your device’s clipboard. Keep the file tab open during checkout.
Direct 40-bit searches can be paused. Explicitly saving progress downloads a JSON file containing a document SHA-256 fingerprint, search method and next key position. It contains no document bytes, password or recovered key. Progress is not stored automatically; resuming requires your chosen progress file and the exact original document.
Cloud password recovery
Only after you choose cloud recovery and continue to checkout does Llaves submit the displayed recovery hash, encryption mode and offer to its recovery service. The server stores an encrypted request while payment is pending. Searching starts only after payment is confirmed. The request does not include your filename, file path, document text, page images or original-file buffer.
PDF bundles contain encryption settings, document identifiers and password-verification values. Office bundles contain encryption settings, a random salt and encrypted password-verification values; document contents, the encrypted package and its key are excluded. 7z bundles can contain encrypted header fragments. The service learns a password it finds and can decrypt any supplied fragments, which may reveal archive filenames. Cloud recovery is not zero knowledge.
The API gateway and GPU service retain records and recovery material needed to run and report a search. Local clearing does not delete remote records or cancel an active search. Our recovery API makes recovered passwords available for up to 72 hours after recovery. Our GPU provider, Modal, separately retains function inputs and outputs for up to seven days; those outputs include any password found. See Modal’s data-retention policy. Operational, purchase and payment records can be kept longer for refunds, accounting and preventing duplicate work.
Purchases and browser cookie
A secure HttpOnly cookie identifies this browser’s purchases for 30 days, renewed when checkout is created or retried. It contains a random token, not a file, filename, recovery hash, password or payment details. The server stores its digest. Blocking or clearing the cookie removes access to purchase history in that browser. It supports the service rather than advertising.
Paid local-result access lasts seven days after payment. Clearing the purchase cookie removes this browser’s access. If the tab was reloaded, choose the existing purchase and reselect the original file and any required references to prepare it again. No document or output is stored on the server for later download, and recomputation may take time. Do not create another purchase to resume an existing one.
Payment uses Stripe-hosted Checkout and Managed Payments, with Link acting as merchant of record. Stripe handles billing information, tax, receipts and payment support. Llaves does not receive or store card numbers, and does not send Stripe original files, recovery bundles or recovered passwords. A checkout return URL alone grants no access to a result.
Website and support
The recovery form includes no analytics, external support widgets, remote fonts or third-party scripts. Marketing pages support optional Abner analytics when configured; it is disabled by default. The shared light/dark theme can remember your preference, without storing files or passwords.
Hosting and recovery providers process request metadata needed to deliver the service. Application code does not log file buffers or recovered passwords.
Email to [email protected] uses HeardKit and FreeSend. Include the issue and purchase reference if useful. You do not need to send an original document, card information or password.