隐私政策 Privacy Policy

1. Information Collection

Authenticator Cloud is designed with a local-first approach, but some features require limited account, sync, and payment-related data to be processed.

• When you stay signed out, your codes are primarily stored on your local device or browser extension storage
• When you sign up or sign in, we collect your email address for account identification, login verification, and security-related communication
• When you enable cloud sync, we upload the required authenticator data to our servers in encrypted form
• When you subscribe to VIP, payment processing is handled by third-party payment providers and we do not directly store your full card details
• We do not sell your personal data and we do not intentionally expose plaintext authenticator secrets to third parties

2. Data Storage

To provide the service, we may store the following information locally or on our servers:

• Authenticator secrets, service names, account identifiers, icons, ordering, and interface preferences on your device
• Account-related information such as email address, session state, device identity, and cached membership status
• Encrypted backup data created during export and import workflows
• If cloud sync is enabled, encrypted authenticator data, sync timestamps, device metadata, and subscription status records on our servers
• If VIP is enabled, the minimum subscription and payment records required to determine entitlement status

3. Data Security

We minimize sensitive data exposure and protect sync data with encryption:

• Authenticator secrets and backup data are stored locally in encrypted form rather than as easy-to-read plaintext
• If cloud sync is enabled, the data uploaded to our servers is encrypted before storage
• Our servers keep encrypted payloads plus the minimum account and device metadata required to operate the service
• Payment details are handled by third-party payment providers; we only receive the status and identifiers needed to manage your subscription
• We continue to update implementation details, access controls, and security practices to reduce exposure risk

4. Feature Description

4.1 QR Code Scanning

QR-related features remain local-first:

• When the extension scans a QR code from a web page, the screenshot is processed locally and is not uploaded to our servers
• When the App scans from the camera or a selected image, the QR content is parsed locally
• The parsed secret is only used to create an authenticator entry; whether it syncs depends on the features you enable

4.2 Data Operations

Different features involve different data flows:

• Daily actions such as viewing, copying, and filling codes are handled locally whenever possible
• Backup export creates an encrypted file that you can move to another device
• Imported or synced data may be cached locally to make the app feel immediate on next launch
• If VIP cloud sync is enabled, account creation, edits, ordering, and deletion may sync in the background

5. Data Access

We request only the access required for the corresponding feature:

• Clipboard access: to copy verification codes
• Local storage access: to store codes, preferences, backup metadata, and local cache
• Tab or page access: for extension features such as QR detection and code fill
• Camera or photo access: only when the App scans a QR code or imports from an image
• Network access: for sign-in, membership refresh, cloud sync, help content, and payment status updates

6. Data Deletion

You control how much data stays on the device or in the account:

• You can delete individual authenticator entries or clear local device data
• When signing out, you can choose whether to keep or remove local cached data on the device
• If you stop using cloud sync, new changes will no longer be uploaded
• You can remove local data, uninstall the extension or app, and contact us for account-level requests if needed

7. Third-Party Services

• VIP payments and subscriptions may be processed by third-party providers such as Paddle, Apple, or Google
• The contact form may use third-party email delivery and anti-abuse services
• Those providers process the minimum data they need under their own privacy policies

8. Security Commitment

• We try to keep plaintext exposure and data transmission to a minimum
• We continue to patch known issues and improve the implementation
• We will update this page when the privacy model, sync behavior, or payment flow changes in a meaningful way