What LearnVerity knows, what parents see, and what you choose to share.
There are three different questions: what the phone can notice, what LearnVerity stores, and who is allowed to receive a summary. They do not need to have the same answer.
The safest way to make LearnVerity more useful
The phone can do more analysis locally, turn it into a small category or count, and discard the private detail. Only that limited result should leave the phone. This is called on-device minimization, but the simple idea is: understand more on the phone; send less to adults.
What the coordinated app update supports
These features require the matching student-app and parent-portal versions. Connection and service status are shown in the dashboard.
| Signal | What it contains | Parent | Teacher |
|---|---|---|---|
| Supported AI activity observations | App name and observation time. No reliable session end or duration in the current Android collector | Yes | No |
| Device coverage | Whether required Android access and notifications are available; gap start, return, and duration | Yes | No |
| Student-shared study support | Subject area, study goal, broad guidance focus, and sharing time | Yes | No |
| Parent context and family preferences | Parent labels, saved questions, attention level, summary timing, and family agreement | Saved to family account | No |
| Learning check-in | Student-chosen subject, goal, understanding, practice, requested next step, time and sharing scope | Yes, when shared | Only reports the parent shares after the teacher accepts; email also requires both adults to opt in |
| Teacher connection request | Teacher name or email, request source, and approval status | Yes | No activity access |
A teacher can request a connection, and a parent can approve the contact. Approval sends an invitation. A teacher signs in with that verified email and accepts or declines. Parents then preview and share only student-permitted check-ins to that teacher’s limited dashboard. Optional summary emails require both parent permission and teacher opt-in.
Private conversation content
- Prompts, answers, and chat messages
- Screenshots, screen recordings, and typed text
- Keystrokes, microphone audio, photos, contacts, and precise location
- Activity from unsupported apps and websites
Study-coach working material
Assignment directions and rewritten learning prompts remain in the app screen’s working memory and clear when the app is left. This helper uses templates and keyword rules, not a local AI model. Copying a prompt puts it on the clipboard until replaced or cleared. Optional reflections stay local. Explicitly shared check-ins are stored in the family account.
Four levels keep power and privacy separate
Could the phone privately read more?
Yes. A future student-selected text or screenshot review could run OCR and a local model while LearnVerity is open, then show the student the exact learning fields proposed for sharing. Hardware support must be checked; local processing must never silently switch to the cloud.
Cloud sandbox analysis is a different option: material leaves the phone, even if deleted quickly. It would require explicit permission, a defined purpose, no raw-content logs or training use, a retention limit, and verified deletion. Neither option is enabled in this release.
We recommend purposeful study inputs over background keystrokes, listening, contacts or precise location. Those sources expose unrelated people and usually add little evidence about learning.
Google’s local AI capabilities and limits · FTC guidance on local-only information and collection
Let the app understand more locally, but make every new adult-facing category an explicit permission.
This creates a more powerful product without turning LearnVerity into surveillance. Parents can receive useful family context. Teachers get only school-relevant information. Students can see what will be shared before it is shared.