Plain English, current practice.
This page describes what actually happens today — on this website and in the product. No legal boilerplate standing in for answers.
This website
The marketing site you are reading runs no advertising trackers and no third-party analytics. There is no cookie banner because there is nothing to consent to: public pages set no tracking cookies.
If you submit the demo or contact form, we receive exactly what you type — name, work email, school or district, role, and your message — delivered as an email to the founder. It is used to reply to you and for nothing else. It is not sold, shared, or added to a marketing list.
The product
Main Office Works, the application, handles school operational data — including student records — on behalf of the schools that run it. That data belongs to the school. Access inside the product is role-based and enforced on the server, sensitive actions are logged with the real actor, and demonstration environments contain only fabricated, anonymized data. Product demos never show real student information.
Written agreements govern any real deployment: what data the platform touches, who can see it, and what happens to it when an agreement ends. Districts evaluating the platform should expect to sign a data privacy agreement before any real data is involved.
Paperwork in progress
Formal privacy documentation for districts — a standard signed DPA, a written security summary, and data-retention and return commitments — is being prepared. If your district needs these documents to evaluate the platform, ask in your demo request and we will tell you exactly where each one stands. We would rather say “in progress” than claim paperwork that doesn't exist yet.
Questions
Write to us through the contact page. Privacy questions get answered by the founder, in plain English.
Last updated July 2, 2026