Privacy policy

AquaDissect supports guided fish-anatomy learning and preparation for faculty-supervised laboratory activities. This page explains how the application handles account and learning information.

Information used by the application

• Account details: name, registered email, student or employee identifier, role, account status and section enrollment. Existing password accounts store a password hash.
• Learning records: assigned activities, safety-module progress, anatomy attempts, formative scores, saved results and tutorial progress.
• Staff records: content submissions, media provenance, review decisions, publication history, documented exceptions, schedules and account-management history.
• Operational information: sign-in sessions, notifications, request logs and offline synchronization identifiers. The hosting server may record request information such as IP addresses and requested paths.

These records support account access, class activities, saved progress, reports, content review and operation of the service. Research participation and consent are separate from account activation and tutorial or lesson completion.

When students enter their own email

With student ID first-time access enabled, the student ID is the initial temporary password. The student must replace it with a new private password before opening the course. Administrators and assigned instructors can reset student access; the audit record stores actor and student account identifiers, role, reason and time, without storing plaintext passwords. A reset ends previous online course sessions and requires another password change. Existing enrollment and results remain retained.

Email is not required for student ID and password access. When that setup option is enabled, students claim an existing roster account with their student ID and a private administrator-supplied setup code, then choose their own password. This does not verify an email address, create an enrollment or grant access to unpublished lessons.

When enabled, a student uses their institutional ID and a privately supplied setup code to claim an existing roster account. AquaDissect sends a short-lived verification code to the email they enter. The email is saved on the account only after verification and completion of password setup. This process does not create a new enrollment, grant access to unpublished lessons, or constitute research consent.

Temporary verification email data is encrypted. Setup codes and verification codes are stored as protected hashes, expire, and are not included in learning reports or the delayed academic-data clone. The configured email service processes the recipient address and verification message for delivery. Do not share setup codes, inbox codes, or passwords.

Google sending account

An administrator may separately connect the designated sending account with Google's send-email permission. The application stores an encrypted refresh credential privately on the server so it can send verification messages. This connection does not read inbox messages, enter the academic-data clone or grant Gmail access to students. The account owner can revoke sending access through Google. Student Google sign-in is separate and does not retain these sending credentials.

When you choose Google sign-in

AquaDissect requests only your basic profile and verified email through Google’s openid, email and profile permissions. Your verified email is used to match an existing account, activate an administrator-provisioned student account, or prepare an instructor access request.

The application stores the Google account identifier, verified email, verification time and link to your AquaDissect account. For a new instructor request, your profile name and email are held in a short-lived verification session; the details you confirm are saved when you submit the request. Google sign-in does not give the application access to Gmail, Drive, Calendar or your Google password. Tokens and profile pictures from student or instructor sign-in are not retained by the application.

Google processes sign-in under its own privacy policy. Google sign-in does not determine your academic role, enrollment, research consent or instructor approval.

Who can see records

Students can view their own account and learning records. Authorized instructors can view records for their assigned sections. Program Heads can view MB 304L section progress and reports and perform permitted content reviews. Administrators manage accounts, sections and publication. Authorized staff can export reports within their permitted scope.

Information is stored on the application’s hosting infrastructure. The application does not send learning results to Google as part of sign-in. It has no advertising or sale-of-data function. Staff media-prompt tools produce copyable prompts; they do not automatically send your information to an AI service.

Storage, backups and offline access

Account and academic records are retained to preserve class history. A delayed SQLite copy receives durable records after 12 hours. This version has no automatic academic-record deletion schedule; ask the responsible administrator about the institution’s applicable retention requirements.

Offline downloads place published learning media on your device. Queued progress is associated with your account and synchronized when a connection returns. Use a trusted device and keep your account details private.

Observation notebook drafts are saved in this browser for the signed-in account, section and lesson version. They are not sent to the server, instructor, academic results or research records. Sign-out closes access within the application; drafts remain on the device until you clear them or browser storage is removed. Other people with access to the same device or browser profile may be able to inspect its storage. Avoid personal identifiers, use a trusted device and download important drafts. Clear draft removes the current saved copy. Browser storage and private browsing do not guarantee retention.

Questions, corrections and removal requests

Contact your class or system administrator to correct account details or request access to, disconnection of, or removal of your information. Requests involving academic history and backups require administrator review; the application does not offer automatic account deletion or Google disconnection. Revoking AquaDissect’s access in your Google account stops that Google authorization but does not automatically erase existing AquaDissect records.

Use the support email shown on Google’s AquaDissect consent screen for Google sign-in questions. Do not send passwords, activation codes or client secrets in a support request.