These are the vendors Casewave uses to provide the service ("subprocessors"), what each one does, and what data it handles. For agents: we keep this page current, and material changes are announced here and by email.
| Vendor | Purpose | Data categories | Location |
|---|---|---|---|
| Cloudflare | Application hosting, networking, queuing, and transactional email delivery | Application data in transit; email content and addresses | US |
| Vercel | Web application hosting (the agent app and client portal front end) | Request data in transit and in memory while serving pages; no service data at rest | US |
| Neon | Database hosting (Postgres) | Service data at rest (with the protections described in the Privacy Policy §8) | US |
| Clerk | Sign-in and authentication | Account identifiers, email, phone, authentication events | US |
| Stripe | Subscription billing (agents) | Billing contact and payment status; card details are collected by Stripe directly and never touch Casewave | US |
| DocuSign | E-signature; system of record for executed documents and the sensitive fields entered in them (Privacy Policy §2) | Signer identity, envelope contents and status | US |
| BoldSign | E-signature for the intake flow (ADR-0054); system of record for the sensitive fields a prospect enters at signing | Signer identity, intake document contents including containment-tier fields (SSN, driver's licence, health) typed directly into BoldSign. Casewave stores only document ids and status; the signed PDF is emailed by BoldSign straight to the agent and never transits Casewave | US |
| Amazon Web Services (KMS) | Encryption key operations only | No personal data transits AWS — key material operations only | US |
| Anthropic | AI model provider for Casey | Conversation content processed to generate responses | US |
Changes. When we add or replace a subprocessor that will process client data, we will update this page and notify agents by email.
Questions: [email protected].