Where your data lives

On this machine

Your workspace is a PostgreSQL database that kyte brings with it and keeps in its own folder — on macOS under ~/Library/Application Support/kyte. No server to install, no separate database to administer.

The app reads and writes there, always. That is why it works on a train.

When you work as a team

Each device holds its user's own slice — the rows that person's role allows, not the whole workspace. It is stored as an encrypted dump, with the key in the operating system's keychain.

The reasoning is dull and important: encryption cannot protect data from the person holding the key, so the first defence is not holding rows that person may not see at all.

Two people sharing one computer need two operating-system accounts. One OS account is one keychain, and one keychain is one person.

What leaves the machine

• What you send the model. The message and what the agent had to read to answer — unless a model runs on your own network. You can replace personal data before it goes: see personal data in a message.
• Changes, when you sync. To your workspace's server, and to nowhere else.
• Error reports. The fault, never your data — prompts, names and rows are stripped before anything is sent. See version and updates.

Backups

Whatever backs up your machine backs up the database folder. If you keep your documents in a folder of files (see Knowledge), they are covered by whatever already covers that folder.

For a team, the server is the copy that matters, and backing it up is part of running it.

Deleting

Reset / start over on the sign-in screen deletes the local workspace and returns to the setup. It asks first, and it cannot be undone.