Last updated: October 26, 2026
When you sign in with Google, we receive your name, email address, profile picture, and confirmation that Google has verified your email. We use this information for authentication, account preferences, usage limits, support, and subscription access.
We keep limited service metadata such as the tool used, grade, subject, time of use, account settings, and payment status. Student roster entries and teaching materials saved in My Students or My Saved are stored in your browser's local storage and do not sync across devices.
When you contact support or submit feedback, we collect the information you choose to provide so we can respond and diagnose the issue.
Text entered into a generation form is transmitted to our configured AI model provider to produce the requested content. ClassMate AI does not intentionally add generation prompts or completed teaching materials to a server-side saved-items library. We do not use submitted content to train our own model.
Do not enter information that directly identifies a student. Use initials, a nickname, or a pseudonym, and follow your school or district's data-handling policy.
We do not sell personal information or generated content.
We record basic first-party page-view statistics independently of the optional analytics-cookie choice. These service records include the page path without query strings, referring site origin, timestamp, a random browser-session identifier in session storage, Cloudflare-provided IP address and approximate location/network metadata, and the browser user-agent. For signed-in visitors, the verified account email distinguishes account activity and excludes configured owner/test accounts from operational reports. We do not add student names, teaching passages, generation results or URL query strings to these page-view records. Browser sessions are a traffic measure, not proof of unique people. Known automated clients are excluded; undetected automation and separate browsers can still affect counts.
Essential cookies keep you signed in, protect the authentication flow, and meter guest trial use. A signed, opaque trial identifier (_gsi) is stored in an HttpOnly cookie for up to one year. Its server-side counter limits repeated trial use and contains no student text. The previous signed trial counter (_gst) may be read to preserve an existing allowance. These metering cookies are not used for behavioral analytics. Clearing cookies can create a new browser identity; separate IP-based usage limits also apply. With your consent, Google Analytics collects usage information such as pages visited, browser type, and approximate session activity. You can decline analytics cookies through the consent banner.
With the same analytics consent, we also record fixed reading-workflow steps, such as starting a form, a missing-field warning, receiving a result, or requesting an export. These diagnostic records contain a random browser-session identifier, a timestamp and action labels, not passages, generated text, student details, email addresses or IP addresses. An export request does not tell us whether a teacher downloaded or used the material. Configured owner checks are marked separately from other activity.
ClassMate AI is a teacher-facing service and does not provide student accounts or a child-facing interface. We do not intentionally store student roster names on our servers. Sensitive tools also omit their topic field from server-side generation history and feedback records.
Teachers are responsible for obtaining any consent required by their school, district, or applicable law. If you believe a child's personal information was submitted improperly, contact us so we can investigate and delete any retained record.
Account, subscription, payment-event, usage, and support records are retained while needed to provide the service, meet payment or legal obligations, and resolve disputes. Browser-local teaching content remains under your browser's controls. Trial counters retain the minimum opaque identifier and count needed to enforce the trial limit. After account deletion, minimal deletion markers prevent old backups or delayed writes from restoring removed records; some payment evidence and previously created backups may remain subject to the stated retention requirements. We use HTTPS, signed session cookies, access controls, and webhook signature verification, but no online service can guarantee absolute security.
You may request access, correction, deletion, or export of personal information associated with your account, subject to payment and legal retention requirements. Email [email protected] from the address linked to your account. We will verify the request before acting on it.
We may update this policy as the service changes. Material updates will be posted here with a revised date.