Sub-Processor List
Last updated: March 2026
innbu uses the following sub-processors to deliver its services. All sub-processors are bound by data processing agreements with obligations equivalent to those in the innbu Data Processing Agreement.
| Sub-Processor | Purpose | Data Types | Location |
|---|---|---|---|
| Anthropic | AI agent responses | Guest messages, booking context | US (SCCs in place) |
| Supabase | Database hosting | All tenant data | EU (Frankfurt) |
| Upstash | Redis cache | Session data, real-time events | EU (Frankfurt) |
| Railway | API hosting | Request data in transit | US (SCCs in place) |
| Vercel | Frontend hosting | Browser analytics (if consented) | Global CDN |
| Clerk | Authentication | User emails, names, auth tokens | US (SCCs in place) |
| Stripe | Payment processing | Payment card details, billing info | US (UK adequacy, SCCs) |
| Twilio | SMS/WhatsApp messaging | Guest phone numbers, message content | US (SCCs in place) |
| SendGrid | Email delivery | Guest/host email addresses, message content | US (SCCs in place) |
| Beds24 | Channel management | Property listings, booking data, guest names | UK |
| Langfuse | AI observability | Anonymised prompt/response logs | EU (Frankfurt) |
Last updated: March 2026. innbu will notify you of any changes to this list at least 14 days in advance, giving you the opportunity to object.
Questions about our sub-processors? privacy@innbu.com