Fields to protect
Member contact details, purchase records, order information and store ownership. In this example, each brand is a separate tenant.
NSECURED MemberGo / E-commerce
A multi-brand marketplace can share an analytics tool while preserving each store’s membership-data boundary. MemberGo uses field tokens and checks tenant and purpose before releasing data to an analytics workload.

E-commerce
Member contact details, purchase records, order information and store ownership. In this example, each brand is a separate tenant.
Where the store has a valid basis for the purpose, it may approve custom fields such as purchase category, spend band and time between orders.
Synthetic data example
repeat_purchasestore_a.category store_a.reorder_gap200 · access_id: demo_b81fStore A’s authorized analytics workload can use category and time between purchases from its synthetic orders to compare repeat buying by category.
repeat_purchasestore_a.category store_b.spend_band ×403 data_access_deniedIf Store A includes a purchase field belonging to Store B, the tenant mismatch blocks the entire request, even though both brands use the same marketplace.
The fields and decisions here are illustrative. Actual access depends on tenant settings, the basis for processing and the approved purpose.
Workflow
Give each store its own synthetic membership and order records so ownership is explicit.
Choose the fields needed for behavior analysis and keep delivery contact details within their own purpose.
First verify access within the store, then add another store’s field token and check that no values are returned.
Proof of concept
Prepare two sets of synthetic orders and one shared analytics brief. Have the marketplace owner confirm the fields each store needs, then test the cross-store denial with an engineer.