Effective September 8, 2026 · Last updated September 9, 2026
ReadBridge is a planning tool for teachers. It has no student accounts and no student logins. It keeps no database and stores nothing about you or your students on any server. Everything you save stays in your own browser on your own device. Passage text is sent to Google only to generate the AI features you request, under paid API terms that prohibit Google from using it to train or improve its products. No data is ever sold, rented, or used for advertising.
ReadBridge is created and operated by Kyle Neer, an intervention specialist. Questions about this policy, or requests from a school district regarding student data, should go to privacy@readbridge.education.
ReadBridge is designed and intended for use by educators — intervention specialists, structured literacy teachers, and other instructional staff. It is not directed to children, does not offer student accounts, and does not ask any user to create a login or provide personal information.
Students may read from a teacher's screen during instruction, but students do not have their own accounts and are not asked to enter information about themselves.
Everything ReadBridge saves is written to localStorage in the browser on the device you are using. It never leaves that device and is not transmitted to us or to anyone else. Specifically:
| Stored item | What it contains | Where it lives |
|---|---|---|
| Saved texts | Passages you paste, upload, or generate, plus any comprehension questions or background primers made for them | Your browser only |
| Running records | Fluency results — words correct per minute, accuracy, miscue counts, and any label you typed to identify the reader | Your browser only |
| Display preference | Light or dark theme | Your browser only |
| Session record (only while one is running) | What happened during one lesson: the passages opened, which words the student tapped for help and which support was used, comprehension score, running-record result, and which drills were run — plus any label the teacher typed | Your browser only, and deleted when the session ends |
A session record is off by default and has to be started deliberately. Nothing about a student's activity is logged at any other time. While one is running it is kept in this browser and nowhere else; ending it produces a report you can print or download for the student's file, and the log behind that report is then deleted. Nothing accumulates, and no part of it is transmitted to us or to anyone else.
The report can name the words a student could not read. That is the point of it clinically, and it is also the most revealing thing this application can hold — so the same guidance applies as for running records: use initials or a student ID, not a full name, and treat the downloaded report as you would any other document in a student's file.
Because this data lives in the browser, it is visible to anyone who uses that same browser profile on that same device, and it is erased if you clear your browser data. It is not backed up, synced between devices, or recoverable by us.
The "student label" field on a running record is free text stored in your browser. We recommend entering initials or a student ID rather than a full name, particularly on a shared or classroom device. ReadBridge never needs a student's full name to function.
ReadBridge sends data off your device only when you actively use a feature that requires it. The relevant flows are:
| When you… | What is sent | To | Why |
|---|---|---|---|
| Use an AI tool (define a word, syllables, morphology, comprehension questions, generate or simplify a passage) | The passage text or word involved | Google Gemini API | To produce the requested result |
| Upload a PDF or photo | The file's text or image content | Google Gemini API | To extract readable text from it |
| Use Read to Me or syllable audio | The text to be spoken | Google Cloud Text-to-Speech | To generate the audio |
These requests pass through a server function that acts only as a relay so that API keys are never exposed in the browser. That relay stores nothing and writes no logs of your content.
Because uploaded files and pasted passages are transmitted to Google for processing, staff should not upload documents containing student personally identifiable information — graded work with names, IEP documents, assessment reports, or class rosters. ReadBridge is intended for instructional passages and reading material.
| Provider | Role | Data it can see |
|---|---|---|
| Google LLC (Gemini API) | AI text processing | Passage text and uploaded file content you submit |
| Google LLC (Cloud Text-to-Speech) | Read-aloud audio | Text you ask to be spoken |
| Netlify, Inc. | Website hosting and relay functions | Standard web server request metadata, including IP address |
| Cloudflare, Inc. (cdnjs) | Serves one open-source library used to read PDFs in your browser | Your IP address when the library is fetched |
ReadBridge uses Google's Gemini API on a paid tier with billing enabled. Under Google's Gemini API Additional Terms of Service, when Paid Services are used, Google does not use prompts — including system instructions, cached content, and uploaded files such as images or documents — or the responses to improve its products. Google retains such content for a limited period only for abuse detection, safety, and legal compliance.
This is a meaningful distinction: the free tier of the same API does permit Google to use content for product improvement. ReadBridge is deliberately not operated on the free tier.
We do not train any model of our own, and we do not provide your content to any other AI provider.
Under the Family Educational Rights and Privacy Act, the school or district — not the vendor — is the party accountable for education records. Where a district determines that ReadBridge processes education records, ReadBridge is willing to operate as a school official with a legitimate educational interest under 34 CFR § 99.31(a)(1), and accordingly commits that it will:
By design, ReadBridge holds no education records on any server, which substantially narrows the scope of any such arrangement.
ReadBridge is a tool for educators and does not knowingly collect personal information from children under 13. It offers no student registration, no student profiles, and no method for a student to submit personal information. We collect no information from any user that would trigger verifiable parental consent obligations under the Children's Online Privacy Protection Act.
ReadBridge administers no surveys, evaluations, or analyses of the categories protected by the Protection of Pupil Rights Amendment, and collects no information for marketing purposes.
ReadBridge is operated from Ohio and is intended to be compatible with state student data privacy statutes, including Ohio Revised Code § 3319.325 through § 3319.327 and comparable laws in other states. ReadBridge does not sell student data, does not use it for targeted advertising, and does not create a profile of any student except in furtherance of the requested instructional purpose.
ReadBridge can execute a district's standard data privacy agreement, including the Student Data Privacy Consortium's National Data Privacy Agreement (NDPA), on request.
We retain nothing, so there is nothing for us to delete. Data you have saved lives only in your browser, and you control it completely: clearing your browser's site data for this domain permanently erases every saved text and running record. Deleting an individual saved text or record inside the app removes it immediately.
A session record is shorter-lived still: it exists only between starting and ending a session, and ending one deletes it. Discarding a session deletes it without producing a report. Any report you printed or downloaded is an ordinary file on your device from that point on, outside this application and under your district's own records handling.
Content sent to Google is retained by Google for a limited period for abuse detection and legal compliance, as described in its terms, and is not used to improve its products.
The site is served exclusively over HTTPS with TLS. API credentials are held server-side and are never exposed to the browser. The application has no database to breach and no stored credentials to steal, because it holds neither.
Data stored in your browser is protected by your device's own security. On shared or classroom devices, follow your district's practice for device security and sign-out.
In the event of a security incident affecting data associated with a district's use of ReadBridge, we will notify the district's designated contact without unreasonable delay and cooperate fully with any investigation and notification obligations.
If this policy changes in a way that materially affects how data is handled, the effective date above will be updated. Districts with an executed data privacy agreement will be notified directly of any material change.
ReadBridge is operated by Kyle Neer.
Privacy, student data, and district agreements — privacy@readbridge.education
District technology or privacy officers are welcome to write directly with review questions, a data privacy agreement to execute, or a request for additional documentation.
Everything else — support, questions, and feedback — kyle@readbridge.education
Use this address for help using ReadBridge, a problem with a feature, or a suggestion about the tool. Please do not send student information to it.