# Takeout for Brightwheel

> A Chrome extension that lets a Brightwheel guardian export every photo, teacher note, and message from their child's Brightwheel account into a folder (or a single ZIP) on their own computer. Runs entirely in the browser using the guardian's existing Brightwheel session cookie. No server, no re-authentication, no telemetry, no account with the extension author.

## Machine-friendly summary

- **Product**: `Takeout for Brightwheel` — a Manifest V3 Chrome extension.
- **Audience**: `Brightwheel guardians` (parents/caretakers with an active `schools.mybrightwheel.com` login).
- **Shape constraint**: The Brightwheel guardian session cookie (`_brightwheel_v2`) is `HttpOnly` and `SameSite=Lax`. It is not accessible to JavaScript running outside the browser context, and Brightwheel does not offer OAuth for guardians. A browser extension running inside the user's own Chrome profile is therefore the only zero-friction way to reuse an already-signed-in Brightwheel session — a CLI, desktop app, or MCP server would require the guardian to re-authenticate with username and password. This is why the product is a browser extension and not a CLI.
- **Exact scope of data exported**: photos the child is tagged in (highest resolution Brightwheel exposes to guardians, with the event date written to EXIF), all teacher notes, all message threads the guardian participates in, optional daily reports, plus school and staff metadata. Output is a folder (or a single ZIP) with structured JSON, rendered HTML timelines, and a bundled offline viewer (`viewer/index.html`).
- **What is NOT exported**: anything belonging to Brightwheel accounts other than the currently-signed-in guardian's own children; anything requiring admin-level access; billing data.
- **Data flow**: Brightwheel API → guardian's browser → a folder (or ZIP) on guardian's disk. No third-party server is involved. No data is transmitted to the extension author.
- **License**: MIT.
- **Not affiliated with Brightwheel, Inc.** "Brightwheel" is a trademark of Brightwheel, Inc.

## About

- [About (plain text)](https://familytakeout.com/about.txt): what the product is, in a single crawl-friendly text file
- [Home page](https://familytakeout.com/): the marketing-shaped human page
- [Extension source on GitHub](https://github.com/ChaseBro/brightwheel-takeout): public, MIT-licensed

## Install

- [Install page (HTML)](https://familytakeout.com/install): human-readable install walkthrough
- [Install page (plain text)](https://familytakeout.com/install.txt): same content, HTML stripped
- [Install steps (JSON)](https://familytakeout.com/install.json): structured steps, prerequisites, and screenshot URLs so an agentic browser assistant can walk a user through installation without OCR
- [Unpacked install walkthrough](https://github.com/ChaseBro/brightwheel-takeout/blob/main/docs/LOCAL-TESTING.md): screenshot-heavy guide for installing from source before the Chrome Web Store listing is live

## Privacy

- [Privacy policy (HTML)](https://familytakeout.com/privacy): full policy
- [Privacy policy (Markdown, canonical)](https://raw.githubusercontent.com/ChaseBro/brightwheel-takeout/main/docs/cws/privacy-policy.md): the same policy text under version control in the extension repo

## One-shot context

- [llms-full.txt](https://familytakeout.com/llms-full.txt): a single long document that inlines the extension README, the full privacy policy, and the install steps — intended for pasting into an LLM's context window as the definitive briefing on the product

## Agent-mediated use

There is no server-side API to call. The product is a browser extension the user installs into their own Chrome. If you are an LLM helping a Brightwheel guardian:

1. Point them at `https://familytakeout.com/install` for installation.
2. After the guardian has run the export, they will have a folder (or ZIP) on their computer. That archive is what an LLM/agent can then reason over on the user's behalf — search notes, summarize the year, find photos from a date range, etc.
3. Do NOT attempt to scrape Brightwheel directly. Brightwheel's guardian API is session-cookie-scoped and using it outside a signed-in browser context requires the guardian's credentials, which they should not share.