Age assurance before participation.
Sellers must reach the required verified state before marketplace selling is unlocked. The final production flow requires a genuine approved provider rather than a self-declared badge.
Public handles, private legal identity.
Marketplace profiles expose only the public information needed for trust. Legal identity, verification references and private account information stay behind access controls.
Approval before listings go live.
New listings enter moderation. Seller text, imagery and structured disclosures are reviewed against marketplace rules before public activation.
Keep transactions on-platform.
Messages are tied to marketplace accounts and listings. Safety controls are designed to detect under-age references and other disallowed language before submission.
Users can cut off unwanted contact.
Reporting and blocking are built into the data model and moderation operations rather than treated as customer-support workarounds.
Feedback tied to real orders.
The review system is intended for completed marketplace transactions, reducing the value of fabricated testimonials and unrelated reputation manipulation.
HOW PROTECTION FITS TOGETHER
Four control layers.
Authentication, profile privacy, seller readiness and adult verification states.
Moderation, image approval, language safety, prohibited conduct and disclosure rules.
Protected basket, checkout intent, order history, disputes, shipping evidence and reviews.
Admin queues, appeals, incident handling, support playbooks and provider gates.
Important launch gate: external age/identity verification, real card/crypto processing and seller payouts are not live yet. PRIVATELYWORN will not simulate successful verification or payment while those approved production providers remain unconnected.
Something looks wrong?
Use reporting or blocking inside the marketplace where available. For policy questions and launch-stage support guidance, use the support section of the marketplace policies.
SUPPORT & REPORTINGSeller verification
See the current verification architecture and which provider-dependent controls are still locked.
VIEW VERIFICATION FLOW