Resources for school review
Clear pages a school can share before a pilot.
These summaries are written for families, school leaders, and staff who need to understand what RewardVault does without digging through a product demo.
Family overview
What students experience
RewardVault gives students a clear wallet, visible progress, and school-approved rewards tied to recognition reasons the school defines.
Teachers recognize positive behaviors selected by the school.
Students sign in with the access method the school chooses, including Google Sign-In when available or school-managed passwords for supervised support.
Students can see their balance, recent awards, avatar unlocks, and progress.
Reward receipts belong to the student's account; standings, when enabled, are separate from private receipt history.
Schools can disable standings or keep them classroom-focused when direct comparison is not a fit.
Classrooms can also build a separate shared goal pool when the school wants group progress.
School stores can use approval and fulfillment steps so rewards stay organized.
RewardVault does not sell student data or use student reward activity for advertising profiles.
Families with questions about a student's reward record should contact the school, because the school controls the program and its records.
Reward paths
Individual wallets and classroom goals
RewardVault can support personal student wallet progress and class-level teamwork without mixing the two balances.
Individual currency belongs to one student and can be spent on school-approved store rewards.
Classroom currency belongs to the room and stays separate from individual student wallets.
Schools can name the individual currency and classroom currency so both feel local to the program.
Teachers can use classroom goals for group celebrations while students keep their own earned progress.
Admins can review both kinds of activity without turning classroom progress into a public student profile.
For teachers
What daily use looks like for teachers
RewardVault is organized around the teacher award board and the school's recognition language.
Teachers select a student or group of students, choose a school-defined reason, and send recognition.
Students see the receipt in their wallet, including what they earned and why it happened.
School-managed reasons keep the language consistent while teachers recognize classroom behavior.
If a mistake happens, school administrators can review activity and help correct the record.
Teachers do not need to manage the store queue unless the school assigns that responsibility.
Pilot launch checklist
How a school launches RewardVault
A successful pilot starts small enough to support, but complete enough that students and staff can see the full loop.
Name the student-facing currency so the program language is school-owned.
Load school-defined recognition reasons teachers can use from the award board.
Import a clean roster from a school-provided CSV with staff, students, and classroom groupings.
Confirm the sign-in path for staff and students before launch.
Add a few real store rewards students can request or save toward.
Run one test award, one student wallet check, and one store request before launch.
Pilot support summary
What a guided pilot includes
RewardVault pilots are meant to prove the daily loop with a manageable first group before a school expands it.
A school-specific demo path using sample data before student information is imported.
Setup support for currency naming, PBIS-aligned award reasons, store items, and staff roles.
A student access plan using Google Sign-In when available or school-managed passwords when supervised support is needed.
A teacher walkthrough focused on using the award board during classroom routines.
A store manager walkthrough focused on order fulfillment, refunds, and mistake correction.
A launch check covering roster accuracy, student access, teacher flow, and store readiness.
Sample Day 30 report
What a pilot review can show
This is an illustrative example, not a claimed result. A real pilot report uses the school's own launch group activity to decide whether to expand.
Launch group: 3 classrooms, 4 staff accounts, and 68 rostered students.
Teacher use: 3 of 4 launch staff sent at least one award during the review window.
Student reach: 51 of 68 students received at least one recognition receipt.
Recognition language: most-used reasons included Respect, Ready to Learn, Helping Others, and Strong Transition.
Store workflow: 24 reward requests were reviewed, with pending, ready, fulfilled, and refunded statuses visible from the queue.
Classroom goals: 2 classrooms used a shared classroom goal pool separate from individual student wallets.
Decision point: the school reviews staff adoption, student access questions, store workload, and parent/privacy feedback before expanding.
IT and privacy review
Questions schools usually ask
RewardVault is designed to support school privacy review with plain answers, data minimization, and school-controlled access.
Schools decide which students, staff, reward reasons, and store items belong in the program.
Student data is used to operate the reward program, not to sell advertising or build marketing profiles.
Role-based access keeps student, teacher, store, and administrator surfaces focused on their responsibilities.
Schools can review what student information is needed before importing a roster.
Schools can request export, retention, and deletion details during review or offboarding.
Formal school review can use the privacy policy and data processing agreement linked from the site footer.
Student data summary
What RewardVault stores
RewardVault stores the information needed to operate a school reward program and avoids unnecessary student data.
Student names, grade levels, and classroom groupings for rostered access.
Reward balances, award reasons, store requests, and redemption history.
School staff accounts and role-based access assignments.
No student payment cards, banking details, advertising IDs, or public student profiles.