Privacy
Privacy policy
Crewboard is built so that the board needs very little: your AI logins, your code and your files stay on your computer. This page lists what the board does keep, why, who helps us run it and what you can ask of us.
Who is responsible
Marius Morutan, The Netherlands runs Crewboard and is the controller of the personal data described here. Write to marius@usecrewboard.com with any question or request about your data.
What the board stores
Your account
You sign in with GitHub. We receive your GitHub user ID, username, display name, profile picture and the email address on your GitHub account. People in your parties see your name and picture.
Your parties
A party is the shared board of a team. For each party we keep its name, its members and invite links, the chat messages, the goals and tasks you and your teammates create, their progress lines, short result summaries, links to the pull requests, the names of projects and repositories, notes, approvals and the activity history. Everyone in a party can read that party's content; people outside it cannot.
Your computers and agents
For each computer you connect we keep its name, its operating system, the connector version and when it was last online. For each folder you add: the label you give it and a one-way fingerprint of its path, not the path itself. We also keep the agents you create, the AI tools the connector found and the names (not the settings) of your MCP servers.
Usage
To show how much of each plan is used: token counts, the % used of each limit window, when it resets, the plan type and the account label the AI tool reports. For some tools that label is the email address of your account with that provider.
Sign-in and logs
A cookie keeps you signed in on the board, and the connector holds its own token for your computer, which you can revoke. Our hosting and database providers keep short-lived technical logs, including IP addresses, to keep the service secure and working.
What never leaves your computer
- Your AI logins, tokens and API keys
- Your code, diffs and file contents
- Folder paths on your computer
- Environment variables and MCP settings
Pull requests go from your computer straight to GitHub, with your own GitHub login.
Your AI tools
Crewboard runs no AI models and sends nothing to AI providers itself. Your agents run on your computer through the provider's own tool (Claude Code, Codex, Cursor, Grok Build or Gemini through the Antigravity CLI), signed in with your account. What such a tool sends to its provider, including the tasks it works on, falls under your agreement with that provider and its privacy policy. How Crewboard uses your subscription explains whose account runs what.
Why we use it
- To run Crewboard for you: your account, parties, computers, agents and usage. The legal basis is our agreement with you (GDPR article 6(1)(b)).
- To keep it secure and working: sign-in, technical logs, preventing abuse and fixing faults. The legal basis is our legitimate interest in a safe, working service (article 6(1)(f)).
- To answer you when you write to us, on the same bases.
No ads, no analytics or tracking cookies, and we never sell your data.
Cookies
Only the cookies that keep you signed in, plus one short-lived cookie during GitHub sign-in. They are strictly necessary, so there is no cookie banner. The board also remembers your settings and the last party you opened in your browser's own storage; those stay on your device.
Who helps us run it
- Supabase: database and sign-in. Your data is stored in the EU, in Frankfurt.
- Vercel: hosting. Our server code runs in Frankfurt; Vercel's network serves the pages worldwide.
- GitHub: sign-in. GitHub handles your GitHub login under its own privacy statement.
- Google Workspace: our email, when you write to us.
Each of them processes data for us under its data processing terms. Where one of them is based outside the European Economic Area, as Vercel, GitHub and Google are, the transfer relies on the EU standard contractual clauses or the EU–US Data Privacy Framework in those terms.
How long we keep it
- Account, party, computer and usage data: as long as your account exists.
- Ask us to delete your account and we delete it, with the data tied to it, within 30 days. Backups are overwritten on our database provider's schedule.
- Technical logs: a short time, as our hosting and database providers keep them.
Your rights
You can ask us for a copy of your data, to correct it, to delete it, to limit how we use it, to object to it, or to receive it in a portable form. Write to marius@usecrewboard.com; we answer within one month. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens, or to the authority where you live.
Security
Traffic is encrypted, and the database only lets members read their own party's data. Each computer's connector has its own token that you can revoke from the board. Found a security problem? Write to marius@usecrewboard.com.
Age and changes
Crewboard is not meant for anyone under 16. When this policy changes, the date below changes with it.
Last updated 9 October 2026.