RTAuthenticator Privacy Policy (HarmonyOS v1.0.1 / 105)

Updated: November 2, 2026

RTAuthenticator is provided by Zhang Zhibao (张治保, “we”) to manage two-factor authentication tokens on this device, generate TOTP/HOTP codes, and import accounts through scanning, photos, manual entry, and Google Authenticator migration data. This statement describes how we handle your personal information.

We value your personal information and privacy and provide appropriate safeguards in accordance with legal requirements and established industry security standards.

The following summary explains the purposes, methods, and scope of personal information processing. In addition to the main features, the following processing activities apply:

Version 1.0.1 is free with no ads, registration or automatic cloud sync. Tokens are encrypted locally. The app supports user-initiated encrypted backup and compatible 2FAS/Aegis/Bitwarden file import. It does not automatically upload tokens or selected files. You choose any encrypted backup recipient through the system interface. Optional scanning, photo recognition and biometrics can be replaced by manual entry and a local password. Engine diagnostics are disclosed separately. Contact: rowstop@yeah.net.

1. How We Collect and Use Personal Information

We use personal information only where there is a lawful basis, such as your consent, necessity for entering into or performing our contract with you, or compliance with legal obligations, as permitted by applicable law.

1.1 We provide local token management, code generation, scanning/migration and file import, encrypted backup/restore, and optional secure unlock. These features require the information needed to perform our contractual obligations. Without it, the corresponding features or services may be unavailable.

With your consent, the app processes local token data: service and account names, OTP secrets, algorithms, code lengths, intervals, HOTP counters, verification codes, import links, and migration QR contents. Secret keys are sensitive authentication credentials used only on this device for import, code calculation, and encrypted storage; they are not uploaded to us or third parties. Local unlock data includes temporarily entered passwords, password derivation parameters, encrypted records, quick-unlock settings, system authentication results, and enrollment-state checks. Plaintext passwords and raw face or fingerprint samples are not stored. Photos are read only when you actively select them. Copying writes a code to the clipboard only at your request; the app does not browse clipboard contents.

“Collection” here means local reading and processing after you enter or select data. The app does not automatically upload tokens or selected files. User-initiated system save/share passes only encrypted backups to the chosen recipient. Camera, photo import, and biometrics are optional; you can use manual entry and a password instead. Keep secrets, QR codes, and verification codes secure to protect your accounts.

2. Third-Party SDKs

Some features use partners' software development kits (SDKs) or similar software. We evaluate their security and require partners to protect personal information. SDKs may change as services or functionality evolve, and we will disclose updates here. SDK versions or policies may change the data involved; consult their official disclosures.

SDK 1

Company: DCloud (Beijing) Network Technology Co., Ltd. (数字天堂（北京）网络技术有限公司)

Product/type: DCloud App Engine (uni-app x, 5.34)

Information types: Engine diagnostics may process device brand/model, processor and display parameters, OS/version, network type and IP address, user agent, language/time zone, emulator or root status, and random anonymous identifiers; app name/package/version/AppId/SDK composition, exception stacks, startup time, and memory use. Support varies by platform. Random anonymous identifiers do not include OAID, IMEI, IDFA, or Android ID. Token secrets, verification codes, camera frames, vault passwords, and raw biometrics are outside this diagnostic scope.

Purpose: Provide native cross-platform runtime support and diagnose engine performance, crashes, or errors to identify problems and improve stability. Diagnostics do not include token secrets, verification codes, imported QR codes, passwords, or raw biometric samples.

When used: Engine performance and error diagnostics during app operation, subject to user authorization and platform support.

Collection method: The engine SDK processes diagnostic information directly under its own disclosures. The local token vault is not passed to the SDK.

Third-party privacy policy: https://dcloud.io/license/appprivacy.html

3. Managing Your Personal Information

You may exercise statutory rights including access, copying, correction, and deletion in the following ways.

3.1 Access

Unlock the home token list with your password or enabled quick unlock to view service names, account names, authentication types, codes, countdowns, or HOTP counters.

3.2 Correction

You have the right to correct or update personal information when necessary or when it is inaccurate.

Open Home > token “Manage” > “Edit Name” > Save to change the service or account name.

3.3 Deletion

Open Home > token “Manage” > “Delete Token” > confirm to delete the account record and local key. Recovery requires a valid backup and its password. External files are not deleted. Keep a recovery method for the third-party service first.

3.4 Withdrawing Consent

Cancel the current operation in the scanner or system photo picker. See “Local Data Protection and Optional Features” for removing saved data and withdrawing quick-unlock authorization.

For other questions, comments, or requests about your data rights, contact us as described under “Contact Us.”

4. Storage Location and Retention

4.1 Unless otherwise required by law, information is retained only for the shortest time necessary to fulfill its processing purpose.

4.2 Diagnostics collected during operations in China are transmitted to and stored on DCloud servers in China as described under “Third-Party SDKs.” Core data such as tokens stays on the device and is not uploaded to any server.

