Subprocessors
Last updated: 17 April 2026
A subprocessor is a third party we engage to process personal data on our behalf. The table below names every subprocessor we currently use, the purpose of their processing, and the region where that processing takes place. This list is kept in git alongside our privacy policy; commit history on this page is the authoritative change log.
Current subprocessors
| Name | Purpose | Region |
|---|---|---|
| Supabase | Authentication, database, file storage | AWS eu-west-2 (London, UK) |
| Amazon Web Services (AWS) | Compute (Lambda), image storage, image moderation (Rekognition), monitoring | eu-west-2 (London, UK) |
| OpenAI | Accessibility alt-text generation for food photos | United States |
| Sentry | Error tracking and crash reporting (PII scrubbed before send) | United States |
| Foursquare | Nearby-venue search for meal location tagging (coordinates coarsened to ~110m before request) | United States |
| Expo / EAS | Over-the-air mobile updates, build infrastructure | United States |
| Firebase Cloud Messaging (Google) | Push-notification delivery to Android devices | United States |
| Apple Push Notification service | Push-notification delivery to iOS devices | United States |
| Cloudflare | DNS and CDN for bemeal.app and the landing site |
Global edge network |
| GitHub (Microsoft) | Source code hosting; incidental to operating the service, does not process end-user personal data | United States |
Changes to this list
We will add a new subprocessor only when necessary to deliver or improve the service. Material additions are reflected here and in the privacy policy. The git commit history of this page provides a dated audit trail of every change; there is no separate mailing-list sign-up required to be informed.
Contact
Questions about subprocessors or data-processing arrangements can be sent to support@bemeal.app.