Privacy Policy
Applies to Velo One Docs Web App & Desktop Client | Effective Date: September 6, 2026
This Privacy Policy outlines how network communications, continuous database synchronization, and local data are handled across both the Velo One Docs Web Application and the Velo One Docs Native Desktop Application.
Summary Statement: Velo One Docs continuously transmits user-generated document content, state changes, and session metadata over encrypted network protocols to a remote cloud database to facilitate real-time synchronization across clients.
1. Scope of Data Transmission
When operating Velo One Docs (either in a browser or as a desktop executable), the application establishes active, ongoing connections to remote database endpoints. Data transmitted includes:
- Document Content & Editor State: Text, title changes, document metadata, and formatting data are streamed in real-time or near-real-time to maintain cloud persistence.
- Authentication Tokens & Session Keys: Security tokens required to authorize database read/write requests.
- Network Identifiers: Standard transport-layer data (such as IP address and user-agent string) transmitted automatically during HTTPS REST calls and WebSocket connections.
2. Web Version vs. Desktop App Behavior
- Web Version (GitHub Pages): Runs entirely inside the browser DOM. Network traffic occurs between the client browser and the designated remote database API endpoint. No tracking cookies or advertising telemetry scripts are injected.
- Desktop App (.EXE): Executes locally on Windows. It maintains direct, background HTTP/WebSocket traffic to the cloud database endpoint exclusively to execute document sync and state recovery.
3. Telemetry and Third-Party Analytics
Velo One Docs does not sell user data, route document contents to ad-targeting networks, or embed third-party marketing trackers. Network communication is strictly confined to the backend server infrastructure required to operate the document storage service.
4. Executable Integrity & Code Signing
Official Windows builds of Velo One Docs are compiled directly from source code via GitHub Actions and digitally signed to verify binary authenticity and source code provenance.
5. Inquiries & Source Code Transparency
Velo One Docs is open source. For questions regarding code behavior or privacy compliance, please review the public source code repository or open an issue on GitHub.