Our Privacy Commitment
Your student data never leaves your computer.
Grow and Glow SPED is built so special education teachers can draft IEPs, goals, and student-specific work without worrying about where that information goes. The short version: it doesn't go anywhere. It stays on your device.
The promise
What we don't do
Most teacher tools collect something. We chose not to — and built the product to make that promise architecturally true, not just a line in a policy.
- No servers store your work. We do not operate cloud storage that receives your IEP drafts, student names, baseline data, or anything else you type.
- No sign-up, accounts, or logins. You don't create a profile to use our tools. There's no password to forget. There's no account for us to be asked to hand over.
- No AI tools see your work. We never send your drafts, student details, or anything you enter to ChatGPT, Claude, Gemini, Copilot, or any other AI / large language model. Not for suggestions, not for features, not for "improvements." Ever.
- No individual tracking. We don't run session-replay tools, user-level analytics, or anything that captures what you type. Where we need any usage signal at all, we use anonymous aggregates only.
- No third-party leaks. We self-host our fonts (so visitor IP addresses don't go to Google), and we don't embed trackers from ad networks or marketing platforms.
Where your work lives
On your device — your choice of where.
Our tools give you three options for saving the work you do. All three stay on your computer (or a cloud folder you already use). We never see any of it.
Browser Storage
Your drafts are saved automatically inside your web browser on this computer. Nothing to set up. Works right away. Best for a quick drafting session.
Desktop Storage
Your drafts are saved automatically to a file on your computer that you choose. Survives browser crashes, browser cleanups, and reinstalls. If you pick a location inside your district's OneDrive, Google Drive, or iCloud folder, your work syncs across your devices — and it stays entirely within the cloud your district already approves. We're not in the middle.
Backup File
One-click download of everything you've drafted. Keep it wherever you keep your other work files. Drop it back in anytime to pick up where you left off.
Why
We built it so we couldn't see your data — even if we wanted to.
The only way to break this would be to rebuild the product from scratch.
Special education teachers are entrusted with some of the most sensitive student information in any profession: diagnosis data, family circumstances, behavioral histories, and the specific services a child legally receives. The tools that support this work should treat that responsibility the same way teachers do.
Most of the web doesn't. Cloud sync, accounts, analytics, and "AI-powered suggestions" are the defaults — each one a data-path that makes a district IT team hesitate, and each one a risk a teacher has to weigh before typing a student's name.
We chose a different default. The product runs in your browser; the data lives on your machine; the saves go to storage you control. There is no server path for your work to travel along, because we didn't build one. That's not a promise we can break with a future update — it would require rebuilding the product, which we're not going to do.
For district IT and administrators
The technical summary, in plain English.
- The site is a static web application. Pages are HTML, CSS, and JavaScript served from a content-delivery network. No application server processes user input.
- Teacher-entered data (IEP drafts, student names, baseline notes) is stored exclusively in the teacher's browser (IndexedDB) and, when they opt in, in a file on their local device via the browser's File System Access API.
- No outbound network calls contain teacher-entered content. No AI or LLM services (OpenAI, Anthropic, Google, etc.) are invoked with user data.
- Web fonts are self-hosted from our own domain, so font loading does not reveal visitor IP addresses to third-party font providers.
- Any error reporting we enable is scoped to non-user-content errors (build errors, route-not-found, asset-load failures) and never captures form input or stored drafts.
If you're a district IT administrator evaluating this site for use by your teachers, you're welcome to reach out — we'll answer any specific question in writing, typically within one business day.
If anything changes
You'll know — clearly and early.
This commitment is central to what we are. If we ever needed to change it, we would announce it prominently on this page and across the site before any change took effect, never retroactively, and never silently.