💻 For District Technology Directors
SPEDGenie™ — Technology Approval Brief
Everything your technology department needs to review before approving district-wide use — data privacy, FERPA compliance, network requirements, and system compatibility.
At a glance
🔒
No PII stored
Student data never leaves the teacher's session
🌐
Browser-based
No installation, no server, no VPN required
📋
DPA available
Data Processing Agreement provided on request
✅
FERPA safe
FERPA warnings on every student input screen
Data privacy — what is and is not stored
Data type
What happens to it
Stored?
Student PII (names, DOB, ID numbers)
Teachers are instructed to use student codes only (e.g. "GL-7th"). FERPA warnings appear on every screen that accepts student input. The platform cannot prevent a teacher from typing a real name, but the policy and UI both direct against it.
✕ Never stored
IEP content generated
Generated on demand in the teacher's browser session. Not saved to any server or database. Disappears when the browser tab is closed.
✕ Not stored
Saved goals and dashboard data
Stored only in the teacher's own browser (localStorage). Never transmitted to any server. Cleared when the teacher clears their browser data or switches devices.
Browser only
Uploaded district form templates
Processed locally in the browser. The extracted text is sent to the AI to detect field names — not student content. Not stored after the session ends.
✕ Not stored
AI prompts (what is sent to the AI)
Prompts contain only teacher-entered information (disability category, grade, assessment scores, goal area). The AI vendor's Zero Data Retention policy means prompts are not stored and not used for model training.
✕ Not retained
Teacher accounts
No user accounts or logins currently exist. Teachers access the platform directly by URL. The District App (coming soon) will add optional account management for district administrators.
No accounts yet
Usage analytics
Aggregate traffic data only (page views, feature usage counts) — no personal identifiers. No third-party analytics scripts are loaded on the platform.
Aggregate only
FERPA compliance
Is SPEDGenie a "school official" under FERPA?
SPEDGenie is a tool used by school officials (licensed SPED teachers), not a school official itself. The teacher remains the educational record custodian. SPEDGenie generates draft content — the teacher reviews, edits, and submits. The final IEP document enters the district's official system (TAMS, Frontline, SpEd Forms) separately.
Does the district need a FERPA-compliant agreement with SPEDGenie?
Because SPEDGenie does not receive, maintain, or transmit student education records, a formal FERPA agreement is not legally required under the current model. However, SPEDGenie provides a Data Processing Agreement (DPA) for districts that require one for any vendor their staff uses. Contact hello@spedgenie.com to request a DPA.
What happens if a teacher accidentally enters a real student name?
The platform does not technically block real names — it relies on teacher training and the prominent FERPA warnings on every relevant screen. The data is not stored on any server, so a real name entered by mistake exists only in that session and disappears when the tab closes. District policy should instruct teachers to use student codes only.
Is SPEDGenie COPPA compliant?
Yes. SPEDGenie is a teacher tool — students never use the platform directly. The Terms of Service explicitly restrict use to licensed education professionals. No student accounts exist and no student-facing features are present.
Compatibility with existing district systems
Does SPEDGenie integrate with our Student Information System (Skyward, PowerSchool, Infinite Campus)?
Not via API — by design. Teachers enter key values manually from Skyward (absences, tardies, grades). This keeps student PII out of SPEDGenie entirely. A future district edition may offer read-only SIS integration with appropriate DPA agreements in place.
Does it integrate with our IEP management system (TAMS, Frontline, SpEd Forms)?
Not via API. SPEDGenie exports completed content as a Word document (.doc) that teachers copy into their official IEP system. The District Template Engine fills your district's own forms, so the exported output matches your official templates exactly. Your district's system of record is unchanged.
Does it require any installation or district IT infrastructure?
No. SPEDGenie is entirely browser-based. No software installation, no server configuration, no VPN, no district hosting. Teachers go to spedgenie.com in Chrome, Edge, Safari, or Firefox. Works on Chromebooks, Windows laptops, and iPads.
Network requirements — domains to whitelist
spedgenie.com
*.netlify.app
fonts.googleapis.com
fonts.gstatic.com
Browser support: Chrome 90+ · Edge 90+ · Safari 14+ · Firefox 88+ · Chromebooks fully supported · iPads supported via Safari. No plugins or extensions required.
Technology approval checklist
Domains whitelisted in content filter — spedgenie.com, *.netlify.app, fonts.googleapis.com, fonts.gstatic.com Network
Browser compatibility confirmed on district-issued Chromebooks, Windows laptops, and/or iPads Devices
FERPA review completed — confirmed no student PII is stored; district policy on student codes reviewed with SPED director Privacy
DPA reviewed — Data Processing Agreement received from SPEDGenie EdTech and approved by district counsel if required Legal
No SIS integration required — confirmed teachers will enter Skyward data manually; no API connection needed Systems
No IEP system integration required — confirmed teachers will copy/export content into TAMS, Frontline, or SpEd Forms manually Systems
SPED director notified — district SPED leadership has reviewed the District Guide at spedgenie.com/tutorial-district Stakeholders
Teacher training plan confirmed — teachers directed to spedgenie.com/tutorial-teacher for 5-minute onboarding Training