Board2Classroom
Privacy Policy
Effective Date: October 26, 2026
This Privacy Policy explains how Clear Education LLC ("Clear Education," "we," "us," or "our") collects, uses, discloses, and protects information in connection with the Board2Classroom platform, websites, and related services (collectively, the "Service"). It applies to visitors to our public websites, to district and school staff who use the Service, and to information our district customers submit to the Service.
Board2Classroom is built for system-level planning, and most of the Service works from district goals, plans, strategies, and aggregate measures. Some features, such as Meeting Companion, can capture information about students when staff discuss them in a recorded or transcribed meeting. Sections 5, 6, and 7 explain how that information is handled and protected.
1. Information We Collect
Information you or your district provide
Account information. Name, work email address, role, school or district affiliation, and login credentials. If your district signs in through Google or Microsoft, we receive the account identifier and email address from that sign-in.
Platform content. Strategic plans, improvement plans, goals, strategies, progress measures, survey questions and responses, uploaded documents and images, and other content users submit while using the Service.
Meeting Companion content. Meeting details (title, date, purpose), the names of facilitators and attendees that users enter, agendas and typed notes, audio recordings made in the Service or uploaded to it, transcripts of those recordings, AI-generated meeting notes, and the recording notice each person confirmed before recording (who confirmed it, when, and the statement shown).
Communications. Messages you send us, such as support requests, demo requests, feedback on AI features, and email correspondence.
Billing information. District billing contacts, invoicing details, and payment records. Card and bank payments are processed by our payment processor (Stripe); we do not store full card numbers or bank credentials.
Information collected automatically
Usage data. Pages viewed, features used, and actions taken in the Service, used for security, support, and product improvement.
Device and log data. IP address, browser type, operating system, timestamps, and referring URLs.
Access and support records. A record of each session in which our staff act in a district's account (who, when, and the reason given), each time one of your administrators acts as another user, and access to Meeting Companion records such as transcript downloads, exports, and legal holds. Districts can see these records.
Cookies and similar technologies. We use cookies necessary for the Service to function (such as session and security cookies) and limited functionality cookies (such as remembering your timezone). We do not use third-party advertising cookies. Some pages load web fonts from Google Fonts, which receives the visitor's IP address and browser information.
2. How We Use Information
To provide, operate, secure, and support the Service;
To authenticate users and enforce district-configured roles and permissions;
To provide AI-assisted features, such as forecasting, alignment analysis, drafting assistance, meeting transcription, and meeting notes, as described in Section 5;
To keep the access and support records described above, so districts can see who accessed their data and why;
To respond to support requests and communicate about the Service, including service and security notices;
To process billing and maintain business records;
To analyze usage in aggregate and improve the Service;
To comply with law and enforce our agreements.
We do not sell personal information, we do not use personal information for targeted advertising, and we do not build profiles of students for any purpose other than providing the Service to their district.
3. How We Share Information
We share information only as described here:
Within your district. Content in the Service is visible to other users in your district according to the roles and permissions your district configures. In Meeting Companion, a meeting is visible to its owner and to district administrators; building administrators can see the notes of meetings about their own schools. Raw transcripts are limited to the meeting's owner and district administrators.
Our personnel. Our staff access district content only as needed to provide and support the Service. When our staff use our support tools to sign in as one of a district's users, a reason is required and recorded, and every session our staff have in a district's account, including sign-ins with their own accounts, is recorded in a log the district can see. Meeting Companion notes, transcripts, and recordings are closed to our staff unless the meeting's owner or a district administrator allows support access to that specific meeting. That access lasts seven days, can be turned off at any time, is limited to our designated support account, and every view is logged for the district.
Service providers (subprocessors). We use the providers below to operate the Service. They may use information only to perform services for us and are bound by contractual confidentiality and data protection obligations. We will update this list before a new subprocessor begins processing district data, and we will give districts that have a signed data privacy agreement at least 30 days' notice (or the notice their agreement requires).
Provider |
Purpose |
Information involved |
|---|---|---|
DigitalOcean |
Hosting for the application, databases, and files |
All information stored in the Service |
OpenAI |
AI processing: meeting audio transcription and AI-generated reports and notes |
Content sent to AI features, with names and identifiers replaced as described in Section 5 |
Amazon Web Services (Amazon SES) |
Email delivery |
Recipient email addresses and email content |
Stripe |
Payment processing |
District billing contacts and payment details |
Zoho |
Company email, including [email protected] |
Messages you send us |
Email validation providers (ZeroBounce, NeverBounce, Emailable, or Abstract API, when enabled) |
Checking that email addresses can receive mail before we send service or marketing email |
Email addresses |
Our personal information detection (Microsoft Presidio) and, when enabled, our meeting transcription service run on our own servers, not with a third party. If your district uses Google or Microsoft for sign-in, those companies act as your district's identity provider under your district's own agreements with them.
Legal requirements. We may disclose information if required by law, subpoena, or court order, or to protect the rights, safety, or property of our users, the public, or Clear Education. Where legally permitted, we will notify the affected district before disclosing district data in response to legal process, so the district can respond.
Business transfers. If Clear Education is involved in a merger, acquisition, or sale of assets, information may be transferred to the successor, subject to this Privacy Policy's commitments, and districts will be notified of any such transfer as required by applicable student privacy law.
4. Data Ownership and District Control
Districts own the data they and their users submit to the Service. We process that data as a service provider and school official at the district's direction under our service agreements. Districts control their data through the Service, including:
Roles and permissions that decide who in the district can see what;
Meeting Companion settings: whether recording and uploads are allowed, whether everyone in a meeting must agree to be recorded, and how long recordings and transcripts are kept;
Legal holds that stop any deletion of Meeting Companion records while a records request, complaint, or lawsuit is pending;
A records export for responding to a parent's request to inspect a student's records, a public records request, or a legal hold;
Support access grants and the access log described in Section 3.
Districts can also export their data using features of the Service, and can request return or deletion of their data as described in our Terms of Service.
5. AI Features and Uploaded Documents
What is shared. AI features send the content needed to produce the requested output (for example, a plan being analyzed or a meeting being summarized) to the AI provider listed in Section 3.
No training. Our AI provider does not use customer content to train its models under our agreement with it. The provider may keep content for a limited time (up to 30 days) solely to detect abuse, unless zero data retention applies.
Meeting Companion. Meeting audio is transcribed by OpenAI or, when enabled, by a transcription service running on our own servers. Before a transcript, agenda notes, meeting title, and purpose are sent to the AI model that writes meeting notes, automated tools replace the names of people other than the meeting's listed attendees and facilitators, and any contact details or identification numbers, with placeholders such as "[Person 1]". The listed attendees' and facilitators' names are included so action items can be assigned. The AI model is also instructed not to include student names or sensitive details in the notes.
Uploaded documents. Before text from an uploaded document is sent to an AI provider, automated tools replace names, contact details, and identification numbers. Other details in a document (such as grades or service information) are not removed, so districts should not upload student records to AI features.
Limits of automated detection. Automated detection may not catch every name or identifier. That is one reason access to Meeting Companion content is limited and logged, and why recordings and transcripts are deleted on the district's schedule.
Human judgment. AI output is reviewed and controlled by district users; it supports, and does not replace, professional judgment.
6. Student Data
The Service is designed for adults engaged in planning, does not offer student accounts, and is not directed to children. Information about students can still appear in the Service when staff discuss students, for example in a Meeting Companion recording, transcript, or notes, or in an uploaded document. When content identifies a student, directly or through details that would let someone in the school community identify them, it may be part of that student's education records, and we treat it as "Student Data" under these commitments:
FERPA. We act as a "school official" with a legitimate educational interest under the Family Educational Rights and Privacy Act (20 U.S.C. § 1232g; 34 C.F.R. Part 99). Student Data remains under the district's direct control, is used solely to provide the Service at the district's direction, and is never re-disclosed except as the district permits or the law requires.
Special education and Section 504 records. Records of meetings about special education or Section 504 services may also be protected by the confidentiality rules of the Individuals with Disabilities Education Act. We log our personnel's access to Meeting Companion records, including the reason given, so districts can keep the record of access those rules require. Each district decides whether such meetings may be recorded.
COPPA. We do not knowingly collect personal information from children under 13 except at a school's direction and with its authorization, solely for the school's educational purposes, consistent with the Children's Online Privacy Protection Act. Meeting Companion should not be used to record meetings where students under 13 speak unless the district has authorized it. If we learn we have collected personal information from a child without appropriate authorization, we will delete it.
Health information. Student health information kept by a school is protected by FERPA rather than by HIPAA. The Service is not designed to store protected health information under HIPAA and is not offered to HIPAA covered entities or business associates for that purpose. We treat any health, disability, or similar information in Student Data as especially sensitive.
State student privacy laws. We comply with applicable state student data privacy laws. We do not sell Student Data, use it for targeted advertising, or build student profiles for non-educational purposes, and we maintain reasonable security for it.
No secondary use. Student Data is never used to train AI models or for any commercial purpose beyond providing the Service.
Deletion. Meeting Companion recordings and transcripts are deleted on the district's retention schedule (Section 10). We delete other Student Data at the district's written request within 30 days, and upon termination of service as described in our Terms of Service, except while a legal hold applies or where retention is required by law.
Parent and eligible student requests. Parents and eligible students should direct requests to review or correct education records to their district. The district can search and export Meeting Companion records to respond, and we will support the district in meeting its deadlines.
Data privacy agreements. We will enter into student data privacy agreements (including state DPA forms) with districts upon request.
7. Recording Meetings
Staff decide whether to record a meeting. Before the first recording in a meeting, Meeting Companion shows a notice based on the district's state: in states that require everyone in a conversation to agree before it is recorded (and when the district's state is not on file), the person recording must confirm that everyone agreed; elsewhere, they must confirm that they are taking part in the meeting and have told everyone it is being recorded and transcribed. Districts can require everyone's agreement in every meeting, or turn recording and uploads off. Each confirmation is saved with the meeting. The district and the person recording remain responsible for giving the notice and obtaining the consent that the law and district policy require.
Demonstrations. We demonstrate Meeting Companion in demonstration districts that hold only fictional data, and the support access limits in Section 3 don't apply to them. If we record part of a demonstration, everyone taking part must agree first, and we delete the recording and its transcript within 7 days.
8. Data Security
We maintain administrative, technical, and physical safeguards designed to protect information, including:
Encryption of data in transit (TLS);
A separate database for each district;
Role-based access controls within the Service and least-privilege access for our personnel, including the support access controls and logs described in Section 3;
Automated replacement of names and identifiers before content is sent to AI providers, as described in Section 5;
Keeping Meeting Companion content and recordings in our production environment: we do not copy them to development or test systems;
Monitoring, logging, and routine backups;
Vendor review of subprocessors that handle customer data.
No method of transmission or storage is completely secure, but we work continuously to protect your information and improve our safeguards.
9. Breach Notification
If we determine that a security incident has resulted in unauthorized access to or disclosure of district data, we will notify the affected district without unreasonable delay and no later than 72 hours after that determination (or sooner if a law or the district's agreement requires), consistent with the needs of law enforcement. We will provide the information reasonably needed for the district to meet its own notification obligations, and we will cooperate with the district's response.
10. Data Retention
Meeting Companion recordings and transcripts are deleted automatically after the retention period the district sets (30 days unless the district chooses otherwise). Generated meeting notes stay with the meeting until the district deletes it or its subscription ends. A legal hold suspends all deletion until it is lifted. Temporary copies made while files upload are deleted within about a day.
Account and platform content is retained for the duration of the district's subscription and handled after termination as described in our Terms of Service (an export window, then deletion, including from backups in the ordinary course of backup cycles).
Access and support records are kept for the duration of the district's subscription. We keep our record of staff support sessions for up to three years so we can show who accessed district data and why.
Application logs are kept for short periods (typically 5 to 14 days) for security and diagnostics.
Support communications and billing records are retained as needed for business and legal purposes.
11. Your Choices and Rights
Access and correction. Staff users can review and update their account information in the Service, or contact their district administrator. Districts control the content of their own workspace.
Email preferences. Marketing emails include an unsubscribe link, and we honor unsubscribe requests as required by the CAN-SPAM Act. Service and security notices are sent as needed to operate the Service.
State privacy rights. Depending on your state of residence, you may have rights to access, correct, delete, or obtain a copy of your personal information, and to non-discrimination for exercising those rights. Because we process most personal information as a service provider to districts, we may refer requests about district-controlled data to the relevant district. To exercise rights that apply to information we control, contact [email protected]. We do not sell personal information or share it for cross-context behavioral advertising.
Do Not Track. Our websites do not respond to browser Do Not Track signals because there is no common standard, but we also do not track users across third-party websites.
12. Where Information Is Processed
The Service is hosted in the United States, and information is processed in the United States. If you access the Service from outside the United States, you understand that your information will be transferred to and processed in the United States.
13. Children
Our public websites and the Service are not directed to children, and we do not knowingly collect personal information from children through them. Any student information handled at a district's direction is governed by Sections 6 and 7.
14. Changes to This Policy
We may update this Privacy Policy from time to time. If we make material changes, we will provide notice through the Service or by email before the changes take effect, and we will not materially reduce our commitments regarding student data during a district's subscription without the district's consent. The "Effective Date" above reflects the latest revision.
15. Contact Us
Questions, requests, or concerns about privacy can be sent to:
Clear Education LLC
Email: [email protected]
Support: [email protected]
Last updated November 9, 2026
Questions? Contact us at [email protected].