A direct, parent-facing explanation of how OpenSpeak treats a child's information ... what we collect, what we don't, the rights you have, and how to exercise them. Required by the U.S. Children's Online Privacy Protection Act (COPPA) and matched by our own commitment.
Effective Date: May 22, 2026 · Version 1.0
Dear parent or caregiver,
This page is for you. It's the plain-language explanation of what happens with your child's information when they use OpenSpeak. The most important thing to know: OpenSpeak is built to be used by the adult who supports the child, not by the child alone. The adult creates the profile, sets the PIN, and controls all settings. The child taps symbols to communicate.
OpenSpeak runs almost entirely on the device. The sentence builder, grammar engine, text-to-speech, learner profile, and progress tracking all work without an internet connection. Symbol images are fetched once from the public ARASAAC library (arasaac.org) and then cached on the device ... so after a symbol has been displayed once, it is available offline. The only optional feature that requires an active internet connection is cloud backup, which only activates if the adult signs in. There are no ads, no behavioral tracking, and no data sale.
We collect the minimum information needed for the app to work. Most data stays on the device. Nothing leaves the device unless you (the adult) sign in for cloud backup. There are no ads. There is no behavioral tracking. There is no data sale.
If anything in this notice is unclear, write to privacy@openspeakaac.org and a human will respond.
This notice supplements our main Privacy Policy and is directed to:
We never use a child's information for advertising, profiling, behavioral targeting, sale to third parties, or any purpose unrelated to delivering the app's core communication features.
The only third parties that ever touch a child's information are infrastructure providers that we need to deliver the app, and only to the extent strictly necessary:
We do not disclose a child's data to marketers, advertisers, data brokers, or social platforms.
Under COPPA (U.S.), GDPR Article 8 (EU/UK), and the parallel statutes in many jurisdictions, you have the right to:
We respond to verified COPPA / parental requests within 10 business days, and to other privacy requests within the timeframes specified in our main Privacy Policy.
To protect children, we verify that requests are coming from the actual parent or guardian. We may ask you to:
If we cannot reasonably verify your relationship to the child, we may decline to act on the request. We will tell you why and what additional information would let us proceed.
Today, OpenSpeak operates on the premise that the adult installing the app is the parent or authorized caregiver of the child for whom the profile is being created. By creating a child profile or enabling cloud sync, the adult attests that they have authority to consent on the child's behalf.
If, in the future, we add features that under COPPA would require verifiable parental consent (e.g., enabling child-initiated cloud sharing), we will implement an FTC-approved verifiable parental consent mechanism such as:
We will notify parents in advance and obtain consent before implementing any such feature.
When OpenSpeak is deployed in a school district, classroom, or clinical practice by an educator, IT administrator, or speech-language pathologist, the institution may, consistent with FTC COPPA guidance, provide consent on behalf of parents for educational purposes only. The institution is responsible for:
Schools and clinics seeking a Student Data Privacy Agreement (SDPA) or Data Processing Addendum (DPA) can email privacy@openspeakaac.org.
Most of it stays on the device. Cloud-synced data is stored on Supabase servers in the United States. If you are outside the U.S., your child's data may be transferred to and processed in the U.S. We use Standard Contractual Clauses and equivalent safeguards for transfers from the EEA, UK, and Switzerland. See our main Privacy Policy for details.
If we materially change our practices around children's information, we will:
For privacy questions, requests, or concerns about a child's information:
Email: privacy@openspeakaac.org
Subject line: "Children's Privacy Request" (helps us route quickly)
Response window: 10 business days for verified COPPA requests.
If you believe we have collected a child's information without proper consent, please write to us right away and we will investigate and remove the information.
Notice for legal counsel reviewing this draft. Items to confirm: (1) the FTC's preferred phrasing of the Direct Notice to Parents under 16 C.F.R. ยง 312.4(c), (2) whether to enroll in an FTC-approved Safe Harbor program (iKeepSafe, kidSAFE Seal, or PRIVO) and the implications for ongoing certification, (3) the verifiable parental consent mechanism we will use when we expand collection, (4) any additional disclosures required if educators in California or Illinois (CIPA / SOPPA) deploy the app at scale, (5) FERPA-DPA template for school districts, and (6) GDPR Article 8 age-of-consent variability across EU member states.