Privacy
A limited record for responsible access.
The portal collects the account, participation, and professional information needed to support the community and protect instructor resources.
Information collected
Email-code authentication stores your email address, account identifier, and session information through Supabase. If you participate in discussions, the portal stores your chosen display name, posts, replies, and any moderation reports you submit. An instructor application additionally collects institution, department, position, institutional-profile URL, optional course context, review status, and administrative decision information. When the portal owner preapproves a known instructor, the portal stores that person’s name, email address, access status, and later whether the exact email was claimed by a verified portal account.
When an authorized account requests an Application Example notebook, the portal records the portal account identifier and email address, notebook identifier and version, selected delivery method, acknowledged notice version, request time, and whether delivery succeeded or failed. These records support access control, security review, and responsible administration of protected materials.
When an approved instructor or portal administrator requests the Instructor’s Manual PDF, the portal records the account identifier, manual edition, accepted copyright-notice version, and the time the short-lived download URL was issued. This record means Download issued; it does not confirm that the browser completed the file transfer. Portal administrators can view the count and latest issuance in the protected user directory.
How information is used
Account information is used to authenticate you and attribute participation. Discussion information is used to operate and moderate the community. Instructor-application and preapproval information is used only to establish eligibility for protected teaching resources, administer that access, prevent misuse, and communicate about access when necessary.
Google Drive and Colab
If you choose Load to Google Colab, the portal asks Google for the limited drive.file permission. This permission allows the portal to view and manage only Google Drive files and folders that it creates or that you open with it; it does not provide general access to the other contents of your Drive.
With your authorization, the portal creates or reuses a private ML4EA folder in your Drive, places the selected notebook there, and opens that copy in Google Colab. It may update a notebook copy previously created through the portal when a new validated version is delivered.
The Google access token and selected Google account address are used transiently in your browser to complete the Drive transfer and open Colab under the account you selected. They are not sent to or stored by the ML4EA portal or Supabase. Google processes the authorization and Drive activity under its own terms and privacy practices. Choosing Download .ipynb file does not use Google Drive.
Visibility and sharing
Public discussion posts, replies, and chosen display names can be read by anyone. Account email addresses are not displayed with discussion content. Teaching Practice discussions are limited to approved instructors and portal administrators. Moderation reports are available only to authorized administrators.
Instructor applications and preapproval records are not public. Database policies restrict applications to their applicants and authorized portal administrators, and restrict preapproval records to authorized portal administrators. Proposed book corrections and teaching resources submitted through the portal repository are generally public and are also subject to GitHub’s privacy practices. Portal information is not sold or used for advertising.
Protected materials
Instructor resources are kept in a private storage bucket. Approved accounts receive short-lived signed download links. Approval does not transfer copyright or permit redistribution.
Retention and requests
Account, discussion, moderation, application, notebook-delivery audit, manual-download issuance, and protected administrator records are retained while needed to operate the portal, administer access, preserve review history, and prevent misuse. To request correction or deletion of your portal account or related information, contact ml4ea.book@gmail.com. Public GitHub submissions must be managed through the corresponding GitHub repository. Some limited records may be retained when necessary for security, legal obligations, or misuse prevention.
Security and changes
The portal uses verified email sign-in, Row Level Security, private storage, and expiring links. No internet service can guarantee absolute security. Material changes to this notice will be recorded on this page and may also be announced through portal updates.