Privacy Policy — Help Desk Training Platform

Effective date: October 18, 2026  

App: Help Desk Training Platform (TAS Help Desk)  

Responsible operator: Michael Yuan  

Privacy contact: msycpu.work @ gmail.com

1. About this application

The Help Desk Training Platform (the “App”) is an educational simulation for learning entry-level information technology (IT) support. Authorized students practice receiving and managing simulated support tickets, troubleshooting, documenting work, using approved resources, and completing assessments. Instructors supervise work, provide feedback, and review student Skills Portfolios.

This policy explains how information is collected, used, stored, and shared when the App is used for instructional activities. Michael Yuan operates the App. A participating school or district may have additional responsibilities for education records handled in connection with its courses; this policy does not override those responsibilities. The App is not a public service desk for real customer problems.

2. Information we collect and create

Depending on your role and the activities assigned, the App may hold:

• Account and class information: student or staff name, assigned Technician ID, internal user identifier, role, class, course term, account status, and assigned permissions. The current student account setup does not require a personal email address or telephone number.

• Training activity: simulated support tickets, assigned work, troubleshooting actions, ticket messages and notes, resolutions, verification steps, escalation or handoff records, knowledge-base contributions, and command/tool practice.

• Learning and assessment records: practice attempts, scores and accuracy where recorded, guidance/progression status, assignments, instructor observations or private notes, final assessments, evidence selections, approvals, and Skills Portfolio information.

• Account and security records: a securely hashed PIN, session-token hash, sign-in/session timestamps, account actions, access-related events, and audit history. The App does not save students’ PINs as readable text in its main credential records.

• Information entered by users: other information that a student or instructor chooses to type into training fields. Please use fictional or authorized training data rather than real personal, confidential, or sensitive customer details.

Google’s hosting and infrastructure services may also process technical information necessary to deliver and secure the App, as described in Google’s own policies.

3. How information is used

Information is used to provide the training environment, authenticate participants, assign and manage simulated work, measure recorded practice, support instructor feedback, protect accounts, investigate technical or security issues, preserve instructional and audit records, and produce instructor-reviewed Skills Portfolios.

The current App does not use participant information for targeted advertising, sell student training records, or automatically send those records to external AI services. If any of these practices changes, this policy must be updated before the new use begins.

4. Google services and account access

The App is built with Google Apps Script. App records are stored in a Google Sheets-based database accessible to the authorized application operator and appropriately authorized staff. Google Drive and Google Docs are used when the App creates archives or generates a Skills Portfolio PDF.

For a Skills Portfolio download, the App temporarily creates a Google document, converts it to a PDF, sends the PDF to the authorized user’s browser for download, and moves the temporary document to Google Drive Trash. The App does not intentionally maintain a permanently shared public PDF link. A downloaded copy may remain on the recipient’s own device or wherever that recipient saves or shares it. Trashed Google files can remain subject to Google’s Trash and retention behavior.

Student sign-in uses a Technician ID and PIN. The current App does not ask students to authorize access to their personal Gmail messages, Google Drive files, or Google Contacts to use its training features. Google may separately manage account access, cookies, service diagnostics, and other platform information depending on the deployment and how the page is accessed. See the Google Privacy Policy (https://policies.google.com/privacy).

5. Who can access or receive information

• Students: may access their own account, assigned training records, and permitted shared training-queue content. A shared training ticket may be visible to other authorized participants involved in that queue.

• Authorized instructors and administrators: may review or manage records as permitted by their responsibilities, class assignments, and the App’s access controls. Certain instructor notes are treated as private within the App.

• Google: supplies the hosting, application execution, spreadsheet, document, and storage services that process the information described above.

• Recipients chosen by the student or school: a Skills Portfolio downloaded and independently shared by its recipient is outside the App’s direct control.

• Other disclosures: records may be disclosed if required by applicable law or an authorized educational records process.

The App is not intended to publish student account records or private instructor comments openly on the Internet.

6. Security and browser storage

The App uses role-based access controls, class/term authorization checks, hashed PIN credentials and server-side session validation. Its browser interface uses session storage for temporary sign-in tokens and, for instructors, a selected Student 360 view. These session items are designed to be cleared when the browser session ends or the user signs out. Older persistent App authentication values are removed when the current interface starts.

These safeguards reduce risk but no online system can guarantee absolute security. Users should keep PINs private, sign out on shared computers, and avoid entering real customer or other sensitive information in simulations.

The current App code does not install third-party advertising trackers. Google services may independently use browser storage or cookies under Google’s applicable policies.

7. Retention, class archives, and deletion

Course records may be maintained for instructional review, assessment, program administration, and audit purposes. Ending or archiving a class term does not automatically delete its historical data. The App can create separate term archive spreadsheets and retain historical records in its underlying database. Student access may be disabled after a term, but the corresponding records can remain stored.

The current App does not implement a universal automatic deletion date for all student records. Specific retention and deletion periods depend on the responsible operator’s approved records policy and any applicable educational-record requirements. To ask about an account, correction, archive, or deletion request, contact the privacy contact listed below. Some records may need to be retained where required or permitted by applicable rules.

8. Access, corrections, and privacy questions

Students and instructors may request information about records held in connection with their App participation or report an inaccurate record through their instructor or the privacy contact. Requests to correct or delete information are reviewed by the responsible operator according to relevant school and records requirements. This policy does not promise that all instructional or audit records can be immediately erased.

If you believe an unauthorized person has obtained access to your account, notify the instructor or privacy contact promptly so access can be reviewed and, if necessary, the account PIN reset.

9. Educational use and younger participants

The App is designed for supervised educational use, primarily with adult learners. It is not intended to collect information from children through an open public enrollment process. Participating schools or programs are responsible for determining whether any additional notices, permissions, or safeguards apply to their students.

10. Changes to this policy

We may update this policy if App features, data handling practices, or applicable requirements change. The current version and its effective date will be displayed on the public policy page. Material changes to how user information is handled should be communicated to affected participants through an appropriate notice.

11. Contact

Responsible operator: Michael Yuan  

Privacy questions and records requests: msycpu.work @ gmail.com  

App: Help Desk Training Platform