Crucible — Subprocessors
Last updated: 14 September 2026 · Version 0.1 (Beta)
Crucible engages the third-party providers below to help deliver the Service. Each is bound by contractual confidentiality and data-protection obligations. This page is referenced by our Privacy Policy and Data Processing Agreement. We will update it before adding or replacing a subprocessor.
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Supabase | Managed PostgreSQL database, authentication, and data storage | All Customer Data and account data | United States |
| Vercel | Application hosting, serverless compute, and CDN | Request/usage data; Customer Data in transit through the application | United States |
| Anthropic (Claude API) | AI processing: structuring screen notes, generating documents, summarizing records | The specific record text sent for a given AI action | United States |
| [EMAIL PROVIDER] (pending) | Transactional and authentication email delivery (e.g., invites, confirmations) | Recipient email address and message content | United States |
| [PAYMENT PROCESSOR] (when paid plans launch) | Subscription billing and payment processing | Billing contact and payment details (card data handled by the processor, not stored by Crucible) | United States |
Notes
- Anthropic (AI): AI calls are routed through a single controlled gateway. We use the Claude API under commercial terms that do not permit training on customer data and that apply limited retention. Only the specific text needed for an action is sent.
- No advertising or data-broker subprocessors. We do not share data with advertising networks or sell data to data brokers.
- Fill in
[EMAIL PROVIDER]once custom SMTP is configured (e.g., Resend), and[PAYMENT PROCESSOR]when billing is activated (e.g., Stripe).
To subscribe to change notifications or raise an objection on data-protection grounds, contact privacy@crucible-crm.com.