Architecture at a glance
The current app deliberately avoids a server-side learner system.
Browser application
Lessons, games, teacher previews, and rewards run in the learner’s browser.
Device-local state
Nickname, grade, preferences, completion, stars, and rewards use browser local storage.
Delivery and protection
Cloudflare serves and protects HTTPS requests and may process standard request and threat metadata.
Current controls
- HTTPS delivery on the public domain
- No configured learner database, D1 store, or R2 object store
- No ad network, analytics SDK, public profile, or child messaging
- No student roster, SSO, SIS, LMS, or grade exchange
- Separate device-only profiles for shared-device homework
- A “Done for now” handoff clears the current tab's learner selection
- Microphone permission is user-controlled and optional
- Audio is not recorded or stored by Lingo Lantern
- Teacher-preview observations remain in the current page session
- Users can remove local profiles and clear browser data
Data flow
| Flow | Data | Destination | Purpose |
|---|---|---|---|
| Site request | IP address, URL, time, browser/device and security signals | Cloudflare delivery/security infrastructure | Deliver and protect the site |
| Learner profiles | Nickname, grade, settings, progress, rewards, and current tab selection | Local browser and session storage only | Keep each shared-device learner's practice separate and resume it later |
| Speech attempt | Temporary microphone audio and recognized text | Browser or device speech service | Optional pronunciation interaction |
| Teacher observation | Anonymous rating choices and aggregate counts | Current page memory only | Support a session-only pilot rubric |
Known limits and required review
- No SOC 2 report, third-party penetration test, public bug-bounty program, or independent security certification is currently claimed.
- No enterprise identity, role-based access, audit-log, rostering, data export, or remote deletion function is active because the current release has no cloud learner accounts.
- Infrastructure log retention and browser/device speech processing must be reviewed against district requirements and contract terms.
- Any future cloud account, roster, analytics, AI, or integration feature requires a new data map, privacy review, security review, and district authorization before use.
Incident and vulnerability route
Report a suspected vulnerability, privacy concern, incorrect content, or security incident to info@saltmarkdesign.com. Do not include student-identifying information. SaltMark Design will triage the report, preserve relevant evidence, contain verified issues, correct product defects, and coordinate notices required by law or an applicable district agreement. Pilot educators should pause student use while a material privacy or security concern is unresolved.