Privacy FAQ
Common Questions About Privacy, Data Use, and Trust
The Short Answer
Kaevor does not read messages, emails, meeting content, or documents. It does not monitor screens, log keystrokes, or profile individual employees. It operates on contextual signals — patterns that describe working conditions without revealing what people are communicating.
The questions below provide more specific answers for organizations and individuals evaluating the platform.
What Kaevor Does Not Access
Does Kaevor read my conversations?
No. Kaevor does not read personal conversations, private messages, emails, documents, or meeting discussions. The platform operates on contextual signals — such as meeting density, communication volume, recovery opportunities, and interruption patterns — that describe working conditions without revealing communication content.
Does Kaevor store message content?
No. The system is designed to operate without collecting or retaining communication content wherever possible. This is an architectural requirement, not a policy aspiration. The safest information is information that never enters the platform.
Does Kaevor monitor my screen?
No. The platform does not require screenshots, screen recordings, or any form of continuous visual monitoring.
Does Kaevor log keystrokes?
No. Kaevor does not collect keyboard content, passwords, written messages, or typed documents.
Can Kaevor listen to meetings?
No. Kaevor does not record conversations or listen to meeting discussions. Where meeting-related signals are used, they are limited to contextual metadata such as meeting duration, frequency, and calendar density — without requiring access to meeting content.
Can Kaevor access health records?
No. Kaevor does not access medical records, clinical histories, diagnoses, prescriptions, or healthcare systems of any kind. The platform is not a medical device and does not provide medical diagnosis, clinical assessment, or health recommendations.
Can Kaevor identify what I am working on?
Not in general. Kaevor’s objective is to understand working conditions rather than the specific content or subject matter of work. Contextual intelligence can be generated from behavioral and environmental signals without identifying what a user is working on.
What Kaevor Does Use
What kind of information does Kaevor use?
Depending on the integrations enabled by the organization and the user, Kaevor may process signals such as:
- Meeting schedules and duration
- Communication intensity and frequency
- Workload patterns
- Recovery opportunities and focus session windows
- Interruption patterns
- Optionally: wearable-derived indicators where the user has explicitly connected a device
The exact signals available depend on deployment configuration and applicable consent settings.
Does Kaevor use wearable data?
Only when explicitly connected by the user or organization. Wearable integrations are optional. The platform does not require wearable devices to operate, and this remains an entirely voluntary signal source.
Why does Kaevor need contextual signals at all?
Because timing depends on context. A recommendation that is useful in one moment may be disruptive in another. Understanding contextual conditions allows Kaevor to reduce interruption, protect focus, support recovery, and minimize unnecessary interactions. The objective is not data collection — it is understanding enough context to act responsibly and at the right moment.
Who Can See What
Can my manager see my messages?
No. Managers cannot access private messages, conversations, emails, documents, or communication content of any kind through Kaevor. The platform is not designed as a monitoring or surveillance tool.
Can my manager see my personal cognitive score?
No. Kaevor does not expose personal wellbeing metrics, cognitive scores, or individual performance indicators to managers or leadership teams. The platform focuses on aggregated organizational patterns rather than individual data.
Can leadership identify specific employees experiencing fatigue?
The default design philosophy is organizational awareness without individual exposure. The platform is designed to identify patterns of friction, overload, and interruption at an aggregated organizational level — not to expose the circumstances of specific individuals.
Specific deployment configurations may vary depending on organizational requirements and the governance policies established by the deploying organization.
Does Kaevor use AI to profile employees?
No. Kaevor is not designed to create behavioral profiles for performance evaluation, disciplinary actions, employee ranking, or any form of comparative individual assessment. The platform exists to improve working conditions — not to evaluate or judge individuals.
Can Kaevor be used for employee surveillance?
No. Kaevor was designed around the principle of Care Without Surveillance. Organizations seeking employee monitoring capabilities, productivity scoring, or behavioral tracking tools are not the intended use case for this platform.
Data Ownership and Control
Who owns the data?
The organization owns its operational signals. Individuals retain ownership of the personal context they choose to share. Kaevor’s role is to generate contextual intelligence from those signals on behalf of the organizations and individuals it serves — not to acquire ownership or control over customer data.
Can organizations control what data is shared with Kaevor?
Yes. Organizations maintain control over integrations, signal sources, deployment configurations, retention policies, and governance settings. Organizational administrators retain the authority to configure and modify these parameters at any time.
Can users opt out of certain data sources?
This depends on the organizational configuration and deployment policies in place. Where supported by the deployment model, users may choose whether to connect optional signal sources such as wearable devices. The availability of individual opt-out controls is subject to the governance framework established by the deploying organization.
How long is information retained?
Retention policies are determined by organizational requirements and deployment configuration. Kaevor promotes data minimization and encourages retaining only the information necessary to deliver contextual intelligence. Organizations are responsible for defining retention policies consistent with their regulatory obligations and internal governance standards.
Compliance and Regulatory
Is Kaevor compliant with privacy regulations?
Compliance requirements vary by jurisdiction and deployment environment. Kaevor is designed around principles that support modern privacy frameworks — including data minimization, transparency, user agency, contextual necessity, and governance controls.
Organizations remain responsible for configuring their deployments in accordance with the specific regulatory obligations applicable to their industry and jurisdiction.
The Most Important Thing
Kaevor was designed around a principle that should not require compromise: people should not have to sacrifice privacy in order to receive support.
The platform exists to understand conditions, not conversations — patterns, not personal thoughts — signals, not content.
Contextual intelligence should strengthen trust. Not require its surrender.