Privacy Policy
Authenticator App for PC generates and manages standard two-factor authentication codes locally in your browser. This policy applies to this extension, including its localized names.
The extension does not send your accounts, setup secrets, passwords, authentication codes, imported files or scanned page images to the developer or a server. Authentication data is processed locally. Optional purchase and purchase-restoration flows use an external online account and payment service. There is no cloud synchronization of authentication accounts, advertising, analytics or telemetry in the extension.
Information processed on your device
When you add or import accounts, the extension processes the service name, account label (which may be an email address or username), setup secret, authentication parameters, and any groups, notes or favorites you choose to save. It uses this information to generate TOTP or HOTP codes, organize accounts, and perform imports and exports. HOTP counters, deletion status, backup timestamps and password-lock preferences are also stored locally.
When you choose Scan page, the extension checks the active tab and captures its visible page to decode a setup QR code locally. The screenshot can include other visible page content; it is used transiently for scanning and is not uploaded or saved as browsing history. The extension does not continuously monitor tabs or browsing activity. Its bundled welcome page uses a bundled public demonstration QR image instead of capturing the page. Images or account files you explicitly select are read locally for scanning or importing.
Local storage and optional password protection
Accounts are saved in the extension's local Chrome storage. A password is optional. Without a password, the device data key is stored alongside the encrypted records, and opening the extension provides access to them. This mode does not offer password protection.
If you enable a password, account records are encrypted using AES-GCM. A key derived from the password wraps the data key; the unprotected device key is removed. The extension does not save the password itself. Changing or removing password protection rotates the data key while keeping account data.
While unlocked, account information is available to the background process. Protected-session key material and its expiry time may be cached in Chrome storage.session, which is browser-session memory rather than persistent local storage. The default unlock period is ten minutes, with configurable periods of one, three, five, fifteen, thirty or sixty minutes, or locking whenever the last extension window closes. Opening again before the chosen period expires restarts that period; ordinary clicks do not extend it. Manual locking, expiry, a browser restart or an extension reload clears protected sessions. An unprotected vault remains accessible without a password.
Exports, migration and clipboard
Choosing Export TXT creates a readable, unencrypted file containing account details and setup secrets, including recently deleted accounts and account parameters. This file is not protected by the vault password. Anyone who can read the file can use its setup secrets. It is saved through your browser's download mechanism and stays on disk until you remove it. The extension does not upload or automatically synchronize backups.
Imports only read a file or text you explicitly select or provide. Copy actions place the requested code or setup information on your system clipboard; the extension does not read clipboard history. Other software with clipboard access may be able to read copied information. It does not automatically fill website forms.
Permissions
- storage: store local account records, preferences and temporary protected-session state.
- activeTab: access the selected tab after your action to identify the bundled welcome page or capture a visible page for local QR decoding.
- clipboardWrite: copy a code or setup information when you choose a copy action.
- alarms: enforce the configured password-lock expiry.
The extension requests no broad host permissions and installs no persistent website content scripts. Its resources, QR decoder and service icons are bundled locally. Its extension-page security policy blocks network connections.
Free accounts, purchases and access restoration
The free plan allows three active authentication accounts, excluding the bundled public demonstration account. An upgrade is offered when adding a new account would exceed this allowance. Existing accounts keep generating and copying codes, and TXT export remains available, even when an upgrade expires or cannot be verified. Imported new accounts are also subject to the allowance. An over-limit import is not partly saved. Editing, deleting and restoring existing records do not trigger a purchase requirement.
Only when you choose to purchase an upgrade or restore a purchase does the extension open an external page at crx.shiplang.com. It sends the product identifier (manifest author), extension identifier, extension version, browser UI language and, if already available, the service account identifier and locally stored membership-expiry value. These values identify the product and restore its purchase state. It does not include your authentication account names, setup secrets, passwords, generated codes, scanned page images or backup files.
The external service may process the identity, payment and transaction information you choose to provide, together with ordinary network-request information such as your IP address, under its displayed terms and privacy policy. Checkout and payment details are handled on that external service; the extension does not request or store card numbers. The extension stores the returned service account and membership record under userInfo in local Chrome storage, including the product identifier, service account identifier and membership expiry, and checks that local record to enable additional accounts. The validity and available plans are shown by the payment service; no permanent lifetime entitlement is promised by this implementation. You can restore a purchase from Settings. Clearing extension data or uninstalling also removes the locally saved membership record.
Retention and your choices
Moving an account to Recently deleted keeps its setup secret and metadata locally so you can restore it; those records are not automatically purged and remain in TXT exports. Uninstalling the extension or clearing its stored data removes the local vault. Downloaded backups and copied clipboard contents are separate and are not removed by uninstalling. Keep a backup before clearing data. The developer cannot recover a lost password or setup secret and cannot remotely access or delete your vault.
Sharing, support and external pages
The authentication data handled by this extension is not transmitted to the developer or payment service, sold, used for advertising, transferred to data brokers or used for credit decisions. The extension does not include analytics trackers or remote executable code. Its locally bundled purchase integration opens the external service only after your action; it does not give that service access to the vault.
If you choose the support link, your browser opens an external email service. Only the support address is prefilled; no vault data is attached. Information you voluntarily include in a support message is handled to respond to your request. Do not send passwords, setup secrets or backup files. Email providers process messages under their own policies.
This public policy is hosted on GitHub Pages. Visiting it is separate from the extension's offline operation; the hosting provider may process ordinary web-request information, such as your IP address, under its own privacy policy. This policy page contains no analytics, external scripts or remote fonts.
Updates and contact
If data practices change, this page will be updated with a new date. For privacy or support questions, contact e@shiplang.com. Developer identifier: xiao_authenticator_c74.