Subprocessors
Last updated: October 13, 2026
Who helps us run VenueDB
When a venue uses VenueDB, we process the venue’s data on its behalf (see our Data Processing Agreement). To do that we use the companies below. Each is bound by a written agreement that requires them to protect the data and use it only to provide their service to us.
Current list
| Company | What they do | Data involved | Location |
|---|---|---|---|
| Supabase | Database hosting and file storage | All venue content and account data; uploaded files | United States |
| Upstash | Redis: background jobs and rate-limit counters | Short-lived job data, IP-address and email counters | United States |
| Resend | Delivery of system emails (verification, password reset, notifications) | Recipient email address, message content | United States |
| Stripe | Subscription billing and client payments | Billing contact, plan, payment status; card details go directly to Stripe | United States |
| Cloudflare (Turnstile) | Bot protection on sign-up, sign-in after repeated failures, and password reset | IP address and browser details of the visitor | United States / global network |
| “Continue with Google” sign-in; Gmail and Calendar, only if the venue connects them | Name, email, profile picture; mailbox and calendar data the venue chooses to connect | United States / global |
Services a venue chooses to connect itself (its own email account, Google Calendar, Stripe account, Social Tables, webhooks) are not our subprocessors: the venue directs that data to them.
Changes to this list
We will add or replace a subprocessor only after updating this page. To be told in advance, email privacy@venuedb.app and we will notify you at least 30 days before a new subprocessor starts handling your data. If you object on reasonable data-protection grounds, tell us in that time and we will work with you on an alternative or let you cancel without penalty.