Skip to main content
For IT, data privacy and procurement

What you would need to say yes

The consent model, the controls enforced on the server, the gaps we name ourselves, and a way of buying that works the way districts buy.

What you are being asked to approve

A clinician wants it

A speech therapist has asked for an AAC app that is free for students, with a clinical layer licensed per clinician.

It handles student data

Communication data from students with disabilities, which is exactly the data your review exists for.

Vendors overclaim

You have been told “yes, we do that” before, and found out otherwise in month two.

How it works

Real screens from our demonstration district. The students are invented; nothing else is.

  1. Families approve first

    A clinician cannot see a student’s data until the family approves the connection. That is how the product works, not a setting.

    Adding a student by pairing code, with caregiver approval required.
  2. Access is logged, including ours

    The district can switch on a log of every access to a student’s record. When our support staff open a record to help you, it appears there as EnrichPoint.

  3. AI, precisely

    AI-generated summaries of student data are off until your organization turns them on, and that is enforced on the server, not just hidden in the interface. The switch covers summaries. Clinicians can use AI to draw pictures for vocabulary and draft lesson activities from text they type, not from student data, and review both before anything reaches a device. Progress reports are assembled from confirmed data by templates.

  4. Export, and deletion with a preview

    The district can export its records, optionally including clinical notes. Before anything is deleted, it shows exactly what would go.

  5. Buying the way districts buy

    Per clinician seat, per year, by quote, never per student. Purchase order, an invoice carrying your PO number, net-30, cheque or ACH, and terms aligned to your fiscal year. Nothing renews automatically, and a late payment is a phone call, not a suspension.

How we handle a review

The gaps are in the product

The organization settings list capabilities that are not built yet, such as Medicaid logging and roster sync, rather than leaving you to discover them.

Documents your counsel can mark up

We send agreements as Word files, and we can work from your state’s template.

The student never pays

The student’s app is free, permanently, and a billing event never removes anything from a student’s device.

What we do not have yet

Better you hear it here than halfway through a term.

  • We do not hold SOC 2. We will complete your security questionnaire in full.
  • Sign-in is by Google or Apple. Microsoft sign-in is not yet confirmed end to end, and there is no SAML single sign-on.
  • Rosters come in by CSV or a OneRoster file. There is no automatic Clever or ClassLink sync.
  • The epSpeak app has not had an accessibility audit. The website has a dated audit that names its own gaps.

Questions

Which documents can you send?

A data processing agreement and a W-9 are ready to send, and the MSA is ready for your review. We complete security questionnaires, and we can work from your state’s data privacy agreement template. Insurance is arranged at the limits your district requires, before signature.

Where is data stored, and who processes it?

Ask for the data inventory and subprocessor list, which set out what is held, where, and by whom. We would rather send you the document than summarise it here.

What happens to our data if we leave?

You can export it at any time, and deletion shows you exactly what will be removed first. The data processing agreement covers return and deletion.

Can we pilot before buying?

Yes. A pilot is a quote option, or a clinician can start a free week on demonstration data before any real student data is involved.

Tell us what you review first

Say which documents you need, in the order your review uses them, and we will send them as Word files your counsel can mark up.