Kidsplorer and CIPA Evaluation Notes

Technical scope and limitations for schools and libraries evaluating Kidsplorer as one browser-level control.

This is product documentation, not legal advice or a certification of compliance. Each school or library is responsible for its internet safety policy, public process, technology protection measures, supervision, configuration, records, and program certifications.

For current E-rate guidance, consult the Universal Service Administrative Company CIPA overview and your program administrator or legal adviser.

Product and control boundary

Kidsplorer Labs is a Windows browser managed through app.kidsplorer.com. It allows navigation to domains in the active profile’s rules and blocks navigation to unapproved domains.

This control applies to navigation inside Kidsplorer. It does not:

  • filter another installed browser or application;
  • inspect or classify every image or page on an approved domain;
  • provide network-wide DNS, firewall, or content inspection;
  • prevent an administrator-level Windows user from altering the device; or
  • create the institution’s policy, public notice, hearing record, monitoring process, or program certification.

Because website content and embedded services can change, an allow-list does not guarantee that all content on an approved domain is appropriate.

Current administrative controls

ControlCurrent behavior
Approved-site rulesAdministrators add and remove domains by profile; Labs supports CSV import/export
Profile assignmentAssign profiles to devices in bulk or map profiles to imported Windows-login rosters
ScheduleConfigure allowed hours per profile
Device enrollmentGenerate bounded codes for a selected profile and device count; codes expire after 48 hours
Device inventoryView computer name, assigned profile, last seen, sync status, and application version
Activity historyRetain full URL events for up to 30 days and daily profile/domain totals for up to 120 days
Staff accessAdd organization staff with dashboard access
Application deliveryMicrosoft Store, with optional Intune assignment and Store-policy-controlled updates

Windows deployment considerations

Use standard, non-administrator accounts for end users. Configure Kidsplorer’s full-screen, browser-lock, PIN, and app-switch restrictions as appropriate. Separately restrict other browsers and applications with Windows or device-management policy and maintain suitable network protections.

Before deployment, test sign-in, accessibility, emergency access, updates, offline behavior, logging, staff permissions, and the process for approving or removing a site.

Evaluating Kidsplorer in a broader program

An institution can use these questions during evaluation:

  1. Are all public or student Windows accounts prevented from using unfiltered browsers and applications?
  2. Who reviews each approved domain, and how often is it rechecked?
  3. What network-level controls cover traffic outside Kidsplorer?
  4. How are adult access and authorized disabling handled under applicable requirements?
  5. Do the institution’s policy, public process, supervision, records, and certifications cover the actual deployment?
  6. Are the 30-day event and 120-day aggregate retention periods appropriate for the institution’s privacy and records policies?

Contact

For factual questions about current Kidsplorer behavior, email support@kidsplorer.com. For legal or program determinations, consult the responsible program administrator or qualified adviser.