Compliance Overview

Prox OS is global-first by default. Compliance planning is split into a global baseline and regional notes so product decisions stay clear without overbuilding before product-market fit.

This guidance is product and operations guidance. It is not a formal compliance determination.

Operating Principle

Do not build a heavy compliance system before the product needs it. Do define trust, privacy, abuse, region, and hosted-content boundaries from day one.

Prox OS treats privacy-by-design as product architecture: user-owned data, portable app contexts, scoped agent permissions, and auditable actions should shape the platform before formal compliance automation exists. The compliance docs describe operating posture and roadmap, not a claim that Prox OS is already fully compliant in every region.

Document Map

• Global Product Boundaries
• EU GDPR Baseline: privacy-by-design, European data sovereignty, agent auditability, v0.1 baseline, and future compliance automation.
• EU DSA Baseline
• US Platform Notes
• Payments And Abuse
• Mobile Policy Boundaries
• CN Lite Strategy