USC Schedule Maker Privacy Policy

Privacy policy for the USC Schedule Maker Chrome extension

View the Project on GitHub TheOligarch/usc-schedule-maker-privacy

Privacy Policy

USC Schedule Maker (the Chrome extension)

Effective date: 2026-11-19

USC Schedule Maker helps USC students build and compare class schedules. This policy explains what the extension does with your information, in plain language. It describes what the extension’s code actually does.

USC Schedule Maker is an independent student project made by Josh Brown. It is not affiliated with, endorsed by, or operated by the University of Southern California (USC) or RateMyProfessors.com.

The short version

What stays on your device

These are kept only in your browser’s storage for the extension (localStorage, IndexedDB and chrome.storage.local). They are not sent to us unless described in the next section.

The schedules themselves are generated and ranked by code running in your browser.

This data stays until you change it, clear the extension’s site data, or remove the extension. Removing the extension from Chrome deletes it.

What is sent off your device, and why

To our AI backend (Supabase), and from there to Anthropic

The AI backend is a set of Supabase Edge Functions run by the project. The extension sends to it only when you use an AI feature. Every AI request also carries the anonymous install ID described under rate limiting.

Feature What is sent
Interview (each question) Selected term, required courses, any pinned sections, your GE or elective slots, your allowed hours, and the interview questions and answers so far, including anything you typed in free text
Schedule explanations Your interview preferences and the top schedules shown (at most 10): their courses, sections, meeting times, instructors and scores
Schedule feedback that the extension cannot interpret on its own The text you typed, the courses being scheduled with their public section details, and the schedule you are looking at

The backend uses this to look up matching courses in the public course catalog and sends a prompt built from it to Anthropic, which provides the Claude AI model. Anthropic acts as our service provider (a processor): it processes the request to generate the reply and handles API data under its own commercial terms and privacy policy. To process repeated requests more cheaply, Anthropic may briefly keep a reusable part of the prompt in memory (about 5 minutes), under those same terms. The AI’s reply (questions, suggested courses, explanations, structured feedback) is shown to you and stored with your plan on your device.

Our backend does not save the content of these requests or replies. It does not log your answers. Its logs record only an error type, such as “the model call failed”, that a request was rate-limited (which feature and for how long), and how many tokens each AI call used (which feature and the counts only). These log lines contain no request content, install ID or IP address. Supabase, which hosts the backend, may keep standard technical request logs under its own privacy policy.

Please do not type sensitive personal information (such as your student ID, health details or passwords) into the interview or feedback boxes. The AI features don’t need it.

If the AI service is unreachable, you can use the built-in offline interview, which sends nothing.

Rate limiting: install ID and hashed IP address

To keep the free AI backend from being overloaded or abused, the backend limits how many AI requests can be made:

Seat alerts (“Notify me”), only if you use them

Seat alerts email you when a seat opens in a full section you choose. Nothing is sent until you click Notify me and enter your email.

To USC’s public course site (classes.usc.edu)

While you view schedules, the extension asks classes.usc.edu for live seat counts. These requests contain only the term and course codes, for example “CSCI-103 in Spring 2027”. They are sent without your cookies, so they carry no login or account information.

Course catalog downloads (GitHub Pages, Supabase Storage)

The extension downloads public course catalog files (courses, sections, final exam times and instructor ratings) from the project’s public GitHub Pages site (theoligarch.github.io), or from the project’s public Supabase storage if that site is unreachable. GitHub may keep standard technical request logs under its own privacy statement. These are ordinary file downloads and contain none of your information.

What the extension does on WebReg (webreg.usc.edu)

The extension runs a content script on webreg.usc.edu pages only. There, it:

The myCourseBin feature is limited by design. Every WebReg request the extension makes is checked against an allowlist that permits only loading a course page and adding a section to your course bin. It cannot register you, drop or remove classes, check out, or change anything else in WebReg. Registration remains something you do yourself in WebReg. Nothing read from WebReg is stored or sent anywhere other than back to WebReg.

The course data pipeline

A separate scheduled job in this project (not part of the extension) collects public information: USC’s course catalog and seat counts, the registrar’s final exam schedule, and public instructor ratings from RateMyProfessors.com (through an unofficial API). It does not collect any information about the people who use the extension.

What we don’t do

The use of information received through Chrome extension APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Your choices

Children

The extension is meant for university students. It is not directed at children under 13.

Changes to this policy

If this policy changes, the new version will be published at this same address with a new effective date.

Contact

Questions or concerns? Open an issue at https://github.com/TheOligarch/usc-schedule-maker-privacy/issues.