Subprocessor model. GastroGrowth uses subprocessors to host, secure, monitor, build, support, and integrate the platform. Some providers are standard platform dependencies; others apply only when a restaurant enables a feature or integration.
Current Subprocessor Categories
| Provider / category | Purpose | Data involved |
|---|---|---|
| Supabase | Database, authentication, storage, edge/platform infrastructure | Customer/order data, account data, staff/admin data, logs |
| Sentry | Error monitoring, crash diagnostics, release health | Technical logs, device/app data, error context, limited account identifiers |
| hCaptcha | Captcha and abuse prevention for account and form flows | Device, browser, network, challenge, and anti-abuse signals |
| Google Analytics | Consent-gated acquisition measurement on the public GastroGrowth marketing website | Canonical page path and title, consented event names, bounded campaign attribution, browser/device and cookie identifiers |
| Google Maps Platform | Address autocomplete, place details, map previews, map embeds when enabled | Address search queries, place identifiers, map interaction data |
| Expo, Apple, and Google | Mobile builds, app distribution support, push notification delivery, app-store operation | Device push tokens, app identifiers, build metadata, notification metadata |
| Hosting, DNS, CDN, and deployment providers | Application hosting, routing, TLS, static assets, logs, backups | Technical logs, app traffic, hosted customer/order data |
| OpenRouter and selected AI model providers | AI-assisted menu import, parsing, extraction, and internal workflow support when enabled | Restaurant-provided menu files, product text, images, and operational context |
| Payment, delivery, POS, email, SMS, and marketplace providers | Optional integrations chosen or approved by the restaurant operator | Only the data needed for the enabled integration, often under separate provider terms |
This page is a public summary. Signed enterprise agreements or app store submissions may require a more exact provider-by-provider list, processing location, and transfer mechanism before production launch.
Changes And Objections
Restaurant operators may object to a new subprocessor where they have a reasonable data protection basis. If the objection cannot be resolved and the subprocessor is required for the service, GastroGrowth may suspend or terminate the affected service as described in the applicable agreement.
Need a different format?
Restaurant operators and app reviewers can request a signed agreement, client-specific privacy notice, store submission copy, or DPA exhibit at privacy@gastrogrowth.com.
Open Privacy Policy