Privacy is architecture, not policy.
Dataken captures desktop activity to power OLi. That is a sentence that requires a precise and defensible privacy story. Here it is.
Activity-graph anonymization
Dataken anonymizes the activity graph as an architectural property of the data layer. This is not a policy overlay or a configuration toggle — it is how the system is built. The activity graph stores structured work patterns, not personally identifiable browsing history.
Privatized LLM inference
Any skill or Ask OLi call that invokes an LLM uses the model provider's privatized-inference feature by default — zero retention, no training on tenant data. For extremely security-sensitive tenants, an open-source isolated-deployment option is available for organizations that commit to the infrastructure cost.
Per-tenant data boundaries
Each customer's rules registry, skills, and activity graph are isolated to that tenant. Cross-tenant data sharing is not a feature. Your data stays in your boundary.
On-device capture
The desktop agent captures and processes activity data on the user's machine. Only structured activity records — timestamp, application, dwell, content type — leave the device. No raw screenshots. No keylogging. No full-screen capture.
Consent your compliance team can defend.
OLi’s capture runs with user awareness and organizational consent. The system is designed so your DPO and compliance team can explain exactly what is collected, where it goes, and how to turn it off — because those answers are architectural, not contractual.
Talk to our security team →