Who processes data for us
EdGauge, LLC runs EdGauge with the help of the outside services below. Each one processes personal information on our behalf, only to provide its part of the service. Our privacy policy says what we collect and why, and how we use AI says what each AI provider receives.
| Subprocessor | What it does for us | Personal information it receives | Where |
|---|---|---|---|
| Amazon Web Services | Hosting: the application servers, database, file storage, backups, email sending, content delivery and logs | Everything the app holds: accounts, activity records, conversations, contributed data and evidence files, problem reports, and server logs with IP addresses | United States, the US West (Oregon) region. Content delivery serves pages from AWS edge locations, which can be outside the United States. |
| Cloudflare | Our public landing page, its interest list, bot checks on its form, web analytics for the landing page, and DNS for our domain | Interest-list entries (name, work email, district, and the optional role and note you enter) and landing-page visitors' IP addresses and browser details. The app's own traffic does not pass through Cloudflare. | The interest list is stored in Western North America. Requests are served from Cloudflare's global network, which can be outside the United States. |
| OpenAI | The default AI provider: Ask EdGauge, review briefs for flagged contributions, text embeddings for search, and reading public documents | Questions and conversation history, tool results, your typed position title and your district, and contribution details for a flagged review, as described on how we use AI | United States |
| Anthropic | An alternative AI provider, chosen by our configuration, and the provider for extracting findings from public audit reports. Our staff also use Anthropic's Claude as a tool to operate the service | The same as OpenAI when it is the configured provider; public document text; and what our staff's database queries and log reads return, which can include account details and IP addresses | United States |
| OpenRouter, and the model behind each route it picks | Routes the position title mapper and the plausibility review of contributed values to a model: TypeSafe's Jev, with an OpenAI model as the title mapper's fallback | Contributed values with their notes (emails and phone numbers removed), the district's type and size, and public payroll job titles with their employer and pay. Never a person's name from a payroll record. | OpenRouter is in the United States. The model host behind each route runs where that host runs; we do not pin it. |
| Microsoft 365 | Email for our own addresses, such as our support address | The messages you send us, with your name and email address, and our replies | United States |
What is not on this list
- Sources we read from. We download public data from government agencies and other public sources, such as the California Department of Education, the U.S. Census Bureau and the Federal Audit Clearinghouse. We send them no personal information about you.
- Code hosting. We keep our source code with a code hosting service that receives no customer personal information.
- Your own AI client. If you connect our tools to your own AI client through MCP, your client and its model receive the results. They are yours to choose, not our subprocessors.
Where your data lives
EdGauge stores its data in the United States. The exceptions are in the table: content delivery and Cloudflare's network can serve requests from outside the United States, and the model host behind an OpenRouter route runs wherever that host runs.
Changes to this list
This page is numbered and dated at the top, and we update it when a subprocessor is added or removed, or when what one receives or where it processes data changes. Questions about a change go to [email protected].
Questions
Write to [email protected].