Юридический документ
ChromVoid Account and Data Deletion
Last updated: May 13, 2026
This page explains how to delete ChromVoid data and how to request deletion of limited service records that ChromVoid LLC ("ChromVoid," "we," "us," or "our") may process.
This page is intended for publication at:
https://chromvoid.com/account-deletion/
This page is not a substitute for the ChromVoid Privacy Policy. The Privacy Policy remains the source of truth for personal-data handling, retention, and privacy rights.
If we publish a translated version of this page, the English version is the source of truth unless we explicitly say otherwise.
1. Overview
ChromVoid is designed as a local-first encrypted vault. ChromVoid license accounts are used for license recovery, entitlement sync, and cross-platform Pro activation. They are not cloud vault accounts, and your vault data stays on your own devices.
ChromVoid LLC does not collect, receive, or have access to vault contents, master passwords, decrypted files, passkeys, passwords, OTP seeds, SSH keys, wallet secrets, local autofill secrets, browser extension secrets, or local device vault data by default.
Because of this design, there are separate deletion paths:
- Local vault data must be deleted on the devices, storage folders, exports, and backups that you control.
- Limited service data held by ChromVoid, including license account records where applicable, can be requested for deletion by contacting us.
2. License accounts and service records
ChromVoid may create or use a license account when you claim a license key, recover access with a license key, sign in with a recovery code, sync a Pro entitlement across platforms, or activate Pro from an account entitlement.
A license account can include an account ID, account status, hashed account session tokens, a hashed recovery code, license-account bindings, entitlement metadata, audit records, and related timestamps. It does not contain vault contents, master passwords, decrypted files, passkeys, OTP seeds, SSH keys, wallet secrets, local autofill secrets, or local device vault data.
A waitlist email, support thread, purchase record, app-store record, license key, license activation, relay room, wake record, analytics event, or license account record may be service data. These records can be handled through the deletion request process below where ChromVoid controls the record.
3. Delete local vault data on your device
Vault contents are local data. ChromVoid cannot remotely decrypt, inspect, recover, or delete local vault contents for you.
To delete local ChromVoid data, remove the copies that you control:
- Use the app's erase, clear-device, or reset flow when it is available on your platform.
- Delete local ChromVoid storage folders that you created or selected.
- Delete exported backups, restored backups, mounted-vault folders, imported copies, and other files you created outside the app.
- Delete operating-system, device, cloud-drive, or computer backups if they contain ChromVoid data and you want those copies removed.
- Uninstall the app if you no longer want to use ChromVoid. Uninstalling may not remove storage folders, exports, or backups created outside the app.
Deleting local data may be permanent. ChromVoid generally cannot recover a deleted local vault, lost vault password, lost master password, deleted recovery material, or deleted local backup.
4. Request deletion of service data
If you joined the waitlist, contacted support, bought or activated a license, used a license account, used relay or wake features, or otherwise gave ChromVoid limited service data, you can request deletion by emailing:
Use the subject:
Delete my ChromVoid data
Include only the information needed to find your service record, such as:
- Email address used for waitlist, support, checkout, or license delivery.
- Purchase ID, app-store order ID, checkout ID, or external payment provider ID.
- License key or activation detail needed to identify the license record.
- Account ID, recovery-code sign-in context, or other non-secret license-account detail needed to identify the account record.
- Support thread, message date, or other non-secret reference that helps us find the request.
Do not send vault passwords, master passwords, recovery material, private keys, seed phrases, OTP seeds, passkeys, decrypted vault contents, payment secrets, or other live secrets.
We may need to verify your request before deleting data. We will respond as required by applicable law. If we cannot fully delete information because of a retention obligation or another allowed reason, we will explain the limitation where required.
5. What ChromVoid cannot delete or access
ChromVoid cannot delete data that it does not control, including:
- Local vault data on your devices.
- Local exports, mounted folders, screenshots, logs, copied files, or backups that you control.
- Operating-system, browser, app-store, payment-provider, email-provider, cloud-drive, or device-backup records controlled by third parties.
- Data you shared with another person or service outside ChromVoid.
- Records that a payment provider, app store, platform provider, or other service provider keeps under its own terms, policies, or legal obligations.
If a third-party provider controls a record, you may need to contact that provider directly.
6. Retention limits
We keep information only for as long as reasonably needed for the purposes described in the Privacy Policy, unless a longer period is required or permitted by law.
Deletion may be limited where we need to retain records for legal, tax, accounting, fraud-prevention, security, dispute-resolution, active license-integrity, platform, or compliance reasons.
Backups may persist for a limited period after deletion from active systems and are removed through normal backup rotation.
7. Contact
ChromVoid LLC is responsible for handling deletion requests for service data that ChromVoid controls.
Company details: ChromVoid LLC, tax identification number (INN) 00547251, state registration number 999.110.1581079, registered on May 7, 2026.
Privacy and deletion requests:
Security vulnerability reports should also be sent to:
Primary public domain: