Security

Responsible disclosure.

Found a security issue in an OpenLoop system? Tell us. We will work with you to understand and resolve it.

At OpenLoop Health we build the technology clinicians use to deliver virtual care. Those systems support real patient encounters and hold sensitive health information, so we treat their security as part of the care itself. No software is perfect, and we would rather hear about a weakness from a researcher who found it than from a patient who was harmed by it.

If you believe you have found a security vulnerability in an OpenLoop system, tell us using the form below. We will work with you to understand and resolve it.

Our commitment to you

If you make a good-faith effort to follow this policy and stay within the scope listed in the form below, we will not initiate legal action against you for your research and we will not report it to law enforcement. An honest mistake you disclose promptly is still good faith.

We cannot authorize testing of systems we do not control, including applications we operate for our customers under their own brands. If an asset is not listed in the form below, assume it is not covered.

What we ask of you

  • Test only against accounts you own or that we provisioned for you. Never interact with accounts belonging to patients, clinicians, partners, or our workforce.
  • Do not access patient data. If you encounter protected health information, stop immediately, do not save or share it, report it to us as urgent, and securely delete anything you hold.
  • Never include patient data in a report. Describe what was exposed, not the data itself.
  • Do not disrupt care. Avoid anything that affects availability or triggers real clinical or administrative activity, including scheduling with a clinician, starting a visit, or submitting an order.
  • Stop once you have proof. Do not escalate further, move laterally, or download, copy, or retain data.
  • Do not modify or delete data or configuration.
  • No denial of service, no social engineering of our people or our patients, and no physical attempts against our facilities.
  • Keep automated scanning at a volume that does not degrade service for others.
  • Do not disclose a vulnerability publicly or to a third party without our written consent. We are glad to discuss coordinated publication once a fix is in place. Patient, customer, and partner identifiers may never appear in a disclosure.
  • Follow applicable law, and ask us first if you are unsure whether something is permitted.

Our commitment above does not extend to activity that intentionally accesses or retains personal data, deliberately disrupts our systems, or is undertaken for extortion or any purpose other than good-faith security research. We can only speak for ourselves, and this policy does not bind our partners, customers, or service providers.

Scope, recognition, and other terms

The form below lists the systems currently in scope along with our response commitments. It is the only way to reach us about a vulnerability, and reports are received and processed through HackerOne, the disclosure platform we use.

This is a vulnerability disclosure program, not a bug bounty, and we do not offer payment for reports submitted here. With your permission, we are glad to acknowledge researchers publicly.

Some reports may also be a fit for our private bug bounty program. Where that is the case, we may invite you to join it, and reports you submit there are eligible for payment under that program’s own scope and terms.

Submitting a report does not create an employment, agency, or business associate relationship with OpenLoop, and it grants us permission to use your report to investigate and fix the issue and to share it with the vendors and partners who help us do so. We may update this policy.

Thank you for helping us keep patients safe.

Submit a report

Scope and response commitments are shown inside the form.