Last updated: 3 October 2026 · OrchestriX PMO Pty Ltd · Melbourne, Australia
These third-party providers process customer data on our behalf to deliver OrchestriX PMO. “Configured but disabled” means the integration exists in the product but is switched off in production and no customer data is sent to it. We will update this page when providers change.
| Provider | Purpose | Data involved | Location | Status |
|---|---|---|---|---|
| Supabase | Managed PostgreSQL database | All account, organisation and project data | Seoul, South Korea (ap-northeast-2) | Active |
| Vercel | Application hosting, serverless compute and edge network | Request metadata, application logs | Provider-managed; serverless functions may run outside Australia | Active |
| Groq | AI inference for KEN (primary provider) | User messages and the project context sent with them (for example RAID items, budget and milestone data) | Provider-managed; may be outside Australia | Active |
| Resend | Transactional email (invitations, password reset, review notifications) | Recipient email addresses and message content | Provider-managed | Active |
| Sentry | Application error monitoring | Error traces and request metadata; may include user and organisation identifiers | Provider-managed | Active |
| Optional “Sign in with Google” | Name and email address, only for users who choose Google sign-in | Provider-managed | Active, optional | |
| Cloudflare Workers AI | AI inference (optional fallback) | Same as Groq, if enabled | Provider-managed | Configured but disabled |
Enterprise customers who need a data processing agreement, or more detail on any provider, can contact privacy@orchestrixpmo.com. See also our Privacy Policy and Security page.