iTeachWise Sub-Processor List
The complete list of every third-party service provider that processes District data on behalf of iTeachWise. Districts under DPA receive 30 days' advance notice of any addition or change to this list.
| Sub-Processor | Purpose | Data accessed | Region |
|---|---|---|---|
| Neon (Neon, Inc.) | Managed Postgres database (primary data store) | Teacher account data, generated artifacts, usage telemetry | United States (AWS us-east) |
| Replit, Inc. | Application hosting, secrets, build & deploy infrastructure | All system data in transit; encrypted secrets at rest | United States |
| Anthropic | Claude (Sonnet) AI model API for content drafting | Teacher prompts; under enterprise zero-retention / no-training agreement | United States |
| OpenAI | GPT-4o model API for content drafting and TTS narration | Teacher prompts; under enterprise zero-retention / no-training agreement | United States |
| Stripe | Payment processing for paid plans (subscription, invoicing) | Billing contact, opaque customer ID; iTeachWise never receives card numbers | United States |
| SendGrid (Twilio) | Transactional email (auth, receipts, weekly digest) | Recipient email, message body, send metadata | United States |
| Google LLC | Optional Google OAuth sign-in and Google Classroom integration | Email, profile basics; Classroom course/post metadata when teacher opts in | United States / global |
| Cloudflare | Edge CDN, DDoS protection, WAF (when enabled) | Request metadata, IP, headers; no application-layer data persisted | Global edge |
Categories of data processed
- Teacher account data — name, work email, school, role, password hash.
- Teacher-generated content — lessons, assessments, rubrics, notes, prompts the teacher submits to the platform.
- Usage telemetry — feature use, generation counts, login times. Used for product analytics and abuse prevention only.
- Billing data — for paid plans, processed by Stripe. iTeachWise never sees or stores card numbers.
Student PII is not required for any core feature and is not collected by default.
Frequently asked questions
How are sub-processor changes communicated?
iTeachWise gives Districts at least 30 days' notice before adding or replacing any sub-processor that processes District data. Notice goes to the technical contact listed on the executed Order Form and is reflected on this page with the date of change.
Can a District object to a new sub-processor?
Yes. The District may object in writing within 30 days. If iTeachWise cannot accommodate the objection, either party may terminate the affected Order Form for material breach with a pro-rated refund.
Is data sent to AI sub-processors used to train models?
No. Anthropic and OpenAI are accessed under enterprise API agreements with zero-data-retention and no-training-on-customer-data terms. Teacher prompts are not stored beyond the response cycle and are not used to improve any model.
Where is District data physically stored?
Primary application data is stored in the United States (AWS us-east region via Neon). Edge / CDN traffic may transit Cloudflare's global edge but is not persisted at the edge. EU/UK Districts are served under SCCs (see /legal/eu-uk-compliance).