OR2BS Privacy Notice

OR2BS stores only the data needed to operate cadet learning, gamified progress, mobile synchronization, messaging, social squads, and command readiness analytics.

Data We Process

• Account identity, email, role, and login security records.
• Minimal cadet player profile fields such as school, ROTC unit, student number, name, age, contact number, year level, and address.
• Learning progress including XP, rank, streak, medals, attempts, topic mastery, and leaderboard records.
• Mobile device sync logs, push token registration, and offline upload metadata.

ROTCMIS Source of Truth

Official cadet identity and records remain under ROTCMIS. OR2BS keeps a lightweight player bridge and synchronization references for learning and mobile app use.

Use and Access

Performance is monitored to support assigned learning, readiness, coaching, and authorized institutional reporting. Cadets may see their own records. Instructors and unit administrators may see verified cadets only within granted units; system administrators have controlled system-wide duties. Guests, regular users, and pending cadets never appear in official cadet-monitoring reports.

Retention and Corrections

Learning and official assessment records are retained only as long as required for the stated purpose and approved institutional policy. Contact the institution's designated privacy office or unit administrator to request access to or correction of an inaccurate record.

Institution placeholder: publish the approved retention periods, privacy-office contact details, correction/appeal process, and lawful basis before production launch.

Security

Mobile access uses Laravel Sanctum bearer tokens. The system records sync activity and supports role-based permissions for protected modules.