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.
On this page
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, push notifications and app crash reports | Google Firebase and Google Cloud Platform | Your account data, since this is where VEXA runs, and crash reports from the iPhone, iPad and Android apps |
| Usage analytics in the Android app | Google Firebase Analytics | The events the library records on its own, such as app opens and sessions, with an app-instance identifier, the device’s advertising ID where Android allows it, and device details. VEXA’s code sends it nothing else |
| 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 reports from every visitor, with email addresses, IP addresses and cookies removed. When you are signed in, a report carries your VEXA user ID. Sampled performance traces are added only if you accepted analytics cookies |
| Analytics on the marketing site | Google Analytics | Site usage, and only if you accepted analytics cookies |
| Usage analytics in the web app | Google Analytics, through Firebase | The pages you open, by path only with no query strings, and product events such as a confirmed import, and only if you accepted analytics cookies. Google Analytics keeps its own browser identifier in a cookie. No VEXA user ID is attached, and advertising storage and ad personalisation stay off |
| 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
The iPhone and iPad app contains no analytics SDK. The Android app includes Firebase Analytics, in the table above. No app contains an advertising SDK. The cookie banner is a web feature and does not appear in the apps. See Cookies and analytics.
What you should see
If you accepted only essential cookies, the marketing site loads no analytics script. You can confirm this in your browser’s network panel. The web app still loads its error monitoring, because crash and error reports are sent for every visitor.
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 on the marketing site and in the web app, and performance tracing in the web app’s error monitoring, are controlled by the cookie banner. Crash and error reporting in the web app runs for every visitor, because it is how VEXA finds and fixes faults. Firebase Analytics in the Android app has no in-app switch. 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.
Related
Still stuck? Email support@vexatrade.ai.