Call Me Booked

Subprocessors

These are the outside companies that handle our clients' data for us, so that Call Me Booked can answer calls, send texts and run the service. Each is bound by a written contract to protect that data, and we require each not to use it for its own purposes, including training or improving any AI model. The last line of each entry shows when that company's data processing agreement with us came into force, where we have recorded it.

We give clients at least 30 days' notice by email before adding or replacing a subprocessor, as our Data Processing Addendum says. Questions: hello@callmebooked.com.

  • Supabase

    What we use it for
    Database, sign-in and file storage (call recordings, photos)
    Data it handles
    All account data: calls, recordings, transcripts, texts, customers, jobs, estimates and invoices
    Where
    Canada (Central)
    Data processing agreement
    In force since September 27, 2026 (accepted with its terms)

  • Vercel

    What we use it for
    Hosting the app and its phone and text webhooks
    Data it handles
    Everything passing between the app, the phone company and users' browsers while it is processed
    Where
    Canada (Montréal) for the app's servers; worldwide network for page delivery
    Data processing agreement
    In force since September 25, 2026 (accepted with its terms)

  • Twilio

    What we use it for
    Phone numbers, calls, call recording, texts, speech recognition and voicemail transcription
    Data it handles
    Call audio and recordings (until copied to our storage), what callers say, voicemail transcripts, texts, phone numbers and caller ID
    Where
    United States
    Data processing agreement
    In force since September 27, 2026 (accepted with its terms)

  • Telnyx

    What we use it for
    Second phone provider: phone numbers, calls, call recording, texts, speech recognition and voicemail transcription (only when it's switched on)
    Data it handles
    Call audio and recordings (until copied to our storage), what callers say, voicemail transcripts, texts, phone numbers and caller ID
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Google (speech recognition through Twilio and Telnyx)

    What we use it for
    Turns what callers say into text on Twilio calls, and in French and Spanish on the real-time voice service
    Data it handles
    Callers' speech while they talk to the assistant
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Deepgram (speech recognition through Twilio and Telnyx)

    What we use it for
    Turns what callers say into text on the live receptionist, on Telnyx calls and on the real-time voice service
    Data it handles
    Callers' speech while they talk to the assistant
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Amazon Polly (voices through Twilio and Telnyx)

    What we use it for
    The assistant's speaking voice
    Data it handles
    The assistant's words, which can repeat a caller's name, number or address back to them
    Where
    United States
    Data processing agreement
    Not recorded yet

  • ElevenLabs (voices through Twilio)

    What we use it for
    The assistant's natural speaking voice on calls
    Data it handles
    The assistant's words, which can repeat a caller's name, number or address back to them
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Real-time voice server host

    What we use it for
    Optional faster conversations (off unless set up in Setup) (only when it's switched on)
    Data it handles
    What callers say and the assistant's replies, as text
    Where
    Set per deployment
    Data processing agreement
    Not recorded yet

  • Anthropic (Claude)

    What we use it for
    The AI model that understands callers and texts, and writes summaries
    Data it handles
    Transcripts and texts (words only, no audio), with the business's own details
    Where
    United States
    Data processing agreement
    In force since September 18, 2026 (accepted with its terms)

  • Stripe

    What we use it for
    Subscription billing, and card payments customers make to a business
    Data it handles
    Billing contacts and payment details; customers' names and emails on payments
    Where
    United States
    Data processing agreement
    In force since September 24, 2026 (accepted with its terms)

  • Resend

    What we use it for
    App emails (alerts, reports, confirmations)
    Data it handles
    Email addresses and email contents, which can include call summaries
    Where
    United States
    Data processing agreement
    In force since September 26, 2026 (accepted with its terms)

  • Google (Calendar and Gmail)

    What we use it for
    A business's connected calendar, and our own sales email (only when it's switched on)
    Data it handles
    Calendar events for booked visits (customer name, address, time)
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Google Maps (Google LLC)

    What we use it for
    Looking up the postal code of an address a caller gives, suggesting addresses as people type on a business's booking page and in setup, and placing addresses on a map: checking whether an address is inside a business's service area, arrival-time estimates, crew start points, local weather, and placing a business's past customers on a map so storm mode can show which were in an official weather warning area (Pro)
    Data it handles
    Street addresses only, as typed or said (no names or phone numbers). Looked-up addresses and map positions are kept by us for 30 days at most, then looked up again or deleted
    Where
    United States
    Data processing agreement
    In force since October 9, 2026 (accepted with its terms)

  • Microsoft (Outlook / Microsoft 365)

    What we use it for
    A business's connected Outlook calendar, when it chooses Outlook (only when it's switched on)
    Data it handles
    Busy times (start, end, free or busy) read from the calendar; events for booked visits (customer name, phone, address, time)
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Jobber (Octopusapp Inc.)

    What we use it for
    A business's connected Jobber account, when it schedules in Jobber or brings its Jobber clients into the app (the business's own account, not our subprocessor) (only when it's switched on)
    Data it handles
    Busy times (start, end, who they're assigned to) read from the schedule; requests for booked visits (customer name, phone, address, time); with Jobber sync, the business's Jobber clients (name, phone, email, property addresses), requests and visits in the next 60 days
    Where
    Canada and the United States
    Data processing agreement
    Not recorded yet

  • JobNimbus

    What we use it for
    A business's connected JobNimbus account, when it schedules in JobNimbus (only when it's switched on)
    Data it handles
    Busy times (start and end of appointments) read from the calendar; appointments for booked visits (customer name, phone, address, time)
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Housecall Pro

    What we use it for
    A business's connected Housecall Pro account, when it schedules in Housecall Pro (only when it's switched on)
    Data it handles
    Busy times (start, end, who they're assigned to) read from the schedule; jobs for booked visits (customer name, phone, address, time)
    Where
    United States
    Data processing agreement
    Not recorded yet

  • CompanyCam (CompanyCam, Inc.)

    What we use it for
    A business's connected CompanyCam account, when it keeps job photos in CompanyCam (only when it's switched on)
    Data it handles
    For each booked visit: the customer's name and the address (to find or make its project), the photos the customer sent before the visit; the project's photos are read back
    Where
    United States
    Data processing agreement
    Not recorded yet

  • Intuit (QuickBooks Online)

    What we use it for
    A business's connected QuickBooks Online account, for its bookkeeping (only when it's switched on)
    Data it handles
    Invoices and payments made in the app, with the customer's name, phone, email and billing address
    Where
    Canada and the United States
    Data processing agreement
    Not recorded yet

  • Firebase Cloud Messaging (Google)

    What we use it for
    Notifications to the crew app (only when it's switched on)
    Data it handles
    Short alert texts about jobs and calls, sent to team members' phones
    Where
    United States
    Data processing agreement
    In force since October 9, 2026 (accepted with its terms)

  • Cloudflare

    What we use it for
    Domain names and email forwarding for our own addresses
    Data it handles
    Emails sent to our addresses while they are forwarded
    Where
    Worldwide network
    Data processing agreement
    In force since September 25, 2026 (accepted with its terms)
Subprocessors · Call Me Booked