Report a security issue
Found a weakness in VenueOS? Tell us privately. The same screens that show a lunch menu can show a lockdown alert, so a person on our team picks up every report quickly — and good-faith research that follows this page is welcome, never punished.
Send your report privately
Please never post details in a public GitHub issue, pull request or discussion, or on social media. That tells attackers before a fix ships.
Last updated October 24, 2026
What we commit to
- to acknowledge your report
- 2 business days
- to assess it and rate its severity
- 10 business days
- fix target for critical and high severity
- 30 days
- fix target for medium and low severity
- 90 days
What to send
Send what you have. A rough report is better than none, and we will ask if we need more.
- What you foundThe issue, and the impact you believe it has.
- How to reproduce itSteps, a proof of concept, a request and its response, or a short video.
- Where it isThe affected address, endpoint or app version.
- What you touchedWhether you accessed, changed or kept any data that is not yours.
What happens next
- 1We confirm we have itWithin 2 business days, a person on our team replies to your report.
- 2We assess itWithin 10 business days, we confirm the issue, rate its severity and tell you what we found.
- 3We fix itOur target is 30 days from triage for critical and high severity, and 90 days for medium and low.
- 4We keep you postedIf we are going to miss one of these dates, we tell you rather than go quiet.
- 5We disclose it togetherWe agree the timing of any public disclosure with you, normally after the fix ships, and we credit you unless you ask us not to.
We do not run a paid bug bounty.
Safe harbor
If you make a good-faith effort to follow this page, we will:
- consider your research authorized, including under the U.S. Computer Fraud and Abuse Act and similar laws;
- waive any Terms of Service restriction that would otherwise prohibit it, for that limited purpose;
- not pursue or support legal action against you; and
- make it clear that your research was authorized if a third party takes action against you.
This does not cover accessing real customer data, triggering a real emergency alert, or breaking the rules below. Not sure whether something is in scope? Ask first at security@venue-os.app.
Scope
In scope
- The dashboard and web player at venue-os.app
- The VenueOS API
- The VenueOS Android player and manager apps
- The source code and build pipeline in our public GitHub repository
What matters most to us
- Taking over a screen — showing content its owner did not choose.
- Suppressing or forging an emergency alert. This is the most serious class of issue for VenueOS.
- Reading or changing another organization's data.
- Reaching an admin capability from a lower role, or from no account at all.
- Reaching student or staff information.
Out of scope
- Missing security headers with no demonstrated exploit.
- Rate limiting on endpoints that are neither sign-in nor destructive.
- Clickjacking on pages with no state-changing action.
- Self-XSS, or attacks that need an already-compromised device or browser.
- Social engineering of our staff or customers.
- Denial of service through traffic volume.
- Automated scanner output without a verified, reproducible impact.
- Issues in third-party services we use — report them to that provider, and tell us too if our customers are affected.
- Findings that need physical access to a device that is already unlocked, unless they get past the kiosk lockdown itself.
Rules of engagement
- 1Use your own trial account and your own data — never a live school or business.
- 2Do not access, change, delete or keep data that is not yours. If you reach someone else's data by accident, stop and tell us what you saw.
- 3Never trigger an emergency alert on a real deployment. Tell us how, and we will reproduce it ourselves in an isolated account.
- 4No denial of service, stress testing or spam.
- 5No physical intrusion and no social engineering.
- 6Stop at proof: demonstrate the issue, then stop — do not pivot, escalate further or stay in.
Security reviews and questionnaires
For a procurement or district security review, email security@venue-os.app. Our security overview for IT teams and network requirements answer most first questions, and the Data Processing Addendum lists every sub-processor.
This page is also published in machine-readable form at /.well-known/security.txt.