Privacy posture for guided pilots.

This page describes the intended operating posture for LearnerLoop design-partner conversations and early pilots. Final customer terms, subprocessors, and compliance controls should be reviewed before using real student data at scale.

Current status

LearnerLoop is currently a guided MVP and design-partner pilot environment. We do not represent the product as fully enterprise-compliant or broadly production-ready for unsupervised student rollout.

Data minimization

Early pilots should start with sample cases, anonymized student states, or limited real student records only after written pilot permissions are agreed.

Student and parent visibility

The default product posture is parent-safe progress: completion, trends, upcoming milestones, missed-work context, and suggested parent action. Private student reflections and raw AI chats are not intended to be parent-visible by default.

AI use

AI can support explanations, tutoring, summarization, and adaptation suggestions. Deterministic application logic should control permissions, module access, task completion, scoring, and escalation thresholds.

Deletion and export

Pilot agreements should define retention, deletion, export, and data-review expectations before any real student accounts are created.

Contact

For privacy, data-use, or pilot-boundary questions, contact hello@getlearnerloop.com.