Cockpitby VEROXA · updated 29 September 2026

Sub-processors

The companies that process personal data on Cockpit's behalf, what for, and where. Each is bound to use the data only to provide its part of the service and never to train AI models on it. Transfers out of the European Economic Area and the United Kingdom rely on the provider's Standard Contractual Clauses or an equivalent safeguard.

CompanyWhat forWhereData
Oracle Cloud InfrastructureHosting: servers, databases, backupsUnited States (Virginia)All data the service holds
StripeBilling and paymentsUnited StatesAccount owner's name, email, billing details
ResendService email: sign-up, sign-in links, invitations, alertsUnited StatesRecipient email address, message content
Google (Gemini, Cloud)AI writing, pictures, video and voice; reads of analytics you connectUnited StatesBusiness content you ask it to work on; analytics you connect
AnthropicThe assistant (RIZ)United StatesYour messages to RIZ and the business context it needs
OpenAIVoiceoversUnited StatesThe text to be spoken
HeyGenPresenter videos, only when switched onUnited StatesThe script and chosen presenter
ApifyPublic trend dataEuropean Union / United StatesIndustry, country and product words only; no personal data
MakeGoogle Business updates, where that bridge is usedEuropean UnionThe post's text, picture and link

Services that receive no personal data

Public weather forecasts (Open-Meteo: a city name), public news and holiday calendars (GDELT, Nager.Date: an industry, a country) and an outside availability check of our public pages (GitHub).

Changes

We update this page before a new sub-processor starts handling personal data. Account owners who want notice by email can ask at hello@veroxa.co; a data processing agreement is available on request.

Contact

VEROXA LLC · 1480 Crabb River Rd, Richmond, TX 77469, USA · hello@veroxa.co · Privacy policy · Security