Hub Subprocessors and Transfer Summary
This page summarizes key processors used to operate Pitch Hub and Client Hub services. It is an operational transparency summary and does not replace contract terms.
| Processor | Purpose | Data Categories (Typical) | Region/Transfer Notes |
|---|---|---|---|
| Google Cloud (Cloud Run / build infrastructure) | Application hosting and runtime infrastructure | Service logs, operational metadata, API request handling data | May involve processing in Google-managed regions according to deployment configuration and provider terms |
| Supabase (PostgreSQL / storage services) | Hub data persistence and related storage operations | Hub metadata, access records, event data, uploaded file metadata | Processed per configured project region and contractual safeguards |
| Resend | Transactional email delivery | Work email addresses, message metadata for delivery | International transfer safeguards apply where needed |
| Microsoft / Azure AD / Graph (where applicable) | Staff authentication and connected Microsoft workflows | Identity claims and authorised Microsoft integration metadata | Subject to Microsoft regional and contractual controls |
Transfer Safeguards
Where data transfers occur internationally, AgentFlow uses applicable legal and contractual safeguards under relevant data protection laws.
Updates
We may update this list as services evolve. Material changes will be reflected by the updated date above.
Contact
For questions about this list, contact admin@goagentflow.com.