Data Collection Policy
Voidwatch is a privacy-aware product. This page describes exactly what telemetry the beta client collects, how it is used, and what we explicitly do not collect.
Voidwatch collects only behavioral process metadata needed for risk analysis. It does not read your files, capture your screen, record your keystrokes, or access any personal data. All collected telemetry is used exclusively for endpoint risk scoring and product improvement during the beta.
What we collect
What we never collect
- Passwords or credentials of any kind
- Private messages, emails, or chat content
- File contents or document data
- Screenshots or screen recordings
- Browser history or cookies
- Keystrokes or clipboard content
- Personal files or user data
- Location data
How collected data is used
Telemetry is analyzed by the rule engine and ML classifier to assign a behavioral risk score to each process.
Risk-ranked events are displayed in the Voidwatch admin dashboard for manual review and labeling.
Admin-reviewed labels can be exported and used to improve future training datasets and classifier accuracy.
Aggregated behavioral patterns (no personal data) help us improve detection quality during the beta phase.
Data storage and retention
Telemetry is stored on the Voidwatch server hosted at api.voidwatch.eranoid.com. Process records are retained for 7 days by default. Alert records are retained for 30 days. Both retention periods are configurable by the server administrator.
No telemetry data is sold, shared with third parties, or used for any purpose outside of Voidwatch product development and your own endpoint monitoring review.
During the beta, participating users consent to the collection of the telemetry described above. Beta participation can be ended at any time by uninstalling the client.