Privacy Policy

RestaurantOS may process restaurant profile data, branch settings, staff accounts, menu records, orders, payments, receipts, inventory, expenses, reports, sync status, and audit logs.

Operational data is used to run POS, kitchen, payment, inventory, expense, reporting, export, staff access, sync recovery, and compliance-ready record workflows.

RestaurantOS uses role-based access, branch scoping, session controls, and audit logs so sensitive records are visible only to users who need them for their work.

Core offline actions can be stored locally on a device until sync. Users should protect devices used for POS or management because local pending records may include order and payment notes.

The MVP may use infrastructure services for hosting, database storage, file storage, and error tracking. Direct mobile money and EFRIS integrations are not part of the MVP.