A blank laptop and privacy-review papers with a navy lock card on a cream and terracotta desk
CaliforniaprivacyCCPA

California Privacy Policy Requirements for a Therapy Practice Website

Photo of Dr. Sofia Reyes
Dr. Sofia Reyes Clinical Documentation & Compliance Editor 11 min read
Outline
Form or widgetData collectedRecipientNotice link
Contact formName, email, message, preferred contact timeHarbor Street mailbox and form hostFooter privacy policy
Booking widgetName, email, appointment request, time zonePractice and booking vendorBooking page and footer
Site analyticsIP-derived data, page path, device eventsAnalytics vendorPrivacy policy tracking section
Clinician notes toolFictional test text only during evaluationHarbor Street reviewer and proposed toolTool acceptance record, not a public policy substitute

The same four rows need a change, tracking, and escalation check before you accept the result.

Form or widgetChange notificationActual tracking behaviorCounsel question
Contact formEmail owner and update effective dateNo advertising pixel; host logs submission metadataDoes the message field invite clinical details that should be excluded?
Booking widgetUpdate policy and booking disclosure togetherVendor sets functional cookies; no unapproved advertising useWhat vendor terms and access limits apply to appointment information?
Site analyticsRecheck after script or vendor changeAnalytics loads only after the configured choiceWhat does the current configuration actually do in California?
Clinician notes toolReopen review when terms or subprocessors changeNo client data entered during testWhat data flow, contract, support access, and deletion terms need counsel review?

Worksheet facts and tool behaviors checked November 2026. Test your own configuration before relying on this example.

The full State Records-Release and Privacy Checklist adds reusable data-flow, recipient, notice-change, tracking, and counsel-question sheets so you can review one website or vendor this week.

Map your privacy data flows

Use the worksheet pack to record one form, widget, or vendor decision this week.

  • California CMIA Release-Validation Overlay with format, signer, scope, expiration, copy, and return-for-correction checks
  • North Carolina Applicability and Release Overlay with Chapter 122C branch, issuer, signer, records, recipient, and revocation fields
  • New York OCA 960 Receive, Review, Respond sheet with Item 9(a) scope and Item 9(b) discussion-authority checks
  • New York Data-Flow Decision Record and California Website Data-Flow and Policy Acceptance sheet for vendors, tracking, notices, and counsel questions

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

The preview is a starting record, not a completed California privacy policy. Compare the policy with the website you actually operate, then replace every fictional name, tool, recipient, and behavior with what your practice actually uses. If you cannot explain a row, pause publication or acceptance and route the question to your privacy lead or counsel.

Before publishing or changing the policy, have qualified counsel review its applicability, disclosures, tracking practices, and rights workflow against your live California website. A privacy policy does not make your practice compliant, create consent to record a therapy session, or authorize a disclosure of therapy records. Facts and guidance on this page were checked in November 2026.

Start with the California website rule

Inventory the website’s real collection points before you adapt any policy language. Start with the inquiry form, booking widget, analytics script, advertising tag, chat tool, downloadable-resource form, and embedded scheduling service rather than a generic template.

California Business and Professions Code section 22575, commonly called the California Online Privacy Protection Act or CalOPPA, addresses a commercial website or online service that collects personally identifiable information through the internet about individual California consumers. The statute says the operator must conspicuously post a privacy policy. It also says the operator is in violation of the posting subdivision only if the operator fails to post within 30 days after notice of noncompliance. That enforcement language is not permission to operate without a policy. Treat the posting requirement as a launch and change-control task.

For your practice, ask what the site actually collects. An inquiry form, newsletter form, booking widget, chat tool, downloadable-resource form, analytics script, advertising tag, and embedded scheduling service can create different flows. A page that does not collect clinical records can still collect personal information. A privacy policy should describe the live practice, not the tool vendor’s generic promise.

Use how Emosapien works as an example of a product explanation, not as a substitute for your own website inventory. Your public policy needs your practice name, contact route, tools, purposes, recipients, choices, and change process.

Put the required disclosures beside the actual flow

