Provider register

Core subprocessors are engaged by QRaff to operate the service. Merchant-directed integrations are enabled by the Merchant and may involve separate or mixed privacy roles under the provider's terms.

core subprocessor

Railway Corporation

Provider privacy terms

Purpose: Backend, database, cache, queues and production infrastructure
Data scope: Hosted application data and request metadata required to operate the service

core subprocessor

Vercel Inc.

Provider privacy terms

Purpose: Web application hosting, serverless execution and content delivery
Data scope: Web requests, hosted content and application data processed by deployed surfaces

core subprocessor

Google LLC and applicable affiliates

Provider privacy terms

Purpose: Asset storage, location lookup, authentication and Firebase messaging where enabled
Data scope: Assets, location queries, authentication identifiers and push-delivery tokens as applicable

core subprocessor

Plus Five Five, Inc. (Resend)

Provider privacy terms

Purpose: Transactional email delivery
Data scope: Recipient address, message content and email-delivery metadata

core subprocessor

OpenAI contracting entity specified by its DPA

Provider privacy terms

Purpose: AI-assisted menu, text and translation features when enabled and invoked
Data scope: Prompts and selected venue content sent for the requested AI operation

merchant-directed integration

Stripe contracting entity

Provider privacy terms

Purpose: Optional payments and Stripe Connect onboarding
Data scope: Payment, account, transaction and compliance data required by Stripe

merchant-directed integration

Wolt and applicable affiliates

Provider privacy terms

Purpose: Optional delivery fulfilment selected by the Merchant
Data scope: Order, recipient, address and delivery-instruction data needed for fulfilment

merchant-directed integration

Dotykačka and applicable affiliates

Provider privacy terms

Purpose: Optional POS synchronization selected by the Merchant
Data scope: Catalog, order, payment-status and operational POS data needed for synchronization