Built for school trust
Student reward data should stay school-owned, access-limited, and difficult to misuse.
RewardVault helps schools run PBIS-style reward programs with data minimization, school-controlled access, and no advertising use of student reward activity.
Public commitment
No student ads. No data resale. No public student profiles.
RewardVault exists to support school-run recognition, student wallets, and reward store operations.
School-owned data
RewardVault is built for school reward programs. Schools control their setup, roster data, reward activity, and store records.
Student data separation
Student reward records are scoped to their school so one school's users cannot browse another school's students, rewards, or store activity.
Limited access by role
Students, teachers, store staff, and school administrators each have a focused view for their responsibilities.
Admin review tools
Admins can review reward activity and store approvals, while roster updates and access changes stay inside admin-controlled workflows.
No ads or resale
RewardVault does not sell student data or use student reward activity for advertising profiles.
Backup and restore planning
Reward records are backed up so student balances and store history can be recovered if a service disruption affects the platform.
School review details
Public trust summary for initial IT and privacy review
This page summarizes the public posture. Schools can request DPA, retention, subprocessor, and security details during review.
Encrypted connections
Connections to RewardVault use HTTPS so student records are not transmitted over unencrypted web sessions.
Role boundaries
Students cannot access store approvals, store staff do not manage school setup, and teachers work inside the award tools assigned to them.
Data retention and offboarding
When a school ends its RewardVault relationship, school data can be exported on request and deletion steps can be reviewed as part of offboarding.
Privacy review contact
Schools can email info@getrewardvault.com to start a privacy, DPA, retention, or data review conversation.
Data used to run the program
What schools may store
Student names, grade levels, and classroom groupings needed to run the reward program.
Reward balances, award reasons, store requests, and redemption history.
School staff accounts and access assignments.
Configuration such as currency names, behavior reasons, store items, and approval settings.
Data we do not need
What the reward system avoids
Student social security numbers.
Student payment cards or banking details.
Advertising identifiers for student marketing.
Public student profiles outside the school's RewardVault environment.
For pilots and school review
Clear privacy answers for school review.
RewardVault can support school review conversations about student data, access, retention, deletion, and subprocessors. Email info@getrewardvault.com or request a school demo to start the review path.