Security & Data Handling

Understand dispatch controls, learner telemetry, data flows, limitations and the evidence to request before a production deployment.

What dispatch controls do

A client connector references a course and a license. At launch, the service checks the license status, expiry, configured hostnames and learner enrollment cap. Publishers can suspend or revoke a license. Check the result with an ordinary learner and a separate pilot license.

These controls reduce uncontrolled distribution of a master ZIP. A browser still receives content needed to render a course; recording, screenshots and copying cannot be made impossible. Hostname checks and possession of a connector are not substitutes for strong user authentication in the client LMS. No universal enforcement latency or uninterrupted-session revocation time is claimed here.

Data flow

  1. The LMS launches its connector and exposes its SCORM API to the connector.
  2. The connector opens the SCORMShield player and relays runtime messages between the player and LMS.
  3. Launch telemetry is sent to the service to apply the license controls and record activity.
  4. Status, score and saved progress may be recorded and relayed back to the LMS.

Launch records can contain a learner identifier, a learner name if supplied, LMS hostname, course/license IDs, timestamps, status, score, session time and saved state. These can be personal or education-related data. Do not upload sensitive personal data without an agreed processing basis and appropriate terms.

Publisher and payment data

Publisher accounts contain contact and authentication information, course/license metadata and subscription references. Stripe handles the checkout payment flow. Hosting, database, email and analytics services support operation of the application. Ask support for the current deployment-specific subprocessors, processing locations, retention schedule and contractual terms.

Evidence to request

  • A written data-processing agreement where required, with roles, subprocessors, transfer terms and deletion arrangements.
  • Access-control and incident-response information relevant to your deployment.
  • Restore, export, deletion and version-rollback procedures, with evidence of the tests you require.
  • A completed LMS pilot test record for the exact tenant, package and browsers you intend to support.

This page does not assert that SCORMShield holds an independent SOC 2 or ISO certification, that learner data is always anonymous, or that a dispatch product automatically establishes GDPR, FERPA or HIPAA compliance. Vendor certifications do not certify this application.

Report an issue

Email support@scormshield.com with a concise description and sanitized reproduction steps. Share private course files, license keys and learner records only through an agreed secure channel. See the privacy policy and privacy evaluation checklist.