Privacy Policy

PulsePoint — Special Education Information System · Last updated: June 2026

What we collect

When deployed for a school or district, PulsePoint may store:

• Student roster fields (name, grade, IEP-related metadata configured by the district)
• Assignment progress, scores, and completion timestamps
• IEP goals, accommodations, behavior incidents, and staff notes entered by authorized users
• Activity logs for classroom monitoring (when enabled)
• Optional wellness device metrics (e.g. Fitbit) only if your district enables that integration

How we use data

Data is used to support instruction, IEP progress documentation, grading, and staff workflows. We do not sell student data. Third-party services (e.g. hosted AI inference) should be configured by the district with appropriate agreements.

Where data is stored

Production deployments use MongoDB under district or operator control. The public demo stack uses an isolated sandbox database (pulsepoint_dev_db) for training and presentations—not live production records.

FERPA

Student education records are handled in compliance with FERPA when PulsePoint is operated by a school or district. Parents/guardians may request access through their school per district policy.

Staff access controls

Staff-only pages use passcode or session gates. Districts should rotate passcodes, restrict network access, and follow least-privilege practices for production.

Retention

Retention schedules are set by the deploying district. Demo sandbox data may be reset during development without notice.

Open source

PulsePoint is MIT-licensed. Source code is available for security and privacy review. See LICENSE and Terms of Service.

Contact

Privacy questions: contact your school administrator or district privacy officer. Software: Aris Tunson · © 2024–2026 · Roosevelt SEIS · Oakland USD.

← Dev hub · Terms of Service · Home