Privacy is designed around role separation.
This page describes the product-level privacy principles currently frozen for MyRashan. Formal legal privacy language should be reviewed before transactional public launch.
Merchant and customer relationship
The primary merchant owns its customer relationship within its storefront. Customer-facing screens do not expose unrelated merchant operational or commercial information.
Assisted fulfilment privacy
Where a store uses network-assisted fulfilment for an unavailable item, the customer experience remains attached to the selected store. Participating merchants should receive only the information necessary to fulfil the item request, not the customer’s full order history or unrelated relationship data.
Role-based visibility
Customer, merchant, rider, field and admin/support views are intentionally separated. Administrative access should be permissioned and audited.
Merchant reassignment
When an outlet slot is reassigned, previous merchant orders, customers, inventory, payments, complaints and reports remain attached to the previous merchant record and are not transferred to the new merchant.