> For the complete documentation index, see [llms.txt](https://appel.gitbook.io/authenticator-an-quan-yan-zheng-ma/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appel.gitbook.io/authenticator-an-quan-yan-zheng-ma/privacy-policy.md). # Privacy Policy Effective date: October 31, 2026\ App: Authenticator / Authenticator — 安全验证码\ Privacy contact: Scope\ This policy explains how the Authenticator app handles information on iPhone, iPad, Mac, and Apple Watch. It also explains support communications and visits to these GitBook-hosted documentation pages. ### Account information stored by the app When you add an authenticator, the app processes the service name, account label (which may include an email address), setup secret, code parameters, preferences, and relevant synchronization metadata. These are used to generate and manage verification codes. The vault is encrypted locally, with encryption keys stored using Apple Keychain. Basic use does not require registration with the developer. The current app contains no advertising SDK, third-party analytics SDK, or cross-app tracking feature. We do not sell your authenticator data or use it for advertising profiles. ### Optional Apple services If available in your installed version and enabled by you, iCloud synchronization transfers an encrypted vault snapshot to your private CloudKit database and synchronizes the vault key through iCloud Keychain. Apple processes account, network, and service information under its own policies. The app stores an iCloud account record identifier locally to detect account changes; it does not receive your Apple Account password. Disabling sync stops app synchronization but does not erase previously stored cloud data. The developer does not operate a server to receive or view your setup secrets. See Apple's privacy information: . ### Paired Apple Watch When you choose accounts to send to a paired Watch, selected TOTP data is transmitted using encrypted app messages and stored in the Watch's local encrypted vault. HOTP is not sent to Watch. Removing an account or authorization on one device should not be treated as proof that all other device copies have been erased. ### Camera, images, screen capture, and authentication Camera frames, images you select, and Mac screen captures are processed locally to detect QR codes. Screen captures are processed in memory and not saved by this feature. The app does not upload captured images to the developer. App lock uses Apple system authentication; biometric templates and your device passcode are not provided to the app. You can manage permissions in system settings. Refusing an optional permission does not prevent manual setup-key entry. ### Clipboard and exported files Copying a code writes it to the system clipboard. The app requests local-only clipboard access and a 30-second expiry on iPhone/iPad; Mac attempts to clear the copied value after 30 seconds if the clipboard has not changed. Other software or user actions can affect clipboard behavior, so do not treat this as guaranteed deletion. Backups are encrypted with your passphrase and saved to a location you select. Migration QR codes contain setup secrets. Copies shared or exported by you are outside the app's control. ### Retention and deletion Active and recently deleted records remain in the encrypted vault until removed through available app or system controls. The current version does not automatically purge Recently Deleted records after 30 days. Disabling sync, deleting an account, or uninstalling the app does not necessarily remove other-device copies, iCloud records, Keychain items, or exported backups. Manage remaining cloud data through Apple's available account/storage controls and remove exported files from their storage locations. Contact support if you need help identifying the applicable controls; we cannot erase data directly from your private Apple account or restore a forgotten encryption passphrase. ### Support requests If you email support, we receive your email address and information you voluntarily provide. We use it to answer and troubleshoot your request, retain it only as needed for support, security, or applicable legal obligations, and do not sell it. Your email provider and our email service may process the message. Please do not send authentication secrets, passwords, recovery codes, or unredacted backup files. You may request deletion of support correspondence by email, subject to any records we must retain. ### Documentation website These pages are hosted by GitBook. Visiting them may involve cookies, IP addresses, browser information, and service logs processed by GitBook under its own policy: . Website processing is separate from the app's local vault; do not paste secrets into website search or feedback tools. ### Children and changes The app is not directed specifically at children, and the developer does not intentionally solicit children's personal information. If you believe a child has sent personal information to support, contact us. We will update this page and its effective date if handling practices materially change. ### Your choices and contact You can use basic offline features without enabling cloud sync, control optional permissions, and contact about privacy questions or support-data deletion. The rights and limits applying to your request may depend on your location. English is the default documentation language; a full Simplified Chinese version is provided on this site.