Subprocessors
These are the third parties we use to provide DistrictWise, and what each one touches. We keep this list current and will notify subscribing districts before adding or changing a subprocessor that handles district data.
| Subprocessor | Role | Data it touches | Location |
|---|---|---|---|
| Anthropic, PBC | AI model processing (Claude, via API) | Masked question text and retrieved policy excerpts. Never un-masked student identity. | United States |
| Amazon Web Services (EC2, SES) | Application hosting; transactional email (sign-in, notifications) | Service data at rest and in processing; staff email addresses. No student PII, no query content in email. | United States |
| Cloudflare, Inc. | DNS and delivery for our public marketing site | Public web traffic to districtwise.ai. No authenticated application data. | United States / global edge network |
| HubSpot, Inc. | CRM for district contacts and outreach | District staff contact details (name, title, email) provided in inquiries or by the district. | United States |
| PandaDoc, Inc. | Contract execution (MOU, DPA, MSA) | Signatory names and email addresses on district agreements. | United States |
| Google Workspace | Business email and document collaboration for DistrictWise staff | Correspondence with district staff; documents shared with a district when the district asks for one. | United States |
How we choose subprocessors
Every subprocessor above is contractually bound to protect the data it processes, consistent with the commitments in our Data Processing Agreement. We do not add a subprocessor that handles district data without reviewing its security and privacy posture first.
Changes to this list
If we add or replace a subprocessor that touches district data, we will update this page and notify each subscribing district's administrative contact in advance, consistent with the change-notification terms in your Data Processing Agreement.
Questions about a specific subprocessor? Ask us.