Sub-processors
Black Ice engages a small set of vetted sub-processors to deliver the service. Each is bound by a written agreement requiring data protection commitments at least as strict as ours. We give 30 days' advance notice before adding or replacing any sub-processor that handles customer content.
| Vendor | Purpose | Region | Data scope |
|---|---|---|---|
| Supabase (AWS) | Database, auth, file storage, edge functions | EU (eu-central-1) | All customer content |
| Cloudflare | CDN, DDoS protection, edge caching | Global | Request metadata |
| Resend | Transactional email delivery | EU / US | Recipient email + message body |
| Stripe | Payment processing & subscriptions | EU / US | Billing contact + payment metadata |
| GitHub | Optional ontology sync to customer repositories | US | Ontology export payloads (opt-in only, to a customer-owned repository) |
| Lovable | Hosting platform & deploys | EU | Application code, build artifacts |
To subscribe to sub-processor change notifications, contact us — we'll add you to the notification list.
Data residency: all customer ontology content is stored at rest in the EU (eu-central-1). GitHub is the only sub-processor that can receive ontology content, and only where a workspace explicitly enables GitHub Sync — in which case data is pushed to a repository the customer owns and controls. Sync is off by default.