MotivAI Privacy Policy

Last updated: May 2026

FERPA-aligned COPPA-aware Google API limited use

1. Introduction

MotivAI is an educational platform designed for K–12 schools. MotivAI provides AI-powered tutoring tools and a token-based reward system that motivates student engagement based on academic performance.

This Privacy Policy explains what data we collect, how we use it, who we share it with, and how long we keep it. MotivAI is operated as a school service under the Family Educational Rights and Privacy Act (FERPA) where applicable. We onboard schools as institutions — individual teachers do not sign up independently.

2. Who This Policy Covers

This policy applies to user types associated with a school that has an active Data Processing Agreement (DPA) or equivalent with MotivAI, including:

Teachers — authorized by their school to connect Google Classroom and manage student rewards.
Students — enrolled in classes that use MotivAI for AI-assisted learning.
School administrators — oversee institutional access and data governance.

Additional duties, subprocessors, and retention may be specified in the DPA or school contract.

3. Data We Collect

3a. Data collected via Google OAuth (read-only Classroom access)

When users connect a Google account, MotivAI requests read-only Google Classroom API scopes appropriate to each role. We use this access to synchronize educational context needed to run the product. MotivAI does not use these permissions to modify, delete, or write grades or coursework inside Google Classroom.

Depending on how your school configures its Google OAuth client, standard sign-in scopes (for example openid and https://www.googleapis.com/auth/userinfo.email) may also be requested for login and account identity.

Scope	Role	Purpose
`https://www.googleapis.com/auth/classroom.courses.readonly`	Teacher · Student	Course names and the learner’s own course list — to show classes inside MotivAI.
`https://www.googleapis.com/auth/classroom.rosters.readonly`	Teacher · Student	Class rosters and related roster information as permitted by Google for the signed-in user (for example, teacher views of enrolled students, and limited roster context for students such as teachers linked to their courses).
`https://www.googleapis.com/auth/classroom.coursework.students.readonly`	Teacher	Course work visible to teachers for classes they teach (for example, assignment titles, due dates, and point values) — to sync the reward system and related teacher workflows.
`https://www.googleapis.com/auth/classroom.student-submissions.students.readonly`	Teacher	Student submissions and grades for coursework in classes the teacher instructs — for token distribution and academic analytics authorized by the school.
`https://www.googleapis.com/auth/classroom.coursework.me.readonly`	Student	The student’s own course work in classes they are enrolled in — to power the in-product “assignments still to turn in” view that helps students earn more tokens.
`https://www.googleapis.com/auth/classroom.student-submissions.me.readonly`	Student	The student’s own submission state for those assignments (for example, not yet turned in) — used only to filter the student’s view to unfinished work.
`https://www.googleapis.com/auth/classroom.profile.emails`	Teacher · Student	Email addresses associated with profiles in Classroom — for identity, roster display, and matching users to enrollments and grades.
`https://www.googleapis.com/auth/classroom.profile.photos`	Teacher · Student	Profile photos — for display in dashboards and rosters where the product shows them.

3b. Data generated within MotivAI

Student chat prompts — text entered when interacting with the AI tutor. Stored in our database. Raw prompts are not shown to teachers or other students. Used to generate responses and may support anonymous, aggregated analytics only.
Engagement analytics — may be derived from usage; when shown to teachers, it is presented in aggregate or de-identified form as designed for the product.
Token records — tokens earned, spent, or distributed as part of the reward system.
Teacher-uploaded materials — instructional content uploaded by teachers (for example, syllabi) directly to MotivAI.

4. How We Use Data

Data is used to provide the educational services described in this policy and in school agreements. Specifically:

Google Classroom data is used to show courses, rosters, assignments (for authorized teacher workflows), and related academic information to authorized users.
Student chat prompts are processed to generate AI tutor responses and to derive anonymous, aggregated analytics. Raw prompts are never shown to teachers, administrators, or other students. We do not use student data for advertising or commercial profiling; we do not sell or rent student data to advertisers or data brokers.
Grades data is used by teachers to determine token distribution. Grades are stored temporarily and deleted at the end of each academic year unless a school agreement specifies otherwise.
Profile photos and emails are used for identity and display within the platform.

MotivAI’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

5. AI Tutor and Third-Party AI Processing

MotivAI’s AI tutor is powered in part by third-party APIs (for example, OpenAI). When a student sends a message, that content may be transmitted to the provider for processing. Safeguards include:

No personally identifiable information (PII) is intentionally included in model-bound payloads beyond what is necessary to operate the feature; students may be referenced with internal session or account identifiers where practicable.
Provider use of API data for model training is governed by our Data Processing Addendum (DPA) with the vendor and the school’s agreements.
OpenAI and other model providers are listed as named subprocessors in the school’s DPA with MotivAI where applicable.

6. Data Retention, Security, and Sharing

Retention periods (for example, for grades or chat logs) may be set by school agreement or operational policy. We implement reasonable safeguards to protect personal information and limit access to authorized personnel and subprocessors as needed to run the service.

We do not sell Google user data. We may share information with service providers under contract, or when required by law, as described in agreements with your school.

7. User Control

Users can revoke MotivAI’s access to their Google account through their Google Account security settings. Doing so may limit or disable Google-dependent features until access is restored.

8. Children’s Privacy

MotivAI is intended for educational use with school involvement. Schools and families should use MotivAI consistent with applicable child privacy laws (including COPPA where it applies) and district policy.

9. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top will change when revisions are posted on this page.

10. Contact

Questions about this Privacy Policy or MotivAI’s data practices may be sent to:

blendzion@motivai.co