Service providers & subprocessors

Panther Hook service providers

Panther Hook relies on the providers below to operate specific service functions. The data sent to a provider depends on the feature being used. This page describes the current product architecture without claiming that every provider has the same legal role for every customer or data category.

Cloudflare

Edge proxying, DNS-facing delivery path, static web assets, and private R2 object storage.

Google Cloud

Application runtime, task queues, scheduling, secrets, and observability.

Neon

Managed PostgreSQL database infrastructure.

Amazon Web Services (AWS SES)

Transactional authentication/security email, owner notifications, and autoresponder delivery.

Stripe

Live payment checkout, subscription billing, and customer portal.

Google

Google OAuth authentication when selected by a user.

GitHub

GitHub OAuth authentication when selected by a user.

Customer-directed integrations

The following production-enabled destinations are configured by the customer and receive data only when the customer creates and uses the relevant integration:

Zapier, Make, Google Sheets, Slack, Telegram, Discord.

These destinations are not described here as always-on Panther Hook subprocessors merely because Panther Hook can deliver data to them. The customer selects the destination and controls whether it is configured for a form. Runtime provider switches remain operational kill switches and can temporarily pause delivery without deleting the customer's saved configuration.

Questions

Questions about providers or data processing can be sent to support@pantherhook.com.