Privacy
Last updated: September 2026
OMYSSEY is currently in a private academic-evaluation phase. Public registration is not enabled and the platform is not commercially distributed through the site. Accounts are created manually by the administrator only for people invited to evaluate the learning material and experience.
1. Data OMYSSEY may process
When an evaluation account is created, OMYSSEY may store the minimum data needed to identify the account and support educational progress: name, email address, internal identifier, account status, assigned courses, current lesson, completed lessons and exercises, hints used, account creation/activation/last-access dates, and minimal security or administration records.
The platform does not store passwords in readable form. It stores only an Argon2id hash with a random salt. The administrator cannot recover the original password from that hash.
2. Purposes
Account and progress data are used only to:
- create, activate, and authenticate the invited account
- assign and control access to authorized courses
- store individual educational progress and unlock modules
- allow the administrator to review progress and support the learner
- protect the security, availability, and integrity of the platform
- evaluate whether lessons and exercises are understandable during this testing phase
3. Payments
OMYSSEY is not a payment gateway and does not request, process, or store card numbers, bank-account details, banking credentials, payment receipts, or other financial data for course payments. Any promotion, contact, enrollment confirmation, and, when applicable, payment take place outside OMYSSEY.
4. Code execution
The current Python laboratory executes learner code locally in the browser using Pyodide and WebAssembly. Code written in that laboratory is not sent to the server for execution, and learners do not receive shell access to the laboratory server.
5. Account security
Account invitations use random, single-use, time-limited links. Each user creates their own password. Sessions use HTTP-only cookies and access controls are verified server-side. The administrator can suspend an account or revoke course access without knowing the user's password.
6. Technical logs
Server infrastructure may process minimal technical logs such as IP address, date and time, requested path, and security events for diagnostics, availability, and abuse prevention. OMYSSEY does not use these records for advertising or commercial profiling.
7. Video-conferencing
Guided sessions are conducted through an external video-conferencing platform. OMYSSEY does not capture or store audio or video by default. The external service applies its own terms and policies. If a session were ever to be recorded, participants would be informed in advance.
8. Retention and access control
During this evaluation phase, data are retained while the account requires access or while needed to evaluate platform operation and security. Administrative access is restricted. Suspending an account prevents new sessions but does not automatically delete its data. Deletion or anonymization should follow the applicable purpose and obligations.
9. Individual rights
Account holders may request information about their data and, where applicable, access, correction, cancellation, or objection under applicable Mexican law. Before OMYSSEY expands beyond this private evaluation, a comprehensive notice must identify the responsible party's address and a specific channel for applicable data-rights requests.
10. Ownership and institutional infrastructure
Temporary hosting of OMYSSEY on a laboratory computer for demonstration, technical testing, or academic review does not constitute an intellectual-property assignment and does not make the institution providing infrastructure the owner of the software or its materials.