Subprocessors

Domza relies on a small number of trusted third-party processors to run the service. Each is bound by a data-processing agreement and appropriate transfer safeguards. This page is the authoritative list referenced by our Privacy Policy and the owner Data Processing Agreement.

We will update this page and notify owners by email before adding new subprocessors, so you (as controller of your guest data) can object before new processing begins.

• Amazon Web Services (AWS)

  RoleHosting, database, object storage, compute, video conversion
  RegionIreland (eu-west-1)
  Data categoriesAll operational data at rest: owner accounts, property data, bookings, guest messages, guest registrations and ID-document photos, media, backups
  Websiteaws.amazon.com
  SCC statusEU region; SCCs in place for any out-of-region support

• OpenAI

  RoleAI model inference: the guest AI concierge and issue detection, message translation and language detection, the owner Help assistant, the property setup assistant, media checks and review-request drafts; once switched on for an owner, reading guest messages received through the owner's PMS to detect departure; voice transcription (whisper-1) when a guest or owner uses the microphone.
  RegionUnited States
  Data categoriesGuest and owner message content, the property's AI prompt and the booking context sent with each request, property photos for media checks, and the records an owner's Help question looks up. Once departure detection is on: one guest message received through the PMS at a time, with when it was sent and the planned check-out (the text is not stored by Domza). Voice clips (transcribed, not stored by Domza or OpenAI). API data not used for training; retention per provider terms.
  Websiteopenai.com
  SCC statusSCCs required (US transfer)

• Anthropic

  RoleReads the identity-document photo a guest uploads during guest registration (is it an ID document, and which fields can be read)
  RegionUnited States
  Data categoriesThe guest's ID-document photo and the fields read from it (name, date and place of birth, citizenship, document type, series and number). API data not used for training; retention per provider terms.
  Websiteanthropic.com
  SCC statusSCCs required (US transfer)

• PostHog

  RoleProduct analytics (events sent from our servers)
  RegionEuropean Union (PostHog EU cloud)
  Data categoriesUsage events keyed by internal random IDs (owner, booking, registration) or a hashed email; landing-demo messages with contact details removed. No IP-based location.
  Websiteposthog.com
  SCC statusEU region; DPA

• Stripe

  RoleSubscription billing for owners
  RegionIreland (Stripe Payments Europe) and United States
  Data categoriesOwner email, billing details and subscription status. Card details are entered on Stripe's own checkout page; Domza never sees them.
  Websitestripe.com
  SCC statusSCCs required (US transfer)

• Resend

  RoleTransactional email delivery (sign-up, password reset, owner notifications, guest chat links, invoices to guests)
  RegionUnited States
  Data categoriesRecipient email address and email content (verification and reset links, owner notifications, a guest's chat link, an invoice the owner sends to a guest)
  Websiteresend.com
  SCC statusSCCs required (US transfer)

• Mapbox

  RoleMaps and address search when an owner sets a property's location in the dashboard
  RegionUnited States
  Data categoriesThe address an owner searches for and the map pin's coordinates, plus the owner's IP address (the owner's browser calls Mapbox directly)
  Websitemapbox.com
  SCC statusSCCs required (US transfer)

• Upstash

  RoleServerless Redis: landing-demo cost ledger and per-session message counter
  RegionIreland (eu-west-1)
  Data categoriesDaily aggregate cost totals (USD float) and per-session message counters (integers) keyed by an opaque random session ID. No message content, no IP, no user identifiers.
  Websiteupstash.com
  SCC statusEU region; SCCs in place for any out-of-region support

If an owner turns on browser notifications, they are delivered through the push service built into that owner's browser (for example Google, Apple, Mozilla or Microsoft). The notification content is end-to-end encrypted, so the push service cannot read it.

When an owner connects a property management system (PMS) or a booking-platform calendar, Domza reads bookings from that service on the owner's instruction (and, once switched on, the guest messages it received, to detect departure; Domza never writes to the guest's booking platform). That service is the owner's own provider, not a Domza subprocessor.

Where a subprocessor operates outside the European Economic Area, the transfer is governed by Standard Contractual Clauses (SCCs) or an equivalent GDPR-approved mechanism, as indicated in the table. Data stored at rest lives in the EU (AWS Ireland).

When we add, remove, or change a subprocessor, we update this page and notify owners by email before the change takes effect. For questions about this list or to object to a proposed change, contact privacy@domza.ai.