Privacy Policy

This policy applies to:

• Visitors to the KinderPath website
• KinderPath family users (parents and guardians)
• KinderPath Pro educators and teachers
• School Administrators
• Participating schools, centers, and early learning programs
• Student information stored through authorized use of KinderPath Pro

Children do not hold KinderPath accounts.

Every account is created and managed by an adult. Children do not sign in, create accounts, or submit information directly. Information about a child is entered by a parent, guardian, or authorized educator.

Account Information

Name, email address, account role, authentication information, and subscription status.

Family and Child Information

Where supplied by a parent or guardian:

• Child name
• Age or date of birth, where collected
• Learning path information
• Assessment responses
• Skill progress
• Other parent-entered information

KinderPath Pro Student Information

Where entered by authorized educators or schools:

• Student name
• Birth month and year, where collected (KinderPath does not hold the day)
• Student identification number assigned by the school
• School and classroom enrollment
• Assessment results and proficiency information
• Teacher observations and notes
• Student evidence, reports, and portfolio items, including photographs and audio recordings uploaded by educators

School and Staff Information

• School name and school ID
• School address and phone number
• Teacher and administrator names
• Staff email addresses
• Classroom assignments
• Subscription and licensing information

Technical Information

• Device and browser information
• Log data
• Authentication and session information
• Error and diagnostic information
• Security events

Cookies and Browser Storage

KinderPath does not use advertising, tracking, or outside analytics services, and it does not set any cookies of its own. Our pages load no scripts, fonts, or other files from advertising or analytics providers. To see how often our public pages are read, we keep our own count on our own servers: for each public page and each day, how many times it was opened, the domain name of the website the visitor came from, and a short reference code if the link they followed had one. The count holds no IP address, browser or device details, cookie, or other identifier, it is not used inside the signed-in app, and counts older than 24 months are deleted automatically. If you start a free trial after following a link with a reference code, we also add one to a count of free trials for that code. That count holds only the day, the code, and a number; it is not linked to you, your school, or your account, and counts older than 24 months are deleted automatically.

Your browser stores a few small items so that KinderPath works. They stay on your device and are not used to track you:

• Staying signed in. After you sign in, your browser keeps a sign-in token so you do not have to sign in again on every page. It is removed when you sign out.
• Where you were going. While you sign in or accept an invitation, your browser briefly keeps the page you were heading to, the invitation code, or the fact that you chose to start a free trial. These are removed once the step is finished or the tab is closed.
• A link’s reference code. If you follow a link that carries a short reference code, your browser keeps that code, and nothing else about the link, for up to seven days so that, if you start a free trial, we can count which link it came from. It is removed when the trial starts and is never saved to your account. A code you do not use expires after seven days.
• A special pricing link. If you follow a special pricing link, your browser remembers that offer for up to 30 days so it applies when you sign up. It is removed once your school account is created.
• Your choices. Your browser remembers which school you have open, whether the side menu is collapsed, and whether animations are on. In KinderPath for families it also remembers which child you have selected, the day a reminder was last shown, and, if you stop partway through a readiness check, your saved answers until you finish it. Saved answers are labeled with the child’s internal ID, not the child’s name.
• Scroll position. Your browser remembers how far down a page you were, for the open tab only.

When you open a payment screen (choosing a plan or entering payment details), our payment provider, Stripe, loads its own code and sets its own cookies to prevent fraud. Those cookies belong to Stripe and are covered by Stripe’s privacy policy. Stripe is not loaded anywhere else on our site.

You can clear this stored information at any time in your browser’s settings. If you do, you will be signed out and your saved choices will reset. Links to other websites (for example, to schedule a demo) leave KinderPath, and we tell you before you go; those sites have their own policies. When KinderPath reports a software error, the report goes to KinderPath’s own server, with names, email addresses, and identifiers removed before it is sent.

Payment Information

Payment processing is handled by Stripe. Card details are submitted directly to Stripe. KinderPath does not store complete payment card numbers. We retain limited billing information such as subscription status, plan, and transaction references.

We use information to:

