KidClimb Child Privacy Notice (for Parents)

Effective date: 2025-12-17

This notice explains how KidClimb handles child-related information in plain language.

KidClimb is parent-managed

• Parents or legal guardians create and control accounts.
• Children do not create accounts.
• KidClimb is designed for families in the United States and Canada.

What child information KidClimb may store

KidClimb stores only what a parent/guardian chooses to enter, such as:

• A child nickname or display name
• Age or birthdate (to recommend age-appropriate activities)
• Milestones, skill status, and activity logs you record
• Preferences like reminders, favorites, and focus areas

We encourage parents to avoid entering unnecessary sensitive information.

What we do NOT do

KidClimb does not:

• Show behavioral advertising to children
• Sell child data
• Allow public child profiles, friend lists, or direct messaging by default
• Collect precise location by default

How we use child information

We use child information to:

• Personalize age-appropriate activities and suggestions
• Save your tracking data across devices you control
• Provide features like activity history, milestones, and preferences

Who can access child information

Child information is accessible only to:

• The authenticated parent/guardian account that created it (and anyone you explicitly authorize, if supported)
• KidClimb service providers who process data on our behalf to operate the Service (e.g., hosting/database), under contractual obligations

Your choices and rights (parents/guardians)

You can:

• Review and update child profile details
• Export your data (where available in Settings)
• Delete a child profile and associated logs
• Delete your account to remove all associated data

See Data Deletion Policy for details.

Contact for child privacy requests

If you have questions or want help with access/export/deletion:

• Email: privacy@kidclimb.com

• Confirm COPPA-required contact details and whether a mailing address must be included.
• Confirm whether any future features (social sharing, community, messaging) would change “child-directed” considerations.
• Confirm data minimization commitments vs. actual fields stored (e.g., birthdate vs. birth month/year).
• Confirm whether a verifiable parental consent (VPC) mechanism is required given the product design and any planned marketing/target audience.