Privacy Policy

1. Overview

This Privacy Policy applies to all Ereading.AI websites, lessons, activities, assignment links, class code flows, and LMS integrations including Google Classroom and LTI 1.3 platforms (Canvas, Schoology, Moodle, Blackboard, and others).

Ereading.AI is designed for educational use. We collect only the data necessary to deliver the service, return grades, generate result documents, and support classroom workflows. We do not maintain user profiles for advertising purposes, and we do not sell or rent personal data to any third party.

2. Data We Collect

Account Data

When you create an account (via Google sign-in or email magic link), we collect:

• email address;
• first name, last name, and display name (if provided);
• Google account identifier (for Google sign-in users);
• role selection (teacher, student, or parent);
• timezone and display format preferences.

We do not collect or store passwords. Authentication uses either Google single sign-on (OpenID Connect) or one-time email magic links.

LMS and Classroom Data

When a teacher connects Google Classroom or an LTI 1.3 platform, we receive:

• course and assignment identifiers;
• LMS-issued user identifiers and display names needed for launch and grade passback;
• submission identifiers and scoring payloads.

For Google Classroom, teacher authorization requests the following OAuth scopes: read-only access to courses, read-write access to coursework (to create assignments and post grades), and read-only access to student submissions (to verify submission status). We use these scopes solely to create assignments, return grades, and attach result links. We do not access roster data, student email addresses, or any data beyond what is required for assignment and grade operations.

For LTI 1.3 platforms, we receive only the data included in the platform's launch payload (user identity, course context, and grade passback endpoint). We request the score posting scope only.

Activity and Lesson Data

• selected answer options, written responses, timing, and completion data;
• scores and feedback artifacts generated by configured grading modes;
• assignment configuration details needed to reproduce launch behavior.

Class Code Session Data

When a student accesses an activity through a teacher's class code, we collect:

• the class code used;
• a student-entered display name (e.g., first name), if provided;
• a hashed IP address for daily usage tracking and abuse prevention (we do not store raw IP addresses for class code sessions);
• activity responses and scores as described above.

Class code sessions do not create user accounts. Students are not required to sign in or provide an email address.

Teacher-Provided Contact Data

• teacher email addresses used for result delivery and assignment workflows;
• parent email addresses provided during student invite flows.

Payment Data

All payment processing is handled by Stripe. We do not receive, store, or have access to credit card numbers or bank account details. We receive from Stripe only the data needed to manage subscription status: customer identifier, subscription identifier, plan type, and billing event timestamps.

3. How We Use Data

We use collected data exclusively for the following purposes:

• launch and deliver lessons and activities with selected settings;
• return objective scores and result links to connected LMS gradebooks;
• generate PDF result documents for teachers and students;
• provide AI-assisted feedback and scoring for eligible paid tiers;
• operate classroom reporting and assignment management features;
• send transactional emails (magic links, membership notices, result delivery);
• enforce usage limits and prevent abuse of class codes and assignment links;
• maintain service reliability and security.

We do not use educational data for advertising, marketing profiling, or any purpose unrelated to delivering the educational service.

4. Third-Party Services

We share data with third-party services only as necessary to operate the platform:

• Stripe (payment processing) — receives billing information provided by the user during checkout. Governed by Stripe's Privacy Policy.
• LMS platforms (Google Classroom, Canvas, Schoology, Moodle, Blackboard, and others) — receive grades, result links, and assignment metadata through their respective APIs. Governed by each platform's own terms.
• AI grading providers — receive educational content only, as described in Section 5 below.
• SMTP email delivery — transactional emails are sent through our configured mail service.

We do not use third-party analytics services, behavioral tracking tools, or advertising pixels. We do not share data with data brokers.

5. AI-Assisted Grading and Feedback

For eligible paid tiers (teacher subscriptions, student licenses, and district/school plans), open-ended student responses may be sent to external AI providers for automated scoring and feedback. The providers we use include OpenAI, Google (Gemini), Anthropic, and xAI. We select providers based on availability, cost, and quality, and the specific provider used may change over time.

What is sent to AI providers

• the reading passage or activity context (text only, truncated to a maximum length);
• the question or prompt;
• the student's written response;
• the scoring rubric, if available.

What is NOT sent to AI providers

• student names, email addresses, or account identifiers;
• teacher or school identifiers;
• class codes, LMS identifiers, or any metadata linking a response to a specific person or institution.

AI grading is never triggered for free-tier usage. It can also be disabled per assignment by the teacher. Each AI provider is subject to its own data processing terms. We select providers that do not use submitted data for model training under their standard API terms, but we encourage schools and districts to review provider policies independently.

6. Cookies and Local Storage

Ereading.AI uses a small number of cookies and browser storage mechanisms, all of which are functional. We do not use tracking cookies, advertising cookies, or third-party cookies.

Cookies

