Beeping

Sub-Processors

Last updated: 2026-05-09

Effective: May 9, 2026

Beeping LLC uses the third-party vendors listed below ("sub-processors") to operate, secure, and bill the Services. Each vendor is bound by a written data processing agreement that requires confidentiality, security, and use limitations consistent with our Privacy Policy.

We update this list whenever our vendor relationships change. To receive notice of changes, write to hello@beeping.io with the subject "Sub-processor Notifications."

Current Sub-Processors

Vendor Purpose Location Privacy Policy
Google Cloud Platform / Firebase Hosting, authentication, database (Firestore), Cloud Functions, Cloud Storage United States (multi-region) policies.google.com/privacy
Cloudflare DNS, CDN, DDoS protection United States / global edge cloudflare.com/privacypolicy
Sentry (Functional Software, Inc.) Error and crash tracking United States sentry.io/privacy
Resend Transactional and marketing email delivery United States resend.com/legal/privacy-policy
Stripe Payment processing United States stripe.com/privacy
OpenAI AI-generated illustrations for blog content (no user data submitted) United States openai.com/policies/privacy-policy

Notes

  • Audio content is never sent to any sub-processor. The Beepbox API processes encoding parameters and metadata; raw audio is not stored or transmitted.
  • Crash reports sent to Sentry are subject to automatic PII redaction before transmission. We never include raw audio content, contact data, IP addresses, or device identifiers.
  • OpenAI is used solely to generate illustrations published on the Beeping blog. We do not submit user-derived content (account data, API payloads, support emails) to OpenAI.
  • Payment card numbers are tokenised by Stripe and never reach our servers in unencrypted form.

Adding a New Sub-Processor

Before onboarding a new sub-processor, we:

  1. Verify the vendor publishes a privacy policy and offers a data processing agreement
  2. Sign the data processing agreement
  3. Update this page
  4. Where applicable, notify users of the change in advance

For questions about any vendor on this list, write to hello@beeping.io.


Last updated: May 9, 2026