Legal

Subprocessors

We use the third-party services listed below to deliver CoreForge Data. We notify customers of material changes at least 30 days before they take effect.

Last updated: October 2026
GDPR · UK GDPRCCPA / CPRASCCs Modules 2 & 3
SubprocessorPurposeData categoriesRegionAgreement
Supabase (Lovable Cloud)Application database, auth, storageAccount, workspace, contact recordsEU / US (region-pinned per workspace)Standard DPA + SCCs
Cloudflare WorkersApplication runtime + CDNHTTP request metadata, encrypted payloadsGlobal edgeCloudflare DPA + SCCs
StripePayments, subscriptions, invoicesBilling contact, card token, invoicesUS / IEStripe DPA + SCCs
FirecrawlPublic web crawling for enrichmentSearch queries, public web contentUSFirecrawl DPA
Google (Gemini via Lovable AI Gateway)AI extraction + scoringPrompt context (no PII inputs by default)USGoogle Cloud DPA + SCCs
Resend (transactional email)Outbound transactional emailRecipient email, subject, bodyUS / EUResend DPA + SCCs
PostHog (product analytics)Product usage analyticsPseudonymous events, IP (truncated)US / EU (configurable)PostHog DPA + SCCs

Change notification

We post material additions or replacements here at least 30 days in advance. Subscribe to notifications by emailing legal@coreforgedata.com.

Object to a subprocessor

Customers with an executed DPA may object in writing within 30 days. If we can't resolve the objection, you may terminate the affected service for convenience.