How Strive protects classroom use
Safety is a set of boundaries we can test—not a promise that nothing will ever go wrong. These are the controls in the Strive classroom beta and the limits teachers should know.
Students enter through a real class
Teachers can create an empty workspace immediately after verifying their email and attesting that they are an adult responsible for the group. That claim never reveals an existing school or student.
Strive does not verify a workspace creator's employment or school affiliation. Every new student membership requires an explicit confirmation after showing the named leader and explaining that the leader can see all class habits, including Teacher only habits.
There is no general student signup. A student account begins only from a current teacher-created class link or code. Codes can be paused or rotated, and a removed student cannot use an old code to add themselves back.
Students can leave a class themselves at any time. Leaving immediately ends access to that class and its smaller groups without deleting the student's account or habit history.
The release is available without a geographic restriction to adult class leaders 18+ and invited students 16+. This is a product boundary, not a claim of legal approval in every jurisdiction. Younger classrooms need a real institutional or parent-authorization process that Strive has not yet implemented.
Classroom boundaries
- Protected actions recheck the account's current role and active class membership. Changing browser or session data cannot promote an account.
- Teachers see students only in classes they own or actively co-teach. School administrators are limited to their own workspace.
- Cross-school reads and mutations return the same unavailable response without confirming that the target exists.
- Public signup, login, verification, joins, invitation lookup, feedback, OAuth registration, and AI use are rate-limited across the deployed application.
Habit visibility
Students choose whether a habit is Public to class, Private to peers. These settings control peer visibility; they do not hide the habit from the student's authorized class teacher. Older records marked Anonymised only are hidden from classmates.
Teacher and pastoral notes are not shown to classmates or included in the ordinary student download. They remain bounded to authorized teacher or school-administration functions.
AI is optional assistance
AI is used only for bounded suggestions during habit design. It does not grade, rank, diagnose, discipline, or make decisions about students. The ordinary habit flow works without it.
Depending on the suggestion, the request can include a habit, cue, location, identity statement, obstacle, backup plan, and cue type. Strive does not intentionally add the user's name, email, school, class, or account ID.
AI is not enabled in this deployment. Strive will identify the provider here when it is enabled.
No engagement traps
- No advertising or sale of classroom information.
- No public leaderboards, XP, streak flames, or shaming.
- No infinite scroll or autoplay designed to prolong use.
- Missed habits remain information for reflection, not a punishment.
Optional teacher connector
Teachers can choose to connect aggregate Strive classroom tools to Claude or another compatible assistant. Those tools return class patterns and habit themes without student names or email addresses, and only for classes the teacher owns or co-teaches. The teacher controls the connection and should not ask the external assistant to infer or identify individual students from aggregate results.
Reporting a problem
If something is visible to the wrong person, a class code is being abused, or an AI suggestion is concerning, stop using that feature and use the in-app Feedback or report control. It confirms delivery and keeps the report available for retry if sending fails. Include what happened and when, but do not send passwords, class codes, tokens, or unnecessary student content. See the privacy page for the contact and data-control details.