Sub-Processors
Last updated: September 2026
Pidgr uses the following third-party sub-processors to operate the platform. Changes to this list are communicated with 30 days' notice as specified in our Data Processing Agreement.
| Provider | Purpose | Region processed | Documents |
|---|---|---|---|
| AWS | Compute, storage, networking, KMS, and SES transactional + campaign email delivery | US (us-east-1) | — |
| AWS Bedrock | AI inference for cohort archetypes and acknowledgement predictions | US (us-east-1) | — |
| AWS Cognito | Authentication and user identity (email OTP, passkeys, JWT issuance) | US (us-east-1) | — |
| Firebase (FCM) | Push notification delivery to mobile and desktop devices | US | — |
| Honeycomb | Backend observability (OpenTelemetry traces and metrics) | US | — |
| PostHog | Product analytics and session replay (EU-hosted) | EU | — |
| PostHog | Web analytics and masked session replay on the public marketing/docs site (pidgr.com): page views, traffic source, device/browser info, IP-derived approximate location, and post-consent session replays with all typed input masked. Does not process customer platform data (campaigns, messages, org members). | US (PostHog Cloud US) | — |
| Sentry | Client and backend error tracking | US | — |
| Temporal Cloud | Durable workflow orchestration for campaign and compliance workflows | US | — |
| Twilio | SMS dispatch for reminder and escalation channels (Ivysaur) | US | — |
All sub-processors maintain appropriate data protection agreements. For questions, contact privacy@pidgr.com.