Subprocessors
Last updated October 27, 2026
We use third-party subprocessors — cloud providers, payment and email services, and the AI and search platforms Beai queries — to run Beai Cloud.
This page lists them. It applies to Beai Cloud only. If you self-host Beai, you choose your own infrastructure and providers, and none of this applies to you.
Infrastructure
| Subprocessor | Purpose | Location |
|---|---|---|
| Railway | Application and background-worker hosting | United States |
| Vercel | Marketing site and documentation hosting, edge network, and file storage | United States |
| Supabase | Managed PostgreSQL database | United States |
| Upstash | Cache for public marketing-site data | United States |
| Amazon Web Services | Underlying cloud infrastructure and object storage | United States |
| Google Cloud | Underlying cloud infrastructure | United States |
| Neon | Managed PostgreSQL database | United States |
| PlanetScale | Managed database hosting | United States |
| Hetzner | Server hosting and cloud infrastructure | Germany and United States |
Running the business
| Subprocessor | Purpose | Location |
|---|---|---|
| Stripe | Payment processing, subscriptions, and invoicing | United States |
| Resend | Transactional email — verification, invitations, billing notices | United States |
| "Sign in with Google" authentication, and icons for the domains shown in the product | United States | |
| Cloudflare | Bot protection (Turnstile) on email sign-up, sign-in, and password reset | United States |
| Mux | Video hosting and playback on our website | United States |
| Sentry | Application error monitoring | United States |
| PostHog | Product analytics | United States |
| Plausible | Cookieless web analytics | European Union |
| Google Analytics | Web and product analytics | United States |
| Microsoft Clarity | Product analytics and session replay | United States |
| Crisp | Live chat support on our website | European Union |
| Loops | Product and marketing email | United States |
| beehiiv | Newsletter publishing and delivery | United States |
| Substack | Newsletter publishing and delivery | United States |
Advertising
We may load advertising and conversion-measurement tags from these platforms on our marketing site, our public demo, and the signup and plan-selection pages of Beai Cloud, subject to your cookie choices. These platforms receive information about ad clicks and signups, along with a hashed copy of your email address when you sign up or subscribe, not the contents of your Beai account.
| Platform | Purpose | Location |
|---|---|---|
| Google Ads | Conversion measurement and remarketing | United States |
| Meta | Conversion measurement and remarketing | United States |
| Conversion measurement and remarketing | United States | |
| X | Conversion measurement | United States |
| Conversion measurement | United States |
AI and search data providers
This is the part that makes Beai work: to measure how answer engines describe a brand, Beai has to ask them. Prompts you configure are sent to these providers, either directly through their APIs or through a scraping provider that queries the consumer product on our behalf. The answers come back to us, are stored in your account, and are analyzed to see how they describe the brands you track.
What they receive is what you've configured in Beai — your prompts, which are market-research queries like "best project management software for agencies", and for some features your brands, competitors, tracked domains, and text from your website — rather than your name, email address, or billing details. Do not put personal data into a prompt.
Which of these is used depends on the platforms your plan tracks and how Beai Cloud is configured at the time.
| Provider | Role | Location |
|---|---|---|
| OpenAI | Model API, and analysis of collected answers | United States |
| Anthropic | Model API, and analysis of collected answers | United States |
| Mistral | Model API | France |
| TypeSafe | Analysis of collected answers: which brands they mention, and the sentiment toward each | United States |
| OpenRouter | Model API gateway | United States |
| Bright Data | Answer-engine and search result collection | Israel |
| Olostep | Answer-engine and search result collection | United States |
| Oxylabs | Answer-engine and search result collection | Lithuania |
| Cloro | Answer-engine and search result collection | Malta |
| DataForSEO | Search engine result data | Estonia |
| SearchApi | Answer-engine and search result collection | United States |
| Jina AI | Web page content extraction | Germany |
Getting notified when this changes
This page lives in the Beai repository. Watch that folder on GitHub to see changes to this list.
If you have a signed agreement with us that requires advance notice of new subprocessors, we'll email you as well. To object to a new subprocessor, email privacy@elmohq.com.