Luxailux.ca

Articles · Health & Care

The toy that answers to a parent

Connected toys carry children’s voices, images, and locations to clouds by default. PlayCheck encodes the parent’s consent as the rule every crossing is checked against.

By Lucian · Lux Automations

The problem

A connected toy is not just a toy. Toys, watches, and monitors for children now carry voices, images, and locations out of the home and into apps and maker clouds, often by default, often in ways a parent never clearly agreed to and could not easily check afterwards.

The cost of getting this wrong is already on the record. In the FTC’s first connected-toys case, a maker paid a $650,000 penalty after a breach exposed records of about 6 million children, with no verifiable parental consent, and took 20 years of security audits. The failure at the centre of that case is the one this door is about: consent that could not be verified, and crossings that could not be proved. A parent’s yes was claimed. It could not be shown, line by line, and neither could what the devices had actually sent, or where.

The technology

PlayCheck gives each device an issued identity. Toys, watches, and monitors are known before they connect, by their own key, rather than trusted because they arrived through the maker’s app.

On top of that identity sits the mandate, and here the mandate has a specific author: the parent. The parent’s consent is encoded as the rule the crossings are checked against. This device may send voice to the learning app, never location to advertisers. What may cross is set by consent, not by default. Every crossing is receipted, so a maker can prove its consent story to a regulator, line by line: who crossed, under which consent, and what never crossed at all. The receipts are data-minimal by design. They name the crossing only, and our layer never holds a child’s voice, image, or location. Crossings only, never content.

What it changes

For parents, consent becomes a working rule instead of a form agreed to once and forgotten. What they allowed is what the device is checked against, and what they did not allow is not a preference buried in settings but a boundary at the door. If they later ask what a device sent, the answer exists as a record of crossings, without anyone having stored the content of their child’s data to produce it.

For makers, the change is the ability to prove the story they tell. Consent, encoded and receipted, is evidence a regulator can read, rather than an assurance offered after the fact. We sell the check, never custody, and PlayCheck’s layer touches no child’s content at any point. A child’s toy should answer to the parent’s consent, and be able to prove it. That is the whole of this door.

See it

Consent, encoded, and crossings, proven, for the devices children play with. PlayCheck — the product page · All the house articles · Lux Automations — ailux.ca