Azure-first footprint
Production-style deployments target Azure resources such as App Service for API and web workloads and Azure SQL for relational data—aligned with the solution’s engineering direction and regional deployment examples.
Trust
Hosting and safety practices that respect clinical data
MyChiro is built to run on Microsoft Azure—giving your team a modern foundation for API, database, and web hosting while keeping patient-facing flows tightly scoped. This page summarizes the posture at a high level; your implementation team can share environment-specific detail under NDA.
Transactional email
Patient-facing notices and document delivery can use Azure Communication Services Email in hosted environments, with safe logging-only behaviors in development so engineers never spam real inboxes by accident.
Bounded public surfaces
Minimal public pages—such as intake and appointment acceptance—are designed to expose only what is necessary for that moment in the journey, while staff tools remain authenticated.
What we encourage you to validate
Every clinic has unique policies, medical aid relationships, and IT standards. We are transparent about phased features so your governance conversations stay grounded.
- Data residency and backup expectations for your region and funders.
- How booking notices, intake invitations, and PDF statements are audited.
- Incident response contact paths and escalation for your deployment.
Plain-language limitations
This marketing site is static and does not collect patient information. The live product’s controls and certifications depend on how your organization configures Azure subscriptions, networking, and access policies.
Nothing here replaces professional legal, clinical governance, or security review for your practice.
Need a security questionnaire or architecture diagram?
Send your standard vendor pack—we will route it to the people implementing your environment.
Request security material