Last updated: 6 July 2026
A sub-processor is a third-party provider that Engine64 (Control Shift Co Pty Ltd, trading as Engine64) engages to process data on our behalf in order to deliver the service. We keep this page up to date and will notify customers of material changes to the list via this page or by email.
These providers are used to run the platform for all customers.
| Provider | Purpose | Data involved | Location |
|---|---|---|---|
| OpenAI | LLM answer generation and text embeddings | Chat messages, retrieved customer content, conversation analysis | US / Global |
| Cohere | Search re-ranking of retrieved content | Chat query and retrieved content snippets | US / Global |
| Neon | Primary Postgres database | All service data | US / Global |
| Vercel | Application hosting and serving | All application traffic | US / Global |
| Railway | Hosts the website-crawling service (Crawl4AI) | Customer website content being crawled | US / Global |
| Inngest | Background job orchestration | Job payloads including conversation and lead identifiers and message content in transit | US / Global |
| Resend | Transactional email delivery | Customer email addresses and lead notification content when configured | US / Global |
| Sentry | Error monitoring | Error metadata tagged with tenant identifiers; message content and PII are scrubbed by policy | US / Global |
| Langfuse | Optional LLM tracing and observability, when enabled by the operator | Prompts and completions | US / Global |
These providers are engaged only when a customer connects the relevant channel or feature.
| Provider | Purpose | Data involved | Location |
|---|---|---|---|
| Meta Platforms | Only when the customer connects WhatsApp, Messenger, or Instagram channels | Message content and sender identifiers (including phone numbers) | US / Global |
| Cal.com | Only when the customer connects booking | Attendee name, email, phone, and slot times | US / Global |
Where a customer chooses to connect one of the following destinations, Engine64 sends the data the customer directs us to send (for example lead and conversation events). These are customer-directed integrations rather than Engine64 sub-processors — the customer controls what is sent and is responsible for the receiving service — but we list them here for transparency:
Engine64 does not currently process payments and does not use a payment processor. If paid plans are introduced in the future, we will add the relevant payment provider to this page with notice.