Clear, factual information on how QRTebly processes guest service requests, venue accounts, and browser storage based on our actual system implementation.
Effective date: November 2026When a guest scans a QR code and sends a request, QRTebly processes the selected request type (such as calling a waiter, ready to order, bill request, table cleaning, or hotel room assistance), request status (Pending, Completed, or Cancelled), the public table or room token, table or room label, assigned waiter snapshot, timestamps (created, completed, cancelled, archived, and elapsed waiting duration in Asia/Riyadh time), and random UUID receipt keys used to prevent duplicate submissions. Guests do not create accounts or provide names, phone numbers, or email addresses. For venue staff and platform administrators, QRTebly processes login email addresses, authentication session tokens, and administrator multi-factor authentication (TOTP MFA) records, along with standard HTTPS and WebSocket request data required to deliver live updates.
We process this information strictly to route guest requests to the appropriate venue dashboard, power live staff alerts and waiting timers, allow a guest to cancel their own pending request, generate daily summaries and 30-day CSV service reports for the venue, and protect the service against duplicate or automated abuse.
Service requests, table or room configurations, and venue reports are accessible to authenticated staff members assigned to that specific venue, as well as authorized QRTebly platform administrators (protected by multi-factor authentication) who manage venue onboarding and platform operations.
Request history is retained for 90 days. Completed requests older than 90 days and their associated event logs are automatically deleted on a daily schedule, while active Pending requests remain open until handled by staff. When venue staff use "Clear completed list" on the dashboard, completed requests are archived from the live screen while remaining available for the venue's 30-day CSV export until the 90-day retention period expires.
QRTebly uses your browser's localStorage to remember your selected language preference (qrtebly:language - English or Arabic), store random pending-request receipt keys for your table or room (qrtebly:guest-receipts) so only your browser can cancel a pending request you sent, remember staff dashboard sound preferences (qrtebly:sound), and maintain staff sign-in sessions. Temporary sessionStorage (qrtebly:admin-job) is used only during admin account creation. No third-party advertising cookies are stored.
Menus (PDFs or images), business logos, and promotional banners uploaded by a venue or administrator are stored in public cloud storage buckets (qrdine-menus, qrdine-logos, qrtebly-ads) or linked via external HTTPS URLs configured by the venue so they can be displayed immediately when a guest scans a table or room QR code.
Promotional banners displayed on guest pages consist solely of static uploaded images and an optional external HTTPS link. QRTebly does not use advertising trackers, behavioral profiling, third-party ad networks, or tracking pixels, and does not sell guest or business data.
For questions about a specific restaurant, café, or hotel visit, please contact the venue's management directly on-site. For questions regarding QRTebly platform privacy, please reach out via the official MEJZAMA UNITY founder page (https://www.mejzama.com/founder) or your venue's designated QRTebly administrator contact.

QR-powered guest assistance for restaurants, cafés, and hotels - in English and Arabic with zero app downloads or guest accounts.
All food ordering, bill, and checkout requests summon on-site staff assistance. QRTebly does not process orders, bills, payments, or checkout.