Gameplay stays in the browser unless you choose to submit it.

Scope

What Mastery Quests itself collects

The public Mastery Quests website, the Faculty Concept Composer, and current Mastery Quests games do not automatically send gameplay records to a Mastery Quests database. The composer processes faculty selections in the browser, and generated games are static files that run in the browser.

Mastery Quests does not require a school email address for its current local game workflow and does not sell personal information or use gameplay information for behavioral advertising.

Local browser storage

What may stay on the device

Games may use browser local storage to preserve the state needed for the student experience. Depending on the game or mode, that can include a display name or pseudonym, current room, saved run, game mode, question-performance records used by the mastery report, streaks, scores, achievements, artifacts, completion status, sound preferences, and local run data used to create a downloadable results file.

This information remains in that browser profile until the game removes it or the user clears site data. Clearing browser storage, using private browsing, changing browsers, or moving to another device can remove or hide saved progress.

Results and CSV exports

Submission is an intentional step

Some games can generate a completion or gameplay CSV file in the browser. Creating or downloading that file does not automatically send it to Mastery Quests or an instructor.

If an instructor requires the file for an assignment, the student chooses to submit it through Canvas, email, another institutional system, or another course process specified by the instructor. Once submitted, that copy is governed by the policies, access controls, and retention practices of the receiving institution or service.

Website hosting data

Ordinary web requests are different from gameplay records

Like other hosted websites, the services that deliver Mastery Quests pages and game files may process ordinary request information such as IP address, browser type, timestamps, and security or diagnostic logs. That infrastructure data is handled by the hosting provider under its own terms. It is not a Mastery Quests question-by-question gameplay record.

Course use

Educational records and FERPA considerations

If a student submits a results file, screenshot, completion code, or other game record as part of a course, that submitted material may become part of the student's education record. The instructor and institution are responsible for handling it consistently with FERPA, institutional policy, approved technology practices, and applicable records requirements.

Students should direct questions about an assigned submission, access, correction, retention, or alternatives to the instructor or institution that assigned the activity.

Research

Formal research requires a separate basis

Mastery Quests does not automatically accumulate identifiable gameplay records for later research. If course-submitted records are proposed for formal research, that 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 teaching or platform performance when individuals cannot reasonably be identified and the use is otherwise permitted.

Your choices

Local data and course submissions

• Clear locally stored game progress through the browser's site-data controls. Doing so may erase saved runs, achievements, artifacts, and scores.
• Use a personal or non-shared browser profile when saved game progress should remain private from other users of the same device.
• Before submitting a results or CSV file for a course, follow the instructor's directions and use the designated institutional submission method.
• If an assigned activity requires a submission and you have a privacy concern, ask the instructor about the purpose, retention, access, and any available alternative.

Security and retention

Protect the copy that actually leaves the browser

Local browser storage is a convenience feature, not a secure gradebook. Anyone with access to the same browser profile may be able to see locally stored progress. A student using a shared device should take that into account.

When a results file is submitted to a course, the receiving instructor or institution should use appropriate access controls and retain the file only as long as needed for the instructional, administrative, research, or records purpose that justified the submission.

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

Service providers

Third-party infrastructure

The public site and linked game pages may use Cloudflare and GitHub Pages for hosting and delivery. Those providers may process standard technical information associated with web requests under their own privacy terms and the site's configuration.

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, local-storage behavior, export workflow, hosting infrastructure, 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.