Subprocessor & Provider List
Version 2026-10-01 · Effective when published
The platform operator's legal identity/contact details have not yet been published. These documents are not to be presented as final external legal terms until the platform legal profile is completed.
Core and optional providers
The exact provider set depends on enabled features. A provider being listed does not mean every Customer's data is sent to that provider. This list is maintained from TradeOps' internal provider inventory.
Calendar integration — Customer-authorised Google Calendar integration
Data categories: calendar event metadata, connected account identifiers
Processing regions: Google infrastructure regions applicable to the connected service
Last reviewed: 01/10/2026
Accounting integration — Customer-authorised accounting synchronisation
Data categories: invoice data, payment data, customer/accounting identifiers
Processing regions: Provider regions applicable to the connected QuickBooks service
Last reviewed: 01/10/2026
Accounting integration — Customer-authorised accounting synchronisation
Data categories: invoice data, payment data, customer/accounting identifiers
Processing regions: Provider regions applicable to the connected MYOB service
Last reviewed: 01/10/2026
AI processing — AI-assisted drafting, summarisation, extraction and other enabled AI features
Data categories: feature inputs, feature outputs, relevant customer/business context
Processing regions: Provider infrastructure may include Australia, the United States and other configured regions
Notes: API data controls depend on the configured OpenAI business/API settings.
Last reviewed: 01/10/2026
Email delivery — Transactional and customer email delivery where enabled
Data categories: recipient details, message content, delivery metadata
Processing regions: Provider infrastructure may include the United States and other regions
Last reviewed: 01/10/2026
Payments and SaaS billing — TradeOps subscription billing and optional customer payment processing
Data categories: billing identity, transaction metadata, payment-provider identifiers
Processing regions: Provider infrastructure may include Australia, the United States and other regions
Notes: TradeOps does not need to store full payment card numbers.
Last reviewed: 01/10/2026
Database, authentication and storage — Core application database, authentication and file storage
Data categories: account data, customer/business records, files, security metadata
Processing regions: Australia (Sydney)
Notes: Current TradeOps project is hosted in ap-southeast-2.
Last reviewed: 01/10/2026
SMS and telephony — SMS and telephony where enabled
Data categories: phone numbers, message/call content, delivery metadata
Processing regions: Australia, the United States and other provider regions depending on configuration
Last reviewed: 01/10/2026
Application hosting and delivery — Application hosting, deployment and edge delivery
Data categories: application requests, service metadata, diagnostics
Processing regions: Provider infrastructure may include Australia and other regions
Last reviewed: 01/10/2026
Accounting integration — Customer-authorised accounting synchronisation
Data categories: invoice data, payment data, customer/accounting identifiers
Processing regions: Provider regions applicable to the connected Xero service
Last reviewed: 01/10/2026
Provider locations and subprocessors can change. Customers with strict residency requirements should obtain written confirmation before enabling an optional integration.
Legal: not yet published · Privacy: not yet published · Support: not yet published