Privacy
How 01crew stores and uses account, work, and diagnostic data while the product is in controlled beta.
Data we collect
Google sign-in gives 01crew basic account information such as account identifiers, name, email, and profile image. On first sign-in, we use that information to create a personal workspace and default project.
When you run a meeting, we store the task, selected crew configuration, meeting messages, interventions, final output, validation reports, and usage data.
- Small artifacts are stored in PostgreSQL.
- Larger artifacts may be stored in S3-compatible object storage when that runtime path is enabled.
- If you attach URLs or ask for web research, the meeting may use public URL snapshots and optional Brave Search results as context.
Provider credentials
Model provider credentials saved through the UI are encrypted at rest with a server-side master key. Runtime credential resolution checks user, workspace, platform, then environment fallback credentials.
The usage ledger records provider, model, cost, latency, and credential id, but product surfaces do not expose raw secret values.
Operational diagnostics and error reporting
Operators can inspect failed runs, queue state, artifact persistence failures, trace ids, session/workspace identifiers, and usage summaries. This is used for recovery, abuse prevention, and reliability work.
In production, when configured, web, API, and worker exceptions may be sent to an error reporting tool. Normal user responses are limited so internal exception details are not exposed by default.
Retention, export, and deletion
Self-serve data export and account deletion screens are not complete in the current controlled beta. Until then, 01crew handles these through operator support.
Saved user/workspace provider credentials can be cleared directly from /setup. Send data export, account deletion, or credential-deletion help requests to support@01crew.com. We may need to verify account ownership before completing a request.