DMHub engages the following third-party sub-processors to provide its services. Each sub-processor operates under a Data Processing Agreement (DPA) and is reviewed annually for security and compliance posture.
Last updated: May 2026
| Processor | Purpose | DPA |
|---|---|---|
| Vercel | Hosting and edge compute — serves the Next.js application globally | DPA |
| Neon | Primary PostgreSQL database — stores all platform data at rest | DPA |
| Stripe | Payment processing and subscription billing | DPA |
| Twilio | SMS and WhatsApp messaging delivery | DPA |
| Resend | Transactional email delivery (receipts, notifications) | DPA |
| Cloudflare R2 | Object storage for user-uploaded files and media | DPA |
| Pusher | Real-time WebSocket events for live conversation updates | DPA |
| Inngest | Background job queue and scheduled cron functions | DPA |
| Upstash | Redis cache and rate-limiting store | DPA |
| Loops | Marketing email sequences and lifecycle messaging | DPA |
| PostHog | Product analytics and event tracking | DPA |
| Sentry | Error monitoring and performance tracing | DPA |
| OpenAI | AI language model inference for AI Agents and Wizard features | DPA |
| Anthropic | AI language model inference (Claude) for AI Wizard features | DPA |
Changes to this list
We will provide 30 days' notice before adding a new sub-processor or materially changing how an existing sub-processor handles data, except where emergency security requirements make shorter notice necessary. Notices are sent to the billing contact on file and posted here.
Questions? security@dmhub.ai