Skip to main content

Trust

Children's privacy

The posture Articarry takes when a child practices through a guardian's account.

Internal beta: synthetic and explicitly-consented test data only.

Articarry is in a private beta. The text below describes how the product is engineered and how it intends to handle data. Use with real patient audio requires BAA-covered infrastructure and a legal review of this text; both are gates between this beta and any wider use.

In plain words

  • Your child’s clinician hears the recordings. They’re never sold, never shared with anyone else, and never used to train outside models.
  • The app never tells anyone how your child sounds. No grade, no score for you or your child to feel judged by. Your clinician does the listening.
  • You can delete a recording, or your whole account, any time. No reason needed. Here’s how.

A child is never a user

There is no child login on Articarry. A child has no password, no email on file, no session of their own. A child practices inside their guardian's signed-in session. The guardian is the account holder, and the guardian is the only party who interacts with us by entering credentials. The first name a clinician enters for the child is the only child-identifying string Articarry stores.

Consent comes from the guardian

Before any audio is recorded, the guardian must read and sign a consent page that names exactly what gets recorded (short voice clips during the practice activities the clinician has assigned) and what those clips are used for (the clinician's review and Articarry's own product maintenance). The consent is per enrollment, versioned, and revocable at any time. After a guardian revokes, the server refuses any new recording creation for that child: the consent gate is enforced server-side, not just in the UI.

What is collected, and why

  • The child's first name, so the guardian and clinician can tell their list of children apart. Articarry does not ask for a last name.
  • The child's date of birth, used only as an age band for the clinician's planning.
  • Short audio recordings from the practice activities the clinician has assigned. Used by the clinician to read what happened between sessions, and by Articarry itself to debug the upload + scoring path and to manually review a recording that a clinician or guardian has flagged. That is the full list. Recordings are not used to train any model that leaves Articarry's infrastructure; they are not shared with any third party; they are not resold. The consent a guardian reads at signup states this before any audio is recorded.

Articarry does not collect a child's address, school name, face data, location, or device identifiers. The practice surface uses only the device microphone, and only while the child has the recorder open.

No clinical claims

Articarry does not diagnose. Articarry does not treat. The product surfaces a record of practice: when it happened, what was practiced, what the scoring engine heard. A clinician reads that record using their own training and tools. The no-clinical-claims posture is a compile-time rule in the codebase, not a policy: a lexicon scanner blocks the words a diagnostic claim would require from every template before it can be deployed.

How a family takes it back

A guardian can remove a child or their entire account from the account page. Deletion is held for 30 days as an undo window, then permanently removed. The audit log records the deletion event; the data itself is gone.

A school district or pediatrician can request a deletion on a guardian's behalf by emailing privacy@articarry.com. We acknowledge in writing and confirm with the guardian on file before acting.

COPPA and HIPAA posture

Articarry is engineered to treat children's voice recordings as protected information regardless of whether COPPA or HIPAA applies to the specific deployment. Real-patient use under HIPAA requires a Business Associate Agreement with the hosting provider; the internal beta runs on a free-tier stack that does not sign BAAs at this tier. Moving to BAA-covered infrastructure is one of the gates between this beta and any real-patient use.

Related: the privacy page covers data collection generally; the security page covers how the data is protected.

Last updated: 2026-05-25.