QUDY Privacy Policy
Last updated: May 2026.
1. Scope
This policy explains how QUDY handles personal data in the student mobile app, the school web app, and the supporting API services.
QUDY is provided to schools. In practice, much of the account and class data in QUDY is entered by a school, while quiz attempts, login events, and language preferences are generated when users use the service.
2. Data we collect
Depending on your role and how QUDY is deployed, we may collect or generate:
| Category | Examples |
|---|---|
| School account and profile data | Display name, school-assigned student or teacher ID, class and class number, login identifier, password hash |
| Authentication and session data | Hashed refresh-session records, session identifiers, role information, password-change state, and student session-kick security events |
| Quiz and learning data | Quiz attempts, submitted answers, scores, timestamps, and immutable snapshots of quiz content at attempt time (for grading, analytics, and dispute handling) |
| Operational and security logs | Request metadata such as HTTP method, path, status code, request ID, and client IP address where our infrastructure records it for security and troubleshooting |
| Audit records | Who performed sensitive actions (for example account changes, quiz publish, imports, exports), on which school or entity, and when |
| Generated files | Import spreadsheets, analytics export jobs, and short-lived exported report files created for school operations |
We may also infer a starting UI language from browser `Accept-Language` headers or device locale settings when no prior language preference has been saved.
We do not collect mobile push-notification tokens or send push notifications as part of the current product scope.
3. Cookies, device storage, and session handling
QUDY uses a small set of cookies and device storage entries to keep the service working securely:
- Web authentication cookies — the web apps use httpOnly cookies for sign-in and token refresh.
- Language preference — the web apps store language selection in the `qudy.lang` cookie.
- Mobile secure storage — the student mobile app stores sign-in tokens, password-change state, and language preference in secure device storage.
- Mobile offline cache — the student mobile app may store downloaded quiz content, pending answers, and related media on the device until they are synced or cleared (for example on logout or account switch).
- Student one-device rule — QUDY enforces one active refresh session per student account. If a student signs in on a new device, the earlier session is revoked for security.
4. Why we use personal data
We process personal data for these purposes:
- Education delivery — authenticate users, show published quizzes, record attempts, grade answers, and return results.
- School administration — manage caps, classes, teachers, students, school settings, imports, and exports within each tenant.
- Security and abuse prevention — rotate sessions, enforce tenant boundaries, investigate incidents, and maintain audit trails.
- Support and troubleshooting — investigate defects, review logs, and resolve operational issues.
- Analytics and reporting — produce school-level reports such as class or quiz performance without using data for unrelated advertising or marketing.
We do not sell personal data.
5. Who can access or receive data
Access inside QUDY is limited by role and school tenancy:
| Role | Typical access |
|---|---|
| Student | Own profile, visible published quizzes, and own attempt history and results |
| Teacher | Students and classes in their school for teaching, school-shared subjects/categories/quizzes/questions they are permitted to edit, and school-level analytics |
| School Admin | All teachers and students in their school, school settings, imports/exports, and school analytics |
We may also use service providers that process data on our behalf to host QUDY or provide supporting infrastructure, such as object storage, logging, or crash/error reporting where those services are enabled for the deployment. Those providers should only process data for operating, securing, or supporting QUDY.
Students cannot access other students' attempts.
6. Mobile diagnostics and error reporting
The QUDY student mobile app may generate local device logs during development or when verbose logging is enabled.
Crash or error reports are sent to a third-party diagnostics service only if that integration is explicitly enabled by the school for the deployment. If enabled, reports may include app version, device OS version, and stack traces. They should not intentionally include quiz answer content unless that is required to reproduce a specific defect.
7. How long we keep data
- Audit events: 24 months, then deleted by scheduled job.
- Structured request logs: 90 days (log aggregator TTL).
- Report export files: 1 hour after creation.
- Import/export spreadsheets in object storage: 24 hours.
- Quiz attempts: life of the school contract plus 12 months, then removed as part of school offboarding.
Some data may be deleted sooner because of user or school actions. For example, deleting a subject, category, or quiz can also remove related quiz attempts and answers through database cascade rules.
8. Security
We use role-based access control, school-tenant isolation, hashed passwords, hashed refresh tokens, and audit logging to help protect personal data. No internet-connected system is completely risk free, but we aim to use reasonable technical and organizational measures appropriate to the service.
9. Your rights (access and correction)
Under the Personal Data (Privacy) Ordinance (Cap. 486), you may request access to or correction of your personal data. Students and teachers should contact their school administrator first, because the school usually manages account and class information in QUDY. Schools may escalate requests to QUDY support where needed.
We may ask for identity verification before acting on a request, and we will respond within a reasonable period.
10. Changes to this policy
We may update this policy when QUDY changes, when retention or security practices change, or when legal requirements require an update. We will publish the updated version with a revised "Last updated" date.
11. Contact
Privacy enquiries: wingxtechm@google.com.
For school-specific questions about what your school submitted to QUDY, contact your School Admin first.