You’re here
This diagram shows where student data enters Impact Suite, where it is stored and processed, and which subprocessors touch it. All persistent data and all AI processing stay within a single U.S. AWS environment (us-west-2 / Oregon).
End-to-end flow
- School district — the Student Information System (SIS), staff, and parents are the sources of data.
- Ednition RosterStream (U.S. subprocessor) — securely syncs roster data and brokers SSO into the platform over encrypted SFTP/API.
- Impact Suite AWS boundary (U.S.) — the application (JWT auth, role-based access, sandbox scoping), the PostgreSQL database, and S3 file storage. All AI runs here too: AWS Bedrock (Anthropic Claude), Transcribe, Polly, and Textract — no AI provider outside AWS.
- U.S. communications & utility subprocessors (under DPA) — Twilio (SMS), Mailgun/SendGrid (email), Mapbox (geocoding), PostHog (analytics).
Trust boundary & residency
- Everything inside the AWS boundary is AES-256 encrypted at rest and served over TLS 1.2/1.3, with VPC isolation.
- External subprocessors are U.S.-based and under DPA/BAA.
- No student data is processed outside the United States.
PII in motion, by hop
| Hop | Data in motion | Direction |
|---|---|---|
| District SIS → Ednition | Roster, enrollment, demographics | Inbound sync |
| Ednition → Impact Suite | Same roster data (encrypted) | Inbound |
| Staff & parents → Impact Suite | Auth, concerns, notes, messages, uploads | Bidirectional (TLS) |
| Impact Suite → AWS AI services | Minimum-necessary data in prompts; documents | Internal to AWS |
| Impact Suite → Twilio | Guardian phone + message body | Outbound |
| Impact Suite ⇄ Mailgun / SendGrid | Guardian/staff email + content | Out / In |
| Impact Suite → Mapbox | Student home address (geocoding) | Outbound |
A formatted diagram is available for download on request, and this page is kept in sync with our subprocessor list.
