Sub-processors
Last updated: 8 November 2026
These are the companies we use to run Restocarte, what each does and the data it receives. See our Privacy Policy for what each kind of data is and how long we keep it.
Providers
| Provider | What they do | Data |
|---|---|---|
| Cloudflare | CDN and reverse proxy in front of the site and images | Connection data such as IP addresses, and the traffic passing through |
| Backblaze (EU Central) | Encrypted off-site backups | A copy of account, menu and order data and images |
| Upstash | Rate limiting | Counters keyed to the request, which can include an IP address |
| Resend | Transactional email | Recipient address and message content |
| Stripe | Guest card payments and verification of a venue's connected account | Order amount, currency, guest email where provided, venue verification details |
| Google (Firebase Cloud Messaging) | Push notifications to the mobile app, forwarded to Apple's push service on iOS | Device token and notification content |
| Sentry | Error and performance monitoring, when enabled | Technical diagnostics that may incidentally include a user identifier or IP address |
Independent controllers
Paddle (subscription billing, as merchant of record) and Stripe act as controllers in their own right for the payment data they hold. If you sign in with Google or Facebook, that provider is also an independent controller of your account with it. The Meta Pixel on our marketing pages runs only with consent and never on venue menus or in the dashboard.
Changes
When we add or replace a provider we update this page. Questions can be sent to [email protected].