• Provide and operate KinderPath and KinderPath Pro
• Support assessments, instructional profiles, and planning
• Generate reports and maintain portfolios and student evidence
• Personalize learning experiences where applicable
• Manage accounts, schools, and subscriptions
• Provide customer support
• Protect the security and integrity of the platform
• Improve reliability, usability, and functionality
• Send transactional communications about accounts, billing, and security

We do not:

• Sell, rent, or trade student information
• Use student information for third-party or targeted advertising
• Build profiles of children for any purpose other than the educational purposes a school or family has authorized
• Use student information to train artificial intelligence models

KinderPath Pro is used by authorized educators, schools, centers, and administrators. Student information is entered by those authorized users as part of their instructional work.

Schools own their student records.

KinderPath does not claim ownership of student educational records and does not use them for any purpose beyond providing the service to the school.

Where a school or program is subject to the Family Educational Rights and Privacy Act (FERPA) — generally public school districts and publicly funded Pre-K programs — KinderPath acts as a school official with a legitimate educational interest, under the direct control of the school with respect to the use and maintenance of education records. We use those records only for the purposes the school has authorized, and we do not disclose them to anyone else except as described in this policy or as required by law.

Many private preschools and childcare centers are not subject to FERPA. Where that is the case, the same protections in this policy apply: the school directs how its student information is used, KinderPath processes it only to provide the service, and the school remains the owner of its records.

For schools using KinderPath Pro, the school provides any parental notice and consent required under the Children’s Online Privacy Protection Act (COPPA), acting as agent of the parent to the extent permitted. KinderPath collects student information only at the school’s direction and for the school’s benefit.

For KinderPath family accounts, the parent or guardian provides information about their own child directly.

Schools and programs remain responsible for determining and meeting their own obligations regarding student records under applicable law.

Some KinderPath Pro features use a third-party artificial intelligence service to help draft narrative summaries of a child’s development, suggest instructional groupings, and recommend teaching resources.

Before any text is sent to the AI service, KinderPath removes the names of children and staff on record at the school. Teachers are asked not to include other personal names in notes. Photographs and audio are never sent.

Where a narrative would refer to a child by name, KinderPath sends a placeholder instead, and replaces it with the child’s first name only after the text comes back — inside KinderPath’s own systems. The name you see in a report is inserted by KinderPath, not by the AI service. This is not a setting that can be turned off.

What Else Is Removed

Before any content is submitted, KinderPath also removes school and classroom names, dates of birth, student identification numbers, internal record identifiers, contact information, and the names of any other children mentioned. What remains is developmental and instructional content: skill and domain names, proficiency levels, assessment dates and counts, progress trends, and filtered teacher observations.

Photographs and Audio Are Never Sent

Media uploaded to the Services is never transmitted to the AI service. This is enforced by a technical control within the platform.

Training and Retention

The AI provider is contractually prohibited from using content submitted by KinderPath to train or improve its models. Content submitted is deleted by the provider within 30 days, except content the provider identifies as violating its usage policy and content it is required by law to keep, which it may keep longer under its published terms; the provider has access to submitted content only for safety, security, and legal-compliance purposes. KinderPath does not use student information to train any model.

Human Judgment

AI-generated text is a drafting aid. Educators must review and may edit any generated summary before approving or sharing it. KinderPath does not make automated determinations about a child’s placement, grouping, eligibility, or evaluation. Every instructional decision remains the educator’s.

A Limitation We Want to Be Clear About

Filtering of teacher-written text relies on automated pattern matching. If an educator types a name the filter does not recognize — a sibling, for example, or a child at another school — it may not be removed. We tell educators this at the point they write observations.

We share information with the service providers necessary to operate the platform. Each holds a data processing agreement with KinderPath:

Each provider is permitted to process information only as necessary to deliver its service to KinderPath. These providers engage their own subprocessors in support of their services; KinderPath subscribes to change notifications from each.

We may also share information where required by law, to protect the safety or rights of users, or in connection with a business transfer. If KinderPath is ever acquired or merged, student information remains subject to protections at least as strong as those in this policy.

KinderPath does not sell student educational information.

KinderPath stores student records, staff information, and uploaded evidence files in the US East region of the United States.