• ereading_session — authentication session token. Set when you sign in. Duration: 30 days for teachers and parents, 24 hours for students. Flags: httponly, secure, samesite.
• ereading_class_session — class code session identifier for daily usage tracking. Set when a student accesses an activity through a class code. Duration: browser session only.
• Google/LTI OAuth state cookies — short-lived CSRF protection tokens used during sign-in and LMS connection flows. Duration: 15 minutes or less. Flags: httponly, secure, samesite.

Local Storage

• ereading_theme — stores your light/dark mode preference. No data is sent to our servers.

Session Storage

• Student display name — temporarily stores the name a student enters during an activity session so it can be included in the submission. Cleared when the browser tab is closed.
• CSRF token cache — used for form security. Cleared when the browser tab is closed.

7. Data Retention

We retain data only as long as necessary for the purpose it was collected:

Free Anonymous Usage (No Account)

Activity responses are processed in memory and not written to our database. PDFs are generated in memory and delivered directly to the browser. No data persists after the browser session ends.

Free LMS and Class Code Usage

Activity attempt records, scores, and stored PDF result documents are retained for 14 days from the date of submission, then automatically purged.

Paid Teacher and Student Accounts

Activity records, scores, AI feedback, and stored PDF result documents are retained for the duration of the active paid subscription. After a paid subscription ends or is cancelled, data is retained for an additional 30 days to allow for reactivation or data export, then automatically purged.

Account Data

Account profiles (email, name, preferences) are retained until the account is deleted by the user or upon a verified deletion request. Inactive accounts with no paid subscription and no activity for 12 months may be flagged for cleanup.

Payment Records

Subscription status records and billing event logs are retained as required for accounting, tax, and legal compliance purposes.

Automated Purge

Expired data is purged by an automated daily process. PDF files are deleted from storage and database records are removed.

8. Security Practices

• All connections use HTTPS/TLS encryption in transit.
• Authentication tokens are stored as SHA-256 hashes; raw tokens are not persisted.
• LMS refresh tokens and API keys are encrypted at rest using AES-256-GCM.
• Session cookies are set with httponly, secure, and samesite flags.
• Short-lived context tokens are used for LMS assignment flows to limit exposure.
• CSRF protection is enforced on all state-changing operations.
• Input validation and prepared statements are used on all database operations.
• PDF result documents are access-controlled via unique, time-limited tokens.
• Credit card data is handled entirely by Stripe and never touches our servers.

No system can guarantee absolute security. We apply reasonable technical and organizational safeguards appropriate to the sensitivity of educational data, and we monitor for unauthorized access.

9. Advertising

• We do not sell student or teacher personal data.
• We do not use student data for advertising targeting or profiling.
• Free (non-authenticated) usage of the site may include standard web advertisements. These ads are not personalized based on student learning activity, responses, or scores.
• Paid teacher subscribers and their students (when accessing activities through a valid class code or LMS connection within the subscription's daily limits) receive an ad-free experience.
• Paid student license holders receive an ad-free experience.
• Signed-in members with an active subscription receive an ad-free experience.

10. Email Communications

We send email only for transactional and service-related purposes:

• Magic link sign-in — one-time login links requested by the user.
• Membership notices — subscription confirmations, renewal reminders, payment receipts, and cancellation confirmations.
• PDF result delivery — activity result PDFs sent to a teacher or student email address at the user's request.
• Parent/student invite notifications — sent when a parent invites a student or when a student accepts an invite.

We do not send marketing or promotional emails. We do not share email addresses with third parties for marketing purposes. PDF result delivery emails are rate-limited to prevent abuse.

11. Access, Correction, and Deletion Requests

Teachers, schools, parents, and authorized guardians may request:

• access to data we hold about them or their students;
• correction of inaccurate data;
• deletion of data, subject to legal retention requirements.

Requests can be submitted to [email protected]. We verify the identity and authority of the requester before processing. We aim to respond to verified requests within 30 days.

Teachers and parents with accounts can also delete their own accounts and associated data through their account settings.

12. Children's Privacy (FERPA and COPPA)

Ereading.AI is designed for educational use in school settings. We are committed to supporting school and district compliance with applicable student privacy laws, including the Family Educational Rights and Privacy Act (FERPA) and the Children's Online Privacy Protection Act (COPPA).

• We minimize data collection from students. Class code access requires no account creation, no email address, and no sign-in.
• Student accounts are created only through a parent or teacher invite flow, not through independent child registration.
• We do not knowingly collect personal information from children under 13 without verifiable parental or school consent, consistent with COPPA requirements.
• LMS-connected students are identified by LMS-issued identifiers, not by Ereading.AI accounts.
• PDF result identifiers use a randomized format that does not contain student names.
• AI grading requests do not include any student-identifying information.

Schools and districts acting as agents of parents under FERPA may consent to the collection and use of student education records in connection with the educational services we provide. If you are a school official with questions about our data practices, contact [email protected].

13. Policy Updates

We may update this policy as features, providers, and legal requirements evolve. Material changes will be reflected on this page with an updated effective date. If we make changes that materially affect how we handle student data, we will make reasonable efforts to notify affected schools and teachers.