V0.1 early technical preview
Privacy policy
1. Scope
This policy covers the VaseDesk HarmonyOS client and VaseDesk Windows Connection Helper V0.1. The endpoints form a local-network workbench configured by the user.
2. Permission and consent gate
The HarmonyOS client declares only network access, used to connect to a local endpoint manually selected by the user. Connection management, scanning, and session binding remain off until the user accepts the exact current policy version. The Windows helper also remains offline and does not listen on TCP 8765 before current-version consent.
3. Data processed locally
| Category | Purpose | Local storage |
|---|---|---|
| Connection configuration | Reach a user-selected Windows host | Name, host, port, and public status in ArkData Preferences |
| Credentials and resume tokens | Optional authentication and pairing resume | AES-GCM ciphertext with the application-owned key managed by HUKS |
| Direct RDP session | Connect to a user-selected RDP endpoint, display its output, and forward input | Host, user name, password, domain, and certificate decision state are transient process data; the password field is cleared after submit |
| Windows remote-window session | Capture one user-selected Windows window and carry its pixels through verified libwebrtc media | Remote pixels are processed ephemerally for the active session; they are not persisted as raw frames or written to logs |
| Windows WebRTC system audio | Carry the active remote session's system audio after the user explicitly enables it | Processed only in the active session process and authenticated media transport; no audio file is created, no log entry is written, and no diagnostic ZIP includes it |
| Consent record | Gate initialization and require re-consent | Policy version, decision, timestamp, and reset state |
| Windows state | Identify the helper and validate resume | Local identity and token SHA-256 hash in agent_state.json |
| Logs and diagnostics | Local troubleshooting | Redacted logs and a user-initiated local ZIP |
4. Network transfer
The host and port select the destination chosen by the user. Pairing and resume data go only to the selected helper. Direct RDP is provided by FreeRDP 3.30.0, and its data is processed only between the HarmonyOS client and the selected RDP endpoint. The verified libwebrtc media payload enables Windows remote-window capture and per-session system-audio transport. System audio is sent only after the user explicitly enables it, the active WebRTC session has audio capability, and privacy consent is current. Audio and remote pixels are processed only during the active session; they are not saved as files or raw frames, written to logs, included in diagnostic ZIPs, or uploaded to a developer server. Disabling audio or ending/reconnecting the session does not automatically restore authorization. RDP audio is outside the current capability.
Virtual-display control works only with a user-installed Parsec VDD identified as ROOT\PARSEC\VDA. VaseDesk does not bundle, install, or auto-enable that driver.
There is no application path that uploads logs, diagnostics, or remote content to a developer server. Web browsing is not complete and is not currently offered publicly. This policy does not describe third-party page requests as a current processing path.
5. Retention and backup
Profiles and credentials remain until the user removes them or confirms a clear. Windows keeps the active redacted log and one size-rotated predecessor. Diagnostic ZIP files remain until deletion or clear. HarmonyOS application backup is disabled in V0.1.
HarmonyOS system logs, crash diagnostics, swap, and platform network telemetry are system-managed. Their retention, backup, and clear behavior is Not verified; VaseDesk does not claim to clear them.
6. Your choices and rights
You may decline and remain offline, remove a profile, or use the endpoint clear actions described under Data rights. To request access, correction, or deletion of feedback that you voluntarily emailed to the developer, contact exusiai231@qq.com.
7. Policy changes
When features, permissions, or processing materially change, the policy version will change. An old consent record does not authorize a new policy; the app requires a new choice.