Public / customer-facing · Updated October 19, 2026
How Agenteach protects student data, district systems, and teacher workflows — with plain-English commitments for educators and implementation detail for technology, privacy, and procurement teams.
Privacy control panel
Minimum necessary data
We collect only what the district-approved workflow needs, and teachers choose what context to use.
US-only storage and processing
All service data is stored and processed in United States regions — encrypted at rest and in transit, with AI processing pinned to a US region as well.
AI data is not used for model training
AI may draft or extract, but it does not train on student data or make final decisions.
Residency
US-only
Azure US hosting; AI processing pinned to a US region.
Access
District SSO
Sign-in through district identity; district MFA policy applies.
AI
Zero training
Teacher review, no model training.
Commercialization
Never sold
No sale, ads, or commercial profiles.
About Agenteach
Agenteach is an educational technology platform dedicated to empowering teachers with intelligent, AI-driven tools that streamline lesson planning, enhance student feedback, and reduce administrative overhead. Built by educators for educators, Agenteach is designed as a school-controlled, teacher-reviewed documentation and workflow assistant: it prepares drafts and records for authorized users, while educators and districts remain in control.
Trust posture
Agenteach's near-term trust posture is to be designed for FERPA/COPPA-aligned, DPA-ready K-12 workflows. We do not claim SOC 2, ISO 27001, 1EdTech, SDPC registry, or iKeepSafe badge completion unless and until the relevant third-party process is complete. Our formal policy set — Privacy Policy, Terms of Service, Subprocessor List, and Retention & Deletion Schedule — is published on this site. For pilots, the priority is a signed district data/privacy agreement, no-training AI commitments, least privilege, deletion/export support, and incident-response readiness.
Signed DPA/DSA, data dictionary, subprocessor list, no-sale/no-ads/no-training commitments, MFA, token encryption, no raw student-content logs, deletion/export process, and incident-response plan.
SDPC/NDPA-style packet, vendor-risk packet, AI-use statement, Google OAuth least-privilege posture, US residency commitment, admin-visible data inventory, and audit export.
SOC 2 readiness then Type I/II, external penetration testing cadence, 1EdTech TrustEd Apps preparation, and iKeepSafe-style FERPA/COPPA review if the product scope requires it.
Part 1
Agenteach is a helper. It can organize notes, draft messages, and prepare work for you to review. You stay in charge.
It does not send family messages, file reports with an agency, change SIS attendance, grade students, discipline students, diagnose students, or confirm IEP/504 service delivery. It prepares drafts. A person approves family content, and staff send it through district channels.
For roster-light workflows, that may mean a student name, class/course, and guardian contact only when a parent draft is enabled. We do not need student web-browsing history, precise location, social media profiles, or extra demographic data.
Districts approve the service, integrations, retention settings, exports, deletion, and subprocessors through a DPA/NDPA or similar agreement. Before Attend handles real district data, we will enforce access by district, school, class, role, and assigned student relationship on every request.
AI helps draft family messages and monthly attendance summaries and summarize case histories from authorized context. It must not invent facts, train on student data, or make decisions about students: no risk scores, predictions, grading, discipline, eligibility, referral, or diagnostic determinations. Flags use district-set thresholds, not AI. Teachers review outputs before use or saving; a person approves family content and staff send through district channels.
Simple promise
Agenteach is for school work only. We do not sell student data, rent it, target ads, build commercial profiles, or use student data to train AI models. The MVP is teacher-only; if student-facing features are added later, they will require additional COPPA and district consent controls.
Part 2
Agenteach uses a district-authorized, teacher-reviewed architecture: React/Next.js for the interface, a policy-enforcing backend for authorization and audit, and encrypted, US-hosted storage for casework and a working copy of district-approved SIS data through Ednition. The SIS remains the record of truth for attendance; Agenteach does not change attendance in the SIS.
Agenteach's encrypted US cloud environment stores casework and a working copy of SIS attendance under a DPA/NDPA or similar agreement. The SIS remains the record of truth for attendance. Before Attend handles real district data, we will scope every record to its district and school and enforce retention, export, erasure, audit, and legal-hold coverage for every record class. Erasure must also reach any linked legacy file content.
Before Attend handles real district data, we will enforce server-side role, district, school, assigned student relationship, data-category, and record-state checks for every request. Counselor-only restricted notes and academics will require explicit permissions, including in reports, exports, and AI context. Role alone is not enough; a person must approve family content before staff send it through district channels.
Traffic uses HTTPS/TLS, security headers, CDN/WAF controls, rate limits, upload size/type limits, and backend-issued short-lived upload URLs. Sensitive student data is not stored in browser localStorage, sessionStorage, or IndexedDB.
Databases, object storage, backups, OAuth tokens, transcripts, exports, and temporary processing artifacts must use encryption, scoped access, lifecycle deletion, and district-tagged metadata where applicable. Before Agenteach Attend handles real district data, we will verify and enforce that coverage across all of its records and generated artifacts.
Teacher sign-in
District identity, no extra passwords
Teachers and admins sign in through their district's Google or Microsoft identity. Agenteach keeps no separate passwords, so the district's MFA policy applies to every sign-in.
Production PII
Scoped, audited access
There is no support tier with standing access to district data. Infrastructure access is limited to named engineering founders, and before Attend handles real district data, we will capture sensitive reads, changes, exports, erasures, and every AI call in a database-enforced append-only audit trail.
District identity
OAuth 2.0, least privilege
District SIS, Clever, ClassLink, OneRoster, Ed-Fi, and SAML/OIDC connections run through our integration partner Ednition (SOC 2 Type 2, ISO/IEC 27001:2022) and are added only through district-approved, least-privilege scopes that the district can revoke at the source.
Privacy governance
Attendance case notes, district-enabled course grades/credits, observations, and family-message drafts are education records when tied to identifiable students. Attend does not collect child-welfare reports, disability/IEP/504 or accommodation records, health records, or discipline records, including in notes and drafts. Staff follow child-welfare procedures outside the tool. Governance is designed to align with FERPA school-official workflows, COPPA school-consent structures where under-13 data is in scope, SDPC/NDPA expectations, and comparable state student privacy obligations.
Default retention windows are published in our Retention & Deletion Schedule. Before Attend handles real district data, we will apply an automated daily purge and district-configurable windows to every record class and verify complete erasure, export, audit, and legal-hold coverage. On contract termination or authorized LEA request, data is returned/exported if requested and deleted within 60 days, subject to the published backup and hold caveats. Records under legal hold are preserved until release; export is never blocked by a hold.
Before Attend handles real district data, we will route AI calls through a backend safety layer, minimize prompts, enforce restricted-note permissions in AI context and exports, and record provider, model, and purpose in append-only audit entries, never raw content. We use DPA/subprocessor terms with no-training and no-retention commitments where available. AI never makes student decisions, risk scores, predictions, or referrals.
Subprocessors needed to deliver Agenteach — currently hosting, staff service email (no family messages), AI processing, and district SIS/SSO integration, per our published Subprocessor List — are bound by DPAs or equivalent terms. We maintain a minimized subprocessor list, review vendor controls before use, and flow down privacy, security, deletion, confidentiality, and breach-response obligations.
District SIS and single sign-on connections are operated through Ednition's RosterStream platform, purpose-built K-12 rostering infrastructure. Ednition is SOC 2 Type 2 attested and ISO/IEC 27001:2022 certified, runs annual third-party penetration tests, encrypts data with TLS 1.2+ in transit and AES-256 at rest, hosts Agenteach's tenancy in US AWS regions, is a 1EdTech member and OneRoster 1.1/1.2 certified, and publishes its controls in real time at trust.ednition.com.
Through the district-approved connection, it processes roster/directory data, daily attendance and absence codes, guardian contacts where shared, and course grades/credits only when the district enables the counselor academic view. It never receives staff-created notes (including restricted notes), contact/home-visit logs, plans, meeting notes, draft messages/summaries, report worksheets, Agenteach audit trails, or AI requests/outputs.
Ednition is bound by its agreement with Agenteach to process only as instructed, use data only to provide the service, prohibit AI training, keep data confidential, delete it within 60 days of termination, and promptly notify Agenteach in writing of a breach or potential breach. Its Privacy Statement states no sale, advertising, or profiling. Full detail: Privacy Policy §7.
District-ready MVP guardrails
For early district use, Agenteach focuses on attendance case notes, support plans, draft communications, district-enabled counselor academics, teacher tasks, field-level data transparency, and admin-visible privacy controls. It does not change SIS attendance, send family messages, or file reports with any agency.
Continuous compliance
Static-analysis and dependency scanning run in CI on every change in both application repositories, cloud workloads are monitored by Microsoft Defender for Cloud, traffic passes a managed web application firewall, and penetration testing is on the pre-pilot roadmap.
In the event of a suspected breach, our response procedures call for immediate isolation of affected systems, investigation and preservation of audit evidence, and notice to impacted LEAs within contractually and legally required timelines — 72 hours or less for district notice under our standard DPA commitments.
Need district review materials?
For security questionnaires, DPA/NDPA or DSA review, data-dictionary review, HECVAT/CAIQ-style diligence, subprocessor review, AI policy review, or pilot planning, contact Agenteach and we’ll share the appropriate supporting materials.