• Teachers can access only the students and classrooms they are assigned to.
• School Administrators can access information for their authorized school only.
• Parents and guardians can access their own child's information.
• KinderPath platform administration may access information only when necessary for support, security, or system administration.

Administrative actions affecting student information — including deletions, account recovery, and administrative overrides — are recorded in an audit log that school administrators can read for their own school but cannot change.

If you believe someone has access they should not have, contact security@mykinderpath.com.

While Your Account Is Active

We retain information for as long as the account or school relationship remains active.

After a School Agreement Ends

When a school’s subscription ends, access to its records is paused but nothing is deleted. The school’s records are preserved, the school can export all of them from School Settings, and starting a subscription again restores everything as it was. Records are deleted only through our reviewed closure process, described under Dormant Accounts below, or when the school asks us to delete them. Lapse or non-payment alone never deletes records.

A closure begins with a full export and a retrieval period before anything is deleted. The retrieval period is 90 days by default, and it is never set shorter than 30 days when the closure is approved. A school may ask in writing for the period to end earlier, once it has exported its data or waived the export in writing. KinderPath records the school’s written instruction, and if KinderPath approves the request, the period ends no sooner than 72 hours after approval. Shortening the period deletes nothing by itself: deletion follows only when the shortened period ends.

Dormant Accounts

Dormancy applies only to accounts that are not paying. A school with an active paid subscription is never treated as dormant, however much or little it uses KinderPath.

A school on a complimentary plan is not treated as dormant while the complimentary period lasts. When it ends, the school’s account is treated like any other lapsed account.

Where a school’s subscription has lapsed, been canceled, or expired without conversion, and there has been no activity by the school’s own staff for six consecutive months, we flag the account for closure and notify the school’s Primary Administrator. We send further notice at seven and eight months. The account becomes eligible for closure at nine months from the last recorded activity.

Eligibility does not delete anything automatically. Closure proceeds only through our reviewed process, which includes producing a full export of the school’s data before anything is deleted. If we cannot reach the school, the account is held and nothing is deleted until we have been able to give notice.

Activity in the account, or a resumed subscription, clears the flag and resets the period entirely.

Family Accounts

Family accounts follow the same principle: information is retained while the account is active and deleted on request.

Getting Your Data Back

A school may request a full export of its data at any time, at no charge. The export includes students, enrollment history, assessments and skill checks, teacher notes, portfolio items and reflections, report data, classroom and group structure, the staff roster, and all evidence files in their original form, with a manifest describing them. It is delivered as a downloadable archive through a link that expires after 24 hours.

Families may request their own data in the same way.

Deleting Your Data

You may request deletion through privacy@mykinderpath.com or through account controls in the product. Before anything is deleted, KinderPath verifies the requester and their authority to make the request.

Deletion of a student record is performed through a reviewed process. Before anything is deleted, an inventory of what will be removed is shown, the person carrying it out confirms the child by typing their full name and entering a fresh code from their own authenticator, and the request can be withdrawn at any time before it starts running. The request is raised by the school’s Primary Administrator; where the school has another active administrator, a different administrator approves and carries it out, and where the school has only one, that administrator does, and KinderPath is notified. Every record is then deleted, evidence files are removed and the storage verified empty, and a set of checks must pass before the deletion is recorded as complete. On completion, KinderPath issues a certificate of deletion and emails the Primary School Administrator who requested it the certificate in full, with a link to download it as a PDF. The email and the certificate name the record by its ID only, never the child: they state what was deleted as counts of records, may identify another child’s record by its ID where a file was kept because that child’s records still refer to it, and contain no name, date of birth, written reason or educational content. The certificate stays available to the school’s administrators in KinderPath Pro.

Deletion of a school account follows the same reviewed process across the whole school, and cannot proceed until the school’s data has been exported or the school has recorded a written instruction waiving the export. It begins with the retrieval period described under Data Retention above. On completion, KinderPath issues a certificate of deletion to the school’s Primary Administrator recording what was deleted, what was retained, and why.

What Is Retained After Deletion

Some records survive deletion because we are required or permitted to keep them:

