All chapters
  1. Overview
  2. 1. The reference clinic
  3. 2. How the reference clinic's site is built
  4. 3. Gaps in the reference clinic's compliance posture (lessons for you)
  5. 4. Business structure, given you are not a clinician
  6. 5. Who can deliver care where (the multi-province problem)
  7. 6. Privacy and data law
  8. 7. Clinical safety, quality and liability
  9. 8. Money: regulatory and tax points that surprise founders
  10. 9. Technology stack
  11. 10. Go-to-market
  12. 11. Global expansion (phase 4+)
  13. 12. Phased roadmap
  14. 13. Questions for your lawyer
  15. 14. Next steps
  16. 15. Sources

Chapter 2 of 15

How the reference clinic's site is built

Front end and hosting

  • Wix website builder (generator: Wix.com Website Builder, Thunderbolt renderer), served through Cloudflare and Wix's CDN (static.parastorage.com, static.wixstatic.com). DNS is Wix DNS (ns0/ns1.wixdns.net).
  • Homepage HTML is about 650 KB, typical of Wix. Pages: home, about, team, contact, referrals, events, media, privacy, per-province pages, per-service pages, per-clinician pages, free skills, books, journal, blog feed.
  • Wix apps installed: Bookings, Forms, Members, Stores/Checkout, Events and Tickets, Blog, Chat, CMS, Pro Gallery, Video, Instagram Feed, Bandsintown and a legacy ShoutOut email tool (several look like unused defaults).
  • SEO: one LocalBusiness and one WebSite JSON-LD block (address field empty), a sitemap, a normal robots.txt. The title targets "DBT Therapy in Ontario, BC, Alberta & Nova Scotia."
  • Error tracking: Sentry, injected by Wix itself.

Back end (what actually runs the clinic)

There is essentially no custom back end. The stack is SaaS glue:

Function Tool
Scheduling, client intake, online booking, group registration, gift cards Jane App (a clinic-specific subdomain of janeapp.com)
Charting/EMR, invoicing, insurance receipts Jane App (assumed, VERIFY)
Video sessions Not stated. Jane's built-in telehealth is the likely choice (VERIFY)
Email Google Workspace (Gmail MX records)
Referral intake Fax number plus email
Public directory presence Psychology Today profile
Social Facebook, Instagram, LinkedIn
Book sales Amazon Associates affiliate tag

Security posture (external view only)

Observed from outside, no intrusion testing was done:

  • HTTPS with HSTS. Good.
  • X-Content-Type-Options: nosniff. Good.
  • No Content-Security-Policy, no X-Frame-Options, no Referrer-Policy, no Permissions-Policy. Wix does not let you set arbitrary headers, so this is a platform ceiling, not a mistake.
  • DMARC is p=none: monitoring only, spoofed mail is not rejected. For a clinic whose emails are trusted by anxious clients, this is a phishing risk. SPF is present but soft-fail (~all).
  • No cookie consent banner detected, while the privacy policy says Google Analytics is used (Quebec and PIPEDA-style consent expectations apply to analytics on a health site).
  • Health-adjacent forms (contact form, Wix Chat, Wix Members) on a general-purpose US-owned builder are a risk: it is unclear whether health details typed into them are covered by a data agreement or stored in Canada (VERIFY).
  • The clinical data itself lives in Jane, which is the correct place. The good pattern is: marketing site collects nothing clinical, and pushes everyone to the EMR's booking flow.

Verdict: acceptable for a marketing site, weak on email hardening and privacy documentation, and fine on clinical data if (and only if) clinical data really stays in Jane.