Everything you need to approve ReadingVox
Pricing, payment terms, data handling, security, and accessibility, in one place. If something your office needs isn't here, email [email protected].
Vendor details
- Legal name
- Available on request
- Doing business as
- ReadingVox
- Address
- Available on request
- State of formation
- Available on request
- Tax ID (EIN)
- Provided on our W-9
- Website
- readingvox.com
- Sales & billing
- [email protected]
- Privacy & data requests
- [email protected]
- Support
- [email protected]
Pricing
All prices are published and in US dollars. No setup fees. The Institution plan is billed yearly and covers your LMS and your public website.
| Institution tier | Enrolled students | Price per year | Fair-use cap |
|---|---|---|---|
| Small | Up to 2,500 | $750 | 5M new chars/mo |
| Medium | 2,501–10,000 | $1,500 | 10M new chars/mo |
| Large | 10,001–30,000 | $3,000 | 25M new chars/mo |
| Extra large | 30,001+ | $5,000 | 50M new chars/mo |
- 30-day pilot before you pay. Cancel before it ends and you aren't charged.
- K-12 Chrome extension: $0.50/student/year as an add-on to an Institution plan, or $1.00/student/year on its own (minimum 100 students).
- Website-only plans (not for LMS use): $19–$149/month, plus a free plan.
Supported platforms & installation
- Native in Canvas and Moodle. Canvas: a JavaScript file uploaded to your account or sub-account theme (custom JavaScript may need to be enabled by Instructure). Moodle: one line in Site administration → Appearance → Additional HTML. No LTI registration, no student accounts.
- Via Chrome extension: Schoology, D2L Brightspace, Blackboard Ultra, Google Classroom. Native integrations for these aren't available yet. Students use the ReadingVox Chrome extension, force-installed from the Google Admin console with your license key pushed by policy.
- Public websites with one script tag, or the WordPress plugin.
Payment & purchase orders
- Credit or debit card. Pay online at checkout. Card payments are processed by Stripe.
- Invoice / purchase order, net 30. Choose to pay by invoice when you start your pilot and add your PO number. We issue the invoice through Stripe when the pilot ends.
- ACH bank transfer or check. Pay a Stripe invoice by ACH or card from the invoice page. For check payment instructions, email [email protected].
- Quotes. The prices on our pricing page are our quote. If your office needs a formal quote document, email [email protected].
Data handling & FERPA
On an Institution plan, ReadingVox processes student records only as a “school official” with a legitimate educational interest under FERPA (34 CFR § 99.31(a)(1)), under the institution's direct control, and only to provide the service. We do not sell student data, use it for advertising, or build profiles of students.
What the LMS widget (Canvas, Moodle) sends us
- The text a user chooses to play, translate, or simplify.
- Standard request information: IP address, browser user agent, and the address of the page.
- Your ReadingVox key, which identifies your institution, not the student.
What it doesn't send
- Student names, email addresses, or LMS user IDs.
- Anything from grade, inbox, people, or settings pages. The widget doesn't run on those pages.
What we store
- Usage logs for billing and abuse prevention: time, page address, character counts, browser user agent, and IP address. On Institution plans, the text being read is not stored in usage logs; only a hash of each sentence is.
- Audio cache: audio and the sentence text it was made from, keyed by a hash of the text, so the same sentence is generated once and replayed. Cache entries aren't linked to any user.
- Account data for the staff who manage the subscription: name, email, billing status.
The K-12 Chrome extension works differently: it uses the student's school email or an external ID to count license seats. See the privacy policy for retention periods and how to request deletion.
We'll sign a student data privacy agreement. Send your template to [email protected].
Sub-processors
These services process data on our behalf. Providers receive only what they need for their task.
| Provider | Purpose | Data |
|---|---|---|
| DeepInfra | Speech generation (text-to-speech voices) | Text to be spoken. No user identifiers. |
| OpenAI | Translation | Text a user asks to translate. No user identifiers. |
| Together AI | Translation fallback and vocabulary simplification | Text a user asks to translate or simplify. No user identifiers. |
| Cloudflare R2 | Audio file storage | Generated audio and word timings, stored by text hash. |
| Neon (managed PostgreSQL) | Application database | Account, billing status, domains, hashed keys, usage logs, and the text cache. |
| Stripe | Payments and invoices | Billing contact and payment details of the purchasing account. We never see full card numbers. |
| Amazon Web Services (SES) | Transactional email to account holders | Account holder email address. Not used for students. |
Staff who manage the account can sign in to the dashboard with Google or GitHub. The readingvox.com website and dashboard use Google Analytics; the widget installed in your LMS does not.
Security
- Hashed keys. API keys and license keys are stored as SHA-256 hashes, never in plain text.
- Domain-locked. Your key only works from the domains you add (your LMS, test instance, website). Requests from any other site are rejected.
- Encrypted in transit. The widget, API, and dashboard are served only over HTTPS.
- No card data on our servers. Payments are handled by Stripe.
ReadingVox has not completed a SOC 2 or similar third-party audit. Our HECVAT Lite answers cover the rest of our security practices; ask for a copy below.
Accessibility
ReadingVox is a reading-support tool, so its own player and toolbar need to be accessible too. Our goal is conformance with WCAG 2.1 Level AA. We have not yet completed a formal conformance evaluation; our Accessibility Conformance Report (VPAT) is in preparation and will state honestly where we meet the standard and where we don't.
ReadingVox adds to, and doesn't replace, the screen readers and other assistive technology your students already use.
If you find an accessibility barrier, email [email protected] with the page and what happened.
Documents
- Available on request
VPAT / Accessibility Conformance Report
WCAG 2.1 AA conformance report for the ReadingVox player and toolbar.
- Available on request
HECVAT Lite
Higher Education Community Vendor Assessment Toolkit, Lite version.
- Available on request
Data Processing / Student Data Privacy Agreement
Our template, or we'll review your state or district agreement (including the NDPA).
- Available on request
W-9
For vendor setup in your purchasing system.