• Audit log entries
• Billing, financial, and tax records
• Signed agreements and authority affirmations
• Deletion requests and their approvals
• A record that a deletion occurred, from which the child's name, date of birth, and all other identifying details have been removed

Where an evidence file is referenced by more than one child’s records, deleting one child retains the file while another child’s records still reference it. This is recorded and stated on the deletion certificate.

Backups

Copies may persist in backup and disaster recovery systems administered by our infrastructure provider for up to seven days after deletion from active systems. KinderPath does not administer those backups. No copy is restored except as part of a system-wide recovery event, and any copy so restored is deleted again promptly.

KinderPath holds a student’s birth month and year only, not the day. Before that change, student dates of birth were stored with the day. The day was removed from our live records when the change took effect, but backup copies made before then keep the exact date until they expire, on the same schedule described above, and a data export a school downloaded earlier still contains it. We do not edit individual records inside a backup.

Contact privacy@mykinderpath.com with:

• Privacy questions
• Requests to access information we hold
• Requests to correct information
• Requests to delete information
• Any other data-related concern

We respond within 30 days, and sooner where the law requires it.

Student records managed by a school. If your child’s records are held by a school through KinderPath Pro, the school is the custodian of those records. Parents and guardians hold rights of access and correction to their child’s education records, and those rights are exercised through the school rather than directly with KinderPath. We will refer your request to the school and assist them in responding. This is a legal requirement, not a way of avoiding the question — the school controls the record and must authorize changes to it.

Georgia. Where a school is located in Georgia, a parent or guardian may also file a complaint with the Georgia State Board of Education concerning the handling of student data.

State privacy rights. Depending on where you live, you may have additional rights, including the right to know what personal information is collected, to request correction or deletion, to obtain a portable copy, and to be free from discrimination for exercising those rights. KinderPath does not sell personal information or share it for cross-context behavioral advertising, so there is nothing to opt out of in that respect. To exercise any right, contact us at the address above.

KinderPath maintains administrative, technical, and physical safeguards appropriate to the sensitivity of the information we hold. These include:

• Multi-factor authentication, required for all KinderPath administrative accounts and all School Administrator accounts. We use authenticator apps only; SMS codes are not accepted. Multi-factor authentication is available to every user, and a school may require it of its own staff.
• Encryption. All traffic between your browser and KinderPath is encrypted using HTTPS/TLS. Stored data, including backups, is encrypted at rest using AES-256.
• Role-based access control, restricting every user to the students, classrooms, and schools they are authorized for, enforced at the database level rather than only in the interface.
• Audit logging of administrative actions affecting student information, in records that school administrators can read for their own school but cannot change.
• Personnel controls. Everyone with access to student information signs a written confidentiality agreement and completes privacy and security training before access is granted, and annually thereafter.
• Account recovery that does not depend on KinderPath: a school’s Primary Administrator can restore access for their own staff, subject to identity verification, a documented reason, and notification to the affected person.
• A written incident response procedure. Where a security incident affects a school’s information, we notify the school without undue delay. Where a school is located in Georgia, we notify within 24 hours as required by Georgia law.

No online service can guarantee absolute security. To report a security concern or suspected vulnerability, contact security@mykinderpath.com. We welcome good-faith reports and will not pursue action against researchers who report responsibly.

KinderPath products are designed for adults — parents, guardians, educators, and administrators — working with children ages 3 to 5.

Children do not create accounts, do not sign in, and do not submit information to KinderPath. Every piece of information about a child is entered by an adult acting in an authorized capacity.

We recognize that children this age cannot consent to how their information is handled and cannot recognize when it has been misused. The protections in this policy exist because of that.

We may update this policy at our discretion. When we do, we will revise the “Last Updated” date above. Where a change is significant, we will notify account holders directly and, for schools, give notice before the change takes effect.

How we send notices. We send notices about your account, this policy, and your subscription to the administrator email address on file for the account. Please keep that address current.

Governing law, liability, and indemnification. Governing law (the State of Georgia), limitation of liability, and indemnification are set out in our Terms of Service, which apply together with this policy. We do not restate them here.

Privacy questions and requests: privacy@mykinderpath.com

Security concerns: security@mykinderpath.com

General questions: hello@mykinderpath.com