No BeforeSubmit account. No automatic cloud sync.
The saved Vault is encrypted in this Chrome profile. Form and document checks run locally. Save an encrypted backup before removing the extension or changing devices.
Information you choose to use.
BeforeSubmit compares supported form answers with information you choose to save in My Vault. This can include your name, date of birth, contact details, addresses, employment and education history, personal characteristics, and optional private identifiers.
You choose when to check a form or a local PDF. New information is suggested for review; it is never saved merely because you checked or filled a form. Unsupported, private or ambiguous content may be excluded from comparison.
Saved on this device.
The saved Vault is encrypted in BeforeSubmit’s local database for this Chrome profile. It is not a separate editable file in Documents, stored in Chrome sync, or sent to a BeforeSubmit server. A Google account does not identify or recover the Vault. Other Chrome profiles and devices have separate copies.
Vault passwords, encryption keys and recovery keys are not saved in the persistent database. Relevant decrypted comparison information is held in trusted extension memory, including Chrome’s memory-only session storage, while checking is available. Private identifiers are excluded from this comparison copy. Locking editing clears editor access while permitting the restricted checking session to continue.
Browser restart, extension reload, disable or update can end checking access. You can unlock checking on the same panel. Viewing or changing saved information requires separate editor authentication.
Forms and documents
Supported field descriptors and selected answers are processed locally for a requested check. The current page, tab and site origin are used to scope that review and detect navigation. BeforeSubmit does not build a browsing-history database. Chrome controls access when you invoke the extension or explicitly approve a site.
Selected documents are processed locally with bundled PDF and OCR code. Field-detection diagnostics omit entered answers and page URLs; you decide whether to share those diagnostics.
You choose what to keep.
You can add or correct information in My Vault. Earlier confirmed versions remain in encrypted history until the active Vault is deleted. Suggestions require your review and approval before saving.
Backups and recovery
You can deliberately download an encrypted .bsvault backup or a plain-text recovery key. Chrome’s download settings determine the destination. Choose a safe location; Downloads or another folder may be backed up or synced by your operating system or another application. Keep recovery keys private and separate from encrypted backups.
Changing the password or replacing the recovery key affects the current Vault. Older backups keep the credentials they were created with. Restored copies on different devices are independent.
If both the password and a previously saved recovery key are lost, the publisher cannot unlock the encrypted data. A recovery key can unlock surviving data; it cannot recreate a lost Vault or backup.
Deletion and removal
Deleting the active Vault removes that local Vault and its history. Separately exported backups and encrypted archived copies remain. Removing BeforeSubmit, deleting this Chrome profile, losing the device or some device-management actions can remove local data. There is no automatic server recovery. Keep an encrypted backup before removal or moving devices.
Contact and updates.
BeforeSubmit is a LastTokn project. Support information is shared only when you choose to contact us. Do not send passwords, recovery keys, identity numbers, Vault files or completed private forms to support.