Can I choose which region my data is hosted in?

Not as a setting on your account. One region serves every organization on a given deployment and it is chosen by us. A region-specific commitment means a separate deployment, which is commissioned work with a price rather than an onboarding checkbox.

Is there an EU-only mode?

No. The sub-processor register is a single list that applies identically to every organization, and it cannot be filtered to EU-region providers for one of them. It currently includes US-region providers for AI, push notification and payment functions.

Are encryption keys separated per organization?

No. Data is encrypted at rest with a single key per deployment, so key separation also means a separate deployment. We would rather say that plainly than let a diagram imply otherwise.

So how do I get a residency commitment?

In a contract, backed by a deployment that actually satisfies it. We will put residency in writing and we will build the deployment that makes it true — what we will not do is describe it as a setting, because it is not one.

Which sub-processors touch my data?

The full register is published, naming each provider, its region and what it is used for. Several are engaged only when you switch the matching feature on, so the list that applies to you is often shorter than the list in full.

How was this page checked?

The residency and hosting-region claims were verified against the codebase on 5 August 2026 and corrected as a result — an earlier version described a per-organization residency and key-separation option that is in fact a property of the deployment. What is on this page is the corrected text.

Verified 2026-08-05

Region is a property of the deployment,
not a switch on your account.

This page exists because the honest answer is more complicated than a flag on a pricing table, and because the version of it we published before was wrong. It was checked against the code on 5 August 2026 and corrected. What follows is the corrected answer.

Sub-processors, published

Region per deployment

Encryption key per deployment

Say it plainly

One region serves everyone on a deployment

It is chosen by us, and it is the same region for every organization sharing that deployment. There is no per-organization region setting to turn on.

There is no EU-only mode

The sub-processor register is one list applying identically to everyone. It cannot be filtered to EU-region providers for a single organization, and it currently includes US-region providers for AI, push notification and payment functions.

Keys are not segregated per organization

Data is encrypted at rest with a single key per deployment. Key separation, like region, means a separate deployment rather than a setting.

The real answer

So how do you actually get residency?

In a contract, backed by a deployment that genuinely satisfies it. That is a commissioned piece of work with a scope and a price, not an onboarding checkbox — and saying so is the difference between a commitment you can rely on and one that reads well in a datasheet.

Tell us the obligation, not the preference

Which regulator, which clause, and what the auditor will ask to see. A residency requirement driven by a supervisory authority is a different piece of work from a preference for a nearer region.

We scope the deployment

A region-specific commitment means infrastructure that lives in that region, with the sub-processor set that follows from it. We price it as the work it is.

It goes in the contract

Written as an obligation we can be held to, with the transfer mechanisms and any residency addenda your regulator expects, rather than as a feature description.

Start that conversation

Where it travels

Every sub-processor, and its region.

Published in full rather than summarised. Several are engaged only when you switch the matching feature on, so the list that applies to your workspace is often shorter than the list in full.

US region · 9 EU region · 3 Africa region · 3

Provider	Region	What it is used for
Amazon Web Services / DigitalOcean	Configurable region (US / EU)	Cloud hosting, compute and encrypted storage of the platform and its databases.
Paystack	Nigeria / Global	Processing of subscription and transaction payments and storage of billing records.
M-Pesa (Safaricom)	Kenya	Mobile-money payment processing for subscriptions and transactions where selected.
Mailjet	European Union	Delivery of transactional and notification email (verification, alerts, receipts).
Africa's Talking	Kenya / Africa	Delivery of transactional SMS and one-time codes where SMS is enabled.
Firebase Cloud Messaging (Google)	Global (US)	Delivery of mobile and web push notifications to devices that opt in.
Cloudflare	Global	Bot and abuse protection (Turnstile) on public forms and sign-in, plus edge security.
Google (Sign-in / OAuth)	Global (US)	Optional Google account sign-in and identity verification for users who choose it.
Google Gemini	Global (US)	Generating insights, summaries and recommendations within AwraIQ features.
Groq	United States	Low-latency inference for AwraIQ assistant and analysis features.
Intuit QuickBooks Online	Global (US)	Two-way accounting sync — engaged only when you connect a QuickBooks company.
Slack	Global (US)	Routing approvals, alerts and notifications — engaged only when you connect Slack.
Meta Platforms (WhatsApp)	Global (US/EU)	Delivering notifications and messages over WhatsApp — engaged only when you connect WhatsApp.
PayPal	Global (US)	Alternative payment processing where PayPal is selected at checkout.

Full register Compliance matrix Trust center

Questions

Asked in procurement.

Can I choose which region my data is hosted in?: Not as a setting on your account. One region serves every organization on a given deployment and it is chosen by us. A region-specific commitment means a separate deployment, which is commissioned work with a price rather than an onboarding checkbox.
Is there an EU-only mode?: No. The sub-processor register is a single list that applies identically to every organization, and it cannot be filtered to EU-region providers for one of them. It currently includes US-region providers for AI, push notification and payment functions.
Are encryption keys separated per organization?: No. Data is encrypted at rest with a single key per deployment, so key separation also means a separate deployment. We would rather say that plainly than let a diagram imply otherwise.
So how do I get a residency commitment?: In a contract, backed by a deployment that actually satisfies it. We will put residency in writing and we will build the deployment that makes it true — what we will not do is describe it as a setting, because it is not one.
Which sub-processors touch my data?: The full register is published, naming each provider, its region and what it is used for. Several are engaged only when you switch the matching feature on, so the list that applies to you is often shorter than the list in full.
How was this page checked?: The residency and hosting-region claims were verified against the codebase on 5 August 2026 and corrected as a result — an earlier version described a per-organization residency and key-separation option that is in fact a property of the deployment. What is on this page is the corrected text.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Region is a property of the deployment, not a switch on your account.