OMBU restaurant apps
App Privacy Policy
Last updated November 1, 2026
This policy covers OMBU iPad for table ordering, Ombu Waitlist for guest registration and arrival, OMBU Remote for authorized staff operations, and OMBU Phone (listed as Ombu Iphone on the App Store) for authorized restaurant management on iPhone.
The participating restaurant operates the configured OMBU server and controls access to its business records. Data sent to that server leaves the app device, including when the server is on the restaurant's local network. For privacy questions, contact the manager at your restaurant using its public location contact details.
This policy describes the restaurant apps. The website privacy policy separately explains how visits to the restaurant website are handled. These app information pages contain no forms. Visits to these pages are covered by that separate website privacy policy.
Information handled by the apps
- Waitlist and reservations. Names, contact phone numbers, party sizes, arrival and seating status, reservation details and related timestamps help staff register, find, contact and seat guests. When enabled, a guest's name may be displayed in a shortened form or announced to call the party.
- Orders and restaurant service. Table and dining-session assignments, menu choices, quantities, options, order notes, service requests, order history, payment methods, amounts, tips and transaction references support ordering and restaurant records. Full card entry may take place on a separate payment terminal; the apps can still handle the associated payment records.
- Staff access and operations. Employee identity, permissions, sign-in sessions, workstation assignments and records of authorized actions support access control and auditing. Staff PINs are sent to the selected restaurant server for verification. Staff-only workflows may include checkout, refunds, attendance and administrative changes.
- Photos, videos and other content. Authorized staff can choose or capture menu photos and upload restaurant promotional images or videos, together with captions and settings. The restaurant server stores this content and supplies it to restaurant displays. Notes and other text entered during restaurant workflows are also stored with the relevant records.
- Device and diagnostic information. App-generated device or client identifiers, device display names, server and pairing information, app and operating-system versions, connection status, source network addresses and technical status help connect, authorize and troubleshoot devices. Depending on the app, status may include battery/charging, device model, display mode, media-cache or playlist status, speech availability and audio route.
- Support information. Information you choose to include in a support email or shared diagnostic report is used to investigate and respond to your request.
How information is used
Information enables registration and reservation matching, table assignment, ordering, payment records, staff authentication, restaurant administration, security, synchronization, recovery and support. Features and employee permissions determine which information a particular app handles.
OMBU Phone provides authorized table ordering, waitlist and reservation management, menu editing, promotional content uploads, reports and printing controls. Its live operations send the relevant records and staff actions to the configured restaurant server. Payment entry remains on the POS; viewing an existing payment report does not enter a new payment. The optional offline demo uses sample data held in memory and does not send demo orders, payments or uploads to a restaurant server.
Guest registration does not require a guest account. That does not make a registration or order anonymous: restaurant records can connect a party, table, dining session, device and related actions.
Restaurant promotions and reporting
Restaurant iPads can display the restaurant's own menu recommendations, promotional images and videos. The ordering app can report promotion exposures, taps and related additions to an order, including the promotion, device and dining-session identifiers, selected language and timing.
The restaurant uses these records and related order information to understand how its promotions perform. These records can be linked to a table or dining session; they are not described as anonymous. Video playback and a downloaded file do not by themselves mean that every app reports a separate viewing event.
The supplied restaurant apps do not include third-party advertising SDKs or implement cross-app advertising tracking. Restaurant promotion reporting is used within the configured restaurant system, rather than for advertising profiles across unrelated apps and websites.
Where information goes and who can access it
In the restaurant, the apps communicate with its configured OMBU server. Where off-site staff access is configured, the staff apps use the restaurant's secure gateway to reach that server. Authorized restaurant staff and system administrators can access records according to their permissions. Providers used to operate the configured server, gateway or backups may process information as part of those services.
The restaurant manages its server, network, gateway and backup arrangements. Ask the operator which providers and staff have access in that deployment. If you contact support, the details you provide may be shared with the restaurant operator or authorized support personnel as needed to resolve the request.
Local storage and retention
The apps keep settings, cached menus and promotional media, credentials and recovery state on the device. A pending order or waitlist registration may be retained locally so an interrupted request can be checked or safely retried. Applicable credentials and waitlist recovery data use iOS Keychain.
Clearing a form or leaving a confirmation screen removes information from that screen; it does not erase the restaurant's server record. Ordinary waitlist entries expire from the active queue at the restaurant's local midnight. Expiry archives the record rather than deleting its name and phone number. Reservation availability may follow the restaurant's configured service day.
Server records, audit information and backups are retained under the restaurant operator's business, security and applicable recordkeeping practices. The retention period depends on the record and deployment. Contact the operator using its public restaurant contact number for its retention period and to request deletion. Uninstalling an app does not delete server records or backups, and iOS Keychain entries may remain after uninstalling.
Your choices and privacy requests
You can ask restaurant staff for assistance instead of entering information on a shared iPad. Staff-only controls require restaurant authorization. Device permissions, including Local Network and any camera or photo selection permissions used by a workflow, can be managed in iOS settings.
For access, correction or deletion of restaurant records, contact the manager at your restaurant using the public phone number on its official location page. Include the restaurant and approximate visit date. The operator may need to verify that you are entitled to the records before acting, and some records may need to be kept for legitimate recordkeeping or legal requirements.
Network access and safety
Local Network access allows communication with the restaurant host. Local deployments may use HTTP within the restaurant's controlled network; remote gateway access uses HTTPS/WSS. The operator is responsible for protecting the local network and server access.
Do not include staff PINs, access tokens, pairing codes, full payment card details or other guests' information in public reports. Remove those details from screenshots before asking for help.
Contact and updates
For privacy or app support, call the restaurant where you used the apps and ask the manager. Public contact numbers are listed on the official Locations page. See App Support for connection and usage help.
This policy may be updated as restaurant app features or data practices change. The date at the top identifies this version.