Privacy
Privacy Policy
What this app collects, why it collects it, and what you can ask us to delete.
Authy Authenticator is published on the App Store by ERSIN LTD and on Google Play by Appqe LLC. It keeps passwords and verification codes in an encrypted vault on your device, with optional encrypted cloud synchronisation and recovery in the iOS app.
Your vault
Passwords, authenticator setup keys, passkey private keys, recovery codes and notes are encrypted locally. Vault and recovery keys are not sent in readable form to the sync service. Device authentication protects local access; the app receives an authentication result, not your biometric templates or device passcode.
Imports and QR decoding run on your device. On Android, the camera is used only when you choose to scan a QR code; frames are decoded on your device and are neither saved nor sent. Files you choose, exports, copied values and screenshots remain under your control. AutoFill provides the device's credential system with the identity suggestions needed to find saved credentials.
On Android, if you choose Authy Authenticator as your Autofill service, Android gives it a description of the screen you are filling, including the app or website and its sign-in fields, so it can offer matching saved logins. If you choose it as your passkey and password provider (Android 14 and later), Android tells it which app or website is asking, including that app's package name and signing certificate. If you tap Save when Android offers to save a login, or create a password or passkey with it in another app, the app receives the username and password you entered or, for a passkey, the website and the account name and user ID that the requesting app or website supplies; the app creates the passkey itself and adds the login or passkey to your encrypted vault only after you confirm. The app does not send the app or website details or the screen description to Appqe LLC or to the cloud service, and saved logins are kept only in your encrypted vault. You can turn either integration off at any time in Android Settings.
On iOS, copy actions use a local clipboard with a short expiry. On Android, copied passwords and codes go on the device clipboard marked as sensitive (Android 13 and later hide them from clipboard previews). After the delay chosen in Settings → Lock & biometrics → Clear copied secrets (60 seconds by default), the app clears the clipboard: while the app is open it leaves anything you copied since then in place, but on Android 10 and later an app in the background cannot read the clipboard, so it clears whatever is there, including text you copied in another app. The clear can come later than the chosen delay if the phone is asleep or Android has paused the app, and if Android closes the app first, the value stays on the clipboard until something else replaces it.
Optional cloud accounts
Cloud accounts in this section are available only in the iOS app. Android Google backup uses your own Google account as described below; it creates no Appqe LLC account and does not use the iOS cloud service. The rest of this section, and the cloud-account deletion steps under Retention and deletion, apply to the iOS app.
Apple or Google processes sign-in under its own privacy policy. Authentication requests include provider tokens and security challenges. Apple sign-in also sends its authorisation code to our API for a verified exchange. The service uses the provider's stable account identifier; it does not store a profile name or email address from those tokens.
Our service stores encrypted vault records and recovery snapshots, along with app account and device identifiers, device public keys, record revisions, account/device status and security timestamps. These support signed access, recovery, authorised-device approval, synchronisation and replay prevention. Account sign-in alone cannot decrypt a vault.
An Apple refresh token is retained encrypted with a separate server-held key so the service can revoke Apple access when you delete your cloud account. This provider token can be decrypted by the service for that purpose; it is separate from your end-to-end encrypted vault content.
Android Google backup
Google backup is optional and starts only after you choose Connect Google account. Authy asks for access to its own hidden Google Drive folder and your account email, which it shows so you can identify the backup account. It cannot see other Drive files. New, edited and deleted vault records are encrypted on the device before automatic upload. A save is shown as confirmed only after Drive acknowledges that version; pending and offline changes are separate.
When connecting, save the recovery passkey in Google Password Manager using the same Google account as the Drive backup. Authy verifies its cryptographic recovery capability and uses its high-entropy output to protect the random vault key. The private passkey key stays in the external password manager; the recovery output is used only in memory. It is never an email-, OAuth- or PIN-derived vault encryption key, and the sole recovery passkey is not stored in Authy itself. On a reinstalled app or a new phone, choose the same Google account and recovery passkey and complete the required Google/device verification. You do not need to retain or enter a separate Authy recovery key for this path. Authy cannot attest which Google account a password manager stores a passkey in; the matching choice matters.
Drive holds the encrypted vault and readable technical metadata: random backup/vault/app-instance identifiers, version history and counters, save time, phone model, and public recovery-passkey details (random user handle, credential identifier, public key and salt) with the encrypted vault-key wrap. These identifiers are associated with your chosen Google account; they are not anonymous. Google can read the public metadata, but the vault contents and wrapped vault key are end-to-end encrypted. Appqe LLC never receives them, your Google email or the vault/recovery keys. Google manages its services and synced passkeys under its own terms and privacy policy. Authy uses Google API information only for backup and recovery, following the Google API Services User Data Policy and Limited Use rules.
The app keeps at least three recent backup versions and the newest version from each device; additional versions can remain while needed to merge changes safely. A separate random phone key may be held by Google Play services Block Store, with a cloud copy only through Android's end-to-end encrypted backup route when available. This is an additional route, not the basis of passkey recovery. Older backups can still need their original phone key or Authy recovery key. Manual encrypted exports and local-only use remain available if you decline or cannot complete setup.
Turning backup off stops future saves but keeps the existing Drive backup. Turn off and delete backup removes this vault's Drive versions and phone restore key, clears the backup account on this installation and revokes its Google access. Google Password Manager may retain the external recovery passkey; you can remove it there when no longer needed. Erasing or uninstalling the local app does not delete the Google backup. You can also remove the hidden app data through Google Drive's Manage apps settings. Keep access to your Google account and recovery passkey; support cannot decrypt the vault for you. Use the support page for privacy or deletion help without sending a vault, password or recovery key.
Android usage analytics and crash reports
The Android app uses Google's Firebase Analytics and Firebase Crashlytics to learn which features are used and to fix crashes. They receive the screens you open; completed steps such as finishing setup, creating a vault, an import (with how many records were added, merged or skipped), turning Google backup on or off, a restore or an export; crash details (the failing code location, app version, phone model, Android version and app state); session times; and random identifiers Firebase creates for this installation. Google derives an approximate location (such as city, region or country) from your network address. They never receive vault contents, passwords, passkeys, setup keys, codes, notes, account titles, websites, usernames, file names, your Google account or the advertising ID. The app shows no ads and does not use this data for advertising or to track you across apps. Google processes this data for Appqe LLC under the Firebase terms and keeps crash reports for 90 days and analytics data for up to 14 months. Both are on by default; turn them off in Settings → Privacy & help → Usage analytics and crash reports to stop sending them. The iOS app does not include them.
Network and support requests
Online services process the network address and request metadata needed to deliver, protect and rate-limit requests. Operational logs may contain request paths, status and network metadata. Do not include passwords, setup keys, recovery keys or provider tokens in a support message.
On Android 14 and later, if you choose Authy Authenticator as your passkey provider and an app other than a browser asks it to sign in with or create a passkey, the app downloads the public /.well-known/assetlinks.json file over HTTPS from the website named in that request after you pick it and verify, to confirm the requesting app belongs to that website (a confirmed result is reused for up to a day). The request contains no account or vault data; like any web request, the website receives your network address.
The support page collects the name, reply address, subject and message you submit. These are stored for handling your request and delivered to our support service by server-side email. Our infrastructure and selected authentication providers process requests required to operate these features.
Optional password checks
After your confirmation, a Pwned Passwords check sends a five-character hash prefix to the Pwned Passwords service. The password and full hash are not sent; matching happens on your device. That service receives an ordinary network request, including your network address. A match is a reason to review a password, not proof that an account was compromised. You can leave this check unused.
Retention and deletion
In the Android app, your local vault stays on your device; an optional encrypted Google backup stays in your own Google account. Appqe LLC holds no copy of either. The optional password check sends its five-character hash prefix directly from your device to the Pwned Passwords service; Appqe LLC does not receive or keep it, and that service handles the request under its own terms. Settings → Erase vault from this device removes the local vault after you authenticate, and uninstalling the app also removes its data. The Android app creates no account with Appqe LLC to delete. The separate Google-backup deletion choices are described above.
Local vault data remains until you remove it. Deleted vault records can be restored for 30 days. Erasing the vault from this device is separate from deleting a cloud account, and does not erase exports or copies held elsewhere.
In the iOS app, use Settings → Account & sync → Delete cloud account, then complete reauthentication and confirmation. Confirmed deletion removes cloud vault content, recovery snapshots, sessions and related operational payloads. Known Apple grants are revoked before normal deletion completes. An unavailable or uncertain reply remains retryable; it is not a confirmed deletion.
Limited identity mappings, the deleted-account marker, revoked-device records and deletion proof/outcome receipts remain to prevent retired access from recreating the account and to resolve deletion retries. These security fences have no fixed expiry. If Apple removal could not be confirmed, the iOS app keeps a local reminder to check Sign in with Apple settings and remove Authy if it is still listed.
Support requests and operational security records are retained as needed for their purpose. We do not promise a fixed time-based log expiry. If you need access, correction, deletion or privacy help, use the support page; for the Android app you can also contact its publisher, Appqe LLC, through the developer contact details on its Google Play listing. Never send a vault or recovery key.
Your choices
You can use the local vault without a cloud account, leave optional password checks unused, manage device permissions, and choose when to export or delete data. The app has no advertising, purchases or subscriptions and does not use your data for cross-app advertising tracking. The iOS app has no analytics SDK; Android usage analytics and crash reports can be turned off as described above.
For Android, the following recovery-key advice applies when recovering without a ready Google backup and its external recovery passkey. Keep your recovery key separately. If it and every authorised device are lost, support cannot decrypt or recover your vault. Revisit this page for changes to the app's data practices.