Who handles your information
Last updated: October 12, 2026
eduScout runs on services from a small number of other companies. This page lists every company that can see information about you, what it sees, and why. It is the same list as in our privacy policy; it lives here as well so you can check it without reading the whole policy.
Who belongs on this list. Any company outside eduScout that can see, or could see, information that belongs to you. Companies that only ever touch school information, which is public, or the tools our own team works with, are listed separately further down, so that you can see the absence is deliberate.
Companies that handle your information today
We don’t sell your information and we don’t share it for anyone else’s purposes. These companies handle information only on our behalf, under contracts that bar them from using it for anything else:
| Company | What it handles | Why |
|---|---|---|
| Supabase | What it handlesYour email, hashed password, sign-in sessions and, if you use Google, your Google profile | WhySign-up and sign-in |
| What it handlesOnly if you choose Sign in with Google | WhySigning you in | |
| Google Workspace | What it handlesEmails you send us, including “Keep me posted” replies | WhyOur email |
| Resend | What it handlesSign-in emails (confirming your address, resetting your password) and our waitlist emails, as they are sent | WhyEmail delivery |
| Railway | What it handlesOur servers and database: saved schools, reviews, the waitlist, and server logs | WhyHosting |
| Mapbox | What it handlesYour IP address and the map area you view, direct from your browser | WhyDrawing the map |
One row is easy to miss: Mapbox. The map is drawn by your browser talking to Mapbox directly, so nothing about you passes through our servers on the way. It is on the list anyway, because looking at a map of schools near your home tells Mapbox something, whether or not our servers are involved.
Named in our Trust Covenant, but not handling anything yet
| Company | Intended role | Today |
|---|---|---|
| Anthropic | Intended roleThe maker of Claude. In a later phase we plan to use it for an assistant that helps you compare schools | TodayNot in use. Nothing about you has been sent to Anthropic. Before that changes, this page and our privacy policy will say so first |
Who is not on this list, and why
- Geocoding services(the US Census Bureau’s, and Mapbox’s for the addresses the Census service could not place). We use them only on schools’ public addresses, to place the pins on the map. Nothing about you goes to them.
- GitHub. Our code and documents. It holds no information about you.
- Figma. Our design files.
- Analytics companies. None. From November 12, 2026 we will count visits ourselves, on our own servers, with no outside company involved; the notice at the top of our privacy policy explains what that counts and how to turn it off.
- Anthropic’s Claude Code. A programming tool our team uses to build eduScout. It is not the product integration above and has no access to the database that holds your information.
What we promise about this list
- It is updated before, not after. A new company that can see your information is added here before it starts, not once it has.
- It names what each company does, not just who it is. “We use Supabase” tells you nothing; “Supabase holds your email and password, and we never see your password” does.
- Absences are stated.A list of six names invites the question “and who else?”, so the section above answers it.
Changes to this page
- October 12, 2026: first published.
Questions: privacy@eduscout.app