Privacy Policy

Information We Collect

If you contact us or request a demo, we may collect your name, email address, institution or organization, role, and any details you choose to include about your course, program, or evaluation needs.

If your institution uses Mark, the product may collect account information, workspace or session information, student identifiers needed to support the workspace, engagement records, current and historical document states (including earlier drafts retained after saves and autosaves), change marker timestamps, estimated saved changes, limited browser-reported counters such as blocked paste or drop attempts and large insertion events, and scenario-assignment records.

Scenario records may include the assignment and saved scenario definition, the participant’s submitted action sentences, the actions Mark interpreted from those sentences, scenario responses and state changes, attempt status, completion or failure reasons, and debrief notes. Participants are instructed to submit one scenario action at a time and not to include names or personal information.

Mark is not designed to collect raw keystrokes, clipboard contents, cursor trails, screenshots, browsing history, or activity in other applications. Document timing and browser-reported counters describe limited activity observed within Mark and do not establish authorship or misconduct.

How We Use Information

We use information to respond to demo requests, provide and improve Mark, support instructors and students, maintain security, troubleshoot issues, and create reviewable records for instructional use.

Mark provides advisory engagement summaries to support an instructor's professional judgment. It does not calculate, determine, submit, or maintain official grades. Instructors determine and record any official grades separately in their institution-approved system. Mark is not designed to serve as the institution's official gradebook or academic system of record. We do not sell student data, create advertising profiles, or provide black-box disciplinary verdicts.

Historical document states support recovery and a reviewable account of how an assignment changed. They do not prove who authored work, whether artificial intelligence was used, or whether misconduct occurred.

Decision Scenarios interpret a participant’s submitted sentence against the finite choices available in the current authored exercise. The scenario engine then applies authored prerequisites, state changes, consequences, and completion rules. Scenario outcomes describe performance inside that modeled exercise; they do not by themselves establish physical, clinical, or professional competency.

Website Analytics

This website uses Google Analytics to understand basic site traffic and improve the public website. Google Analytics may use cookies or similar technologies. You can limit analytics tracking through your browser settings or privacy tools.

Sharing Information

We do not sell student or instructor information. We may share information with service providers who help operate the website or product, when required by law, or with an institution or instructor as needed to provide Mark for a workspace or program.

To interpret a scenario action, Mark may send the submitted sentence and limited current scenario-choice context to a configured language-model service provider. The provider helps select an authored action; it does not define the scenario’s facts, rules, or outcome. Institutions should review the applicable provider and data-handling terms during pilot planning.

Student Privacy And Education Records

When Mark is used by an educational institution, information maintained in Mark may constitute education records subject to FERPA or other applicable privacy requirements. Institutions should establish appropriate access, use, retention, deletion, and security terms before adopting Mark broadly.

A downloaded Mark assignment package (.mark_zip) contains the student's current document content, copies that can be opened outside Mark, and a signed internal record with a frozen metadata work story created at download time. Because the package may contain education records and remains readable outside the live Mark database, recipients should store, share, and retain it according to applicable institutional privacy and records policies.

Retention

We keep information only as long as needed to provide Mark, respond to requests, meet legal or institutional obligations, resolve disputes, and maintain appropriate records. Specific retention terms may be set by agreement with an institution.

In the live Mark database, students may view and restore historical states of their own assignments. Instructors may read historical states for assignments in their own workspaces to provide feedback and review student work, but cannot use revision history to alter a student's assignment. A restore creates another saved state and does not erase the state it replaced. Historical document states are retained while their parent student assignment exists and are deleted when that assignment is deleted. Copies may remain temporarily in protected backups according to the applicable backup-retention schedule. Institutions should establish who else may request or receive revision history and how long assignments and backups are retained before using Mark with students.

Scenario progress is saved after interpreted actions. Closed scenario assignments and their completed or unfinished attempts remain available for read-only review. Institutions should establish appropriate retention and deletion terms for scenario submissions, interpreted actions, outcomes, and debrief records before teaching use.

Security

We use reasonable administrative, technical, and organizational safeguards to protect information. No system can be guaranteed perfectly secure, but Mark is designed to avoid collecting more information than is needed for the instructional purpose.

Your Choices

You may contact us to request access, correction, or deletion of information where applicable. Students should also contact their instructor or institution for requests involving course or workspace records.

Contact

Questions about this policy or Mark's data practices can be sent to mark@bashtime.com.