Data rights and clearing

1. HarmonyOS in-app clear

After confirmation, the client stops sessions and transports, clears profiles and encrypted credentials, deletes the application-owned HUKS key, clears ArkWeb storage, resets in-memory state, and saves a non-granted reset-complete state.

System audio is temporary media for the active session and has no separate export or delete action; ending the session, disabling audio, or clearing active state releases it. Audio is not included in diagnostic ZIPs.

If clearing fails, the app stays offline and asks the user to retry. This action does not claim to clear system-managed HiLog, crash diagnostics, swap, or platform caches.

2. Windows local clear

Choose the tray clear action or run the documented --clear-local-data command. The cleaner accepts only the consent INI, Agent state, logs, and diagnostics below %LOCALAPPDATA%\HarmonyRemoteWorkbench. It rejects filesystem roots, the user-profile root, program directories, and reparse-point trees.

3. Re-consent and re-pair

After either endpoint is cleared, the prior authorization and pairing-resume state is no longer valid. Further use requires accepting the current policy again and pairing again. Clearing is not uninstalling and does not delete data on a remote host.

4. Diagnostics and feedback

Local diagnostics are not uploaded. You may delete a ZIP directly or use the Windows clear action to remove the application-owned diagnostics directory. For feedback voluntarily sent to the developer, contact exusiai231@qq.com to request access, correction, or deletion. Minimum identity verification may be needed to prevent an unauthorized request.

5. System-managed boundary

The exact retention and clear behavior of system logs and platform caches is Not verified. Manage it through device settings, organizational policy, or applicable uninstall behavior; VaseDesk does not describe unknown platform behavior as cleared.