MyParental SDK
Try demo

Family safety · Enterprise integration

Parental controls that install, pair, and connect in minutes.

Ship a complete parent-and-child experience: secure device connection, remote policy updates, per-child blocking rules, and custom schedules—without rebuilding infrastructure.

Try the demoSDK for teams

Remote control parents understand

Full-device focus, surgical blocks, and time-based rules—for the apps and routines families care about.

Full or selective blocking

Enforce a strict mode or block individual services—YouTube, TikTok, social, games—using a catalog your integration maps to real DNS or app rules.

Custom schedules

Define when rules apply: homework hours, bedtime, weekends vs school nights—per child, without duplicating accounts. Parents adjust windows remotely and policies follow automatically.

Per-child policies

Each child profile carries its own allow/block list and schedule. Update one device without touching the rest of the household.

Built for operations

REST APIs for children, pairing, blocked-service sets, and schedule configuration—rate-limited pairing endpoints and clear parent scoping for production rollouts.

Three steps from zero to protected

Designed for a smooth parent flow and a minimal child-device footprint.

  1. 01

    Install

    Deploy the child experience on the device. Parents keep a separate app or portal—no complex provisioning.

  2. 02

    Pair

    The parent claims a short-lived pairing code. Your backend ties the child device to the right account securely.

  3. 03

    Connect

    Policy travels over an encrypted tunnel to DNS and network enforcement—so blocks apply wherever the child is online.

Unlimited children, independent rules

Register as many child profiles as a parent needs. Map each to its own policy so a teenager and a younger sibling are not forced into the same template.

  • One parent account, many child records
  • Different blocked services and schedules per child
  • Scale from single-family to managed deployments

See it in action

Walk through pairing, remote updates, and blocked-service changes with our reference implementation.

  • Live pairing and claim flow
  • Parent UI for managing multiple children
  • Blocked-service catalog and custom schedules wired to enforcement
Open demo

SDK and API for B2B integrators

Embed parental controls into carriers, device OEM programs, MDM suites, or family safety products. You bring distribution; we keep the control plane predictable.

  • Versioned REST API: children, pairing, blocked-service assignments, schedules
  • Server-to-server auth with API keys; parent scope via headers
  • Extend with your own analytics, billing, and support tiers
View integration outlineContact sales

Advanced parental control roadmap

Committed themes on our product and platform backlog.

  • Always on

    Planned

    Raise the bar against casual bypass: stronger OS integration, integrity signals, and policies that stay effective after reboots.

  • Content-aware filtering

    Planned

    Move beyond named services with parent-defined categories, custom lists, and safer defaults for younger ages.

  • Analytics & realtime alerts

    Planned

    Give parents timely visibility—aggregated usage, risk signals, and notifications when policies are stressed or changed.

Questions teams ask before integrating

What happens if pairing fails or expires?

Pairing codes are short-lived by design. Parents can regenerate a code from the parent app while rate limits protect your API from abuse.

What data does the platform retain?

You should document your own retention policy for end users. The API is structured around child records, parent identifiers, and blocked-service selections—minimize what you store for compliance in your jurisdiction.

Can we white-label the experience?

Yes. Tokens and semantic colors are isolated so you can reskin the reference web surfaces or embed flows entirely inside your existing apps.