Private beta. Use fictional credentials only while independent security review is pending.

Privacy notice

Clear information about your information.

This notice describes the current Android private-beta architecture. Future features will require a new disclosure review before release.

Information XVRON handles

The current private beta may handle your account email and identity identifiers; session and trusted-device records; device public keys and enrollment state; security-event outcomes; and encrypted Vault synchronization packages with integrity metadata.

Vault item contents and passwords are designed to be encrypted on your device before synchronization. The service is not designed to receive a readable Vault key or readable Vault contents. This design still requires an independent security review before a public release.

Recovery records are separate from encrypted Vault contents. Authorized server components can read verified-email destination snapshots, identity identifiers, recovery-attempt metadata, and completion receipts used to finish or reconcile interrupted recovery.

Authenticator setup keys and labels are stored as encrypted Vault records. QR enrollment decodes camera frames on your device; the implementation does not save or upload camera images or record audio. Manual setup is also available.

Authenticator search and password generation run locally. Search text is not saved and is cleared when the authenticator screen is hidden. A generated password stays in the editor until you save it; saved entries follow the existing encrypted Vault storage and synchronization flow.

Choosing Copy places a code or password on the system clipboard. XVRON attempts to clear matching copied authenticator codes at expiry and copied Vault passwords after a short interval. App suspension, process termination, clipboard history, and content pasted elsewhere mean that erasure of every copy cannot be guaranteed.

How information is used

XVRON uses this information to authenticate accounts, enroll or revoke trusted devices, synchronize encrypted Vault data, prevent abuse, respond to requested support, and operate and secure the service.

The current build has no advertising SDK and XVRON does not currently sell personal information. Billing, live AI, live support, VPN, analytics, and background browser protection are not included in this notice because they are not enabled in the current private-beta architecture. Optional breach checks are described below; availability depends on your beta version.

Service providers

The QA architecture uses Amazon Web Services for account authentication and gateway hosting, and Supabase-hosted PostgreSQL infrastructure for application data. A final subprocessor and data-location review is required before publication.

Optional breach checks use Have I Been Pwned (HIBP). Review HIBP's privacy policy for its handling of requests.

Optional breach checks

Password checks are optional. After confirmation, your device sends the first five characters of a password hash to HIBP's Pwned Passwords service and compares the returned matches locally. It does not send the plaintext password, complete hash, email address or Vault label. The provider can observe your network address and request timing.

Email breach checks require explicit consent. When you choose Check now, XVRON sends your complete verified account email address through its server to HIBP. This is not the hash-prefix method used for passwords. HIBP receives the queried email and the gateway's request metadata, including its network address and timing. You cannot use this feature to query an arbitrary third-party email address.

The HIBP API key stays on the server. Email checks do not send your passwords, readable Vault contents, XVRON PIN or recovery phrase. XVRON stores consent information, an account-bound keyed email digest, and the latest breach-result snapshot and check status in its hosted database.

Stop and delete removes your monitoring enrollment and saved results without deleting your XVRON account or Vault. Completed account deletion also removes monitoring records. Limited shared rate-limit timing can remain without the cleared account identifiers. These controls do not remove records from HIBP's independent breach database or promise immediate erasure from infrastructure backups.

Checks are user-triggered, not continuous background monitoring. A failure or offline check is not a safe result, and no known match does not prove that an account or password is secure. This feature is not malware scanning or a search of the entire dark web.

Storage and security

Hosted requests use encrypted transport. Local protection uses Android-protected key material and an XVRON PIN. Phone PIN or biometric unlock is an optional fallback, disabled by default. Recovery requires your XVRON recovery phrase and a verified-email code. Security measures reduce risk but cannot guarantee that any system is completely secure.

XVRON support will never ask for your password, PIN, authentication code, recovery secret, or readable Vault contents.

Retention and deletion

Exact production retention and backup-deletion periods are awaiting legal and operational approval. They will be stated here before public beta publication.

When a verified deletion request completes, XVRON removes account access and associated application data, except limited records that must be retained for a documented legal, security, fraud-prevention, or financial-record obligation.

The deletion design retains a minimal inactive identifier, one-way identity digest, non-secret receipt identifier, and deletion timestamp to prevent replayed identity assertions from recreating a deleted account. It does not retain the deleted email address, Vault ciphertext, device keys, session tokens, or plaintext secrets in that tombstone.

That tombstone is not the same as recovery records, provider copies, or records retained for a documented obligation. Expiry of a recovery challenge does not itself mean all related records have been erased. Interrupted provider operations can require reconciliation before deletion completes.

In-app account deletion is available. The separate external deletion request workflow is not yet accepting public requests. Signing out or clearing app storage does not delete your hosted account.

Contact and publisher

XVRON is published by Dramonx Labs LLC. Privacy questions may be sent to privacy@xvron.net. Support requests may be sent to support@xvron.net.