Data map
Investor review distinguishes product data, support data, payment data, and proof artifacts.
Flux privacy messaging separates account data, gameplay data, wallet data, support data, and proof data. The fairness layer must prove the hand without turning folded strategy into public information.
Flux's trust story depends on showing enough evidence to verify the hand and withholding enough private state to protect players.
The privacy story is part of the moat. Flux is not simply trying to reveal more data. It is trying to reveal the right data to the right audience.
That distinction matters in poker because hidden information has strategic and commercial value.
The final privacy policy remains subject to legal review, while the investor message is clear: verification and privacy reinforce each other.
Investor review distinguishes product data, support data, payment data, and proof artifacts.
Hands, actions, table events, rake, and verifier payloads are core operational records.
Crypto settlement creates payment and reconciliation data that needs controlled handling.
Redacted verification protects hidden strategy while preserving the integrity claim.
Public legal pages communicate the operating posture without implying approvals or terms that require final review.
Access, jurisdiction, account responsibility, and platform changes.
Account data, wallet events, verification artifacts, and support records.
Growth mechanics remain subject to final rules and status labels.
Limits, help resources, and clear user protections.
Legal pages stay clear, compact, and explicit about launch dependencies and review status.