Cobolt8Back to Cobolt8

Effective August 6, 2026 · Private beta

Privacy notice

What Cobolt8 collects

Account data includes your email, display name, organization, authentication records, and membership. A beta application includes the business contact, company, role category, team size, industry, work volume, channels, current tools, primary pain, approval needs, and feedback-call preference you submit. Workspace data includes the teams, workflows, knowledge, artifacts, approvals, integrations, usage, and audit evidence created for your organization. Support requests include the contact, category, priority, summary, details, and immutable intake history you submit.

Why it is used

Cobolt8 uses this data to authenticate users, isolate organizations, operate requested workflows, enforce approvals and budgets, assess private-beta fit, provide onboarding and support, secure the service, investigate incidents, and measure reliability, quality, activation, and cost. Cobolt8 does not enrich beta applications with sensitive personal attributes and does not sell application or workspace data.

Service providers

Vercel hosts the web application and Supabase provides hosted authentication and PostgreSQL data services. Additional AI, media, billing, email, and connector providers are used only when that capability is configured and the documented authorization boundary permits it. Provider credentials are not exposed to browser clients.

Retention and deletion

Beta applications and support records are retained for operating the beta and resolving requests. Workspace records are retained while the organization is active and according to their configured retention class. You may request export or deletion through the support form. Security, approval, billing, incident, or legal-hold evidence may be retained where deletion would break an audit or legal obligation.

Security and access

Cobolt8 uses tenant-scoped database policies, private operational schemas, least-privilege RPCs, protected routes, session controls, immutable evidence, and explicit external-action gates. No system can promise absolute security; suspected security issues should be submitted through the Security category in support.

Your choices

You can decline beta feedback calls, stop using the beta, request correction, export, or deletion, and revoke configured providers through supported account processes. Applying does not guarantee an invitation.

Submit a privacy or data requestRead beta terms