LegalPublic surface

Privacy policy

Privacy needs to explain the split between public proof surfaces and private user data.

This page should clarify what becomes publicly inspectable through the protocol, what remains account-level or notification-level data, and how those boundaries are maintained.

Privacy model

The core distinction is between verification and identity exposure.

Explain wallet, session, analytics, communications, and support data collection clearly.

Differentiate public marketplace/proof artifacts from internal account and notification records.

Document retention expectations, consent boundaries, and regional compliance posture.

Call out any anonymous subscription flow that reduces counterparty visibility.

VERIFIED-ALPHA-SURFACE

Bring verifiable trust to trading intelligence

Modernize discovery and subscription flows with proof-backed seller surfaces, cleaner due diligence, and protocol-grade security posture.

Build with proof-backed sellers

Compare pricing tiers, public proof summaries, and marketplace positioning without dropping into gated flows too early.

Marketplace details

Understand the trust model

Read the verification stack, token utility, security posture, and public operating surfaces before integrating deeper.

Open docs