Privacy Policy: AI Teacher Assistant

Last Updated: May 31, 2026

This Privacy Policy describes how the AI Teacher Assistant ("the Application", "we", "us") collects, utilizes, and strictly protects your data and the data of your students.

Because we process educational materials and classroom rosters, we have built this Application from the ground up on a Zero-Trust, Stateless Architecture specifically designed to eliminate the persistent storage of Personally Identifiable Information (PII) on our servers.

1. Data We Do NOT Collect or Store

The most important aspect of our privacy system is what we do not retain:

• No Passwords: We use Google OAuth chrome.identity to authenticate you. We never see, touch, or transmit your Google password.
• No Student Databases: We do not maintain any persistent databases of student names, target Flesch-Kincaid grade levels, or transformation directives.
• No Document Retention: We do not save copies of your Master Lesson Plans or differentiated documents on our cloud infrastructure.

2. PII Scrubbing & Demographic De-identification

Before any student parameters or class rosters are sent to our language models for lesson customization, the Application executes a strict, automated PII Scrubbing Boundary locally on our secure proxy gateway:

• Tokenization: All student names are completely stripped and replaced with anonymous sequential placeholders (e.g., [[STUDENT_1]], [[STUDENT_2]]). Student names are only restored at the very final stage when creating the final document inside your own Google Drive.
• Allowlist Filtering: We enforce a strict pedagogical column allowlist. Any columns not matching approved headers (such as Student Name, Flesch-Kincaid Grade Level, or Transformation Directives) are completely discarded from the payload, ensuring sensitive information (like student IDs or grades) never reaches the AI.
• Bias Mitigation: By anonymizing names and stripping non-essential demographics, our safety boundaries prevent LLM demographic biases during generation.

3. How We Access Your Data

In order to orchestrate lesson plan generation, the Application requests specific Google Drive API scopes (e.g., https://www.googleapis.com/auth/documents and https://www.googleapis.com/auth/spreadsheets).

When you click "Distribute" or "Generate", the Application uses a secure, temporary, short-lived API token explicitly generated by your browser to perform the following:

• Read: Securely fetch the text of your uploaded Master Lesson Google Doc or Roster Google Spreadsheet from your personal Google Drive into our proxy’s temporary memory.
• Write: Generate brand new Google Documents containing the differentiated lesson plans and place them directly back into your personal Google Drive.

The temporary API token expires automatically, and our servers cannot access your Google Drive asynchronously when you are not actively using the Chrome Extension.

4. How We Process Data (Stateless Execution)

When you submit a request, the text from your Google Doc and your Roster Spreadsheet is transmitted to our securely hosted API Gateway on Google Cloud Run.

• Our API Gateway passes the text to an Enterprise Language Model (LLM) to meticulously execute the requested pedagogical transformations.
• The moment the LLM finishes generating the final text and writes the Google Doc into your Drive, our cloud servers completely wipe the data from their memory (Stateless Execution).

Because the backend is entirely stateless, if our servers were hypothetically breached, there would be zero historical student or teacher data for an attacker to steal.

5. Student Data & COPPA / FERPA Compliance

Because our Application does not store or stockpile student data natively, the absolute "source of truth" and ultimate jurisdiction of the data remains natively within your school district's Google Workspace domain (inside your Google Sheets and Google Docs).

• We strongly advise keeping student rosters restricted to your protected Google Drive.
• We do not sell, rent, or trade any data with third-party data brokers or marketing agencies.

6. Third-Party AI Integrations

We route our lesson plan synthesis through Google's Gemini Large Language Model APIs. This data is transmitted securely over TLS encryption. The data processed through these enterprise APIs is strictly kept private and is explicitly opted-out of being used to train Google's foundational models or build marketing profiles.

7. Your Data Rights

Because your roster data and generated lesson plans live entirely inside your own Google Drive, you have total 100% control over deletion.

If you simply delete the Google Spreadsheet titled "AI Teacher Assistant Rosters (DO NOT DELETE)", the system instantly loses all memory of your classroom. Likewise, you can revoke the Application's permissions entirely at any time from your Google Account settings (Google Account Permissions Dashboard).

8. Contact Us

If you have any questions regarding this privacy policy or our stateless architecture, please contact us at our support portal.