Subprocessor list
The infrastructure and communications providers used for barber client data, with planned providers clearly separated from active ones.
Last updated 13 September 2026
Active providers
| Provider | Purpose | Data involved | Status |
|---|---|---|---|
| Supabase | Database, authentication and profile-photo storage | Account, profile and future booking data; authentication identifiers; files | Active |
| Vercel | Application hosting, content delivery and operational logs | Requests, IP and device information, rendered content and fault logs | Active |
| Resend | Authentication and service email | Email address, message content and delivery events | Active |
| Cloudflare | Turnstile bot check on the signup, login, password-reset and newsletter forms | IP address, device and browser signals, and the interaction with the challenge | Active |
| Stripe | LineupUK’s single flat monthly subscription, billing portal and invoices. No Stripe Connect, client deposits or barber payouts. | Barber email address, payment method and billing records. Card details are entered on Stripe’s own page and never reach LineupUK. | Active |
Planned but not active for booking data
| Provider | Purpose | Activation gate |
|---|---|---|
| Twilio | Booking confirmations, reminders and cancellation SMS | Added when SMS notifications are enabled and the sender registration is ready. |
Locations and transfers
The primary Supabase database region is London. Providers may use global infrastructure or support operations. The signed provider agreements, current subprocessor disclosures and any applicable UK transfer mechanism determine the exact processing locations. Those records are reviewed before activation and maintained internally.
Changes
We update this page before a planned provider begins handling barber client data and provide reasonable advance notice to affected barbers. A barber may object on reasonable data-protection grounds under the Data Processing Agreement. Questions can be sent to bookings@lineupuk.com.