Saudi Arabia’s national Tawakkalna application serves more than 36 million citizens, residents and visitors, according to the Saudi Press Agency report published on 2 October 2026. The report describes the app as a unified digital gateway bringing together services from several public bodies. Its examples span health, justice, commercial integrity, municipal affairs, housing, transport and telecommunications. This is a breadth-of-services announcement as well as a reach figure: the agency does not provide a breakdown by user type, location, frequency of use or individual service. The wording “more than 36 million” is a lower bound, not an exact subscriber count, and the source does not specify the date on which the user total was measured. It should not be converted into a precise value or treated as a count of active monthly users.

The reported functions include checking medical insurance policies, following unified health records and accessing electronic notarizations from the Ministry of Justice. The app also connects users with Social Insurance and the Social Development Bank. For commercial checks, the report says people can inspect commercial registrations, verify e-commerce platforms through the Saudi Business Center and validate electronic invoices through the Zakat, Tax and Customs Authority. In daily mobility and urban services, the examples include scheduling vehicle inspections, using Riyadh’s Darb public-transport journey planner, accessing municipal parking systems and managing a Saudi Post national address. The publication also mentions a “my numbers” telecom inquiry service and public-service evaluations with the National Center for Performance Measurement. These examples describe functions reported by SPA; they do not establish that every listed feature is available to every user in every circumstance.

A shared app can reduce the need to locate separate government portals, but the announcement does not quantify time saved, completed transactions, service reliability, user satisfaction or cost. Nor does it state how many of the more than 36 million people used Tawakkalna during a particular month. A registered or eligible user is not necessarily an active user, and one person may interact with several services. The headline reach figure therefore cannot be used as a transaction count, a measure of adoption rate or evidence of a particular economic effect. No denominator for the population, method for counting distinct users, or breakdown of accounts and visitors is included in the release. These limits matter when comparing the figure with another platform or using it in a forecast: the underlying definitions and observation dates would need to match.

The list nonetheless shows the stated integration ambition: a common interface links identity-related, administrative and practical tasks that people may otherwise complete through different agencies. The source presents this as a national gateway and groups examples across everyday public services. It does not publish technical details about the app’s architecture, data-sharing permissions, service-level agreements, accessibility audits, cybersecurity controls or complaint resolution. Those are separate dimensions of digital public-service quality and should not be inferred from the number of users or the length of a feature list. The report also does not say whether a feature is newly launched, continuously available or dependent on another agency’s system. Readers can take the announcement as a catalogue of functions attributed to the platform at publication, while recognizing that operational performance requires additional evidence.

For a data-driven reading, the only quantified reach measure in the SPA article is a lower-bound user figure: more than 36 million. The accompanying dataset preserves that fact as a null numeric value with the unit “users” and explains the lower-bound wording in its methodology, because the schema has no inequality operator. The value is not replaced with 36,000,000, which would falsely imply equality. No derived rate or forecast is provided. A robust time series would require dated observations collected with a consistent definition of distinct users, plus context on active use, population coverage, successful transactions and service availability. Until such data are published, the release supports a carefully attributed scale statement and a list of described functions, not a model of public adoption or administrative impact.