Trust
Security and hosting.
Where this site runs, how staff sign in, and how the public record is protected.
Where it runs
The website runs on Vercel. Records, accounts and uploaded files are stored in a Supabase (PostgreSQL) project. Live video uses LiveKit, and email, when switched on, is sent through Resend. Every connection to the site uses HTTPS.
The public side needs no account
Agendas, minutes, search, feeds and the records request form work without signing in. The public pages do not set cookies and carry no advertising or analytics scripts. The page text, fonts and styles are served from this site; stock photographs on some pages are loaded from a public image host until the district supplies its own.
How staff sign in
Staff sign in with an email and password. Publishers and district administrators must also use an authenticator app, and consequential actions (publishing, canceling a meeting, changing settings) check that second step again on the server, not only in the page.
Who can see what
Each person has a role: viewer, contributor, author, publisher or district administrator. The rules are enforced inside the database (row level security), so a district sees only its own data even if a page had a mistake. People who only submit agenda items can see only their own submissions. Subscriber addresses and records request contact details are visible only to the few roles that need them.
The record cannot be quietly changed
A published agenda is stored as an immutable snapshot with a receipt. A correction is a new version, and earlier versions stay on the record. The audit history of who changed what, and the history of each records request, can be added to but never edited or deleted.
Your data in the emails and forms
Email addresses are used only for the alerts a person chose. Every message has a one-click unsubscribe, and links in emails never change anything until a button is pressed. Records request forms show the requester only a reference number and a private access code.
The live meeting room
The video room is private to staff and invited guests. Calls are not recorded and chat is not kept.
How it is tested
Changes are checked by automated tests that include, for every database change, a second district and each role trying things it must not be allowed to do. Accessibility checks run against the public pages.
What is not claimed
- No security certification (for example SOC 2) is claimed for this product. The hosting providers publish their own.
- The physical location of the data and the backup schedule depend on the hosting plan the district chooses. Ask us for the current details before relying on them.
- An independent penetration test has not been carried out.
- This page describes the product. It is not legal advice, and it does not replace the district’s own records-retention and counsel review.
Questions about security or hosting: contact the district or write to [email protected].