Privacy FAQ
Frequently Asked Questions About Privacy, Trust, and Data Usage
This document answers the most common questions organizations and individuals ask about how Kaevor handles contextual intelligence, privacy, and workplace signals.
Does Kaevor read my conversations?
No. Kaevor is not designed to read personal conversations, private messages, emails, documents, or meeting discussions. The platform operates on contextual signals — such as meeting density, communication volume, recovery opportunities, interruption patterns, and focus availability — that describe working conditions without revealing communication content. The objective is understanding the environment in which work is happening, not monitoring what is being said.
Does Kaevor store message content?
No. Kaevor’s architecture is built on the principle of Signals Over Content. The system is designed to operate without collecting or retaining communication content wherever possible. The safest information is information that never enters the platform, and this principle is treated as an architectural requirement rather than a policy aspiration.
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, and does not provide managers with visibility into individual communications.
Can my manager see my personal cognitive score?
No. Kaevor is not designed to 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 surveillance, enabling organizations to identify systemic conditions without requiring visibility into personal data.
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, meeting duration, communication intensity, workload patterns, recovery opportunities, focus sessions, and optionally wearable-derived indicators where the user has explicitly consented to that connection. The exact signals available depend on the deployment configuration and applicable consent settings.
Does Kaevor use wearable data?
Only when explicitly connected by the user or organization. Wearable integrations are optional and Kaevor does not require wearable devices to operate. The platform is designed to generate contextual intelligence from multiple signal sources, of which wearables are one possible and entirely voluntary input.
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.
Does Kaevor monitor my screen?
No. Kaevor is not screen monitoring software. The platform does not require screenshots, screen recordings, or any form of continuous visual monitoring to perform contextual analysis.
Does Kaevor log keystrokes?
No. Kaevor does not collect keyboard content, passwords, written messages, or typed documents. Any contextual signals related to activity patterns are designed to capture behavioral indicators without recording the content of what users type.
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, meeting frequency, and calendar density — without requiring access to the content of the meeting itself.
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 details of work activities. In most cases, contextual intelligence can be generated from behavioral and environmental signals without identifying what a user is working on.
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 assessment between individuals. The platform exists to improve working conditions at the individual and organizational level, not to evaluate or judge the people within them.
Can Kaevor be used for employee surveillance?
No. Kaevor was explicitly designed around the principle of Care Without Surveillance. Organizations seeking employee monitoring capabilities, productivity scoring systems, or behavioral tracking tools are not the intended use case for this platform.
Can leadership identify specific employees experiencing fatigue?
The default design philosophy of Kaevor is organizational awareness without individual exposure. The platform is intended to identify patterns of friction, overload, and interruption at an aggregated organizational level rather than to expose the circumstances of specific individuals. Specific deployment models may vary depending on organizational requirements and the governance policies established by the deploying organization.
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 assume ownership of 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. Kaevor is designed to accommodate different trust and compliance requirements, and 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.
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.
Why does Kaevor need contextual signals at all?
Because timing depends on context. A recommendation that is genuinely useful in one moment may become disruptive in another. Understanding contextual conditions allows Kaevor to reduce interruption, protect focus, improve timing, 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.
What is the most important thing to know about Kaevor’s approach to privacy?
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.