QOCTS Privacy Notice

Account data: name, email, role/access level, account status.
Training data: programme/module/session progress, completion conditions, session scores, drift notes, next adjustments, reflections, final 90-day plan, QOCTS-E efficiency traces.
Feedback data: session, module, programme, burden, support, and facilitator feedback.
Institutional data: organisation name, contact, role, email, sector, cohort size, enquiry message.
Admin/review data: reviewer notes, support flags, internal review status, cohort assignment, readiness status.

To provide the platform, track training progress, generate evidence reports, support pilot learning, review readiness, improve usability, identify support needs, manage institutional enquiries, and protect method fidelity.

QOCTS development data is designed for learning, support, progression, and review. It should not be used for punishment, coercive ranking, exclusion, or identity judgment.

QOCTS does not currently sell participant data. Institutional sharing, if any, must be governed by consent, purpose limitation, minimum necessary access, and agreed data boundaries.

Retention periods are not finalised. Draft policy: retain pilot training data while the account or pilot remains active, then review retention before wider launch.

Users may request access, correction, export, or deletion review through the data request form. The exact operational process will be finalised before commercial launch.

Hosting / database provider · authentication provider · analytics provider if used · email provider if used · payment provider only if later activated · AI tooling only if later connected. To be finalised before launch.

QOCTS uses role-based access controls, restricted admin routes, and user-specific data access where implemented. Security review remains part of launch readiness.

Submit a request via /data-request.