Subprocessors
Last updated: June 4, 2026
Template — pending legal review.
This document is the bhildOs starting template. It will be reviewed by counsel before bhildOs takes its first paying customer. If you're evaluating bhildOs and need a counter-signed version, email legal@bhildos.com.
bhildOs uses the third-party services below to deliver the platform. We list each subprocessor along with the purpose, the categories of data they receive, and where the data is processed. Customers can subscribe to subprocessor change notifications by emailing legal@bhildos.com.
Per the Data Processing Addendum, bhildOs imposes equivalent data protection obligations on each subprocessor and remains liable for their performance.
| Subprocessor | Purpose | Data | Region |
|---|---|---|---|
Vercel Privacy policy ↗ | Hosting + edge networking for the bhildOs application. | All application traffic. | United States (us-east). |
Supabase Privacy policy ↗ | Managed Postgres database, file storage (call recordings, photos, tenant logos), and authentication. | All customer business data, end-caller records and recordings, integration tokens. | United States. |
Twilio Privacy policy ↗ | Inbound + outbound voice telephony, SMS messaging, phone number provisioning. | Phone numbers, voice call metadata, SMS message bodies, A2P 10DLC registration data. | United States. |
Vapi Privacy policy ↗ | Real-time voice AI orchestration (STT, LLM, TTS pipeline) for the AI receptionist. | Live voice audio, transcript, assistant configuration. | United States. |
Anthropic Privacy policy ↗ | Claude models for post-call lead extraction, the knowledge interview, the onboarding concierge, and the feedback categorizer. | Call transcripts (post-call), knowledge base content, concierge chat content. | United States. |
Inngest Privacy policy ↗ | Background workflow orchestration (Inngest Cloud). | Event payloads referencing tenants, calls, appointments, and other bhildOs entities. | United States. |
Stripe Privacy policy ↗ | Subscription billing for bhildOs customers; Stripe Connect Express for tenant-to-customer deposit collection. | Billing details, payment methods, Connect onboarding KYC. | United States. |
Resend Privacy policy ↗ | Transactional email delivery (lead alerts, weekly digest, magic-link logins via Supabase Auth custom SMTP). | Email addresses, message content. | United States. |
Google (Maps + Calendar + Ads + Business Profile) Privacy policy ↗ | Geocoding, distance matrix, calendar free/busy sync, conversion uploads, GMB call tracking. Per-tenant OAuth tokens are encrypted at rest. | Addresses, calendar event metadata, hashed PII for conversion uploads (per-tenant configuration). | United States (Google Cloud). |
HubSpot Privacy policy ↗ | Optional per-tenant CRM push for qualified leads. | Contact records for qualified leads (per-tenant configuration). | United States. |
Meta (Facebook) Privacy policy ↗ | Conversions API (CAPI) for optional ad attribution. | Hashed PII (email, phone) and event metadata for conversion uploads (per-tenant configuration). | United States. |
Microsoft (Bing Ads) Privacy policy ↗ | Conversions API for optional ad attribution. | Hashed PII and event metadata (per-tenant configuration). | United States. |
NOAA Privacy policy ↗ | Public weather and climate data used to seed the knowledge base auto-populate pipeline. | ZIP code only. | United States. |
Change notifications
We update this page whenever we add or remove a subprocessor. Customers who have requested notifications will also receive an email at least 30 days before any change takes effect. To object to a new subprocessor, email legal@bhildos.com within 30 days of the notice.
How we choose subprocessors
Each subprocessor is selected for a specific function we cannot perform in-house and is vetted on:
- Security posture (SOC 2 / ISO 27001 / equivalent).
- Data residency and transfer mechanisms.
- Published privacy policy and DPA terms.
- Operational reliability track record.