Beeping← Back to Home

Sub-Processors

Last updated: 2026-05-09

Effective: May 9, 2026

Beeping uses the third-party infrastructure vendors listed below ("sub-processors") to operate and secure the platform. 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. For questions regarding sub-processors, write to hello@beeping.io.

Current Sub-Processors

Vendor Purpose Location Privacy Policy
Google Cloud Platform / Firebase Hosting, database (Firestore), Cloud Functions, Cloud Storage European Union & Global multi-region policies.google.com/privacy
Cloudflare DNS, CDN, DDoS protection Global edge network cloudflare.com/privacypolicy

Notes

  • Audio content is never sent to any sub-processor. The acoustic protocol processes data locally and transiently on device; raw ambient audio is never recorded, stored, or transmitted to any server.
  • Zero payment processing: Pre-release and developer access are provided free of charge (0,00 €). We do not collect or process payment card data.

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