Privacy Policy

Students, parents/guardians, faculty/staff, and visitors. Roles may see different data. School or district pilots may also be covered by a separate student data agreement.

• Account data: name, email, role (student, parent, faculty), password (stored by our auth provider).
• Learner profile: age or grade band, nickname, school type, interests, learning preferences, and progress.
• Under-13 parental contact: when a learner is under 13, we ask for a parent/guardian email and hold full platform access until a parent grants consent.
• Learning activity: lesson progress, scores, badges, reflections, and (where enabled) read-aloud transcripts scored on-device or on our servers.
• Wearable / media evidence: when a program uses it, teacher-reviewed reflections or uploads — public portfolios stay off by default.
• Technical data: device/browser basics and optional analytics only when configured for the deployment.

• Provide accounts, personalize learning paths, and save progress.
• Support teachers and (with appropriate permissions) parents.
• Operate safety features such as under-13 parental consent holds.
• Improve curriculum quality using aggregated or de-identified signals where possible.
• Communicate about the account, security, or program updates.

We do not sell personal information. We do not use student data for targeted advertising.

We collect limited information from under-13 learners to run the educational service and require a parent/guardian email plus parental consent before unlocking the full student experience. Today’s verification uses a parent account and a one-time consent code. We are working toward additional verifiable parental consent methods and school-managed roster flows. We do not claim full COPPA certification until those controls, notices, and contracts are complete.

When schools or districts use LYMBQ Academy, student education records may be subject to FERPA and local policy. We intend to act as a school official / service provider under written agreements for those deployments. Until a district agreement is in place, treat school pilots as requiring separate contracting and roster controls.

We use infrastructure and tools such as Firebase (authentication and database) and may use a text-to-speech service for lesson narration. Processors only receive what is needed to provide the feature. We will maintain a current subprocessors list for school customers on request via privacy@lymbq.academy.

We keep account and progress data while the account is active. Parents, schools, or account holders may request deletion or export by contacting privacy@lymbq.academy. We are adding in-product deletion and export tools; until then, requests are handled manually.

We use industry-standard authentication and access controls (including Firestore security rules). No method of transmission or storage is 100% secure; report concerns to privacy@lymbq.academy.

• Parents may grant or later ask us to revoke under-13 consent.
• Faculty review wearable evidence before it can become portfolio-ready.
• Contact us to correct inaccurate profile data or close an account.

We may update this policy as the product and legal requirements evolve. Material changes will update the effective date above and, where required, additional notice.

Privacy questions: privacy@lymbq.academy