SLEEVECAST
Privacy Policy
Last updated: October 30, 2026
This policy explains what personal data [legal entity name and address] ("we") processes when you use Sleevecast, and why. Sleevecast is designed so that your AI agents run on your own machines: much of what they handle never reaches us.
What we collect
| Data | Where it comes from | Why |
|---|---|---|
| Name and email address | Your account (sign-in at auth.sleevecast.com) | To run your account and contact you about the Service |
| Organization data: name, members and roles, specs and their versions, Dock names and machine details (operating system, architecture, Docker and Dock versions) | You and your Docks | To provide the Service |
| Sealed model keys, their fingerprints and last four characters | Your browser | So your Docks can use your keys; we cannot read the keys |
| Sleeve status, lifecycle events (no task text), token counts, the images your sleeves draw | Your Docks | To show your fleet, history and usage |
| Audit log entries: who did what and when | Your use of the console and API | Security and accountability |
| Beta requests: name, email, company and note you send, and a hashed form of your network address | The form on sleevecast.com | To run the beta and limit abuse |
| Technical logs: request paths, status codes, times | Our servers | To operate and secure the Service |
What we do not collect
- Your model keys in readable form.
- What you ask your agents or what they answer: messages pass through while they happen and are not stored.
- Your agents' traces: forwarded only while you watch, never stored.
- Your agents' memory: it stays on your machine.
Cookies
The console uses a session cookie to keep you signed in. The public site at sleevecast.com uses no cookies and no analytics.
Who processes data for us
| Provider | What for |
|---|---|
| Contabo | Servers that host the console, API and database |
| Cloudflare | Network delivery and protection for our sites |
| PikaPods | Hosting of our sign-in service |
| GitHub | Software images and the status page |
| Backblaze | Encrypted backups |
| Paddle | Payment, once paid plans open (as merchant of record, under its own policy) |
How long we keep it
- Lifecycle events are kept for your plan's history period: 7, 30 or 90 days.
- Other organization data is kept while the organization exists and deleted within 30 days after it is deleted, except encrypted backups, which expire on their own schedule.
- Beta requests are deleted when the beta ends.
Your rights
You can see and change most of your data in the console. You can ask us for a copy of your personal data, to correct it, or to delete it, by contacting us at [contact address]. Depending on where you live you may have further rights, including the right to complain to a data protection authority.
Security
See our security page for how keys are sealed, what stays on your machines, and how the Service is protected.
Changes
We will post changes here and, for material ones, notify you in the console or by email.