Subprocessors

ClientConnect (operated by Client Connect LLC, which also operates the SkyConnect brand on the same platform) uses the third-party services below to provide the Services. A "subprocessor" is a company that processes Personal Data on our behalf so that some part of the product can work — sending a text message, taking a payment, storing a file.

This page is the list referred to in our Data Processing Agreement. We update it when we add or replace a subprocessor, and we do so before the new subprocessor begins processing Personal Data for you. If you object to a subprocessor, contact us at support@clientconnect.tech.

Each entry says what the service is used for, what data it receives, and whether it applies to every account or only when you turn on the relevant integration. Nothing in the "only when connected" group receives anything at all unless you connect it yourself.

Used for every account

Google Cloud Platform (Google LLC)

• Used for: Hosting the application itself. Our servers run on Google Cloud Run in the United States (us-central1).
• Data received: Everything the Services process passes through these servers in the course of being handled, along with the technical request data (IP address, browser or app version) any web server receives.
• Applies to: All accounts.

MongoDB Atlas (MongoDB, Inc.)

• Used for: The database in which the Services store their records.
• Data received: All stored service data — accounts and profiles, appointments and calendars, booking links, contacts, message history, and billing records. Third-party access tokens are encrypted by us before they are written, so the database holds ciphertext for those.
• Applies to: All accounts.

Google Cloud Storage (Google LLC)

• Used for: Storing uploaded files — documents exchanged between a business and its clients, invoice PDFs, and business logos.
• Data received: The file contents and file names, together with whatever Personal Data those files happen to contain.
• Applies to: All accounts, wherever a file is uploaded or an invoice PDF is generated.

Stripe (Stripe, Inc.)

• Used for: Subscription billing for our own service, and payments taken by a business from its clients.
• Data received: Payer name and email address, transaction amounts, descriptions and dates, and payment references. Card details are entered directly with Stripe and do not pass through our servers. A business that accepts payments also provides Stripe with the identity and bank details Stripe requires to verify it.
• Applies to: All accounts.

Twilio SendGrid (Twilio Inc.)

• Used for: Delivering transactional email — booking confirmations and notices, account email, and invoice copies.
• Data received: Recipient name and email address, the content of the message (which includes appointment details), and any attached invoice PDF.
• Applies to: All accounts.

Vonage (Vonage Holdings Corp.)

• Used for: Sending and receiving the text messages the Services send, and placing automated phone calls.
• Data received: Sending and receiving phone numbers, the full content of each message, the content spoken in an automated call, and delivery metadata such as timestamps and delivery status.
• Applies to: All accounts that send text messages or automated calls.

Google Firebase (Google LLC)

• Used for: Delivering push notifications to our mobile apps (Firebase Cloud Messaging) and receiving crash reports from them (Firebase Crashlytics).
• Data received: Device push registration tokens and the content of each notification, which is limited to event metadata such as "New booking from Jane Smith at 2:00 PM". Crash reports carry stack traces and device metadata (model, OS version, free memory), not screen contents or request bodies.
• Applies to: Accounts used through our mobile apps.

Apple (Apple Inc.)

• Used for: Delivering push notifications to iOS devices through the Apple Push Notification service (routed via Firebase), Sign in with Apple, and confirming the status of subscriptions bought through the App Store.
• Data received: Device push tokens and notification content as above; for Sign in with Apple, the account identifier and email address Apple itself issues; for App Store subscriptions, the transaction identifiers Apple issues.
• Applies to: Accounts used through our iOS app.

Only when you connect the integration

Google Calendar and Google Meet (Google LLC)

• Used for: Writing booked appointments to your Google Calendar, reading your existing calendar so busy times are respected, and creating Google Meet links. Google also receives your name and email address if you choose to sign in with Google.
• Data received: The appointment title (which contains the client's name), start and end times, the client's email address as an attendee, and the event description, which carries the service booked, the client's phone number and address, and any notes they entered.
• Applies to: Only accounts that connect a Google account.

Microsoft Outlook Calendar and Microsoft Teams (Microsoft Corporation)

• Used for: The same calendar sync and meeting links as above, through Microsoft Graph. Microsoft also receives your name and email address if you choose to sign in with Microsoft.
• Data received: The same appointment details as the Google entry — subject containing the client's name, times, the client's email address as an attendee, and a body carrying the service, phone number, address and notes.
• Applies to: Only accounts that connect a Microsoft account.

Zoom (Zoom Communications, Inc.)

• Used for: Creating a Zoom meeting for appointments booked as a Zoom service.
• Data received: The meeting topic, which contains the client's name, plus the start time, duration and time zone. Connecting also identifies your own Zoom account to us.
• Applies to: Only accounts that connect a Zoom account.

Apple iCloud Calendar (Apple Inc.)

• Used for: Reading your iCloud calendar over CalDAV so that existing commitments block out availability. We read from iCloud only — appointments booked through the Services are not written to it.
• Data received: The Apple ID and app-specific password you supply, which we send to Apple to authenticate the connection.
• Applies to: Only accounts that connect an iCloud calendar.

Intuit QuickBooks Online (Intuit Inc.)

• Used for: Creating and sending invoices in your own QuickBooks company when you choose QuickBooks invoicing.
• Data received: Your client's name and email address (as a QuickBooks customer record), and the invoice amount, line description and date.
• Applies to: Only accounts that connect a QuickBooks company. If no QuickBooks account is connected, nothing is sent to Intuit.

PayPal (PayPal, Inc.)

• Used for: Connecting your own PayPal business account, through PayPal Commerce Platform, so that your clients can pay you with Venmo.
• Data received: An identifier we generate for your account, used to track the onboarding. Your business details are entered by you directly with PayPal, on PayPal's own hosted onboarding pages.
• Applies to: Only accounts that connect a PayPal business account.

Analytics and advertising on our website and apps

These services are not used to process your business records. They measure how our website is used and how our advertising performs. They are loaded on all pages of clientconnect.tech, which includes signed-in pages and booking pages, so they see the addresses of the pages visited there.

Google Analytics and Google Ads (Google LLC)

• Used for: Measuring website usage and advertising conversions.
• Data received: Page addresses viewed, referring page, device and browser information, IP address, and cookie identifiers.
• Applies to: All visitors to our website.

Microsoft Clarity (Microsoft Corporation)

• Used for: Understanding how pages are used, through heatmaps and session recordings.
• Data received: The same page, device and cookie information as above, plus a recording of the page as rendered in the browser and the interactions with it.
• Applies to: All visitors to our website.

LinkedIn Insight Tag (LinkedIn Corporation)

• Used for: Measuring advertising conversions and building advertising audiences.
• Data received: Page addresses viewed, device and browser information, IP address, and cookie identifiers.
• Applies to: All visitors to our website.

Questions

To ask about this list, or to object to a subprocessor, contact us at:

Email: support@clientconnect.tech
Address: 1404 Beechwood Ave Nashville, TN 37212