Data-processing terms for restaurants using OrderNow modules. Effective from: 05.05.2026
This is a base data-processing annex for the individual restaurant agreement, not a standalone online checkbox. It reflects the current product map and Article 28 GDPR structure. The final scope of processing may be specified in the individual agreement with the restaurant.
The processor is: Robert Dziak, operating an unregistered business activity under the OrderNow brand, Warsaw, Poland, unregistered business activity (not entered in CEIDG), contact: kontakt@ordernow.pl, +48 514 192 425.
The restaurant is the controller for personal data it enters into restaurant modules or collects through its own storefront, including guest, customer, staff, courier and supplier data.
OrderNow remains a separate controller for its own account administration, support, security, billing, legal claims and product analytics described in the Privacy Policy.
Depending on enabled modules, processing may include names, email addresses, phone numbers, delivery addresses, table or order identifiers, reservations, order history, loyalty balances, feedback, staff accounts, roles, shifts, courier assignments, supplier contact data and uploaded operational documents.
OrderNow may use the following providers to operate the service. The table is a working subprocessor list for the restaurant agreement annex. It must be verified before signing a final DPA.
| Provider | Purpose | Verification status |
|---|---|---|
| Vercel | Application hosting, deployments, logs, Vercel Blob, optional Vercel Analytics and Speed Insights after consent. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
| Supabase | Application database. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
| Supabase Storage | Private operational file storage. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
| Upstash Redis | Rate limiting and cache. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
| Pusher | Realtime POS/KDS/order/reservation/courier channels. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
| Resend | Transactional email. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
| DeepL | Admin-requested product/menu text translation. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
| Leaflet / OpenStreetMap / Nominatim | Map tiles and delivery-address geocoding where the delivery module sends an address query to Nominatim/OpenStreetMap. | Provider region, transfer mechanism and contractual documents are maintained in B2B/internal documentation and may be updated after provider verification. |
Material changes to sub-processors should be communicated through the Privacy Policy, product notice, email or other durable channel allowing the restaurant to object where required by law or contract.