About this list
These are the third-party service providers that process personal information when IntelliDent provides its platform, including information we handle on behalf of dental practices. It forms part of our Privacy Policy and Terms of Service. We update this page when we add or change a provider.
Several providers process information outside Australia. Section 9 of the Privacy Policy explains overseas disclosure.
Service providers
Amazon Web Services (AWS)
- Purpose: Hosting and infrastructure: application servers, the database (Amazon DynamoDB), file storage including call recordings (Amazon S3), transactional email (Amazon SES), and secret storage.
- Personal information: All information held in the platform, including account details, patient records, appointments, call recordings, transcripts, and uploaded documents.
- Location: Australia. Application data is configured for the AWS Asia Pacific (Melbourne) region; email is sent through AWS Asia Pacific (Sydney).
Twilio
- Purpose: Phone numbers, connecting and recording calls, streaming live call audio to the AI agent (ConversationRelay), and sending SMS and WhatsApp messages such as appointment reminders.
- Personal information: Caller and recipient phone numbers, call audio and recordings, speech-to-text results, message content, and call details such as time and duration.
- Location: United States. The platform uses Twilio’s default region; no other Twilio region is configured.
Google (speech services through Twilio)
- Purpose: Converting callers’ speech to text and agent replies to speech during live calls. Google is the default speech provider configured for Twilio ConversationRelay; a practice’s agent may be set to another provider offered by Twilio.
- Personal information: Live call audio and the text produced from it.
- Location: Outside Australia. The processing location is determined by Twilio and Google.
OpenAI
- Purpose: Generating AI agent replies (the default model provider), classifying what a caller is asking for, creating text embeddings for knowledge base and patient search, the in-app assistant, and fine-tuning when a customer requests it.
- Personal information: Conversation text (with certain identifiers removed on phone calls), agent instructions and clinic information, relevant knowledge base content, caller context such as name and upcoming appointments, documents being indexed, and training files a customer uploads for fine-tuning.
- Location: United States.
Anthropic
- Purpose: Generating AI agent replies for agents set to use Claude models, the IntelliDent website chat assistant, and summaries of IntelliDent’s own sales conversations.
- Personal information: For Claude agents, the same types of information as OpenAI above. For the website chat, messages and any contact details a visitor types.
- Location: United States.
Stripe
- Purpose: Subscription billing, invoices, and payment links.
- Personal information: Billing contact name and email, business name, transaction records, and payment details entered on Stripe’s pages. IntelliDent does not receive full card numbers.
- Location: United States and other countries where Stripe operates.
Google (reCAPTCHA and Google sign-in)
- Purpose: Protecting website forms from spam and abuse, and optional “Sign in with Google” for dashboard users.
- Personal information: For reCAPTCHA: IP address, browser and device information, and interaction data. For Google sign-in: name, email address, and profile identifier.
- Location: Outside Australia.
Integrations a practice chooses to connect
These are not IntelliDent’s subprocessors. When a practice connects one, information flows to the practice’s own account with that service, under the practice’s agreement with the provider.
- Google Calendar: Reading availability and writing bookings to the practice’s calendar.
- Microsoft Outlook calendar: Reading availability and writing bookings to the practice’s calendar.
- CalDAV calendars: Reading availability and writing bookings to a calendar server the practice provides.
- HubSpot and Salesforce: Syncing contacts and activity with the practice’s CRM, where the practice connects one.
- Webhooks and custom connectors: Sending booking and contact information to an endpoint the practice configures.
- The practice’s own OpenAI or Anthropic account: When a practice supplies its own AI API key, that provider processes the agent’s conversations under the practice’s account.