5. Local Data Protection and Optional Features

Applies to RTAuthenticator (行止密令), HarmonyOS v1.0.1 (105), bundle ID top.rows.cloud.security.ml.
1. The app is free, without ads, registration, paid services or automatic cloud sync. Token data is processed locally and encrypted on this device. The operator does not receive your vault and cannot reset passwords or recover secret keys remotely.
2. Local data includes service/account names, OTP secrets, types, algorithms, digits, periods, HOTP counters, current codes, import links and QR results. Unlock processing uses temporary passwords, derivation parameters, encrypted records, biometric capability/results and enrollment-state checks. Plaintext passwords and raw face/fingerprint samples are not stored. Token secrets are sensitive authentication credentials; keep them private.
3. On HarmonyOS, opening the scanner requests camera permission. System Scan Kit processes the camera preview locally to recognize QR codes. Capture stops when scanning finishes or you cancel or leave the page; preview frames are not saved or uploaded. For photo recognition, the app reads only the image you select through the system file picker and decodes it locally. It does not scan your entire photo library or upload the image or QR content. You may decline camera access or cancel photo selection and enter a secret manually. Pasted import content is supplied through system input; the app does not traverse the clipboard. Copy writes only the current code.
4. Biometric quick unlock is optional, enabled after a local password and separate agreement. System authentication handles raw biometrics. Enrollment-state checks prevent reusing authorization after enrollment changes. Use the password if unavailable. To remove all local unlock data, secure your recovery methods and clear app data; this also deletes the local vault.
5. Local retention follows your use/deletion. HarmonyOS Asset Store protects the local key with cross-device key sync disabled. Without a valid backup and its password, uninstalling, clearing data, device loss/damage or losing the unlock password may make tokens unrecoverable. Deleting local tokens does not delete external backups.
6. There is no online account to cancel. Access, rename or delete tokens locally. Email privacy requests to rowstop@yeah.net; we reply within 15 business days. Provide only necessary descriptions/contact details, never authentication credentials. Support correspondence is retained only as needed, subject to legal retention duties.
7. The app is not specifically directed at children and does not collect ages, identity or guardian records. Minors should use it under guardian guidance; users under 14 need guardian consent and help with authorized accounts, permissions and recovery methods. Local token data is not used for ads or profiling. Guardians manage device data locally; the operator cannot remotely access or delete it.

When you initiate backup or import, the app reads the selected file location and contents in an unlocked session to validate, decrypt, preview and merge OTP records. A system file provider may supply the file. The app does not automatically scan your files or upload the selected file. Cancellation or leaving the page ends read-only waiting. Entering the background clears account previews and passwords; third-party files are read again after unlocking.

Export creates an encrypted .rta file locally after local password verification. It contains account data such as service/account names, OTP secrets, types, algorithms, digits, periods and HOTP counters, encrypted within the file. It contains no plaintext unlock password or raw face/fingerprint samples. The system save/share interface passes ciphertext to the destination you choose. The app does not schedule cloud backups. Your chosen destination may be another app, file service or cloud provider; its subsequent processing and storage locations depend on that service and your choices.

Export writes ciphertext to the app cache. Cancellation or failure attempts to clean it up. After successful handoff, the encrypted cache is temporarily retained so the recipient can read it, then managed under the system's cache rules. This cache is not a reliable device-migration backup. Import plaintext is processed only in unlocked-session memory and is not saved as a plaintext temporary file, log or clipboard content.

You export 2FAS, Aegis or Bitwarden files in the original app, then select them through the system file picker. RTAuthenticator does not connect to those services' accounts or servers. It saves only supported OTP records to the local vault; Bitwarden passwords, notes, cards and other non-OTP fields are not added. Encrypted third-party files, unknown versions or invalid OTP parameters are rejected. The app does not automatically delete the source file. After verifying migration, manage external files and copies held by recipients yourself.

You may request explanations, access, copying, correction, deletion or withdrawal of consent. If remote handling is technically impossible, we explain available local options. Withdrawal does not affect earlier lawful processing. New purposes, data types, recipients or optional services are disclosed and any required consent obtained separately. Security incidents are addressed and notified as required by applicable law. DCloud states that diagnostics collected during operations in China are stored in China; runtime and platform capabilities affect diagnostics. The server-location statement applies to diagnostics, not the local vault.

6. Contact Us

Email: rowstop@yeah.net

Operator and personal information handler: Zhang Zhibao (张治保). Email: rowstop@yeah.net. Send access, correction, deletion, withdrawal, or other requests by email. We will reply within 15 business days of receipt. Do not send token secrets, QR codes, vault passwords, or valid verification codes.

If you are dissatisfied with our response, particularly where processing infringes your lawful rights, you may seek relief from a court with jurisdiction, an industry self-regulatory organization, or the relevant government authority. You can also ask us about possible complaint channels.

Effective: November 2, 2026