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. Versions with basic usage statistics also process device and usage metadata as described above, without requiring sign-in.

• 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
• Cloud sync sends required authenticator data over HTTPS, and the server encrypts credentials before storage
• When you subscribe to Pro, 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
• Backup data created during export and import; passphrase-encrypted App backups and extension JSON use different, non-interchangeable formats
• If cloud sync is enabled, encrypted authenticator data, sync timestamps, device metadata, and subscription status records on our servers
• If Pro is enabled, the minimum subscription and payment records required to determine entitlement status
• We retain necessary request methods, request URLs and error logs to operate the service and troubleshoot failures. These logs may contain account identifiers and are not used for advertising tracking

3. Data Security

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

• Local authenticator secrets use encrypted storage. Exports differ: App backups use a passphrase; extension JSON contains unencrypted secrets that you must separately encrypt and protect
• Cloud sync sends secrets and account details over HTTPS. The server encrypts credentials with a protected server-side key before storage; this is not end-to-end encryption
• The server can decrypt credentials for authorized sync requests. Service labels, sync timestamps, account and device metadata are outside the encrypted credentials; this is not data that only the user can decrypt
• 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
• Restore backups in a compatible client of the same kind. App backups require a passphrase; extension JSON is not encrypted. Do not share it through chats, public links or email attachments
• Imported or synced data may be cached locally to make the app feel immediate on next launch
• If Pro 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, payment status updates, and basic usage statistics in versions that support it

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
• In app versions that support account deletion, select Delete Account on the Account screen, verify your identity and confirm permanent deletion. If your version has no such option, use the contact details below
• The deletion process removes account, cloud authenticator, device-link and payment records held by this service and requests deletion of the corresponding RevenueCat customer. Apple-linked accounts require reauthentication to revoke sign-in authorization. A completion email is sent and failed steps are retried. Backup files and copies on other devices are not remotely erased; payment platforms may retain transactions under their own policies
• Uninstalling, signing out or deactivating an account does not delete cloud data. Send privacy or deletion requests through Contact in the app or to [email protected]
• Account data and support emails currently have no uniform fixed retention period and are not automatically cleared merely because the app is uninstalled
• Deleting data or stopping use of the app does not cancel an Apple subscription. Cancel renewal separately in your Apple account subscription settings

7. Third-Party Services

• Pro payments and subscriptions may be processed by third-party providers such as Paddle, Apple, or Google
• iOS purchases use Apple and RevenueCat. RevenueCat receives the app user identifier, purchase and receipt information for verification, restoration, entitlement management and subscription analytics; it does not receive authenticator secrets
• Account verification emails are delivered through Resend, which processes the recipient email address and email content for delivery. Email verification codes are not the secrets used to generate two-factor authentication codes
• Cloud sync is hosted on Cloudflare. Contact requests send your email, message, submission time, IP address and User-Agent to our support mailbox through the configured email service (Resend or an email gateway). The website form also uses Cloudflare Turnstile for abuse prevention
• We do not use this data for advertising or cross-app advertising tracking, and we do not sell user data
• 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