Building for Qatar: Small Market, High Expectations, Real Privacy Law

Qatar is not a volume market and pretending otherwise leads to the wrong product. Three million people, a majority of them expatriates on fixed contracts, with among the highest per-capita spending in the world. That combination favours narrow, high-quality, genuinely bilingual products over mass-market storefronts.

The payment layer changed recently

Qatar Central Bank has been rebuilding the domestic rails. Himyan is the national card scheme, and Fawran is the instant payment service — both recent, both increasingly expected. NAPS was the older domestic debit network many integration guides still describe. For an online business, that means the payment layer must be treated as something that will change again, not as a one-time integration. I build it behind an interface for exactly that reason.

Qatar has an actual data protection law, and it predates the others

Law No. 13 of 2016 on Personal Data Privacy Protection was the first standalone data protection law in the GCC. It requires a lawful basis and consent, restricts processing of children's data, and imposes breach notification duties. This is not a copy of GDPR and the differences matter: your consent capture, your retention policy and your breach process need to be designed against the Qatari text, not against an EU template. Most agencies quoting Qatar work simply ignore this.

Bilingual is not a translation task

With a majority-expatriate population and Arabic as the official language, both languages carry real traffic. That means an Arabic-first RTL layout that was designed as Arabic, English that reads as English rather than as a translation, and reciprocal hreflang so search engines serve the right one. Bolting a translation plugin onto an English site is visible immediately to Qatari users.