Processors that may see data AIRAmax handles on behalf of an agency, including restricted-scope Google user data (Gmail/Calendar) under Google's Limited Use policy.
This page is cross-referenced from privacy-policy.md §6 (also rendered publicly at /sub-processors, linked from /privacy), and reuses that document's controller (the agency) / processor (AIRAmax) framing: everything below is a processor AIRAmax itself engages — a "sub-processor" in the GDPR Art. 28 sense — to run the Service on the agency's behalf, not a party the agency has a direct relationship with.
| Processor | Purpose | Location | Sees Google user data |
|---|---|---|---|
| DigitalOcean | Hosting, Postgres, Spaces object storage | EU (FRA1) | Yes |
| Google (Gemini API) | Inbox AI triage — classification and summarisation | EU/US | Yes |
| OpenRouter | Listing copywriting, agentic chat, inbox reply drafting (always), inbox triage/extraction when no Gemini key is configured, and any inbox extraction turn that carries Gmail attachments (images/PDFs), always, regardless of the Gemini key | US | Yes |
| Mailgun | Outbound transactional and campaign email | EU | No |
| Stripe | Subscription billing | US/EU | No |
| Sentry | Error telemetry, PII scrubbed before send | EU | No |
Gmail message content is normally processed by Google's own Gemini API. OpenRouter processes the same kind of content instead in three situations: when an organisation has not configured a Gemini API key, when a message includes an attachment that AIRAmax's Gemini integration cannot carry, and for AI-drafted inbox replies, which currently always use OpenRouter. Neither provider uses this content to train their models.
Questions about a specific sub-processor, or a request to review the list before it changes, can be sent to [email protected] — the same address as the Privacy Policy's contact.