About this list
These are the third-party service providers (sub-processors) that Barbeza uses to provide the Service and that may process personal information, including Client Data we process for shops. Each one is bound by a written contract that requires it to protect personal information and to use it only to provide its services to us. Read this list together with our Privacy Policy and our Data Processing Addendum, which sets out how we engage and oversee sub-processors.
Where personal information from the EEA, the UK or Switzerland is transferred to a country without an adequacy decision, we rely on Standard Contractual Clauses (with the UK International Data Transfer Addendum where relevant) or another lawful transfer mechanism. For transfers from Australia, we take reasonable steps to make sure each provider handles information consistently with the Australian Privacy Principles.
Current sub-processors
| Provider | What it does | Data involved | Location and transfer basis |
|---|---|---|---|
| Google Cloud / Firebase (Google LLC) | Database (Cloud Firestore), file storage (Cloud Storage) for photos and logos, and sign-in (Firebase Authentication, including phone one-time codes and Google sign-in). | All account and Client Data held in the Service, photos, sign-in identifiers, phone numbers, IP addresses. | The database region chosen for the Service, and other countries where Google operates. Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
| Vercel Inc. | Hosting and running the website, apps and server functions, and scheduled daily jobs. | Data passing through requests to the Service, IP addresses, technical logs. | United States and other countries where Vercel operates its network. Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
| Stripe (Stripe, Inc. and its affiliates) | Subscription billing, client payments through Stripe Connect, Tap to Pay, payouts, and payment fraud prevention and verification. | Names, email addresses, payment card and bank details (held by Stripe, not us), transaction amounts, device and fraud signals. | United States, Ireland and other countries where Stripe operates. Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
| Amazon Web Services (Amazon Web Services, Inc.) | Sending account and system email (Amazon SES), and storing the daily encrypted disaster-recovery backup (Amazon S3). | Email addresses and email content; for backups, a copy of the database, sign-in accounts and stored files. | Email: AWS Sydney region (ap-southeast-2) and other countries where AWS operates. Backups: Sydney, Australia (ap-southeast-2). Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
| Twilio Inc.Only for shops that enable SMS. | Sending SMS messages (reminders, confirmations and campaigns) for shops that turn SMS on. | Phone numbers, message content, delivery status and replies such as STOP. | United States and other countries where Twilio operates. Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
| Anthropic PBCOnly when a shop uses an AI feature. | AI model behind the AI booking assistant, the booking connectors and the shop AI helpers (such as menu photo import and reply drafts). | Chat messages, booking details, and the text or images a shop sends to an AI helper. | United States and other countries where Anthropic operates. Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
| Functional Software, Inc. (Sentry)Only when error monitoring is turned on. | Error monitoring, so we can find and fix faults. | Error details, technical logs, IP addresses and, occasionally, data contained in a failed request. | United States and other countries where Sentry operates. Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
| Browser push services (Apple, Google, Mozilla and other browser makers)Only if you allow notifications. | Delivering web push notifications to the browser or device you allowed. | Push subscription endpoint and the notification content (encrypted end to end to your browser). | The countries where your browser maker runs its push service. |
| Google Calendar API (Google LLC)Only when a barber connects calendar sync. | Calendar sync: reads busy times from a barber’s Google Calendar so those times cannot be booked, and adds the barber’s bookings to that calendar. | Calendar busy times and event times; booking times and service names written to the calendar. | United States and other countries where Google operates. Standard Contractual Clauses (and the UK Addendum) or an adequacy decision where required. |
Services you choose to connect
Some services are not our sub-processors because you or the shop choose to use them directly, under their own terms and privacy policies: Google or Apple sign-in, AI assistant platforms such as ChatGPT (OpenAI) or Claude (Anthropic) when a client books through a booking connector, and the Stripe account a shop connects to take payments.
Changes to this list
We update this page before a new sub-processor starts processing personal information, and show the new “last updated” date. Shops that want to be told about changes, or that wish to object to a new sub-processor on reasonable data protection grounds, can email hello@barbeza.com. How objections are handled is set out in our Data Processing Addendum.
Contact us
Brazaustra Pty Ltd (ABN 45 647 949 488). Email: hello@barbeza.com.
Bạn có câu hỏi về tài liệu này?
Chúng tôi thường phản hồi trong vòng hai ngày làm việc.