Privacy

sick.cat keeps your workspaces on its own server, for as long as you chose. Sign-in, tokens and credits are Sykbot's (sykbot.com); GitHub sees only what you send it from Source Control. This page is about the one part of sick.cat that sends your work to other companies: Sick Copilot.

What Copilot sends, and to whom

When you send Copilot a message, the model you picked receives: your message; the workspace's map (each file's path and size, and the names its code defines); its rules file (VENICE.md, AGENTS.md or CLAUDE.md) and any file you pinned; the files and lines Copilot reads to answer; the output of commands it runs in your sandbox; the chat so far (or its summary); and the names of your secrets and variables. It never receives a secret's value: it is told only their names, and commands in the sandbox run without them. Its own tools never read a file that holds secrets (.env and the like, key files). A command could print one, since the sandbox has the workspace's files, so Copilot refuses a command that names a secrets file or prints the environment; and in Write mode, and in Auto unless you allow commands, a command runs only after you have read it and pressed Run. No filter catches every command: read one before you run it.

Depending on the model you pick, that goes to one of these companies:

Terms that differ

What sick.cat keeps

Your chats are stored with the workspace they belong to, count toward its storage, and are deleted with it. sick.cat does not use them for anything but showing them to you and continuing the chat, and keeps no copy of what a provider answered beyond the chat itself. sick.cat's own logs never record a request's address or contents.

sick.cat home