Third-party services VEXA uses

The outside services VEXA relies on to run, grouped by what they do and what kind of data reaches each one.

Same on every platform Updated 26 July 2026

What this does

VEXA is not built end to end in-house. It runs on infrastructure it does not own and calls services it does not operate. This lists them by function, and what reaches each one.

The controlling document is the VEXA Privacy Policy, sections 6 and 13. Where this article and the policy differ, the policy wins.

Before you start

VEXA does not sell your personal information to any of these providers or to anyone else.
A provider that receives your data is contractually restricted to processing it for VEXA, not for its own purposes.
Some of these are your choice. Broker connections, health platforms and Discord only receive data if you connect them.

The services

What it does	Provider	What reaches it
Sign-in, database, file storage, backend functions, hosting and push notifications	Google Firebase and Google Cloud Platform	Your account data, since this is where VEXA runs
AI coaching, chat, voice and scoring	VEXA’s AI service, described in the Privacy Policy as a secure, US-based third-party AI service	Trades, P&L, journal notes, chat messages, voice audio and the biometric summaries listed in How VEXA uses AI with your data
Health data on iPhone and Apple Watch	Apple Health	Nothing. VEXA reads from Apple Health and never writes to it
Health data on Android and Wear OS	Google Health Connect	Nothing. VEXA reads from Health Connect and never writes to it
Sign in with Apple and push notifications on iOS	Apple	Your sign-in identifier and device push token
Automatic trade import	Your broker, through its own API	Read-only requests for your trade history. See What VEXA can do with your broker connection
Market data for charts	Market data providers	The ticker symbols and time windows VEXA needs to draw a chart
Payments on the web	Stripe	Your payment details, which Stripe holds. VEXA does not store card numbers
Payments on iPhone, iPad and Android	Apple App Store and Google Play	Your purchase, which the store handles under its own terms
Error monitoring on the web app	Sentry	Crash and error diagnostics, and only if you accepted analytics cookies
Analytics on the marketing site	Google Analytics	Site usage, and only if you accepted analytics cookies
Community chat and support tickets	Discord	Only what you post there, and only if you link a Discord account

What is not on this list

There are no analytics or tracking SDKs in the iPhone, iPad or Android apps. The cookie banner on the web does not extend to mobile because there is nothing on mobile for it to control. See Cookies and analytics.

What you should see

If you accepted only essential cookies, the web app loads no error-monitoring script and the marketing site loads no analytics script. You can confirm this in your browser’s network panel.

If it doesn’t work

You want the current subprocessor list in writing. Ask support@vexatrade.ai. Sections 6 and 13 of the Privacy Policy are the published position.
You want one of these switched off. Analytics and error monitoring are controlled by the cookie banner. Health platforms, brokers and Discord are controlled by disconnecting them. Infrastructure, AI and payments cannot be switched off individually, because the product does not run without them.

How VEXA protects your data Encryption in transit and at rest, per-user access rules, how broker credentials are held, and the plain statement that VEXA does not sell your data. How VEXA uses AI with your data The consent you are asked for, exactly what each AI feature sends for processing, and how to withdraw that consent on any device. Cookies and analytics What the cookie banner controls, what choosing Essential Only actually switches off, and why the mobile apps never show one.

Still stuck? Email support@vexatrade.ai.