Privacy policy.

This policy covers the PromeXion Labs website and the current PrivXion development extension. PrivXion temporarily shields supported browser tabs behind a local passcode and restores their destinations after authentication. PrivXion is not yet publicly available; legal compliance work and the Chrome Web Store submission and review process are in progress.

1. Data handled on your device

Chrome extension storage may hold preferences; salted passcode, recovery-key, and optional administrator-passcode verifiers; authentication cooldown state; limited security-event records; and tab destinations needed to lock and restore your session. PrivXion restricts extension storage to trusted extension contexts.

When you enable Mixed-content detection, selected resource URL attributes on the currently loaded HTTPS page are checked locally. PrivXion records a local signal, not the page URL, resource URLs, or page content.

2. Passcodes and recovery keys

The session passcode strength gauge uses the locally bundled zxcvbn library to evaluate the passcode on this device. The library does not transmit the passcode. Its strength result is an estimate; for responsiveness, it evaluates at most the first 100 characters.

PrivXion does not store session or administrator passcodes in plaintext. Passcode verification uses PBKDF2-HMAC-SHA-256 with a random salt. The salted verifier is stored only in Chrome extension storage on your device. PrivXion does not transmit your passcode or its verifier to PrivXion or any other server. New verifiers use 600,000 iterations. Recovery keys are generated locally using cryptographically secure randomness; a salted verifier is retained after setup.

3. Tab restoration and encrypted backup

While a session is locked, PrivXion keeps the original destinations of tabs replaced by its lock pages so they can be restored after successful authentication. Temporary copies are held in session storage and removed after restoration where possible. A persistent backup is encrypted using AES-GCM for restoration after browser restarts. The AES key is stored in the same persistent extension storage area as the encrypted backup. This encryption does not protect the backup from someone or software that can directly read your Chrome profile or extension storage. It is not a passcode-encrypted vault.

Unlock and restore your browsing session before removing the extension. If PrivXion is removed while locked, Chrome may close tabs still showing its lock screen, and the saved return destinations may be removed with the extension. PrivXion may then be unable to restore those tabs to their original destinations. You can manually reopen previously visited pages from Chrome History (Ctrl+H on Windows/Linux or ⌘+Y on macOS), if Chrome still has the entries. This reopens page URLs and may not recover unsaved page state. If you cannot unlock, use the recovery-key option if available or contact support before removal. Chrome's normal extension controls remain available; PrivXion cannot prevent removal.

4. Optional browsing safeguards

• HTTPS protection can warn before an HTTP page loads and allow a one-time exception.
• Mixed-content detection checks selected resource attributes locally when enabled.
• Sensitive-site protection can match likely login, banking, payment, or wallet URLs locally when enabled.
• Automatic locking and lock-on-tab-switch behavior depend on settings you choose.

5. Permissions and host access

The current extension manifest requests storage, idle, declarativeNetRequestWithHostAccess, and webNavigation, along with HTTP and HTTPS host access. These support local settings and authentication, optional inactivity locking, locking and restoring supported website tabs, and enabled navigation safeguards.

6. Third parties and voice playback

The current extension contains no third-party advertising SDK, behavioral analytics SDK, remote executable code, or active subscription service. When a locally bundled voice recording is unavailable, a lock page may use speech synthesis voices supplied by your browser or operating system. Voice-provider behavior is governed by that provider’s own privacy terms; PrivXion does not send browsing URLs or passcodes as speech text.

7. Website hosting and Cloudflare

The website is hosted through Cloudflare Pages and related Cloudflare security and delivery services. Cloudflare may process network and request information needed to deliver and protect the site, such as IP address, requested URL, browser and device characteristics, timestamps, and security signals, under Cloudflare’s own privacy terms.

If Cloudflare Web Analytics is enabled, it may collect page-view and performance measurements. Cloudflare describes this service as cookie-free and says it does not track individual users across customer sites. The current source does not include advertising trackers or a separate behavioral analytics SDK.

8. Payments and PayMongo — not active

No live PrivXion checkout is currently active. If PayMongo checkout is enabled later, PayMongo and its payment partners may collect and process the name, contact details, payment information, device information, IP address, transaction identifiers, and fraud-prevention information needed to complete and protect the transaction. PromeXion Labs should receive transaction and entitlement details needed to reconcile the purchase, provide support, and maintain access; it should not receive or store full card credentials.

The checkout and this policy will be reviewed again before activation. PayMongo’s handling of payment data is governed by its own privacy policy and payment terms.

9. Support communications

If you contact support, the message may contain your email address, name, transaction reference, diagnostic details you choose to provide, and the content of your request. This information may be retained as reasonably necessary to answer the request, document a transaction or dispute, prevent abuse, and meet legal obligations. Do not send passcodes, recovery keys, full card details, browser history, or confidential page content.

10. Website accounts and planned features

You may create an optional website account using an email address and account password. Supabase Auth processes your email address, a user identifier, authentication events and credentials to create and secure your account. Your password is sent to Supabase for authentication and stored as a salted hash by Supabase; it is separate from the extension passcode, which remains local to your device. Resend processes the address and message details to deliver confirmation and account recovery emails. Providers may also process technical, security and delivery data. Resend reports that it stores customer data in the United States, regardless of the selected sending region.

The Supabase client attempts to store sign-in session data, including authentication tokens, in browser local storage to keep you signed in. Signing out clears the local session through the client. Avoid sharing your browser profile with others. The website account is not connected to payment or extension access.

Trials, licensing, device activation, subscriptions and referrals are not active. This policy will be reviewed before any such feature is enabled.

11. Retention and your choices

Extension data remains in Chrome storage until removed by normal product behavior, settings reset, profile deletion, or extension removal, subject to the restoration risks described above. Website account information is retained while the account is maintained and may be removed on request, subject to applicable retention obligations. Security, support, delivery logs and backups may be retained separately for operational, security, dispute or legal needs and may persist temporarily after deletion. Retention varies by provider, plan and configuration; contact us for details relevant to your request.

To request access, correction or deletion of website account information, email privxion.ext@gmail.com. We may verify control of the account email before acting. Do not send your account password, extension passcode, recovery key or verification codes. Self-service deletion is not currently available. Deleting a website account does not remove the extension or its local passcode and restoration data.

12. Security limits

PrivXion is designed to deter casual access to supported tabs. It does not encrypt website sessions or replace your operating-system lock. A person who controls your device account, Chrome profile, or extension-management interface may be able to bypass the extension. Replacing a page may also lose unsaved page state.

13. Changes and contact

We will review and update this policy as our practices change and before payment, licensing, analytics, or referral processing is activated. For privacy or support questions, contact privxion.ext@gmail.com. Merchant details and launch status are available on the Merchant & Contact page.