The subprocessors EZ2Stay uses to run the platform — what each does, what data it sees, and whether it is platform-wide or a hostel's own vendor account.
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 |
| Google (Drive) | Off-server storage of the platform's backups (the database and uploaded files, without the biometric selfies) | Only files encrypted before upload, with a key Google does not hold; Google cannot read their contents | Global | 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 |
| Telegram | Optional staff chat: a team member who connects their own Telegram receives guests' chat messages in the hostel's Telegram bot and can answer from it | Guests' chat messages (text), shown with the guest's name, the booking, the room and the channel; the team member's Telegram chat ID. No ID documents, no biometric images, no payment data | Global | Per-hostel, optional — only when the hostel switches it on for a team member; only that member's own Telegram account receives the messages. Bot chats are encrypted between each device and Telegram's servers, not end to end |
| Anthropic | AI concierge — answering guest questions — and chat message translation (Claude Haiku) — optional, opt-in per hostel | Guest messages/questions only, and the text of chat messages sent for translation; 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 or turns on chat translation in Settings |
Keeping this list current
This list is updated before a new platform-wide subprocessor is added, not after. Customers are notified of subprocessor changes via this page; material changes are also reflected in the DPA's next review.
This is a general list, not a substitute for your contract
This page describes EZ2Stay's general subprocessor practices and is not legal advice. The signed Data Processing Agreement for your account is the governing reference for subprocessor terms.
Contact
Questions about a subprocessor, or to request notice of changes directly: contact@ez2stay.com.