Privacy

Public market data is not private account data.

Bazarse public web is designed to make stores, products, deals, cities, and categories discoverable while keeping logged-in account, wallet, order, and internal operational data out of public pages.

Privacy boundary

Public pagesMarketStores, products, deals, cities, and categories

Private flowsGatedAccount, wallet, orders, messages, and settings

Public infoLimitedOnly shopper-facing listing information

CorrectionsOpenPublic data fixes can be requested by contact

Privacy principle

Bazarse pages show store, product, deal, and market information. Account, payment, order, wallet, and message data stay behind authentication and permission checks.

Request correction Trust model

What this means

Market listings

What can be shown.

Bazarse may show store identity, category, city, products, active deals, and listing information needed for browsing.

Store pages

Product and deal pages

Category and city pages

Private app

What should stay gated.

Logged-in customer, vendor, admin, wallet, order, message, platform configuration, and internal operations routes are not meant to be indexed as public web pages.

No public account pages

No public wallet pages

No public admin routes

Controls

Corrections and removals.

If a public store, product, deal, city, or category page is wrong, outdated, duplicated, or should not be public, contact Bazarse with the page URL and issue details.

Data correction

Outdated listing review

Duplicate listing cleanup