Privacy at BUPOS

The public demo

The public demo uses sample store data and does not require an account. Actions stay inside the simulated demo experience; they do not update a live store or process a real payment.

Do not enter real customer or payment information into the public demo.

Information BUPOS handles

When a store account is used, BUPOS can hold account and staff details, store and location settings, product and inventory records, supplier and purchasing records, customer records, transaction and tender records, and operational audit history.

How store information is used

Store information supports the register, inventory, purchasing, customer, reporting, employee-permission, and audit workflows selected by that store. BUPOS does not use the public demo as proof of how a particular store configures or governs its own data.

Access, retention, and deletion

Access to store data is controlled through store accounts, roles, and assigned locations. Retention and deletion needs should be agreed during evaluation before live store data is imported or entered. Existing operators should use the authenticated Help area to generate a support packet without placing customer records in a public request.

Service boundaries

BUPOS is a web application and depends on hosting, database, and network services to operate. A store may also choose integrations or payment workflows with their own terms and privacy practices. Those external services are not covered by this page.