1Information we collect
The information handled depends on the journey and the role using the system. It may include:
- identity and contact details, such as name, NRIC or passport number, nationality, date of birth, gender, phone, email, and address;
- account and role details for Workers, Employers, Agencies, Admin, and Finance users;
- company, agency, employer, worker, geography, referral, and relationship records;
- registration, course-language preference, application, external e-SICW reference, progress, result, verification, and certificate-status records;
- Module Credit, wallet, purchase, transfer, payment, invoice, receipt, statement, and financial-control records;
- support information, uploaded documents or payment proof, audit activity, and technical or security logs.
2How we use information
JSC uses information to operate the public and authenticated journeys, including to:
- validate referrals, register accounts, and connect Workers, Employers, and Agencies;
- provide role-aware portal access and enforce available actions;
- prepare applications, Module Credit activity, payments, statements, and operational reporting;
- connect to the related external e-SICW environment and record returned status information;
- provide support, investigate problems, maintain auditability, and protect the service;
- meet applicable record-keeping, business, security, and legal obligations.
3Referrals and role relationships
A registration started from an Agency referral link or QR code carries that attribution into the Worker journey. Employer-linked Workers, Employers, supporting Agencies, and authorised JSC roles may see information needed for their permitted workflow. Visibility and actions are limited by the user’s role, relationships, and current record status.
4External e-SICW and service providers
JSC and the related e-SICW environment are separate systems. Information required to create or connect an enrollment, launch learning, receive status updates, or support certificate actions may be exchanged through authenticated integration routes. Payment providers, hosting infrastructure, and other service providers may also process information required to deliver their part of the service.
Each external service may have its own terms, privacy practices, availability, and technical requirements.
5Cookies, sessions, and local storage
The site uses session and authentication technologies to keep users signed in, protect forms, preserve the current registration referral, and remember a selected course language. The public pages may store the current referral code and selected language in browser local storage. Browser settings can clear local storage and cookies, although doing so may interrupt login or registration continuity.
6Retention
Information is kept for as long as reasonably needed for the purposes described here, including operational continuity, account and transaction history, auditability, dispute handling, security, and applicable record-keeping obligations. Different record types may require different retention periods.
7Security
JSC uses role-aware access controls, authenticated routes, password controls, transaction boundaries, audit records, and other administrative and technical measures appropriate to the system. No internet service can guarantee absolute security, so users should protect credentials, use the correct account, and report suspected unauthorised access promptly.
8Access and correction requests
To request access to or correction of personal information held in JSC, contact the organisation using the details below and describe the relevant account or record. Identity or authority may need to be verified before a request can be handled. Requests remain subject to applicable law and record-keeping requirements.
9Contact
Use the verified contact details below for privacy questions, access or correction requests, or concerns about information handled in JSC.
