This policy explains how CMJ Consulting LLC d/b/a BoardOps (“BoardOps,” “we,” “us”) collects and uses information on boardops.org, on our product websites (such as parleynegotiation.com), and in the BoardOps family of applications (Parley, Sunshine, SuptEval, Quorum, Compass, AgendaIQ, and BoardEval). If your school district has signed a Master Subscription Agreement and Data Privacy Agreement with us, those signed agreements control how we handle your district’s data; this policy supplements them and governs our public websites, hub accounts, and customer-relationship records.
Information we collect
- Website analytics. On our public marketing pages — not in signed-in areas such as the hub dashboard — we use Google Analytics 4 and Microsoft Clarity to understand how visitors use the site: pages viewed, links clicked, device and browser type, approximate location, and, for Clarity, interaction heatmaps and session replays with sensitive form fields masked. This data is pseudonymous and we do not attempt to identify individual visitors from it, though a session replay can show how a particular visit unfolded.
- Account information. When you create a BoardOps hub account, or an account in one of our applications, we collect your name, email address, role, and district affiliation. If you sign in with Google or Microsoft, that provider shares your name and email address with us; we never receive your password for those services. If you sign in by email link, the link is sent through our authentication provider, Google Firebase.
- Accounts created for you. When a district official is added to our records, we may create a BoardOps account for them and, where their district uses one of our applications, an account in that application, so they can sign in by email link. You can ask us to delete an account you did not request.
- Customer-relationship records. When someone at a district signs up for one of our applications, requests access, or is provisioned into one, that product sends us the signup contact details (name, email, district) so we can administer the district’s account and follow up. We use this for account management and sales. We do not sell this information or use it for third-party advertising.
- Information from public sources. To maintain our records of school districts and their leaders, we collect publicly available information about districts and their elected and appointed officials — such as names, titles, and work contact details published on district websites, in meeting materials, and in state education directories. We may use automated tools, including AI-assisted web search, to check whether that information is current; a person reviews any change before it is recorded. We use this information to contact districts about our services.
- Single sign-on. When you launch an application from your BoardOps dashboard, we pass your identity to that application to sign you in.
- Product usage. Our applications send us daily usage statistics — such as how many people used a feature and in which districts — so we can understand adoption and support our customers.
- Contact forms and email. Messages you send us, including through contact forms, are delivered and stored through our email providers.
Information organizations give us about others
Some of our applications hold information about people who never use them, because a school district or employee organization uses the application to do its work. In each case that organization controls the information, decides who may see it and whether any of it is public, and is the place to send requests about it. We process it only to provide the service.
- People who write to a district (Sunshine). Messages sent to a district’s board are stored, organized, and summarized for board members, including with AI-assisted tools. District correspondence may be government data, and parts of it may be public.
- Board-vacancy applicants (Quorum). Applications are collected on the district’s behalf. Under Minnesota law some application details are public and appear on the district’s vacancy page; contact details and other fields are private unless the law makes them public.
- Bargaining-unit members (Parley). Survey responses are collected on behalf of the bargaining unit and belong to it, not to the employer.
- Staff who are evaluated (SuptEval). Evaluation records, including a superintendent’s reviews of cabinet staff, are personnel data held for the district and are generally private under the Minnesota Government Data Practices Act or Iowa Code ch. 22.
- Board members who respond to a self-evaluation (BoardEval). Results are reported only in aggregate, after a minimum number of members respond, and no one — including the district and BoardOps staff — is given an individual member’s responses through BoardEval.
How we use information
To provide and improve the services, administer accounts and subscriptions, respond to inquiries, contact districts about our services, and understand website usage. We do not sell personal information, and we do not use customer content to train AI models (see below).
Email from us
If you subscribe to the BoardOps newsletter, we use your email address to send you new articles. Subscribing requires confirming your address, newsletters are sent through Postmark, and every message includes a one-click unsubscribe link. We may also email district officials individually about our services; you can opt out of those messages at any time by replying or by emailing contact@boardops.org. Account and security messages are sent regardless of these choices.
AI features
Several of our applications include AI-assisted features (branded “Sage” in some products) that process content you submit to generate drafts, summaries, and suggestions. These features run on third-party model providers — currently Anthropic and Google (Gemini), with Voyage AI for document search in AgendaIQ — under paid commercial terms that prohibit using your data to train their models. We also use these providers internally, for example to help keep our district-leadership records current. AI output is assistive only and should be reviewed by a person before it is relied on. Read more in How Sage works.
Service providers
We rely on third-party providers to operate the services, including Google LLC (hosting, database, authentication, and business email), Anthropic, Google, and Voyage AI (AI model providers), Postmark and Resend (email delivery), Stripe, Inc. (billing), and Google and Microsoft (website analytics). District Data is stored and processed in the United States; website-analytics providers may process visitor data in other countries. The current list of subprocessors for district customer data is maintained at boardops.org/legal/subprocessors.
Cookies
When you sign in, we set a session cookie that keeps you signed in for up to seven days. It is shared across boardops.org and its subdomains so you can move between our applications, and it is not used for analytics or advertising. On our public pages, Google Analytics and Microsoft Clarity set analytics cookies as described above. We remember that you dismissed our privacy notice in your browser’s local storage.
Your choices
You can block analytics cookies through your browser settings or a browser extension, and Google offers an opt-out at tools.google.com/dlpage/gaoptout. Blocking analytics does not affect your ability to use the site.
Your requests
You may ask us to tell you what personal information we hold about you, to correct or delete it, or to stop using it to contact you about our services, by emailing contact@boardops.org. We respond within 45 days. We may need to confirm your identity first, and we may keep information we are required to retain by law.
Data a school district or employee organization holds in our applications belongs to and is controlled by that organization, and may be government data under the Minnesota Government Data Practices Act or another state’s public-records law. To inspect, correct, or request a copy of it, contact that organization directly. If you send that kind of request to us, we will refer it there.
Students and children
Our services are built for school-district governance and administration, not for use by students, and we do not knowingly collect information from children. Districts control the data they submit; our handling of district data, including any student information a district submits, is governed by our Data Privacy Agreement.
Retention and security
We use administrative, technical, and physical safeguards designed to protect the information we hold, and we limit access to authorized personnel; see our Security overview. Account and customer-relationship records are kept for as long as needed to provide the services and administer accounts, then deleted or de-identified. For school districts, retention, export, deletion, and security-incident notification for District Data are governed by our Data Privacy Agreement; if we become aware of a confirmed security incident affecting a district’s data, we notify the district as required by that agreement.
Changes to this policy
We will post any change to this policy on this page and update the “Last updated” date above. If we make a material change to how we use personal information, we will notify account holders by email before it takes effect.
Contact
CMJ Consulting LLC d/b/a BoardOps · boardops.org. Questions or requests about your information? Email contact@boardops.org.