K-Waiter is used by authorized restaurant and organization staff. The organization that provided your account and operates the configured server is the controller of operational data. The app processes that data only to deliver the organization’s services.

Data processed

• Employee account, branch, permissions, device identifier, and app version.
• Customer information entered by staff, including name, phone number, address, and delivery notes.
• Orders, items, tables, payment methods, print jobs, and shift records.
• Limited technical diagnostics, such as connectivity state and error trace identifiers.

Purposes

Data is used for authentication, order fulfilment, delivery and pickup, table service, collection records, KOT routing, receipt printing, synchronization, duplicate prevention, operational audits, and support.

Storage and offline operation

Data is transmitted over HTTPS to the organization’s configured server. Login tokens are stored in the operating system’s secure storage. Order drafts, menu and table data, and synchronization operations may be stored temporarily on the tablet until connectivity returns.

Local network and printing

The app may use the local network or Bluetooth to reach a printer configured by the organization. Bluetooth is not used for location tracking. Direct printing to a printer on the same network can work without internet access.

Sharing and tracking

The app does not sell data, show advertising, or track users across other apps or websites. Hosting or realtime service providers may process data as service providers under the organization’s configuration and agreements.

Retention and rights

The organization defines retention periods under its legal and operational requirements. To request access, correction, deletion, or device revocation, contact the organization that provided your K-Waiter account or use the contact details published on the configured server’s domain. Records required for legal or financial audit purposes may be retained.

Security and changes

The app uses HTTPS, role permissions, idempotency keys, secure token storage, and audit records. No electronic system is completely secure. This policy may be updated when app functionality changes; the effective date appears above.