Subprocessors

Our subprocessors

These are the third-party services that process data on our behalf to run Ping Bouncer.

• Cloudflare (hosting and network). Purpose: runs the Ping Bouncer app, the alert ingest endpoints, storage, and delivery queues. Data: alert data and account data as described in the privacy policy, plus standard request metadata. Cookieless analytics for the marketing site only. Cloudflare's terms are in its Customer DPA.
• Clerk (authentication and subscription billing). Purpose: sign-in, sessions, and subscription management. Data: account email, sign-in details, and billing identifiers. Card details are entered through Clerk's billing and never reach Ping Bouncer. Clerk's own sub-processors, including its payment processor, are listed in Clerk's legal documents.

Not subprocessors

Destinations you connect yourself, such as Slack, Linear, incident.io, or a webhook you own, receive only the alerts your rules send to them. They act on your instructions and aren't our subprocessors.

Changes

We'll give at least 30 days' notice before adding a subprocessor that processes customer data. Our notice will appear on this page, and we'll email account holders when we do.

Questions

Email privacy@pingbouncer.com about any of the above.