Country coverage

Global by design. Local by law.

Every ISO country and territory appears in this selector. Mapped frameworks remain launch-gated, and every unmapped location stays disabled until local review is complete.

No market approved for production launchResearch reviewed: 16 July 2026

Select a location to see the mapped framework and launch gate.

“Framework mapped” does not mean “legally approved.”It means the principal official framework has been identified for engineering. Release still requires controller identity, legal basis, language, age rules, vendor locations, retention, transfer, breach, rights, AI/profiling and consumer review.

Global minimum, everywhere

Control

Access, export, correction, deletion and consent/objection controls with proportionate verification.

Minimization

No advertising, no data sale, no sensitive-trait inference and no public-model training on household content.

Accountability

Vendor contracts, transfer mapping, audit history, security testing, incident response and human review.

Principal mapped regimes

The selector provides detailed release gates for Egypt, the EU/EEA, Romania, United Kingdom, United States, Canada, Brazil, Australia, New Zealand, Singapore, Japan, South Korea, India, China, South Africa, United Arab Emirates and Saudi Arabia.

For EU/EEA countries it applies the GDPR baseline and explicitly requires national review for child-consent thresholds, regulator routes, language, electronic communications, consumer law and sector rules.

Why other countries are disabled

Privacy law is only part of release readiness. A country may also impose consumer subscription, electronic-marketing, accessibility, child-safety, AI/profiling, data-localization, health/financial, encryption/import, sanctions, tax or representative requirements. Enabling a store territory without this review would make a worldwide policy misleading.

Official sources used