Last updated: July 20, 2026
This article explains how JoggMini is designed to support COPPA-focused child privacy, parental control, teen independence, and classroom learning. It is a product and implementation reference for families, teachers, reviewers, and the JoggMini team. It is not legal advice. JoggMini should continue to review its policies and implementation with qualified legal counsel before public release and store submission.
Why COPPA Matters for JoggMini
The Children's Online Privacy Protection Act, known as COPPA, applies to online services, websites, and apps directed to children under 13, and to services that have actual knowledge that they collect personal information from children under 13. The Federal Trade Commission explains that covered operators must provide clear privacy notice, obtain verifiable parental consent when required, give parents rights to review and delete child information, protect the confidentiality and security of collected data, and avoid collecting more information than is reasonably necessary for the child to participate.
JoggMini is built for children and families, so child privacy is not a small legal page at the end of the product. It is part of the account architecture. The core design goal is simple: children should be able to learn, play, earn progress, and feel independent, while adults remain responsible for identity, consent, settings, deletion, and safety boundaries.
The JoggMini Privacy Model
JoggMini uses different modes for different users:
- Guest learner mode
- Parent-managed kid profiles
- Teen learner accounts
- Parent and co-parent accounts
- Teacher accounts and classrooms
These modes are separated because a young child, a teen learner, a parent, and a teacher do not need the same permissions or data access.
For under-13 learners, the preferred model is not that the child creates their own account. Instead, the parent signs in as the responsible adult and creates a kid profile. The kid profile can hold learning progress, world progress, Stars, badges, certificates, classroom activity, task results, quiz history, and settings, but the parent remains the account holder and control point. This reduces unnecessary child identity collection and keeps account-level actions with the adult.
Guest mode is local-first. A family can try JoggMini without creating a cloud account. Guest progress is stored on the device. If local app data is cleared or the guest profile is deleted, local guest progress can be removed without a cloud deletion request.
Teen accounts are separate. Eligible teens can have more independence than parent-managed children, including learning progress and quiz participation where allowed. Even then, JoggMini keeps teen data collection limited and avoids social-network-style features.
Teachers use a classroom model. A teacher can create classrooms, share classroom codes, assign classroom tasks, and view classroom-specific results. Teachers do not get unrestricted access to the child's family profile or parent dashboard.
What JoggMini Collects and Why
JoggMini follows data minimization. The product should collect only what is needed to deliver learning, progress, safety, account recovery, subscriptions, notifications, and classroom functionality.
Guest Mode Data
Guest mode may store locally on the device:
- Display name or local learner label
- Local Stars, Gems, badges, streaks, and progress
- Local quiz/practice history
- Local settings
- Local certificates or saved result files
Guest mode should not require a cloud account, child email address, phone number, address, or precise location.
Parent Account Data
Parent accounts may use adult authentication through supported providers such as Google or Apple. Parent account data may include:
- Adult account identifier
- Email address from the identity provider
- Parent display name
- Subscription status
- Co-parent relationship data
- Device notification token if notifications are enabled
Parents use this account to manage kid profiles, settings, tasks, deletion, subscriptions, and recovery.
Kid Profile Data
A parent-managed kid profile may include:
- Kid display name
- Age or age band where needed for age-appropriate learning
- Avatar or visual preference
- Learning progress
- Stars, Gems, Tiers, streaks, badges, and certificates
- World progress
- Daily Quest results
- Quiz and Arcade activity
- Parent task and classroom task results
- Parent-controlled settings such as reminders, timeouts, and quiz join permission
A parent-managed kid profile does not need a child email address.
Teacher and Classroom Data
Teacher and classroom features may store:
- Teacher account and classroom metadata
- Classroom name and classroom code
- Student/classroom membership
- Assigned classroom tasks
- Due dates and reminders
- Quiz/task results and answer reports
This data exists so teachers can run classroom learning. It should not expose unrelated parent dashboard information or unrelated child activity outside the classroom context.
Notifications
JoggMini uses notifications for Daily Quest, reminders, assigned tasks, quiz starts, and classroom updates. Notifications should be purposeful and configurable. Device notification tokens are used to deliver notifications and should be protected and removed or invalidated when no longer needed.
Notification categories should include:
- Daily Quest
- Daily reminders
- Task notifications
- Quiz notifications
- Classroom notifications
What JoggMini Does Not Do
JoggMini's child privacy posture should be clear:
- No third-party behavioral advertising to children.
- No sale of child data.
- No open chat between children.
- No public social feed.
- No precise location tracking for learning.
- No requirement that under-13 children create their own cloud identity.
- No paid scoring advantage. Subscriptions expand access and allowances, not scoring quality.
If advertising, analytics, SDK, or data-sharing behavior changes in the future, the privacy policy, consent flow, store declarations, and technical controls must be reviewed before release.
Parent Notice, Consent, and Control
COPPA emphasizes parental notice and parental control. In JoggMini, this is handled through the parent account and parent profile features.
Parents can:
- Create and manage kid profiles
- Add co-parents
- Load or remove a kid profile from a device
- Permanently delete a kid profile
- Control reminders and timeout settings
- Control whether a child can join organized quizzes
- Assign learning tasks
- View progress, quiz history, task reports, classroom activity, badges, and certificates
- Review what learning activity has been completed
The distinction between device removal and permanent deletion matters. Removing a kid profile from a device clears that device's active child profile view without deleting the child's cloud profile. Permanent delete is stronger: it removes the kid profile and associated learning data from the parent/co-parent relationship, subject to legal, security, backup, transaction, and retention limits described in the privacy and deletion policies.
Child Access Without Child Account Sprawl
Many learning apps create a separate login for every child. JoggMini avoids that for parent-managed children. The child can still have a rich learner experience: worlds, quizzes, Arcade, badges, certificates, tasks, and classroom work. Account-level responsibilities remain with the parent.
This supports privacy in two ways:
- It reduces child identity collection.
- It gives parents a practical control surface for settings, data, recovery, and deletion.
A parent-managed child should not be able to permanently delete the parent-managed profile from the learner edit-profile screen. If they tap Delete Account, the app should show a clear message such as: Ask your parent to delete your profile from the parent profile. In guest mode, deletion can remove the local guest profile from the device because the profile is not connected to a parent cloud account.
Teen Accounts
Teen accounts balance independence and privacy. Teens may be able to sign in, learn, join quizzes, and create quizzes where permitted by age and account policy. JoggMini should still limit unnecessary data collection and avoid exposing teen activity beyond the contexts the teen uses.
Teen mode should not be treated as an adult account. It is a learner account with more autonomy than a parent-managed child profile, not unlimited control over family or teacher systems.
Teacher Accounts and Classroom Boundaries
JoggMini teacher accounts are designed for classroom learning without giving teachers unnecessary family access.
A teacher can:
- Create a classroom
- Share a classroom code
- Assign classroom tasks
- Create organized quizzes
- View classroom-specific student participation
- View quiz/task results for students in the classroom
- Save or share reports where supported
- Remove a student from a classroom
- Delete classroom tasks or classrooms
A teacher should not:
- Create or own a child's private parent-managed profile
- Access unrelated family dashboard information
- Override parent deletion rights
- Access unrelated child activity outside classroom context
Parents should be able to see classroom activity for their child. This gives teachers enough classroom functionality while preserving parent oversight.
Age Gate and Role Routing
JoggMini uses an age gate and role flow to decide whether the user should continue as a child learner, teen learner, parent, or teacher. A neutral age screen is important for mixed-audience apps because the app must not nudge children into adult flows or ask for unnecessary child information.
The FTC issued a 2026 COPPA policy statement on age verification technologies. The statement recognizes that limited collection used only to determine age, with prompt deletion and safeguards, can support child protection. JoggMini's age gate should follow that principle: collect only what is needed for role routing, avoid retaining more than necessary, and clearly explain why age is requested.
Security and Retention
COPPA requires reasonable steps to protect the confidentiality, security, and integrity of child information. JoggMini's architecture should continue to apply:
- Role-based access rules
- Parent/co-parent entitlement checks
- Teacher/classroom scope checks
- Secure local storage for sensitive device-side secrets
- Provider-based adult authentication
- Deletion and local clearing flows
- Limited retention of unnecessary data
- Export handling that explains files saved outside the app may remain outside app control
Retention should be purpose-based. Data should be kept only as long as needed for learning history, safety, account support, legal obligations, transaction records, or backup integrity, as described in the privacy policy.
Google Play Families Alignment
Google Play Families policies require developers of apps for children and families to protect children, comply with applicable laws, accurately declare audience and data practices, avoid inappropriate content, and restrict problematic identifiers and advertising practices for children. JoggMini's website and Play listing should align with the actual app:
- Child-directed learning content
- No ads in the child experience
- No sale of child data
- No location-driven learning feature
- Accurate Data Safety disclosures
- Accurate target audience declaration
- Clear parent controls
- Clear deletion and account management paths
If JoggMini includes Apple sign-in buttons on Android builds, the app should handle that platform mismatch gently. A disabled or informational message such as Sign in with Apple is available on Apple devices is more appropriate than a red failure message.
Apple Kids and App Store Alignment
Apple's Kids guidance emphasizes safe, age-appropriate experiences, careful handling of personal information, age-appropriate advertising rules, and parental gates for adult actions such as purchases or external links. JoggMini's iOS build should align with these principles:
- Parent gates for adult-only actions
- Clear subscription handling
- No unnecessary child personal data collection
- No open child social features
- Age-appropriate content
- Clear privacy documentation
- Teacher and parent roles separated from child learner mode
Practical COPPA Controls in JoggMini
The most important JoggMini controls are:
- Parent-managed kid profiles for under-13 learners
- Local guest mode for account-free trial
- Co-parent controls with entitlement checks
- Teacher classroom boundaries
- No child email requirement for parent-managed profiles
- No ads or child data sale
- No open chat
- No precise location tracking
- Parent deletion and device removal options
- Task and quiz controls
- Notification category controls
- Secure provider authentication for adults and eligible teens
What Must Stay True as JoggMini Evolves
Every new feature should be checked against these questions:
- Does this collect child information?
- Is the information necessary?
- Is the parent informed?
- Does the parent have control?
- Can the data be deleted or removed where required?
- Is the teacher scope limited to classroom use?
- Does teen mode preserve privacy?
- Is the notification useful, configurable, and not manipulative?
- Are Google Play and Apple declarations still accurate?
- Does the website describe the feature honestly?
Official References
- FTC COPPA FAQ: https://www.ftc.gov/business-guidance/resources/complying-coppa-frequently-asked-questions
- FTC 2025 COPPA Rule update announcement: https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-finalizes-changes-childrens-privacy-rule-limiting-companies-ability-monetize-kids-data
- FTC 2026 age verification policy statement: https://www.ftc.gov/news-events/news/press-releases/2026/02/ftc-issues-coppa-policy-statement-incentivize-use-age-verification-technologies-protect-children
- Google Play Families Policies: https://support.google.com/googleplay/android-developer/answer/9893335
- Apple Kids developer guidance: https://developer.apple.com/kids/
Author: JoggMini Team, Mokingbird.xyz
For more info, contact support@joggmini.mokingbird.xyz