Healthcare software lives or dies on trust. We built Indigo Health so that trust isn't a marketing claim — it's the architecture.
This page is the short version. The full policy library is available to prospects and customers under NDA, our Business Associate Agreement is available on request, and our team is happy to walk your security and compliance reviewers through any of it.
Indigo Health doesn't practice medicine, doesn't supervise clinicians, and doesn't decide what counts as a medical record. Our customers — the covered entities who treat patients — make those decisions, and we process protected health information only as their Business Associate Agreement directs.
A single, focused legal role means fewer surprises in your vendor risk review and a cleaner story for your regulators.
The single most important thing about how Indigo Health is built: identifiable patient data never lands on laptops, analytics warehouses, or test environments. We call this our minimum-access PHI architecture, and it's not a policy we ask people to follow — it's how the platform is built.
When a vendor is breached, every covered entity asks the same question: how much of our patient data did that vendor have sitting around? For Indigo Health, the honest answer is that it stayed within production controls, and it was never on anyone's laptop.
The platform runs on Microsoft Azure, on HIPAA-eligible services covered by Microsoft's Business Associate Agreement — inheriting enterprise-grade physical security and the global compliance certifications of one of the most heavily audited cloud platforms in the world. Data is encrypted in transit and at rest. For email that may carry protected health information, we use Paubox under a Business Associate Agreement.
We don't ask you to take our infrastructure on faith. We build on a foundation your own auditors have almost certainly assessed before.
Compliance shouldn't be a vibe. Ours is a documented library of policies and procedures, organized to the HIPAA Security Rule, so your reviewers can map our controls to the regulation directly.
Documented subprocessor management, with every third party that handles protected health information bound by a HIPAA-compliant agreement
This isn't a slide deck. It's a maintained, version-controlled library that our own team operates against every day.
We know what a vendor risk questionnaire looks like. We've designed our compliance posture so the answers are ready before you ask.
Every control above produces a trail. Activity is captured in tamper-resistant, append-only logs, and governed evidence is retained in a write-once evidence repository built to satisfy a regulator, not just to check a box. When a reviewer asks to see something, the answer is documented evidence with a date on it, which we share during a security assessment or where the law requires it.
We notify affected customers of confirmed security incidents involving their protected health information, in accordance with the executed Business Associate Agreement and HIPAA's Breach Notification Rule. Incident triage, containment, and notification are governed by our Security Incident Response and Breach Notification Policy and its supporting procedures — so the response on the worst day isn't improvised.
Last reviewed: 2026-08-19
Security and compliance reviewers — we'd rather meet you early than late. Reach us at security@indigo.health, or for general inquiries, hello@indigo.health.