Commercial

SimplePractice EU Client Data Checklist

SimplePractice EU client data checklist for therapists: privacy roles, clinical records, exports, connected services, payments, AI add-ons, portal access.

By Tregovia Editorial · How we verify what we publishPublished 6 min read
SimplePractice EU Client Data Checklist
Summary

SimplePractice EU client data checklist for therapists: privacy roles, clinical records, exports, connected services, payments, AI add-ons, portal access. It covers data categories to separate, documents and questions to review, ai add-ons deserve their own line in the review, not a general assumption, and Tregovia review scope.

SimplePractice and EU Client Data: What EU Therapists Should Verify

EU therapists comparing SimplePractice with a CRM should treat client data as the central issue, not an afterthought. Therapy records can include identity details, appointment history, billing, intake forms, consent forms, clinical notes, client portal messages, payment references, telehealth context, and insurance-related data.

The risk is not only where data is hosted. It is whether the therapist understands which system holds which data, who can access it, how it can be exported, how long it must be retained, and whether the receiving system is suitable for that type of record.

As checked on July 19, 2026, SimplePractice listed Starter, Essential, and Plus plans on its official pricing pages. Its Terms of Service page showed a last-updated date of August 2, 2023 and included sections on fees and billing, user data, data privacy, third-party materials, and service-specific terms. SimplePractice support material also referenced the Business Associate Agreement, privacy documents, trust and security information, and AI add-on terms. Verify the current pages directly before making a decision.

Data Categories To Separate

Use this table before export or comparison:

Data categoryExamplesShould it move to CRM?
Client identityname, email, phoneOften yes
Appointment datafuture bookings, cancellationsOften yes
Billing datainvoices, balances, refundsOften yes
Intake formsoperational or clinical answersCase by case
Consent formssigned documents, portal recordsCase by case
Clinical notestherapy notes, diagnosis contextNot by default
Telehealth recordssession-related recordsNot by default
Insurance recordsclaims, payer detailsNot by default
Messagesadmin or clinical contentReview carefully

If a record is clinical, do not move it simply because a CSV export exists.

Documents And Questions To Review

Ask these questions while reviewing current vendor pages:

  • What role does the vendor say it plays for client data?
  • Which privacy policy applies to clinicians and which applies to clients?
  • Are vendor terms available for EU client-data handling?
  • Which connected services handle hosting, support, analytics, SMS, email, payments, AI, or telehealth?
  • What export options exist for clients, appointments, invoices, forms, notes, and messages?
  • What happens after cancellation?
  • Can client portal access continue, close, or change?
  • How are AI add-ons governed if they touch sessions, transcripts, or notes?
  • Which payment-provider terms apply?
  • What does the practice need to retain independently?

For wider context, read the EU data-hosting guide. It should help structure questions, not replace legal review.

AI Add-Ons Deserve Their Own Line In The Review, Not A General Assumption

Practices using AI-assisted note-taking, session summarization, or transcript features need to review those specifically, separately from the platform's general privacy terms, because AI processing introduces a data flow that traditional record storage does not: a third-party model may process session content, even briefly, to generate a summary or draft note. Whether that processing happens within the same vendor's infrastructure, through a sub-processor, or through an external AI provider changes the actual risk profile in ways a general "is my data hosted securely" question does not capture.

A practice that has enabled an AI add-on without separately reviewing its specific terms has effectively made a data-processing decision about clinical session content without documenting it, which is a different and more consequential gap than simply not knowing where backups are stored. Any EU therapist reviewing SimplePractice, or comparing it against a CRM, should ask explicitly whether AI features are enabled, what they process, and whether that processing has been separately assessed against the practice's own data-protection obligations, rather than assuming it falls under the same general privacy umbrella as ordinary record storage.

Tregovia Review Scope

For therapists, evaluate Tregovia only against the operational side first:

  • Client contact records
  • Future appointments and reminders
  • Invoices, balances, refunds, and reports
  • Online booking where it fits the practice
  • Operational intake or form status
  • Non-clinical follow-up
  • Import and export planning

Tregovia can be evaluated for client records, appointment operations, billing, reminders, intake, and follow-up workflows. Tregovia does not guarantee GDPR compliance or replace SimplePractice clinical records, therapy notes, telehealth, prescribing, insurance, or therapy-specific compliance workflows.

Use SimplePractice total cost for EU therapists before modelling a switch, then use Tregovia pricing only after the data-role split is clear.

Client Portal Access After Cancellation Is Easy To Overlook

A therapy client who has used a client portal to message the practice, view session history, or complete forms has built a specific expectation of continued access to that history, and a practice switching systems should have a clear answer about what happens to that access before, not after, the switch happens. If portal access simply disappears on cancellation without warning, clients lose access to records they may reasonably believe belong to them, including past intake responses or their own message history with the practice.

This is a different concern from data retention on the practice's side. Retention obligations govern what the practice must keep; portal access governs what the client can see. A practice should decide and communicate, before cutover, whether clients will be notified of a portal change, given an export of their own message history, or told explicitly how to request access to past records, rather than letting portal access lapse silently as a side effect of subscription cancellation.

A Safer Import Rule

Use a default rule:

Import operational records only.

Operational records are client contact details, future appointments, invoice status, high-level service category, reminder preference, and form status. Clinical notes, diagnosis context, therapy summaries, portal messages, and telehealth context stay out unless the receiving system is verified for that purpose and the practice has documented the decision.

This rule also helps staff permissions. A receptionist may need appointment and billing status. They do not automatically need clinical notes.

Red Flags

Slow down when:

  • Export options are unclear
  • Terms around data use are hard to understand
  • AI add-ons are enabled but not reviewed
  • The practice cannot explain client portal access after cancellation
  • Staff roles are too broad
  • Sensitive form answers would be visible to non-clinical staff
  • The CRM is being chosen only because it is cheaper

Cost savings do not compensate for a poor clinical-record decision.

Therapy Data Questions

What SimplePractice documents should EU therapists review?

Review current pricing, Terms of Service, Privacy Policy, Client Portal Privacy Policy, Business Associate Agreement where relevant, AI add-on terms if used, export documentation, and payment-provider terms.

What SimplePractice facts were checked?

As checked on July 19, 2026, SimplePractice listed Starter, Essential, and Plus pricing, had Terms of Service last updated August 2, 2023, and support material referenced BAA, privacy, trust, security, and AI add-on terms.

Can Tregovia guarantee GDPR compliance?

No. Buyers should verify current hosting, vendor terms, connected services, transfers, retention, deletion, exports, SMS, payment, and access controls directly.

Which therapy data needs special care?

Clinical notes, diagnosis context, intake forms, consent forms, client portal records, payment data, telehealth records, insurance details, and sensitive messages need careful review.

What is the practical takeaway?

Separate clinical records from CRM records, minimize imports, verify legal documents, and avoid moving therapy-specific data into a CRM unless the receiving workflow is verified.

Data Rule

EU client-data review should happen before feature comparison. If the practice cannot clearly explain which records are clinical, which are operational, and what happens after cancellation, it is not ready to switch systems.

14-day free trial

Review client-data roles before switching

Check privacy documents, exports, clinical records, client portal access, payments, add-ons, retention, and staff permissions before importing records.