LiteracyLens stores every walkthrough, teacher record, and score on the device. There's no cloud database to breach, no student data to leak, and no automatic sync running in the background — because there's nothing built to send data off-device in the first place.
Not a simplified summary — this is the actual data flow.
Stored here. Only here. Encrypted at rest with AES-256.
The only door out of the device — and you choose what goes through it.
Separately: signing in to activate your license passes through Firebase Authentication — that connection verifies who you are and nothing else. It never carries a walkthrough, a teacher's name, a score, or any school data. See the Privacy Policy and subprocessor list for the full technical detail.
This isn't a policy promise layered on top of a cloud product — it's how the app is built.
Walkthroughs, teacher rosters, scores, and coaching notes are written to on-device storage, encrypted with AES-256. There's no background sync writing your school's data to a server you've never seen.
Activating your license authenticates through Firebase (Google, Apple, or email). That's account verification, not data storage — no observation ever rides along with it.
Data leaves the device exactly once: when you tap Export and choose a file. Nothing uploads automatically, on a schedule, or in the background.
The app doesn't merely tolerate a dead zone — it's built around one. A small banner confirms offline mode; nothing blocks, spins, or queues waiting for a connection.
Most walkthrough and evaluation platforms sync every observation to a shared cloud database by default. LiteracyLens was built the other way around.
| Your school's observation data… | Typical cloud tool | ✓ LiteracyLens |
|---|---|---|
| Stays on the device, not a shared cloud database | ✕ | ✓ |
| Is fully usable with zero internet connection | ✕ | ✓ |
| Leaves the device only when you deliberately export it | ✕ | ✓ |
| Adds no new vendor data-flow to your security review | ✕ | ✓ |
| Has no subprocessor list covering observation data | ✕ | ✓ |
| Requires no teacher or student accounts | ✕ | ✓ |
| Works the same in a windowless gym as in the office | ✕ | ✓ |
"Typical cloud tool" reflects the common architecture of sync-by-default SaaS walkthrough and evaluation platforms — an observer account, a live connection, and a subprocessor list that includes your observation data. Not every vendor is identical; these are worth asking any vendor directly, including us — see our own subprocessor list.
One decision — keep the data on the device — pays off differently depending on your seat at the table.
Walk into a supply closet, a portable classroom, or a gym with no signal, and know your observation is safe the moment you tap Save — not the moment it happens to sync. No "did that upload?" anxiety between visits.
Nothing to whitelist, no new cloud data-flow to threat-model, and no observation data added to a vendor's breach surface — because there isn't one. Sign-in is the only thing that touches a server, and it carries no school data.
FERPA's school-official framework and a signed DPA still apply — request one at sorvia.io/dpa — but the review is shorter because there's less ongoing data transmission to govern in the first place.
You export it. Every CSV, PDF, and Word file LiteracyLens can produce — column by column, section by section — is documented in the Data Export Spec Sheet, built for the IT and data teams who need to know exactly what's inside before they approve it.
See the Data Export Spec Sheet →There's a lightweight sign-in (Google, Apple, or email through Firebase Authentication) to activate your school's license. That connection verifies who you are — it never carries a walkthrough, a teacher's name, a score, or any school data. See the full breakdown in the Privacy Policy.
All observation data, teacher records, and school settings are encrypted on the device with AES-256. An administrator can revoke that device's sign-in credentials through Apple, Google, or email, cutting off further access to the license — see Offline use and device storage.
Yes. A signed DPA, current subprocessor list, and one-page security overview are available for any school or district purchase — request the packet at sorvia.io/dpa. The on-device architecture makes that review shorter, not unnecessary.
You export it — CSV, PDF, or an editable Word summary, whichever sections you choose, whenever you choose. Nothing leaves the device until you deliberately tap Export. Full column-by-column detail is in the Data Export Spec Sheet.
No — this page describes the product's architecture, not a certification. For the legal commitments (FERPA, COPPA, state student-privacy laws) and the signed paperwork your district needs, see the Privacy Policy and DPA & Procurement page.
3 walkthroughs free. Building License from $599/year unlocks unlimited observations.