Section 22575 identifies several subjects your policy must address. Use the table as a review map for the California privacy policy requirements that apply to your site, then have counsel confirm how the statute applies to your facts.

California policy subjectWhat you should record before publishingPractice-specific check
Information categoriesCategories collected through the site, such as name, email, message, appointment request, device data, or online activity informationDoes the form invite therapy details? Do the policy categories match the fields and scripts?
Third-party categoriesCategories of third parties with whom the site may share collected informationName the actual recipient category and verify the vendor’s current role and terms
Access or correctionWhether you maintain a process to review and request changes to information collected through the siteProvide a monitored contact or state that no such process is maintained, subject to counsel review
Material changesHow you notify visitors or consumers of material policy changesRecord the owner, effective-date update, archive method, and notice location
Effective dateThe date the policy takes effectKeep a dated copy and a change log
Do Not Track or similar signalsHow you respond if you engage in collecting online activity over time and across third-party sitesTest the live configuration instead of copying a vendor statement
Other-party online activity collectionWhether other parties may collect information about online activity across websites while a visitor uses your siteReview analytics, pixels, embedded media, chat, and booking scripts

Statutory subjects summarized from California Business and Professions Code section 22575, checked November 2026. Confirm the current text and application with counsel.

The California Attorney General’s Making your Privacy Practices Public recommendations also emphasize plain language, readability, data collection, tracking, use and sharing, individual choice, security safeguards, effective dates, and accountability. The recommendations are not a replacement for the statute or legal advice. They are a useful prompt to compare what your policy says with what your site does.

A policy link in the footer is useful only if the link works, remains conspicuous, and reaches the current version. Test it from a private browser window and from the form, booking, and resource pages where a visitor may first provide information.

Separate CalOPPA from CCPA applicability

California privacy policy requirements and CCPA rights can overlap in a public policy, but they are not one legal test. Keep the two analyses distinct in your evidence file.

The California Consumer Privacy Act, as amended by the California Privacy Rights Act, is a separate analysis. The California Privacy Protection Agency’s CCPA FAQ describes for-profit businesses that do business in California, determine why and how personal information is processed, and meet a threshold such as adjusted annual gross revenue of at least $26.625 million for the preceding calendar year, buying, selling, or sharing personal information of at least 100,000 California residents or households, or deriving at least 50 percent of annual revenue from selling or sharing California residents’ personal information. The FAQ also identifies separate obligations for some service providers, contractors, and other recipients.

Do not infer from a small practice’s size that the CCPA never applies. Do not infer from a California visitor that every CCPA right or threshold applies to your practice. Revenue, ownership, data activity, purpose, exemptions, service-provider relationships, and current law matter. Ask counsel to document the conclusion and the facts supporting it. If the conclusion changes, update the public policy and your internal decision record together.

If you are subject to CCPA obligations, your consumer-rights workflow must match what you publish. The CPPA FAQ describes rights including to know, delete, correct, opt out of sale or sharing, limit certain sensitive personal-information uses, and receive equal treatment, subject to the law and exceptions. Do not promise a right, response process, or opt-out mechanism that your practice cannot operate. Do not copy a generic notice and assume its thresholds, categories, or exemptions describe your website.

Keep the website policy separate from clinical privacy documents

A website privacy policy covers online collection and use. Under 45 CFR 164.520, a HIPAA Notice of Privacy Practices covers protected health information and the rights and legal duties that apply when HIPAA requires a notice. A release or authorization document addresses a specific use or disclosure under 45 CFR 164.508. A consent-to-record form addresses recording when the applicable law and facts require consent. These documents can refer to one another, but one does not replace the others.

For the broader federal workflow, start with the HIPAA compliance checklist and the HIPAA compliance hub. When you need a specific release workflow, use a current authorization reviewed against your services and state law. A footer notice cannot authorize you to disclose therapy records because an authorization has its own requirements under 45 CFR 164.508, and a client’s use of a contact form is not consent to record a session. California Penal Code section 632 addresses recording a confidential communication without the consent of all parties in its current official text.

