Hosting and encryption
The BoardOps hub and its applications run on Google Cloud (Firebase) in the United States. Data is encrypted in transit with HTTPS and encrypted at rest by our cloud host. Google Cloud maintains industry certifications such as SOC 2 and ISO 27001; those are our host's certifications, not a certification of BoardOps itself.
Separation
Each application runs in its own cloud project with its own database, and each district's data is logically separated within an application. Applications exchange only what an integration needs, over authenticated connections.
Sign-in
There are no BoardOps passwords to steal or reuse. People sign in with Google, with Microsoft, or with a one-time link sent to their email address. Signed-in sessions use a secure, HTTP-only cookie that expires after seven days.
Access control
Privileged changes happen only in server code, and our database rules block direct access to everything else. Administrative access is limited to named BoardOps staff, and every privileged change is written to an append-only audit log.
Vendors
We use a short list of established providers, each bound to data-protection terms. The current list is on our subprocessors page, and districts with a signed Data Privacy Agreement get 30 days' notice before we add one that handles District Data.
Incidents
If we confirm a security incident affecting a district's data, we notify the district without undue delay and in any event within 72 hours, and we cooperate with its own notification obligations.
Reporting a vulnerability
If you believe you have found a security problem in any BoardOps site or application, email contact@boardops.org with “Security report” in the subject and enough detail for us to reproduce it. Please don’t access or change data that isn’t yours, disrupt the services, or share the issue publicly before we have had a reasonable chance to fix it. We will acknowledge your report and keep you updated, and we won’t pursue anyone who reports in good faith and follows these guidelines.
For districts
We’re glad to complete your district’s security or vendor questionnaire. Our contractual commitments are in the Data Privacy Agreement; see also our subprocessors and Privacy Policy.