Sub-processors
The providers that process data on our behalf.
Last updated: 4 September 2026
We use the providers below to run Travise. Each processes personal data only on our instruction. Most are covered by a data-processing agreement that forms part of the provider's standard terms; where a provider asks us to accept or sign one separately, we are working through those. We do not sell your data.
| Provider | Purpose | Data shared | Location |
|---|---|---|---|
| Supabase | Database, authentication, file storage | All account and trade data | United States |
| Vercel | Web hosting and delivery | Request data in transit | United States |
| Railway | Hosts the Travise API | All account and trade data in transit, plus server logs | United States |
| Anthropic | Generates the read and coaching from your trade notes | Trade text and figures (no email or account id) | United States |
| Whop | Subscription, membership, and billing | Email, Whop ids, payment status | United States |
| Resend | Sends transactional and lifecycle email | Email address and email content | United States |
| Sentry | Error monitoring | Error diagnostics (PII-minimized) | United States |
| SnapTrade | Broker connection aggregation | Your broker login (entered on SnapTrade's own page or your broker's, never seen by Travise), and the holdings and trade activity it reads for us | United States |
| Interactive Brokers (Flex) | Broker data import (IBKR only) | Positions and executions you import | United States |
| Financial Modeling Prep | Market data for grading | Tickers only (no personal data) | United States |
| Telegram | Alerts us to business events so a small team can respond | Your email and account id; the ticker, direction, asset class and result of a trade you log; your plan; the campaign and landing page you signed up from; an excerpt of a support message you send us; and the reason code if you delete your account | United Arab Emirates |
Every provider in the table is in the United States except one. Telegram, which carries our team alerts, is operated from the United Arab Emirates, a country the European Commission has not found to offer adequate protection. That transfer rests on Standard Contractual Clauses and our own risk assessment, and those alert messages stay in our team's chat history with no deletion timer we can set. We are working to cut these alerts back to an account reference and a link so nothing identifying you goes there at all. Until then you can ask us to keep your data out of them at info@travise.ai.
Meta and Google sit outside the table above. When you consent to analytics cookies, our Meta Pixel sends Meta your browser identifiers and the events you trigger (for example signing up or starting a subscription), and our Google Ads tag sends Google the same kind of browser identifiers plus a one-way code made from your email if you sign up. Both use that data for their own advertising and measurement, so each acts as an independent controller for it, not a provider acting only on our instruction. Meta's pixel does not load at all until you accept analytics cookies. Google's tag does load either way, but declining keeps every advertising permission off, so it sets no cookie, never receives the code made from your email, and gets nothing that identifies you. You can change your choice anytime through Cookie preferences in the footer.
We will post any new provider here before it starts handling your data, and we give at least 30 days' notice for one that processes personal data. For the full picture, see the Privacy Policy.