Parent account information
Examples: email address, normalized email address, account status, email verification timestamp, last login timestamp, role assignments, parent feedback type, message, and submission timestamp.
Purpose: Create and manage parent-owned accounts, verify email, authenticate sessions, route parents to the correct product area, and receive parent feedback and support reports.
Authentication and security information
Examples: password hash, session cookie, verification token records, password reset token records, IP address in security events, route and session ID in security events.
Purpose: Sign users in and out, protect accounts, verify email addresses, reset passwords, rate-limit abuse, and maintain sanitized security logs.
Student profile information
Examples: student display name or nickname, grade level, selected interests, student preferences, household student list, age band and parental-consent status, version, method, and timestamp, Founding Beta code redemption and student-specific grant status.
Purpose: Create student profiles under the parent account and present Grade 7 practice in selected interest contexts.
Student learning activity
Examples: topic progress, mastery progress, practice sessions, answer submissions, first-attempt accuracy, Hint usage, section quiz attempts and scores, continued practice after mastery.
Purpose: Run practice, preserve progress, score section quizzes, show parent dashboard summaries, and improve curriculum quality.
Generated problem and report data
Examples: topic ID, variant ID, problem seed, generated problem values, expected-answer metadata stored for administrators, problem-report description, optional problem-report screenshot reference, viewport width and height, device pixel ratio, app version.
Purpose: Reproduce reported issues, correct curriculum defects, and verify that generated problems match their validators.
Payment and revenue records
Examples: Stripe customer and subscription identifiers, student profile identifier associated with a membership, subscription status and paid-through period, checkout reservation and webhook event records, payment, invoice, refund, and cancellation status.
Purpose: Create and administer parent-initiated paid Student memberships, prevent duplicate checkout, synchronize access, and maintain required billing records.
Operational logs and backups
Examples: request path, operational error metadata, provider-controlled request metadata, encrypted backup copies of application and file data.
Purpose: Operate, secure, troubleshoot, and restore the service within the configured backup window.