Your gameplay produces a learning record.

Scope

Which games transmit data

The Faculty Template demonstration is local-only: it asks for a display name, does not send gameplay telemetry, and stores progress in the browser.

A published course game may enable telemetry when it asks for a school email address. Those games should display a notice before play begins and link to this page.

Data collected

Information sent during gameplay

When a published course game requests a school email and enables telemetry, the record may include:

• School email address entered by the player
• A pseudonymous player name or display name associated with the run
• Date and time, game title, run identifier, engine version, and game mode
• Start, resume, question, rapid-guessing, boss, and completion events
• Current room or stage and the question identifier
• Whether the response was correct
• Question tag, type, learning objective, and adaptive state
• Response time, elapsed time, attempt count, and streak information
• Total time, accuracy, maximum streak, and total attempts at completion
• Completion or verification code
• Score, best score, and score-event information in Score Attack mode
• Browser and device information supplied through the browser user-agent string

The standard telemetry record identifies the question and whether it was answered correctly. It does not ordinarily send the full question text or the exact answer option selected.

Local browser storage

Information kept on the device

All games, including the Faculty Template demonstration, may use browser local storage to preserve progress and preferences. This may include the email address, generated player identity, current room, saved run, sound preference, achievements, artifacts, completion status, recent scores, best scores, and hub progress.

Local storage remains on the device and browser profile until the game removes it or the user clears site data through browser settings.

Use of information

Why the data is collected

• To operate course-related completion and verification workflows
• To review student participation and performance when assigned by an instructor
• To diagnose question, scoring, timing, or progression problems
• To evaluate and improve adaptive selection, remediation, and mastery reporting
• To investigate technical failures, rapid guessing, duplicate events, or unusual records
• To create aggregated or de-identified summaries of platform use

Mastery Quests does not sell personal information and does not use gameplay records for behavioral advertising.

Storage and sharing

Where the record goes

In published course games with telemetry enabled, gameplay records are transmitted through an instructor-configured Microsoft Power Automate workflow and written to a spreadsheet. Access is intended to be limited to the site operator, the responsible instructor, and other authorized institutional personnel with a legitimate instructional, administrative, technical, or compliance need.

Data may also be processed by the technology providers used to host the site, deliver the games, transmit the telemetry, and store the receiving spreadsheet. Personal information is not shared with advertisers.

Course use

Educational records and FERPA considerations

When a game is assigned as part of a course and the record is tied to an identifiable student, the information may become part of the student's education record. The instructor and institution are responsible for using the game consistently with FERPA, institutional policy, approved technology practices, records requirements, and any required student notice.

Students using a Mastery Quest for a course should direct requests to inspect, correct, or discuss course records to the instructor or the institution that assigned the activity.

Research

Formal research requires a separate basis

Operational telemetry may be reviewed to improve instruction and the platform. Identifiable records will not be used as human-subjects research merely because they exist. Formal research use should occur only after the appropriate institutional review, authorization, notice, consent, data-minimization, and confidentiality requirements have been satisfied.

Aggregated or properly de-identified information may be used to describe platform performance when individuals cannot reasonably be identified.

Your choices

Questions, alternatives, and local data

• Review this notice before entering an email address or beginning a game.
• When a game is required for a course, contact the instructor before playing to ask about the purpose of collection, retention, access, or an available alternative.
• Clear locally stored progress through the browser's site-data controls. Doing so may erase saved progress, achievements, and scores.
• Contact the responsible instructor or site operator to ask about access, correction, or deletion. Some records may need to be retained under course, institutional, legal, or records-management requirements.

Security and retention

Safeguarding the record

Reasonable administrative and technical measures should be used to restrict access to the receiving workflow and spreadsheet. No internet transmission or storage system can be guaranteed to be completely secure.

Identifiable telemetry should be retained only as long as needed for the stated instructional, administrative, technical, research, or records purpose. When it is no longer needed, it should be deleted or de-identified when feasible.

Gameplay records and verification codes should not be treated as infallible proof of identity or academic integrity. They may support course administration, but they should be considered alongside other evidence.

Service providers

Third-party infrastructure

The public site and games may use Cloudflare, GitHub Pages, Microsoft Power Automate, Microsoft 365, and related hosting or storage services. These providers may process standard technical information such as IP address, browser information, request data, and service logs under their own privacy terms and the configuration selected by the site operator or institution.

Children

Intended audience

Mastery Quests is designed primarily for higher-education use and is not directed to children under 13. A school or instructor considering another audience is responsible for determining whether additional notice, authorization, or parental consent is required.

Changes

Updates to this notice

This notice may be revised when the platform, telemetry fields, storage workflow, instructional use, or legal requirements change. The effective date at the top of the page will be updated when material revisions are made.

Contact

Privacy questions

For a course assignment, contact the instructor or institution that directed you to the game. For questions about the Mastery Quests platform, contact William Jennings Byrd at wjbyrd@troy.edu.