Trust Center

Security Overview

How PracticPro protects customer data across our infrastructure, applications, and staff.

Last updated October 20, 2026

This page summarizes the technical and organizational security measures PracticPro uses to protect customer data. It is intended to be readable by privacy and security professionals as well as the business owners who are our customers. For the full contractual commitments, see our Data Processing Addendum.

Hosting and Infrastructure

The PracticPro application is hosted on DigitalOcean in the United States (San Francisco region). The production application, database, uploaded files, call recordings, and server backups live within DigitalOcean's infrastructure. DigitalOcean maintains industry-standard physical security controls and is independently audited (SOC 2, ISO 27001).

All public traffic to PracticPro is routed through Cloudflare for TLS termination, DDoS protection, and content delivery. Some PracticPro services run on Cloudflare's platform itself: the MCP server and Copilot service (including its sign-in sessions and conversation audit records), hosted forms and booking pages, and public phone-greeting audio. We enforce HTTPS-only access with HSTS.

Call recordings are first created by our telephony providers (Telnyx and Twilio). PracticPro copies each recording to its own storage, and the provider's copy is deleted about 60 days later. Each customer chooses how long PracticPro keeps recording audio (kept until deleted by default, or automatically deleted after 30 days up to 5 years); transcripts are kept until deleted. Customer websites hosted by PracticPro are hosted and delivered through Cloudflare.

Encryption

In transit

All public connections to PracticPro use TLS 1.2 or higher, and we do not accept unencrypted connections from browsers or apps. The database and cache run on the same server as the application and are not exposed to the network.

At rest

Sensitive values, including connected-account tokens (such as Google and QuickBooks), API keys, bank account numbers used for check printing, and sign-in codes, are encrypted at the application level before they are stored. PracticPro does not store full card numbers; card and bank details for payments are held by Stripe.

Access Controls

Customer access to the application

PracticPro does not use passwords. Customer users sign in with a one-time six-digit code sent to their registered phone number or email address. Codes expire after 30 minutes, repeated wrong codes lock the sign-in, and a fresh code is required again for sensitive payment actions such as refunds, bank-account changes, and payouts. Within a customer account, access to records is governed by role-based permissions configurable by the account administrator.

AI assistants that you connect through MCP sign in with OAuth 2.1 (with PKCE). Their access tokens last one hour, and higher-risk actions require your explicit approval.

PracticPro staff access to customer data

Access to customer data by PracticPro personnel is restricted to those with a documented business need (for example, to provide support requested by the customer or to investigate a security incident). Such access is logged.

Production system access

Direct access to production servers and databases is limited to a small set of authorized engineers, secured with strong authentication and audit logging.

Network Security

  • Cloudflare provides perimeter protection (DDoS and WAF) at the edge, and restricts access to the application to a list of allowed countries.
  • Firewalls restrict ingress to production hosts to required ports only, and web traffic is accepted only from Cloudflare.
  • Operating systems and dependencies are patched on a regular cadence; critical security patches are applied promptly after disclosure.
  • Security headers (HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy) are enforced on every response.

Logging and Monitoring

  • Significant administrative actions affecting customer data are logged.
  • Application logs and access logs are retained for operational and security purposes.
  • Sign-in events (code requests, successful sign-ins, and failed attempts) are logged.
  • Attempt limits, lockouts, and resend cooldowns on sign-in codes protect against brute-force attacks.
  • Payment actions and actions taken by AI employees are recorded in dedicated audit logs.

Personnel Security

  • PracticPro personnel are bound by written confidentiality obligations.
  • Personnel with access to customer data receive privacy and security training.
  • Access is provisioned on the principle of least privilege and revoked promptly on role change or departure.

Vendor and Sub-processor Management

Every third party that touches customer data is engaged under a written agreement that imposes data-protection obligations no less protective than those we owe our customers. The current list of sub-processors is published at practicpro.com/trust/sub-processors. We provide at least 30 days advance notice before adding a new sub-processor.

Backups and Disaster Recovery

  • Customer data is backed up automatically each week through DigitalOcean's backup service.
  • Database logs are kept for three days so recent changes can be recovered between weekly backups.

Incident Response

We maintain documented incident response procedures covering triage, containment, communication, remediation, and post-incident review.

In the event of a Personal Data Breach affecting a customer's data, we will notify the affected customer without undue delay, and in any event no later than 72 hours after becoming aware. Details of what the notice will contain are set out in Section 8 of our DPA.

To report a suspected security issue, see our Vulnerability Disclosure page.

Application Security

  • CSRF tokens are enforced on all state-changing requests.
  • Parameterized queries are used to prevent SQL injection.
  • Input validation and output encoding protect against XSS and injection attacks.
  • Sign-in uses single-use codes generated with a cryptographically secure random number generator; no passwords are stored.
  • Session cookies are flagged Secure, HttpOnly, and SameSite=Lax; sessions invalidate appropriately on sign-out.
  • Incoming webhooks from our telephony and payment providers are verified by their signatures.
  • Dependencies are tracked and security advisories are reviewed regularly.

Data Residency and International Transfers

Customer data is processed in the United States. Where customer data of EEA, UK, or Swiss residents is transferred to the United States, the EU Standard Contractual Clauses, the UK International Data Transfer Addendum, or equivalent Swiss mechanisms apply, as incorporated into our DPA.

Compliance and Certifications

GDPR / UK GDPR / FADP

Processor obligations met via our DPA, including 72-hour breach notification, sub-processor controls, and SCC-based international transfers.

In place

CCPA / CPRA

Service Provider obligations met via our DPA and Privacy Policy.

In place

SOC 2 Type II

Independent third-party attestation of our security controls.

Planned

ISO 27001

Information security management system certification.

Planned

HIPAA

PracticPro does not currently support HIPAA-covered use cases and does not sign Business Associate Agreements. The Services should not be used to store Protected Health Information.

Not supported
Certifications marked "Planned" represent active or near-term work. We will update this page when status changes. To follow updates, you can subscribe to Sub-processor change notifications, which we also use for material trust-related announcements.

Customer Responsibilities

Security is a shared responsibility. PracticPro secures the platform; customers are responsible for:

  • Protecting user account credentials, including enabling multi-factor authentication where appropriate.
  • Granting platform access only to authorized personnel and revoking it promptly when no longer needed.
  • Configuring the platform appropriately for their use case (for example, AI feature settings, recording controls, retention preferences).
  • Complying with applicable law when processing personal data through the Services, including any necessary disclosures to end clients.

Contact

To report a suspected security issue, email security@practicpro.com and see our Vulnerability Disclosure page. For privacy or data-protection questions, email privacy@practicpro.com.