BenchCraft privacy notice

Last updated: 2 November 2026

BenchCraft is operated by CogWorks. This notice describes the current pilot. Contact us at dhruv@cogworksai.com with privacy questions or account requests.

Your account

We use Supabase Auth for sign-in. Signing in with Google shares your email address and basic profile information with BenchCraft. Email sign-in uses a one-time verification code delivered by Resend. Account identifiers let us link sign-in methods, manage invitations and associate usage and payments with the correct account.

Google profile information is used for sign-in, account linking and account administration. BenchCraft does not use that profile information to train AI models.

Your workspace and AI requests

Lab programs run on your computer and connected equipment. When you use an AI model, conversation context can include instructions, code, data and tool results from your workspace. Your selected model provider processes that context to produce a response.

BenchCraft-managed models use Microsoft Azure. Background responses can be retained temporarily by the provider to support reconnection and usage settlement. When you bring your own provider account, that provider's terms and data practices also apply.

Usage and payments

Our backend retains account identifiers, invitations, model usage, credit transactions, payment identifiers, refunds, disputes and reconciliation records. These records support accounting, prevent duplicate grants and let us recover interrupted work accurately.

Stripe handles hosted checkout and payment details. BenchCraft stores the identifiers and receipts needed to associate payments with your credit account. Signing out or cancelling a subscription does not by itself erase accounting records.

Service providers and security

We use Supabase for authentication, database and application services; Google Cloud for the portal; Microsoft Azure for managed inference; Resend for sign-in email; Google for optional sign-in; and Stripe for payments. These providers may process information internationally. Service logs can include network and diagnostic information needed to operate the service.

Privileged database and provider credentials stay on the backend. Ordinary accounts cannot access another account's financial records or change their own balances directly.

Retention and your choices

We retain account records while operating your account, and may retain accounting records and backups for payment handling, reconciliation and security. Contact dhruv@cogworksai.com to request access, correction, export or deletion; we will explain any records that need to be retained.

You can sign out, disconnect a provider, use your own model account, or stop using the pilot. Changes to this notice will be reflected in the date above.