Who processes data, and on whose behalf
Some vendors below run on EZ2Stay's own account and serve every hostel on the platform ("platform-wide"). Others run on a vendor account that each hostel opens and pays for itself — EZ2Stay's software calls that account's API using the credentials the hostel entered, but the hostel is the one with the contract and the data-protection relationship with that vendor ("per-hostel"). The signed Data Processing Agreement for your account is the authoritative reference where this page and the DPA differ.
| Name | Purpose | Data categories | Region | Platform-wide or per-hostel |
|---|---|---|---|---|
| Supabase | Database, authentication, and file storage | Guest and account data, credentials, encrypted secrets | EU (Frankfurt) | Platform-wide |
| Vercel | Web hosting for the platform and marketing site | Request/traffic data, server logs | EU (Frankfurt, region fra1) | Platform-wide |
| Hetzner | API hosting (from September 2026) | Request/traffic data, server logs | EU (Germany) | Platform-wide |
| Cloudflare | Edge network / tunnel in front of the API today, and DNS | Request metadata (no guest content) | Global network, EU-adjacent | Platform-wide |
| SendGrid | Transactional email to guests (check-in links, confirmations, guidebook) | Guest email address, message content | US/Global | Platform-wide |
| Stripe | Card payments and payment status | Payment status and metadata — EZ2Stay does not store full card numbers; card data is handled by Stripe | EU/US | Per-hostel — each hostel connects its own Stripe account |
| Didit | ID document verification and selfie match, on Didit's own hosted page | ID document images, biometric selfies | EU | Per-hostel, and NOT an EZ2Stay subprocessor: each hostel holds its own Didit account and contract, so Didit processes on the hostel's own instructions, not EZ2Stay's |
| Beds24 | Channel manager and PMS sync — bookings and availability from Booking.com, Airbnb, Expedia and direct | Booking details, guest contact info | Depends on the hostel's own Beds24 account | Per-hostel — each hostel connects its own Beds24 account |
| SmartBill | Fiscal invoicing and e-Factura, in beta for Romania | Guest/company billing details | Romania (EU) | Per-hostel — each hostel connects its own SmartBill account |
| sms-gate.app | SMS relayed through the hostel's own Android phone and SIM | Guest phone number, SMS content | Per-hostel phone, wherever it is located | Per-hostel — nothing is shared with other properties on the platform |
| Meta Platforms (WhatsApp), via a linked device | Guest messaging over the hostel's own WhatsApp Business number (linked-device relay) | Guest phone number, message content | Global | Per-hostel — the hostel's own WhatsApp number; EZ2Stay relays messages, it does not operate a shared WhatsApp account |
| Twilio | SMS/WhatsApp messaging and phone verification (OTP) — optional | Guest phone number, message content | US/Global | Per-hostel, optional — only where a hostel configures it; not the default SMS or WhatsApp channel |
| Anthropic | AI concierge — answering guest questions — optional, opt-in per hostel | Guest messages/questions only; no ID documents or biometric images are ever sent (redacted before the request is built) | US/Global | Per-hostel, optional — only when a hostel enables the AI concierge |