Overview
To deliver the PracticPro services, we engage carefully selected third-party providers ("Sub-processors") to process customer data on our behalf. This page lists those providers, what they do, and where they operate. We update this list as our infrastructure changes.
Our use of Sub-processors is governed by our Terms of Service and our Data Processing Addendum. Each Sub-processor is contractually bound to data-protection obligations no less protective than those in our agreement with you.
Pills explained: core means the Sub-processor is used by all customers as part of standard service delivery. optional means the Sub-processor is engaged only when a customer enables a specific feature or integration.
Get notified of changes
We give at least 30 days advance notice before adding a new Sub-processor or making a material change. To subscribe to those notifications, email us at privacy@practicpro.com with the subject "Subscribe to Sub-processor Updates".
Hosting and Infrastructure
Compute, storage, networking, and content delivery.
| Sub-processor |
Purpose |
Categories of data processed |
Location of processing |
| DigitalOcean, LLC core |
Cloud hosting for the PracticPro application, database, uploaded files, call recordings, and server backups. |
All customer data processed by the platform. |
United States (San Francisco region) |
| Cloudflare, Inc. core |
Content delivery network, TLS/HTTPS termination, DDoS protection, web application firewall, and DNS. Hosting and delivery of the websites PracticPro hosts for customers. Also runs PracticPro services on Cloudflare's platform: the MCP server and Copilot service, hosted forms and booking pages (with Turnstile bot protection), storage of public phone-greeting audio, and routing of inbound calendar-reply emails. |
Traffic metadata, IP addresses, request payloads in transit; content of customer websites and data their visitors submit; Copilot and MCP sign-in sessions and conversation audit records; form and booking-page submissions; phone-greeting audio; calendar-reply emails. |
Global |
Email Infrastructure
Used to send PracticPro's transactional emails (sign-in codes, system notifications) and emails from our website. Emails that you send through PracticPro to your own clients are sent through the Gmail account or mail server you connect, which you engage directly, or through this Sub-processor where your account uses PracticPro's default sending mailbox.
| Sub-processor |
Purpose |
Categories of data processed |
Location of processing |
| Google LLC (Google Workspace) core |
SMTP delivery of PracticPro's outbound transactional emails to customer users. |
Recipient email addresses, sender display names, message content (limited to PracticPro-system messaging). |
United States |
Communications
Voice calls, SMS, voicemail, and call-recording infrastructure.
| Sub-processor |
Purpose |
Categories of data processed |
Location of processing |
| Telnyx LLC core |
PracticPro's primary carrier: voice calls, SMS/MMS messaging, number search, purchase and porting, in-app calling, eSIM lines, and messaging (10DLC) registration. Also provides the AI platform for call transcription (Deepgram speech recognition), call summaries and AI text replies (open-weight language models hosted by Telnyx), and the AI Receptionist (language model plus voices from Telnyx, ElevenLabs, Microsoft Azure, Amazon Polly, or OpenAI, provided through Telnyx). |
Phone numbers, call metadata, message content, call recordings, voicemail; call audio and transcripts, message history, and your receptionist knowledge base for AI features. Telnyx's copy of a recording is deleted about 60 days after PracticPro has stored it. |
United States |
| Twilio Inc. core |
Voice calls and SMS for numbers hosted on Twilio, sign-in code text messages, in-app calling and call notifications, and phone-number lookups that return a contact number's carrier, line type, and location. |
Phone numbers (including your contacts' numbers, for lookups), call metadata, message content, call recordings, voicemail. Twilio's copy of a recording is deleted about 60 days after PracticPro has stored it. |
United States |
Maps, Location, and Notifications
Address lookup and maps, approximate location of IP addresses, and delivery of notifications to the PracticPro apps. Browser notifications are delivered through the push service of the user's browser vendor.
| Sub-processor |
Purpose |
Categories of data processed |
Location of processing |
| Google LLC (Google Maps Platform) core |
Address geocoding and autocomplete, maps, and time-zone lookup for job sites and time clock locations. |
Addresses and coordinates entered or recorded in PracticPro; IP address of the user's browser. |
United States |
| Mapbox, Inc. core |
Interactive maps of jobs and tickets, and map search. |
Addresses typed into map searches, map locations displayed; IP address of the user's browser. |
United States |
| ip-api.com core |
Approximate location of IP addresses for sign-in security and electronic-signature records. |
IP addresses of users, signers, and visitors to client-facing pages. |
To be confirmed |
| Google LLC (Firebase Cloud Messaging) optional |
Push notifications to the PracticPro Phone app on Android. |
Device push tokens, notification content (for example, caller or message details). |
United States |
| Apple Inc. (Apple Push Notification service) optional |
Call and message notifications to the PracticPro Phone app on iOS. |
Device push tokens, notification content (for example, caller or message details). |
United States |
Optional Features and Integrations
These Sub-processors are engaged only when a customer uses the corresponding feature or integration. Anthropic and OpenAI process data under business API terms and do not use customer data to train their models. AI voice, transcription, summary, and text-reply features run on Telnyx, listed under Communications above.
| Sub-processor |
Purpose |
Categories of data processed |
Location of processing |
| OpenAI, L.L.C. optional |
Speech-to-text for voice input, text-to-speech, and language-model inference when an OpenAI model is selected for the Copilot. Engaged only when these features are used. |
Text content submitted to AI features; audio for speech-to-text and text-to-speech. |
United States |
| Anthropic, PBC optional |
Language-model inference for the Copilot, AI employees, report questions, reading of uploaded images and documents, and as a fallback for AI text replies. Engaged only when these features are used. |
Prompts and the business records, messages, call information, images, and documents the feature needs to complete the request. |
United States |
| Google LLC (Gmail and Google Calendar) optional |
Sending email from a user's connected Gmail account, and Google Calendar synchronization, using Google sign-in (OAuth) to connect the account. |
Outgoing email content and recipients, email metadata, calendar events, attendee email addresses, OAuth tokens, Google account identifiers. |
United States |
| Stripe, Inc. (Stripe Connect) optional |
Online payments from your clients by card, Apple Pay, Google Pay, and bank transfer (ACH), plus account verification and payouts for your Stripe connected account. |
Payer name, email, and payment details (card and bank details are collected directly by Stripe), payment amounts and invoice references; business and owner identity details you give Stripe during account setup. |
United States |
| Intuit Inc. (QuickBooks Online and QuickBooks Payments) optional |
Accounting synchronization for customers who connect their QuickBooks Online account, and card or bank payments for customers who use QuickBooks Payments. |
Customer financial records, invoices, payments, bills, vendors, contacts; payment details (card details are tokenized in the payer's browser). |
United States |
Customer-Initiated Integrations
PracticPro offers ways for you to connect your account to third-party services of your choice, including AI assistants and automation platforms like Zapier, Make, and n8n via the Model Context Protocol (MCP), your own AI provider accounts, and direct API access. When you choose to connect a third party, that third party processes your PracticPro data under your own agreement with them, not under PracticPro's Sub-processor obligations. We do not direct or control what these third parties do with the data you ask them to access. Listed here for transparency about what is and is not in scope of our Sub-processor obligations.
| Connection type |
What it is |
Who is responsible for the third party's data handling |
| Model Context Protocol (MCP) |
You connect an AI assistant of your choice (for example, Claude or ChatGPT) to your PracticPro account. The AI assistant can then read and act on your PracticPro data under your direction. |
You and your chosen AI provider. PracticPro does not contract with the AI provider on your behalf. |
| Your own AI provider account |
You connect your own Anthropic, OpenAI, or Google (Gemini) account with your own API key, and PracticPro's AI features use that account. |
You and that AI provider, under your agreement with them. |
| Your own mail server |
You connect your own email account (for example, Outlook or another provider) by its mail-server settings so PracticPro can send email as you. |
You and your email provider. |
| REST API and OAuth |
You connect any third-party application of your choice to your PracticPro account using PracticPro's API or OAuth. |
You and the third-party application provider. |
| Outbound webhooks |
You configure PracticPro to send events to a URL you specify (for example, an automation platform). |
You and the operator of the destination service. |
Website Analytics and Advertising
The providers below collect data from visitors to PracticPro's public website. They do not run inside the PracticPro application and do not have access to data you store in PracticPro. For visitors from the European Economic Area, the United Kingdom, and Switzerland, Google Analytics and the Meta Pixel stay off until the visitor accepts them in the cookie banner; elsewhere they start on and can be turned off at any time in Privacy Controls. A Global Privacy Control signal keeps the Meta Pixel off. PracticPro does not use session-recording tools. See our Cookie Policy.
| Vendor |
Purpose |
Categories of data processed |
Location of processing |
| Google LLC (Google Analytics) |
Aggregate visitor analytics for the PracticPro public website, run in Google Consent Mode with advertising storage, advertising user data, and ad personalization denied. Loaded only with Performance cookies on: off by default for visitors from the EEA, UK, and Switzerland until they accept; on by default elsewhere until turned off. |
IP address, device and browser information, page-view events, referrer. |
United States |
| Meta Platforms, Inc. (Meta Pixel) |
Measuring and targeting PracticPro's advertising on Meta's platforms, from visits to the PracticPro public website. Loaded only with Targeting/Advertising cookies on: off by default for visitors from the EEA, UK, and Switzerland until they accept, on by default elsewhere until turned off, and always off when the browser sends a Global Privacy Control signal. |
IP address, device and browser identifiers, pages viewed, referrer. |
United States |
| CleanTalk |
Spam filtering for forms on the PracticPro public website. |
Submitted name, email address, message, and IP address. |
To be confirmed |
PracticPro Billing
The provider below processes data only in connection with PracticPro's billing relationship with you (the customer). It does not access or process data you store in PracticPro about your own clients, contacts, or projects. Listed here for full transparency.
| Vendor |
Purpose |
Categories of data processed |
Location of processing |
| Stripe, Inc. |
Processes subscription payments and other charges from PracticPro to the customer. |
Customer's billing contact information, cardholder data, and payment metadata for the PracticPro subscription. |
United States |
Cryptographic Timestamping (RFC 3161)
When you finalize a document in PracticPro, we generate a court-admissible timestamp proving the document existed in its finalized form at that point in time. To do this, we send a SHA-256 hash of the finalized PDF to a public Timestamp Authority (TSA), which returns a signed timestamp token that we store with the document. We send only the hash. The Timestamp Authority does not receive, see, or store the document itself or any of its content. Because no personal data is transferred, these Timestamp Authorities are not Sub-processors. They are listed here for transparency.
| Vendor |
Purpose |
Categories of data processed |
Location of processing |
| DigiCert, Inc. |
RFC 3161 Timestamp Authority. Returns a signed timestamp token for finalized documents. |
SHA-256 hash of the finalized PDF only. No document content, customer data, or personal data is transmitted. |
United States |
| Sectigo Limited |
RFC 3161 Timestamp Authority. Returns a signed timestamp token for finalized documents. |
SHA-256 hash of the finalized PDF only. |
United Kingdom |
| SSL Corp (SSL.com) |
RFC 3161 Timestamp Authority. Returns a signed timestamp token for finalized documents. |
SHA-256 hash of the finalized PDF only. |
United States |
| Entrust Corporation |
RFC 3161 Timestamp Authority. Returns a signed timestamp token for finalized documents. |
SHA-256 hash of the finalized PDF only. |
United States / Canada |
How we evaluate Sub-processors
Before engaging a new Sub-processor, we perform a written assessment that covers data protection, security posture, and contractual safeguards. Each Sub-processor is bound by a written agreement that imposes data-protection obligations no less protective of customer data than those we owe you.
Changes to this list
We will provide at least 30 days advance notice before adding a new Sub-processor or making a material change, except in cases of urgent operational need. To receive notifications, email privacy@practicpro.com with the subject "Subscribe to Sub-processor Updates".
Questions
If you have questions about a Sub-processor or want to object to a planned change, contact us at privacy@practicpro.com.