This register lists the subprocessors Vary Services LLC uses to provide Pricey that may receive or store personal data processed for Customer under Schedule C. Additions and replacements after the date of this register follow Schedule C5 and are recorded in a new dated register.
Subprocessors
| Subprocessor | Purpose | Personal data | Processing location |
|---|---|---|---|
| Render Services, Inc. | Hosting and compute for the Pricey dashboard, APIs and background workers | All Customer data the service processes, in transit and in memory | United States, Oregon (Google Cloud us-west1) for www.priceyticketing.com; other Pricey services [confirm] |
| Cloudflare, Inc. | Network edge in front of the hosted service, and hosting of the booking page files at booking.priceyticketing.com | IP addresses and request data of guests and staff passing through the network | Global edge network [confirm] |
| MongoDB, Inc. (MongoDB Atlas) | Primary database | Guest and booking contact details (name, email, phone and billing address, stored encrypted), orders, reservations, payment and refund records, form and waiver responses, staff accounts | [confirm] |
| Amazon Web Services, Inc. (Amazon S3) | File storage | Member photos where photo verification is used, uploaded import files that may contain guest details, merchant images | United States, Ohio (us-east-2) [confirm for production] |
| Redis Cloud [confirm provider] | Job queues and short-lived caches | Order, booking and job identifiers [confirm that no contact details are queued] | [confirm] |
| Postmark (ActiveCampaign, LLC) | Transactional email: confirmations, tickets, invoices, sign-in codes and staff invitations | Recipient name and email address, and message content including booking details | [confirm] |
| Twilio Inc. | SMS notifications, where enabled | Recipient phone number and message content | [confirm] |
| Stripe, Inc. | Payment processing on Customer's own Stripe connected account | Card and billing details entered in Stripe's own payment fields, purchaser name and email address on the Stripe customer record, payment and refund records | [confirm] |
| PayPal, Inc. | Payment processing, only where Customer enables PayPal | Payment details entered with PayPal, payment and refund records | [confirm] |
| Okta, Inc. (Auth0) | Sign-in for Customer staff | Staff name, email address and sign-in records | United States [confirm for the production tenant] |
| Anthropic, PBC | AI booking assistant, only where Customer enables it without supplying its own AI provider key | Guest chat messages, which may include names, dates and party details | [confirm] |
| Google LLC (Google Wallet) | Digital wallet passes, only where offered | Ticket holder or member name, and the event, date and order reference shown on the pass | [confirm] |
| Functional Software, Inc. (Sentry) [confirm whether enabled] | Error monitoring | Error reports, with request bodies, credentials, IP addresses, email addresses and phone and card-like numbers removed before sending | [confirm] |
Customer-connected providers
These systems are connected because Customer uses them and contracts with them directly. Pricey exchanges booking data with them on Customer's instruction. They are not Vary's subprocessors. The providers connected for a particular Customer are identified in its Order Form and Statement of Work.
| Provider | What Pricey exchanges with it |
|---|---|
| Cloudbeds | Hotel availability, reservations, guest name and contact details, and folio payments and adjustments |
| RocketRez | Activity availability, bookings and guest details |
| Other booking systems Customer connects (RocketBooking, Roller, RMS, Newbook, OCTO suppliers such as Xola, Peek, Ventrata and Zaui) | Availability, bookings and guest details |
| Distribution channels Customer connects (GetYourGuide, Viator) | Bookings received from the channel and their guest details |
| Retail systems Customer connects (Shopify, Square) | Retail order lines, with the purchaser's name and email address (and phone number, for Shopify) |
| Email providers Customer connects for its own sending (SendGrid, Mailgun, Amazon SES, Resend or its own SMTP server) | Recipient email address and message content |
| Marketing and analytics tools Customer connects (Mailchimp, ActiveCampaign, Constant Contact, Google Analytics, Google Tag Manager, Meta Pixel) | The contact or event data Customer configures them to receive |
| An AI provider whose key Customer supplies (OpenAI or Anthropic) | Guest chat messages to the AI booking assistant |