Security at JasperTrack

Effective 2026-09-13Last updated 2026-10-19

In plain language

Security and privacy are core design requirements for JasperTrack. We build on Microsoft Azure's cloud infrastructure and add application-level safeguards for clinical teams, while keeping this public overview focused on the protections that matter rather than publishing an exhaustive map of our architecture.

Our approach

Clinical software carries a particular responsibility. JasperTrack is designed to protect sensitive information throughout its lifecycle, from the way the platform is built to the way access and security events are handled.

Our approach follows widely accepted security and privacy practices: limit access, separate each clinic's data, make important activity traceable, review changes before release, and prepare for security incidents.

Built on Microsoft Azure

JasperTrack is hosted on Microsoft Azure in Canada. Azure provides the foundation for physical data center security and the underlying cloud platform; JasperTrack remains responsible for protecting the application, identities, access and customer data.

This shared-responsibility approach lets us build on Azure's mature, defense-in-depth cloud capabilities while keeping application security firmly our responsibility. Microsoft explains that model in its Azure shared-responsibility guidance.

Access and clinic separation

Access is based on a person's role and the work they need to perform. Clinic data boundaries are part of JasperTrack's application architecture, so one clinic's records remain separate from another's.

Clinic administrators are responsible for assigning the right access to each team member and removing access promptly when responsibilities change.

Accountability

JasperTrack is designed to make security-relevant activity traceable. This supports review of access and important changes while keeping clinical content out of operational logs.

Secure development

Security and privacy are considered throughout design, development and release. Code changes are reviewed and tested before deployment, dependencies are maintained, and production access is limited to authorized operational needs.

We deliberately do not publish every implementation detail. Clinics evaluating JasperTrack can contact us with security questions relevant to their own review.

Incident readiness

Our security approach includes preparation for identifying, containing, investigating and communicating security incidents. Contractual notification commitments are set out in the Business Associate Agreement, the Data Processing Addendum and the Privacy Policy.

Security is shared

JasperTrack protects the platform; each clinic protects how its team uses it. Clinics should assign access carefully, use strong and unique credentials, promptly offboard former team members, and secure the devices used to access JasperTrack.

← Back to Trust Center