Child Safety

Child-safety commitments

Products for children get the strictest treatment we offer. Here's what we commit to — and how it maps to the law. Last updated July 2026.

A child's voice is among the most sensitive data a product can touch. When VoiceQuest powers a toy, companion, or any product used by children, these commitments apply — by design, not by policy alone.

Our commitments

How this maps to the law

COPPA

By keeping voice on the device and de-identifying cloud memory, we help device makers minimize the personal information collected from children and support verifiable parental consent, access, and deletion — the core obligations of the Children's Online Privacy Protection Act.

BIPA and biometric-privacy laws

A voiceprint is a biometric identifier under laws like Illinois' BIPA. Because raw voiceprints never leave the device, the biometric is not collected, stored, or transmitted by our cloud — reducing the biometric-privacy surface for products built on VoiceQuest.

Maryland's 2027 AI-toy rules

Maryland's requirements for AI toys take effect in January 2027. Our edge-first architecture is designed to meet them ahead of the deadline, so device makers can treat compliance as a shipped feature rather than a scramble.

For device makers

The Edge SDK ships with child-data compliance packaging — consent flows, a parent data-sovereignty panel, and the audit trail your compliance review will ask for. We join at product-definition stage so safety is built in, not bolted on. See the Data Sovereignty page for the technical detail.

Reporting a concern

If you're a parent or researcher with a child-safety concern about a product built on VoiceQuest, contact us at ops@voiceq.ai. We take these reports seriously and respond promptly.

This page describes our design commitments and is a general summary, not legal advice.