ReadFluent Privacy Policy

1. Why this app has its own policy

ClearStack Apps ("we", "us", "our") operates ReadFluent, an oral reading fluency timer for tutors, dyslexia specialists and speech and language therapists. The records it holds are about children, entered by the adult who measured them, so this policy is deliberately specific rather than pointing at our general one.

Short version: what you enter stays on the phone. There is no account, no sign-in, no sync and no server holding a child's readings. The app shows no advertising. The only things that leave the device are anonymous crash and usage reports sent to Google, and a backup file you choose to save or share.

2. What the app cannot do

These are properties of the build rather than promises about our intentions:

• It does not listen. RECORD_AUDIO is explicitly removed from the app's manifest, so no library can reintroduce it at merge time. ReadFluent times a reading and counts your taps. It never records a child's voice.
• No camera, and no access to your photos. CAMERA and the media-read permissions are removed the same way. There is no way to attach a photograph of a child to a record, because there is no photograph feature.
• No location. All three Android location permissions are removed. The app never asks where you are.
• No advertising. There is no advertising SDK in the app at all, so there is no advertising identifier to collect and both advertising-ID permissions are stripped from the manifest.

3. What you enter, and where it stays

All of the following is created by you and kept in a local database on your device. None of it is sent to us or to anybody else:

• Children — a display name, and optionally a date of birth, a year group note and a note of your own. Nothing else is asked for, and a display name can be initials or a code if that is how you prefer to work.
• Passages — the title, word count and any notes for the texts you use
• Readings — when the reading was taken, how long it ran, the words the child got through, the error and self-correction counts, and any note you wrote
• Error taps — the second of the reading each tap fell at, and what you later named it (a substitution, an omission, a self-correction and so on)
• Your own details — your name, role note, organisation and email if you add them, so they can appear on a session report

ReadFluent holds no benchmark, norm, percentile or grade band, so nothing it stores is a comparison between one child and another or between a child and any published table.

4. The backup file

The app can write a single backup file containing everything above so you can move to a new device or keep your own copy. That file is produced only when you ask for it, and where it goes afterwards is entirely your choice.

Treat it as a record about children, because it is one. It holds display names and every reading against them, it is not encrypted or password protected, and it should be kept wherever you already keep records about the children you work with. The app tells you the same thing on the backup screen.

5. What does leave the device

Two things, both from Google's Firebase libraries, and neither contains your records:

• Crash reports. If the app crashes, a diagnostic report is sent to Firebase Crashlytics so we can fix it. It describes what the software was doing, not what you had entered.
• Usage analytics. Anonymous, aggregated figures about how the app is used, through Firebase Analytics. We do not set a user identifier, and no child's name, reading or figure is ever sent.

Google processes both as our service provider. Their handling is covered by the Firebase privacy documentation and the Google Privacy Policy.

6. Purchases

Subscriptions and the lifetime unlock are handled by Google Play Billing. We never see or hold your payment details. Google tells the app only whether a purchase is active.

7. Children's data, and who is responsible for it

ReadFluent is a tool for a professional adult. It is not aimed at children, it is not designed to be used by a child, and nothing in it asks a child for anything.

Because the records live on your device and never reach us, you are the one who decides what is recorded about a child, who can see the device, and how long the record is kept. If you work under an employer's, school's or professional body's rules on holding information about children, those rules apply to what you put in the app in exactly the same way they apply to a paper file.

8. Deleting it

Delete a child inside the app and everything recorded about them goes with them: every reading, every tap and every note. The confirmation tells you how many readings that is before you commit to it. A single reading can be deleted on its own the same way.

A passage works differently and deliberately so. Passages are archived rather than deleted, because a reading whose text had vanished would be a hole in a record about a child. An archived passage stops being offered when you start a reading and stays attached to the readings that already name it. A passage holds a title, a word count and your own notes, and never anything about a child.

Uninstalling ReadFluent removes the whole database. Because we never held a copy, there is nothing for us to delete on your behalf and no request you need to send us.

9. Changes to this policy

If this policy changes, the date at the top of this page changes with it. Material changes will be described in the app's release notes.

10. Contact

Questions about this policy or about ReadFluent: support@clearstackapps.com.