Privacy

Your work stays on your devices.

What we store

Waitlist submissions store your email and submission time without creating an account. Within the private service, KeenCow stores website accounts, device ownership, public identity keys, versions, online metadata and essential device-management audit events. Verification codes and connection tickets are hashed.

What stays local

Projects, agent login credentials, conversations, terminal history and usage records are stored on your own devices. KeenCow does not upload these as a cloud backup.

How connections work

The first release uses TLS and WSS through the KeenCow relay. The relay can read data temporarily while forwarding it. Terminal and workspace content is not persisted or included in application logs. This is not end-to-end encryption.

Your control

Public access is currently restricted. Within the private alpha, device owners can disable remote access locally or revoke a device from the website. A remote terminal grants the same execution access as the device owner.