CrewSecurity and your data
Your work on your Mac
Your projects, conversations and agent data stay on your Mac; we do not collect them into Crew's website or membership service. Your AI coding tools may send prompts and project content to the providers you choose, under their own terms and privacy policies. This is separate from Crew's membership records.
Membership lapse makes Crew read-only. Crew never deletes your local work. Deleting your online account does not erase files on your Mac.
What leaves your Mac
We use your email to sign you in (Supabase's sign-in, in your browser). We store membership status, plan type, customer and subscription identifiers, price identifier, billing-period dates, and an update time so Crew can check access.
To check that a membership belongs to your Mac, Crew uses a key created on your Mac. Its private part never leaves the Mac. With each membership check we receive its public part, to verify the check, and we store only a one-way fingerprint of it. For each Mac we store that fingerprint, the Mac model (for example “Mac14,2”), the macOS version, when we first and last saw it and, if you or we sign that Mac out, when. We use this only to run your membership and to count how many Macs each account uses. Crew does not read or send hardware identifiers (such as serial numbers), and we never sell this data.
- Vercel: website and endpoint hosting.
- Supabase EU: account sign-in and membership records in an EU region.
- Resend: planned sign-in and account emails, and a few getting-started emails.
- Paddle: payment processing as Merchant of Record, billing support and refunds.
When Crew checks for an update, your Mac asks our update server whether a newer version exists and, if one does, downloads it. Like any website visit, that server sees your IP address and which version of Crew you have; we use this only to deliver updates.
Your AI providers (for example Anthropic or OpenAI) are not our service providers: you use them under your own accounts and their terms, and we don't receive what you send them.
Read the Privacy Policy for the full account, payment and retention details.
Your approval has its own key
Pairing gives this Mac its own approval key, kept in its Secure Enclave. When you press Allow, your answer is signed with that key, and Crew checks the signature before anything runs.
Pairing this Mac · How approvals work
Sharing your screen
Presenting covers Crew’s own windows. Other apps on your screen show as they are. Before a stream, check what you have marked public and clear Notification Center.
Don’t run first-run setup on stream. Its fields can show what you type. If you show a terminal on stream, viewers can see everything it prints, keys included.
Read the Presenting guide for the controls, version-specific limits and Blank Crew shortcut.
Signed releases
That release will use Crew’s Developer ID signature and Apple notarization before distribution.
If macOS cannot verify the developer or reports damage or malware, stop opening that copy and contact the person who supplied your Crew build. Don’t turn off macOS’s protections to get past the message.
Optional usage counts
The planned “Share anonymous usage counts” setting is off unless you turn it on. Settings › Privacy will show the numbers before anything is sent. If there’s nowhere configured to send them, nothing is sent even if the setting is on.
Report a security problem
If you think you’ve found a security problem in Crew, email support@fift.studio with “Security” in the subject, and please don’t post the details publicly until we’ve replied.
Never send us a password, an API key, a sign-in code or a card number. We never ask for them, and nobody from Crew will.