This page is a transparent preview of the planned process. It is not consent, and it does not enroll a student. Invitations will begin only after the safety, permission, and review steps are complete.
1. Planned participants
The first beta is planned for a small number of invited Alabama students ages 15–17. Participation will require parent or legal guardian permission and the student's own affirmative agreement.
Students under 13 are not eligible. A student should not participate if the activities conflict with school, family, or device rules.
2. What a tester may do
- Complete a short orientation and device check.
- Try bounded sessions using clue training, trigger training, solving, confidence checks, Mistake Replay, and PulseCheck.
- Describe what was confusing, useful, frustrating, or motivating.
- Optionally complete a pre-check and post-check if the activity is covered by an approved research protocol.
The final invitation will state the exact number of sessions and expected time before anyone agrees.
3. Voluntary participation
Testing is optional. It will not affect grades, team status, access to school opportunities, or a relationship with the project creator. A student may skip a question, take a break, or stop at any time without punishment.
MethodLens will not use punitive streaks, artificial urgency, public rankings, or shame-based notifications to pressure continued use.
4. Privacy during preparation
The public preview keeps guest learning work in the browser. Signed-in accounts also save profiles, learning cases, events and Workpad drafts in MethodLens account storage. Optional product-feedback reports are submitted separately. The Privacy Policy explains these distinctions. None of these actions silently enrolls a learner in research.
Before a data-backed beta begins, testers and parents will receive a specific list of data fields, who can see them, how long they are kept, how they are protected, and how to request deletion or withdrawal where applicable.
5. Private materials and idea protection
Invited testers may be asked not to share private access links, source code, unreleased exercises, internal study materials, or screenshots that identify another tester. This protects the test environment and participants.
No agreement can make a broad product idea impossible to imitate. MethodLens will rely on careful access control, dated development records, distinctive execution, brand protection when appropriate, and narrowly written agreements reviewed by an adult or lawyer—not exaggerated promises of secrecy.
6. What must exist before invitations
- A tested product build and accessibility check.
- Parent permission and student assent documents.
- A beta protocol, support contact, data map, deletion process, and incident-response plan.
- An ethics or IRB determination if outcomes will be used as research.
- Written school or district approval if recruiting or testing through a school.
7. Questions
Parents, students, mentors, and educators may send planning questions to pyatharth@gmail.com. Do not email student records or sensitive personal information.