AWRA OpsHub Search
AWRA OpsHub · Trust & Legal

Official register

Sub-processors

The third parties we engage to deliver AWRA OpsHub, and exactly what each one does with data — the companion to our Data Processing Agreement.

Effective
October 8, 2026
Change notice
30 days
Entries
18 listed

How we govern sub-processors

A sub-processor is a vetted third party that may process personal data on your behalf so we can run the platform. We stay responsible to you for each one. These are the commitments behind every name on this page.

Advance notice of changes

We give at least 30 days’ notice before a new sub-processor begins handling personal data, so you can review it.

Right to object

You may object to a new sub-processor on reasonable data-protection grounds, as set out in our Data Processing Agreement.

Flow-down obligations

Every sub-processor is bound by written terms with data-protection obligations no less protective than those in our DPA.

Data minimisation

Sub-processors receive only the categories of data they need to perform their specific function — nothing more.

Google data stays out

Data from a connected Gmail, Google Calendar or Google Drive is never passed to our AI, analytics or operational-tooling sub-processors — Section 7a of our Privacy Policy governs it exclusively.

Core platform

Active for every workspace

10 listed
01 C

Cloud infrastructure provider

One region per deployment, chosen by AWRA

Cloud hosting, compute and encrypted storage of the platform and its databases.

Account data Operational content Usage & device data
02 P

Paystack

Nigeria / Global

Subscription billing in Kenyan shillings (KES) and storage of billing records.

Billing & payment data Account data
03 M

Mailgun

United States

Sending of transactional and notification email (verification, alerts, receipts).

Contact data (email) Message content
04 M

Mailjet

European Union

Delivery of transactional and notification email (verification, alerts, receipts).

Contact data (email) Message content
05 A

Africa's Talking

Kenya / Africa

Delivery of transactional SMS and one-time codes where SMS is enabled.

Contact data (phone) Message content
06 F

Firebase Cloud Messaging (Google)

Global (US)

Delivery of mobile and web push notifications to devices that opt in.

Device tokens Notification content
07 C

Cloudflare

Global

Bot and abuse protection (Turnstile) on public forms and sign-in, plus edge security.

IP address Device & challenge data
08 R

Redis Cloud

United States (US East)

Cache, session and queue storage that keeps the platform responsive.

Session data Cached operational content Queued job data
09 S

Sentry

United States

Error monitoring. Error reports and diagnostics may include request metadata.

Error & diagnostic data Request metadata
10 G

Google (Sign-in / OAuth)

Global (US)

Optional Google account sign-in and identity verification for users who choose it.

Authentication data Contact data (email)

AI features

Active when you use AwraIQ

02 listed
01 G

Google Gemini

Global (US)

Generating insights, summaries and recommendations within AwraIQ features.

Operational content submitted to AI Prompts
02 G

Groq

United States

Low-latency inference for AwraIQ assistant and analysis features.

Operational content submitted to AI Prompts

Optional integrations

Active only if you connect it

06 listed
01 I

Intuit QuickBooks Online

Global (US)

Two-way accounting sync — engaged only when you connect a QuickBooks company.

Accounting records Customer & vendor data
02 S

Slack

Global (US)

Routing approvals, alerts and notifications — engaged only when you connect Slack.

Notification content Contact data
03 M

Meta Platforms (WhatsApp)

Global (US/EU)

Delivering notifications and messages over WhatsApp — engaged only when you connect WhatsApp.

Notification content Contact data Recipient phone numbers
04 M

M-Pesa (Safaricom)

Kenya

Mobile-money sales collections and vendor payments — engaged only when your organization connects its own M-Pesa (Daraja) credentials. Subscriptions are not billed through M-Pesa.

Payment data Phone number
05 G

Google Workspace

Global (US)

Gmail sending, Calendar events, Drive archiving and Sheets export — engaged only when you connect a Google account. Governed by Section 7a of our Privacy Policy.

Documents the app generates Operational email content Calendar event details
06 O

Other connectors you enable

Varies by provider

Dropbox, OneDrive / Microsoft 365, Salesforce, Airtable, Mailchimp, Twilio, Infobip and the other connectors listed in Settings — each engaged only when your organization connects it, and only for the data that connector needs.

Data the connector sends or syncs
Stay informed

Get notified of changes

Subscribe and we'll email you at least 30 days before any new sub-processor begins handling personal data — so your privacy team has time to review and object.

We will email you when our sub-processor list changes. You can unsubscribe anytime.

Prefer to object directly?

Raise a data-protection objection or request the signable DPA through our team.

Contact us

Questions

A sub-processor is a third party we engage to help deliver the platform that may process personal data on your behalf — for example, our hosting provider or payment processor. We remain responsible to you for their handling of that data.

Subscribe to change notifications below. We give at least 30 days’ advance notice before a new sub-processor starts processing personal data, giving you time to review and object on reasonable grounds.

AI sub-processors only receive data when you use AwraIQ features. Content you submit to AI is processed to generate the requested insight and is not used to train third-party models.

No. Integrations such as QuickBooks, Slack, Google Workspace or M-Pesa only act as sub-processors after you explicitly connect them, and only for the data scope you authorise.