What the extension can access
AliasX + PasswordX has two separately authorized connections. Connecting one does not automatically authorize the other. Sign-in and approval take place on the chosen service’s account website.
AliasX. A new mail connection authorizes all existing aliases available to the current account and service, as well as aliases it creates, and read separately encrypted new-message copies for those aliases. You can use an AliasX account or a supported service such as Slevin Mail. Sending and replying are not supported.
PasswordX. You choose which vaults you own to authorize. The extension can decrypt and manage records within that grant, including saved logins, passwords, website addresses, notes and time-based verification (TOTP) secrets and codes. It does not gain unrestricted access to every vault or to shared vaults.
Sign-in does not transfer your account sign-in password, main account private keys, primary mailbox private key or recovery material to the extension. Messages and records you choose to open may themselves contain personal or sensitive information.
Data we handle
- Alias and message data. The service processes alias addresses, optional labels, state, routing and ownership information. The extension receives only the aliases in its grant and separately encrypted message copies containing sender and recipient information, subject, limited plain text, receipt time and attachment or truncation indicators. It detects possible email verification codes on your device. These limited copies do not provide full MIME or attachment access.
- Selected PasswordX records. The extension handles encrypted records and decrypts the authorized fields on your device. New and edited record content is encrypted before it is sent to PasswordX. The service also processes identifiers, revisions and access metadata needed to store records and enforce the grant.
- Connection data. The services process installation and device identifiers, public keys and fingerprints, approvals, authorized aliases or selected vaults, granted capabilities and creation, expiry and revocation times. Each connection has separate device credentials and access/refresh tokens.
- Local state. Separate encrypted IndexedDB stores hold the device keys, connection tokens and pending operations for mail and PasswordX. Interface language preferences use a separate local store. Optional site-to-alias associations stay local. These associations and preferences are not synchronized through Chrome Sync.
- Site information. On HTTPS sites you allow, an isolated content script recognizes eligible focused fields and can show email and password suggestions. The extension checks the current site origin and field and form metadata. When you explicitly choose to generate and save a password, the visible email address in the same form may be saved as the login in that encrypted PasswordX record. It can retain an optional local site-to-alias association. Saved PasswordX website addresses are part of the user’s encrypted record. The extension does not collect or upload a passive browsing history.
- Connection and security metadata. Our services and network providers process IP addresses and request metadata needed to deliver requests, limit abuse and protect the service. We do not request GPS access or track your location.
Optional access to websites
Installation does not grant access to every website. Copying an address, login, password or code requires no website permission. When you allow filling for a site, Chrome requests permission for that specific HTTPS origin. The packaged content script then runs on that approved origin, including future visits, until you remove its site permission.
Insertion is an explicit action. The extension checks the active top-level document, field type, visibility, emptiness and form destination. PasswordX insertion is restricted to the record’s saved website. It leaves filled fields unchanged and fills a value only after you choose a suggestion or an insertion action. It never submits a form. PasswordX suggestions require opening the selected vaults; matching is limited to the exact saved HTTPS origin. Generated passwords are encrypted and saved in the selected vault before insertion, and a matching empty confirmation field can receive the same password.
Only the value you choose is inserted. Once inserted, that website can read it under its own privacy practices. Copying puts the selected value on your system clipboard, where other applications may be able to read it. It does not upload page contents or browsing history. It does not read passwords saved by Chrome, the operating system or another password manager. The email address included in an explicitly requested generated-password record is handled as described above. Remove optional site access through Chrome’s extension settings.
New-message indicators
While a mail device is connected, the extension periodically checks the authorized alias message list, including when its popup is closed, to update a count on the browser icon. Checks normally run about once a minute while Chrome is running; sleep, browser scheduling and connection failures can delay them. Background checks do not read or decrypt message contents, detect codes or access PasswordX vaults.
A separate local IndexedDB store keeps a bounded set of message and alias identifiers, receipt times and read flags for up to seven days. It contains no addresses, subjects, message bodies, passwords or device credentials and is not synchronized through Chrome Sync. Opening a message marks it read for this browser. Counts are scoped to the current mail device; a plus sign indicates a partial count. Disconnecting mail stops its scheduled checks.
Separate keys and protected connections
Each authorized browser connection has a separate device key. The public key is sent to the service; the private key and connection state are encrypted in the extension’s IndexedDB storage with a non-extractable browser cryptographic key. This is protection for stored data, not a hardware guarantee against a compromised browser profile or malicious extension code.
PasswordX records remain encrypted in transport and storage and are decrypted in the trusted extension context for the authorized vaults. The extension uses packaged cryptographic libraries. Sign-in does not transfer your account password, home private key or recovery kit from the account website to the extension.
API connections use HTTPS. The mail service prepares separate encrypted copies for approved devices. Message text is displayed without running email HTML or loading remote email images. Ordinary SMTP email is processed by the mail service before archive and device copies are encrypted; ordinary email is not thereby made end-to-end encrypted.
Locking clears foreground PasswordX data and cancels pending local actions. PasswordX also locks after inactivity. JavaScript memory cleanup cannot guarantee erasure of every browser or garbage-collector copy. A value already copied or inserted into another site cannot be taken back.
Retention, disconnection, and removal
Alias message retrieval is limited to authorized messages received after access was activated and, for an existing alias, after it was authorized, within the most recent seven days. The retained archive is managed separately by AliasX or your connected mail service. This window is an extension access limit, not a promise that every server record or backup is deleted after seven days.
PasswordX records remain in your account until changed or deleted through the service. Server access is limited to the device grant and selected vaults. Access metadata, revocations and operation receipts may be retained to enforce permissions and resolve interrupted operations.
Locking PasswordX clears its foreground data but does not revoke the device grant. An explicit device retirement or revocation stops future access. Mail and PasswordX are separate connections: disconnect or revoke each one you no longer want. A local forget action or uninstall alone does not prove that server access has been revoked.
Disabling an alias stops new mail to that address; it does not erase the retained archive. Reconnection uses a new device key and does not automatically open earlier device copies. Removing the extension does not close your service accounts, delete their aliases or erase their mail and password archives. Revocation cannot erase copies already obtained, text on the clipboard or values inserted into a website.
Your account and privacy controls
Review or revoke mail installations in the device settings for AliasX or Slevin Mail. Review PasswordX devices through PasswordX device settings. The extension also provides separate mail disconnection and PasswordX lock or device-retirement controls.
Manage retained mail and records in the corresponding service. Use Chrome’s extension settings to remove site permissions or uninstall the extension. Keep account and recovery material outside the extension. For questions or a data request, contact support@aliasx.io.
Policy updates
We update this page when the extension’s data practices change and revise the date above. A change requiring new access or consent is presented through the relevant extension or account flow before that access is granted.