Information used
RewardStudies stores account names, email labels and the WhatsApp mobile number supplied for account-verification setup, student nicknames and study preferences, submitted answers, examination results, study time, points and reward redemptions. Administrator settings and audit records identify the profile making a change. Passwords are stored as salted hashes rather than plain text.
Why it is used
These records support student profiles, marking, worked explanations, adaptive topic practice, progress reporting, rewards and administration. Keep student details limited to what is needed; a nickname can be used instead of a full name.
Where records are stored
The current edition stores application records in the browser’s local storage and school PDFs in IndexedDB on the device. Exported backups contain private records and should be protected. The hosting service may process normal request and access information when serving the website.
Local AI and read-aloud
WhatsApp contact permission and its date/time are saved with the account. The browser edition does not send verification codes or verify ownership of the number. A server identity service and WhatsApp provider must be configured before delivery and verification can operate.
AI features send selected learning material to a configured local model service when used. RewardStudies does not bundle a hosted AI model. Question read-aloud uses installed local browser voices where supported. Uploaded papers should not contain unnecessary personal information.
Children and family profiles
A parent or guardian should oversee creation and use of a child’s profile. Each student has separate learning records within the selected family account. Browser-only profile checks do not provide the security of a deployed identity server.
Access, correction, retention and deletion
You can review progress and edit profile preferences in the application. The administrator can export browser data for access or correction requests. Local data remains until it is removed, replaced or cleared; reward-point expiry does not delete learning records. Clearing the site’s browser data removes local application records and stored PDFs on that device. Export only what you need before clearing data. Contact the operator for help and requests concerning any separately held records.
Payments and social login
Payment collection, stored cards, recurring billing and social login are not active in this edition. A future server deployment must update this notice to identify its providers, purposes, retention, transfers and contact arrangements before activating these services.
Questions and withdrawal
Contact the operator using the details below for privacy questions, access or correction requests, or to discuss withdrawing consent. The operator should explain any effect on services and any records that must be retained.
Separate purposes and choices
Account and learning information is used for the stated service functions. Terms agreement, Privacy Policy acknowledgement and optional cookie choices are recorded separately. Optional tracking is not required for an account. A checkbox does not authorise unrelated marketing or undisclosed disclosure. Collection and use must remain appropriate to notified purposes and applicable law.
Acceptance evidence
Sign-up records the account identifier, UTC time, document title, exact policy text, acknowledgement statement, SHA-256 version fingerprint and optional cookie preference. Signed-in cookie changes append records rather than replacing original ones. Times can be displayed in Singapore time. No visitor IP is verified. Browser records are not tamper-resistant server evidence.
Security limits
Local profile checks and salted password hashing do not prevent someone with access to the browser or its files from viewing or changing records. Avoid sensitive information on untrusted devices. A server deployment must introduce appropriate identity controls, access restrictions, protection and backups. This notice cannot guarantee security.
Providers and transfers
The local edition does not require cloud AI or document storage. Hosting infrastructure may process request information to deliver pages; a configured local model receives selected text when used. New providers, purposes, overseas transfers or tracking must be reviewed and disclosed before activation with safeguards required by law.
Retention and accountability
Local records remain until removed, replaced or cleared; exported backups remain with their holder. Point expiry does not delete learning or acceptance history. Identifiable information should be kept only while it serves an appropriate legal or business purpose; separately held server records need an appropriate retention schedule.
Requests and withdrawal
Users and authorised parents can request access or correction, discuss withdrawal of consent and raise privacy concerns through the operator’s published privacy contact. Authority may need verification and lawful exceptions, effects on service or required retention should be explained. Statutory rights and complaint routes are not waived by acknowledgement.
Incidents and updates
Report suspected unauthorised access promptly through the operator’s published contact. The operator should investigate, contain and assess incidents and notify affected parties or authorities where legally required. Material collection or use changes should be disclosed before taking effect; history retains the version previously shown.
Account and student activity records
We record account login and explicit logout times, page navigation, clicks or taps, counts of keyboard and form actions, scroll activity, and application-operation outcomes to support service security, troubleshooting, parent/guardian learning oversight and administration. Records identify the account and, where selected, the student profile. We do not capture passwords, one-time codes, payment-card details, typed text, answer contents or mouse-movement trails through the activity recorder. These counts are not a diagnosis or a reliable measure of effort, understanding or ability.
IP addresses, TXT logs and access
A server can record the connection IP it observes. The optional local launcher writes per-account TXT files with server receipt times and observed peer IPs; local visits normally show a loopback address. Browser-reported identity and events can be altered and do not establish verified identity. Without the logging endpoint, the IP is marked unavailable rather than guessed or fetched from an external IP service. Parents can review their account and linked students; administrators have access for the notified purposes. TXT exports and backups contain personal activity data and must be protected.
Activity retention and choices
The local activity view retains at most 5,000 recent events and 90 days of daily totals; exported or locally appended TXT files remain until their authorised holder removes them. Session records are bounded and may lack a logout when a browser is closed. Keep identifiable records only for an appropriate legal or business purpose, restrict access and dispose of them securely when no longer needed. Optional learning-interaction collection can be disabled under profile settings; essential account/security operation records are separate. Updated notices and any required consent must be provided before deploying new collection or using data for a new purpose. This notice is not permission for unrelated marketing, covert monitoring or unlimited retention.
Assessment reports and achievement rewards When you submit previous and current assessment evidence, we use the reports, student profile, subject, marks, dates and submitting adult’s declaration to verify improvement, prevent duplicate claims and maintain reward records. Reports are private and are not used to train the question-generation model. Server archive copies are kept while needed for verification, reward disputes, fraud prevention or legal obligations and reviewed for deletion or de-identification when those purposes end. Browser-only storage is not a permanent company archive. Optional publicity permission is separate from reward eligibility: only the specified public display name, level, subject and approved improvement may be featured after administrator review. Reports, full report images, contact information and school identifiers are excluded. Withdraw publicity permission in Results & achievements; future website features cease without loss of reward points.
Email verification and payment configuration
Configured SMTP services deliver short-lived account verification codes to your email address. Codes expire after ten minutes, have limited attempts and are not written to activity logs. Google Analytics is optional and controlled through cookie preferences. A saved PayPal receiver identifier is configuration only: payment collection is not activated by saving it, and card numbers are not stored by this application.
Account security records include login and logout times, IP addresses, connection source and security events. We estimate the country of public IP addresses locally to flag sudden country changes for administrator review. IP location is approximate; private networks, VPNs, travel and data errors may affect results. We do not record passwords, session tokens or verification codes in these records. Account security history is restricted to the account holder and authorised administrators. We retain records under our applicable retention policy and legal obligations. Contact the operator using the details in this policy for privacy requests.
Game features record student-specific study-time credits, earned and used playtime, validated game progress, reward-point awards, accepted friendships and challenge-room results. Study and playtime measurements reflect tracked activity, not proof of attention or learning. Friend game invitations require acceptance; each participant uses their own playtime balance. Authorised account holders and administrators can review applicable records. Unused playtime carries forward; game reward points follow the reward-point expiry policy.