Your vendor review should follow the same separation. A booking vendor may receive appointment information without receiving therapy notes. An analytics vendor may see page and device events without being appropriate for a clinical message. A note tool may require a separate contract, access review, and security analysis when it creates, receives, maintains, or transmits protected health information for a covered entity. HHS business associate contract guidance explains that the contract requirement and permitted uses depend on the vendor’s business associate role and the services and data flow. Ask what data enters the tool, who can access it, why it is processed, how long it remains, how it is deleted, and what happens when the vendor changes its terms or subprocessors.

Check the live configuration before you accept a vendor

Read the public policy and vendor terms, then test the website. Use browser tools or a documented test to record whether the analytics script loads before a choice, which cookies appear, what the booking widget sends, whether a contact message is stored by a third party, and whether embedded content makes additional requests. Record the date and the test environment.

Do not describe a tool as compliant because its sales page uses that word. Do not promise that a tool never shares data when your configuration has not been tested. If the tool’s behavior is unclear, record the exact question and stop the acceptance decision until someone with authority resolves it.

When documentation is part of the decision, you can see how notes are drafted and reviewed. That product workflow does not answer your California website analysis. Keep client data out of a buying test unless your privacy and legal review supports its use. Use fictional names and fictional clinical details, and keep the clinician responsible for review and signature.

Keep the evidence with the policy

Save the dated policy, prior versions, change approvals, vendor terms, data-flow map, script inventory, test results, and unresolved counsel questions in one controlled location. Assign an owner and review date for each item. Reopen the review when you add a form, booking widget, chat service, analytics provider, advertising tag, resource gate, or documentation tool.

Keep the California privacy policy requirements record with the evidence so another reviewer can trace each disclosure to the live website configuration.

A practical evidence folder can contain:

  • A page and form inventory with each collection point
  • A recipient and vendor list with the data each recipient receives
  • A current privacy policy and dated prior versions
  • A tracking and cookie test with the date, browser, and configuration tested
  • A material-change process with the person who approves updates
  • A CCPA applicability memo or counsel question log, if relevant
  • A separate HIPAA Notice of Privacy Practices review, if relevant
  • A fictional-data vendor test showing entry, review, export, access removal, and deletion behavior

Choosing tools that respect these rules

Your California privacy policy requirements review should end with a dated owner, a tested configuration, and a question log for anything counsel must resolve. Recheck those requirements whenever a collection point or vendor changes. Choose tools by their actual data flow and your ability to explain, review, and change that flow. Emosapien can draft therapy notes from a session for clinician review and signature, but it is not an EHR, practice-management system, scheduling or billing product, or legal-compliance service. A clinician sets the session language, and the clinician remains responsible for the final note and the privacy analysis.

If you evaluate a session-note workflow, start with fictional material. Review the draft, verify that the clinician can edit and sign it, and keep the tool decision separate from your California website policy. Legal review is required for applicability and for any question about recording, disclosure, contract terms, or consumer rights.

Use the California privacy policy requirements worksheet again after counsel resolves an open question or you change a vendor.

See clinician-reviewed session notes

Try a fictional session, review the AI-drafted note, and keep the final clinical decision with the clinician.

See notes
  • Free plan
  • No credit card
Fictional session
Fictional clinician · Maya R.

Test record

A fictional client describes a difficult week and asks for a coping plan.

Clinician review

Draft ready for review and signature.

Review the session note… →

References

Free PDF: State Records-Release and Privacy Checklist

A seven-page worksheet pack for validating California, North Carolina, and New York records releases, plus New York and California website and vendor data flows.

  • California CMIA Release-Validation Overlay with format, signer, scope, expiration, copy, and return-for-correction checks
  • North Carolina Applicability and Release Overlay with Chapter 122C branch, issuer, signer, records, recipient, and revocation fields
  • New York OCA 960 Receive, Review, Respond sheet with Item 9(a) scope and Item 9(b) discussion-authority checks
  • New York Data-Flow Decision Record and California Website Data-Flow and Policy Acceptance sheet for vendors, tracking, notices, and counsel questions

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

Ready to transform your practice?

Join 10,000+ therapists using Emosapien.