Subprocessors

Customize this list for your deployment. Only providers you actually use apply.

Infrastructure and application

• Hosting / database: the cloud or datacenter where you run the Laravel application and database (for example AWS, GCP, Azure, Fly.io, or on-prem).
• Email: your configured mail provider (for example Postmark, Resend, SES) for verification and transactional messages.

Payments

• Stripe: payment processing, billing portal, tax calculation when STRIPE_AUTOMATIC_TAX is enabled, and related fraud prevention. Stripe acts as a processor under your Stripe agreement.

Authentication (optional)

• GitHub / Google: OAuth sign-in when enabled; subject to each provider’s terms and privacy policy.

Observability (optional)

• Error reporting for Pulse itself: if you configure reporting to Sentry or similar, that vendor may process stack traces and request metadata from the Pulse app. See docs and your operations runbook.

For privacy practices regarding ingest payloads from your end users’ applications, see the Privacy Policy.