Supported regions

Phase 1 launch markets

Brazil — Portuguese UI, BRL projection layer over the USDC-denominated balance, PIX-primary deposit flow (Asaas), CPF-aware KYC. The aunt-from-Brazil persona test (ADR-007 / ADR-008) is the acceptance criterion for that experience.

Mexico — Spanish (es-MX) UI, USDC-primary display, SPEI deposit/withdrawal once real-money flips on. Launch order #1 — Mexico is the first non-Brazil region to flip the real-money switch (Gate B, post-validation).

Canada (excluding Ontario) — Canadian English (en-CA) by default, Quebec French (fr-CA) when your browser prefers it, USDC-primary display, Plaid + Interac e-Transfer at deposit time. Ontario is excluded from Phase 1 due to provincial regulatory specifics.

India — English (en-IN) UI, USDC-primary display, Razorpay/Cashfree on-ramp planned with the 1% TDS withholding required by Indian tax law surfaced transparently at deposit time.

Detection runs via Cloudflare's CF-IPCountry header. The first paint after that detection writes a granbay.region cookie; subsequent visits read the cookie. You can switch any time via the flag picker in the header — the picked locale carries detected:false so the auto-detection won't override your choice.

Outside Phase 1

If your IP isn't in a Phase 1 market, you land on the default English UI with USDC-primary display and no jurisdiction-specific compliance copy. Real-money signup is gated to Phase 1 markets in the closed beta; non-Phase-1 visitors see a 'Coming soon to your region' notice + waitlist when they hit deposit / withdrawal flows. Trading the virtual-cash flow during the closed beta is unrestricted globally.

Some jurisdictions are blocked entirely from signup due to regulatory ambiguity or explicit prohibition on prediction markets: mainland China, Iran, North Korea, Russia, Cuba, and Sudan. The signup flow rejects accounts created from those IPs. OFAC-sanctioned individuals are excluded everywhere — even a Phase 1 signup can fail KYC if the user appears on a sanctions list.

What the region controls

Region drives four things: (1) the UI language (per the Phase 1 mapping above; every user can override via the picker), (2) the displayed currency framing (BRL projection for Brazil; USDC primary everywhere else, with optional inline conversion to MXN/CAD/INR/USD per /settings/display), (3) the payment-rail menu at deposit / withdrawal time (PIX for Brazil, SPEI for Mexico, Interac for Canada, UPI for India — only fires once real-money operations open), and (4) the jurisdiction-specific compliance framing in the privacy policy, terms of service, and KYC disclosures (LGPD for Brazil, LFPDPPP for Mexico, PIPEDA for Canada, DPDPA + 1% TDS for India, generic industry-standard for everywhere else).

Region does NOT control which markets you see — the market list is global. A Brazilian user can trade a US-politics market and a Mexican user can trade a Brazilian-football market, each in their own preferred locale.

Changing region

Use the flag picker in the site header to switch regions any time. The choice writes to the granbay.region cookie with detected:false, which pins the override and stops the IP-based auto-detection from second-guessing you. Backend persistence (when authed) saves the locale on your account so the choice follows you across devices.

If you've moved permanently and want a Phase 1 region you can't IP-detect into (e.g., a Brazilian user travelling abroad who wants the Brazilian framing), the flag picker is the answer — there's no support flow to navigate. VPN-driven region spoofing for KYC-bypass purposes is a violation of the terms of service and will result in account suspension. The geographic gating is real and load-bearing for our regulatory standing.