Report a security vulnerability

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

In plain language

If you find a security problem in JasperTrack, we want to hear about it before anyone else does. Report it responsibly within the scope below and we will not pursue legal action against your good-faith research.

Scope

In scope: www.jaspertrack.com, app.jaspertrack.com, and the JasperTrack APIs used by the application.

This policy applies only to systems operated by JasperTrack. Third-party services are outside its scope unless the issue results from how JasperTrack has configured or integrated that service.

Out of scope: social engineering, physical attacks, denial-of-service or load testing, automated testing that generates excessive traffic, brute-force attacks, and any testing involving real patient data or another customer's account. Use only accounts and data that you own or are expressly authorized to test.

Testing safely

Use an exploit only as far as necessary to confirm that a vulnerability exists. Do not access, copy, modify or delete another person's data; establish persistence; or use one affected system to reach another.

If you encounter patient information, personal information, payment data or other confidential data, stop testing, do not retain or share the data, and report the issue immediately.

How to report

Email help@jaspertrack.com with the subject line “Security vulnerability report”. Include the affected page or endpoint, the steps needed to reproduce the issue, its potential impact, and any supporting screenshots or proof-of-concept material.

Do not include patient information or other sensitive data in email. If sensitive material is necessary to investigate the issue, say so in your initial report and we will arrange an appropriate way to share it.

Safe harbour

If you make a good-faith effort to follow this policy, we will treat your research as authorized and will not initiate or recommend legal action against you in connection with it. If a third party initiates legal action concerning research conducted in accordance with this policy, we will make our authorization known where we are legally permitted to do so.

Our response commitment

We aim to acknowledge a report within 3 business days and complete our initial triage within 10 business days once we have enough information to reproduce the issue. We will tell you whether we confirmed the issue, need more information or consider it out of scope.

Remediation time depends on severity and complexity. For a confirmed issue, we will provide an expected next step and keep you informed when there is a material change or delay.

Disclosure coordination

Please keep the report confidential and give us a reasonable opportunity to investigate and address the issue before public disclosure. We will work with you on the timing and content of any disclosure so that customers are not placed at unnecessary risk.

No bounty program at this time

We do not currently run a paid bug bounty program. We say this plainly rather than leaving it ambiguous.

← Back to Trust Center