Telemetry
KolaOS collects a small amount of operational data to keep the product fast and reliable. Your organization decides whether it's shared, and it never includes your code or your team's work.
- Admin controlledOnly an organization admin can turn telemetry on or off.
- Metadata onlyTimings, error codes and versions. Never content.
- Storage regionUS PostHog storage, with EU storage when the EU project is configured.
- AuditedEvery change appears in your organization's audit log.
What we collect
- Performance
- How long actions take.
- Reliability
- Error types and KolaOS error codes, without error messages.
- Versions
- The versions of the KolaOS apps and agents in use.
- Identifiers
- Random IDs for users, organizations and workstations.
What we never collect
- Source code and file contents
- Prompts and model responses
- Session transcripts
- Terminal output
- Clipboard contents
- Passwords, keys and tokens
- Request and response bodies
- Names and email addresses
How it's protected
- Allowed fields onlyEach app sends a fixed list of fields. Anything else is removed before the data leaves the device or server.
- Encrypted in transitData travels over HTTPS to PostHog's ingestion service, and the apps refuse any other destination.
- Send onlyThe key inside KolaOS apps can send data but can't read it.
- Checked before sendingApps confirm your organization's setting before each send. When telemetry is turned off, data waiting to be sent is deleted.
Governance
- Storage
- PostHog Cloud. EU organizations use the EU project when configured. Otherwise telemetry goes to the US project, including for EU organizations.
- Access
- A small group of KolaOS staff, whose access is reviewed regularly.
- Defaults
- Off until an admin of your organization turns it on.
- Changes
- Under Organization, General. A change reaches every app and server within two minutes.
- Deletion
- Turning telemetry off stops new data. To delete data already sent, contact KolaOS.