Skip to content
Keelra

Language: ENPL

Book a call

Subprocessors

Last updated 2026-08-19

Keelra uses the following service providers to run the platform. Each processes personal data under data processing terms, and only for the purpose listed.

ProviderPurposeDataRegion
OVHcloudPlatform and database hosting (application, Postgres, workflow orchestration)All platform data: account, workflow, and audit log dataWarsaw, Poland (EU)
AWS Bedrock (Claude)LLM inference for AI workflow steps; default endpoint for EEA clientsWorkflow text sent for processing; identifiers are tokenised before any model call; provider bound by zero-retention and no-training terms. Inference runs in an EU region.Frankfurt, Germany (EU); US-parent (EU SCCs)
Anthropic PBC (Claude, first-party API)Alternative LLM inference endpoint; not the EEA defaultAs above; used where separately agreed, typically for clients outside the EEA. The first-party API offers global or US routing only.United States / global (EU SCCs)
Postmark (ActiveCampaign)Transactional email deliveryName, email address, notification contentUnited States (EU SCCs)
WorkOSAuthentication and sign-inName, email address, authentication identifiersUnited States (EU SCCs)
StripePayments, subscriptions, and invoicingBilling contact and payment detailsEU and United States (EU SCCs)
CloudflareDNS; encrypted database backups (R2)DNS traffic metadata; database backups stored encryptedGlobal network (EU SCCs)
VercelHosting of the marketing site keelra.com only; no platform dataWebsite visitor data and cookie-free analyticsUnited States (EU SCCs)
Google Ireland Limited (Google Tag Manager)Tag container on the marketing site keelra.com only; loads no tag until the visitor consentsWebsite visitor data: page URL, referrer, and identifiers stored in cookies once consentedIreland (EU), with onward transfer to the United States (EU SCCs)
TradeTracker (affiliate network)Affiliate referral attribution and commission settlement on keelra.com only; loads only after the visitor consentsReferral identifier stored in a cookie, plus the lead id of a submitted contact form as the transaction referenceEuropean Union

Self-hosted components

Workflow orchestration (n8n) runs self-hosted on Keelra's own OVHcloud infrastructure in Warsaw. It is part of the platform, not an external subprocessor, so no data leaves our infrastructure through it.

Changes to this list

We update this page before adding or replacing a subprocessor. Questions: hello@keelra.com.