Key takeaways
- Service use does not automatically authorize training
- Training datasets need provenance
- De-identification reduces but does not erase governance duties
- Opt-in status should travel with every training example
The short version
Therapy recordings are collected to deliver a service to a patient; training data is reused to improve or build a model. Those are different purposes and should have different consent, access, provenance and retention rules. The practical question is not whether the concept can be reduced to a single score or rule, but whether the information is specific enough to support the next clinical or family decision. Articu’s editorial position is to preserve context, target, language, practice level, cueing, recording quality and uncertainty, rather than present false precision.
Service use does not automatically authorize training
Service use does not automatically authorize training. In real speech practice, this distinction matters because the same surface result can come from different causes and can require different responses. A useful record therefore keeps the observation close to its context instead of converting it immediately into a diagnosis or universal recommendation.
FTC, 2025 Amendments to the Children’s Online Privacy Protection Rule is useful context here. The amended COPPA Rule strengthens requirements around children’s personal information, retention/deletion, security and consent; compliance with most amended provisions was required by April 22, 2026. The lesson is not that every product or clinic must copy one study protocol; it is that claims should stay within the population, language, task and evidence that were actually evaluated.
Training datasets need provenance
Training datasets need provenance. In real speech practice, this distinction matters because the same surface result can come from different causes and can require different responses. A useful record therefore keeps the observation close to its context instead of converting it immediately into a diagnosis or universal recommendation.
FTC, COPPA Enforcement Policy Statement on Voice Recordings is useful context here. The FTC explains that an audio file containing a child’s voice is personal information under COPPA; a narrow non-enforcement policy for brief voice-command audio has important limitations and does not turn child voice into low-risk data. The lesson is not that every product or clinic must copy one study protocol; it is that claims should stay within the population, language, task and evidence that were actually evaluated.
De-identification reduces but does not erase governance duties
De-identification reduces but does not erase governance duties. In real speech practice, this distinction matters because the same surface result can come from different causes and can require different responses. A useful record therefore keeps the observation close to its context instead of converting it immediately into a diagnosis or universal recommendation.
FTC, Amazon Alexa children’s voice data enforcement case is useful context here. The FTC’s Amazon case highlights practical consequences of indefinite retention, ineffective deletion and undisclosed secondary use of children’s voice data. The lesson is not that every product or clinic must copy one study protocol; it is that claims should stay within the population, language, task and evidence that were actually evaluated.
What this means in practice
- Define the workflow and decision owner before selecting the AI feature.
- Measure review burden, override rate and failure modes, not just adoption.
- Make source evidence and uncertainty available at the point of review.
- Write down retention, training-use, vendor-update and stop/rollback rules before the pilot expands.
What technology can help with, and where it stops
A dashboard or model can reduce clerical friction only when it is embedded in a workflow with clear ownership. Automation should not convert missing context into confident documentation, and “human in the loop” should mean the reviewer has enough time and evidence to disagree. For higher-consequence uses, local validation, monitoring and a stop path matter as much as initial vendor accuracy.
Questions to ask before acting on the output
Ask what population and task the system was validated on, what the model does when it is uncertain, which version produced the result, whether a clinician can inspect the supporting evidence, and how corrections are recorded. For any feature that can influence documentation or clinical decisions, the workflow should make disagreement easy and preserve a human-owned final decision.
The Articu perspective
Articu’s workflow goal is selective review: summarize routine practice, route uncertainty to a clinician, preserve the supporting recording where policy allows, and keep model output separate from clinician-confirmed data.
Sources and further reading
- FTC, 2025 Amendments to the Children’s Online Privacy Protection Rule
- FTC, COPPA Enforcement Policy Statement on Voice Recordings
- FTC, Amazon Alexa children’s voice data enforcement case
- NIST, AI Risk Management Framework 1.0
Editorial status: Draft prepared from current literature and authoritative guidance; clinical reviewer pending.
Educational disclaimer: This article is general educational information, not an assessment, diagnosis, or individualized treatment plan. Speech development varies by age, language, dialect, hearing, motor and developmental context. For individual concerns, consult a qualified speech-language pathologist.