Privacy and data-use notice
This template describes the system's intended data practices. Replace the controller identity, contact details, retention periods, lawful bases, and organization-specific procedures before production use.
Data collected
The core account collects an email address, username, password hash, email-verification status, random device-registration tokens, coupon/entitlement records, and limited learning-app access events. Raw coupon codes and raw passwords are not stored. The design intentionally avoids collecting demographic or sensitive profile fields unless a future feature has a justified need.
Purposes
Data is used to authenticate users, enforce access and device limits, deliver learning content, prevent abuse, maintain accountable coupon issuance/redemption, provide user/admin analytics, and support security and troubleshooting.
Analytics and recommendations
Any forecast or recommendation shown by this system is an aid, not an authoritative human decision. The default analytics use access and coupon activity rather than sensitive characteristics. Avoid using analytics to discriminate, rank learners unfairly, or make high-impact decisions without appropriate human review.
Rights and requests
Subscribers can review their account/device/access information and request account deletion. Production procedures should also support applicable requests for access, correction, objection, erasure/blocking, and other rights required by Philippine law and institutional policy.
Retention and security
Retention periods are configurable and should be approved before deployment. The application uses role-based authorization, CSRF protection, parameterized database queries, secure password hashing, hashed verification/device/coupon tokens, rate-limited sign-in attempts, audit trails, and sandboxed uploaded learning apps. HTTPS remains mandatory.