Add to Chrome

Privacy policy

ClassAdd is a Chrome extension with no server and no accounts. Last updated November 1, 2026.

What stays on your computer

ClassAdd keeps this in Chrome's own storage on your computer. None of it is sent to the ClassAdd developer, because there is no ClassAdd server.

  • Your plan: the classes you picked, their backups and sections, the term, and which classes you told ClassAdd you are already registered in.
  • If you connect Gmail, the email address of that Google account, and the identifier of the one email conversation that ClassAdd's own notices are grouped in (an ID that Gmail returns for an email ClassAdd itself sent; ClassAdd cannot read your mail). Google's access token is held by Chrome, not by ClassAdd.
  • A short activity log: when ClassAdd checked, and what it noticed or did. It never contains passwords, cookies, or the contents of WebReg pages.

Your USC password

You sign in on USC's own pages. ClassAdd never sees or stores your password or your Duo codes. It uses the WebReg session your browser already has.

Where data goes

  • classes.usc.edu: your computer asks USC's public class data about the classes in your plan, to see open seats. This is public information.
  • webreg.usc.edu: your computer talks to WebReg with your own signed-in session. In Manual mode ClassAdd does not contact WebReg at all. Only when you turn on Auto, it reads your Course Bin and checkout pages, adds the sections you chose to your Course Bin, schedules and registers them, and, only to replace a class you marked as registered with a better section from your plan, drops that class in the same step. It sends nothing else to WebReg, and what it reads from those pages stays on your computer.
  • Google, only if you connect Gmail: you give ClassAdd permission to send email from your Gmail account, to you. It cannot read your inbox or anything else. The alert emails contain class codes and section numbers, and they travel through Gmail like any email you send.
  • Professor ratings come from a copy of RateMyProfessors data packaged inside the extension. Looking one up sends nothing anywhere.

Google user data

ClassAdd's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. The only Google data ClassAdd uses is your email address (to send alerts to you) and the permission to send those emails. It is used only to send you ClassAdd's alerts. It is not sold, not shared, not used for advertising, and no person at ClassAdd can see it.

How we protect your data

The best protection is that ClassAdd has no server, no database and no accounts, so there is no ClassAdd system that holds your Google data or could be breached. These are the safeguards that apply to the Google user data ClassAdd handles (your Gmail address and permission to send alerts):

  • Encryption in transit: everything ClassAdd sends to Google, USC and this website goes over HTTPS (TLS). The extension's site permissions are all HTTPS addresses.
  • Google's token is not kept by ClassAdd: Chrome's identity system obtains and holds the access token, and ClassAdd asks Chrome for it only when it connects, sends an alert, or disconnects. ClassAdd never stores the token, never writes it to its activity log, and never sends it anywhere except to Google.
  • Stored only on your computer: the only Google data ClassAdd keeps, your email address and the identifier of its own notice conversation, stays in Chrome's extension storage on your computer. Chrome keeps each extension's storage separate from websites and from other extensions. It is never transmitted to the ClassAdd developer or to any third party.
  • No human access: no person at ClassAdd can read your data, because it never leaves your computer. ClassAdd does not use remote code: everything the extension runs is inside the package you install.
  • Least access: ClassAdd requests only the permission to send email, not to read, list or delete anything in your Gmail. It sends only to your own address, uses fixed message templates, and is limited to 20 emails per hour.
  • Revocation: disconnecting Gmail in ClassAdd deletes the stored address and asks Google to revoke ClassAdd's access. You can also remove ClassAdd at myaccount.google.com/permissions at any time.

How long data is kept

Your email address and the notice conversation's identifier are kept only while Gmail is connected and are deleted when you disconnect Gmail or remove the extension. Your plan and activity log stay on your computer until you remove the extension, and the log keeps only the most recent entries.

Extension permissions

  • Sites: webreg.usc.edu and classes.usc.edu, as described above, and Google's gmail.googleapis.com, www.googleapis.com and oauth2.googleapis.com, only to connect Gmail and send your alerts.
  • Alarms: to check for open seats every 30 seconds.
  • Storage: to keep your plan and log on your computer.
  • Power: to ask your computer to stay awake while ClassAdd is watching.
  • Identity: to connect your Gmail account if you choose to.

This website

No analytics, no ads, and no third-party fonts or scripts. Its host may keep standard server logs, such as your IP address, when a page loads. The extension itself loads nothing from the web except the services listed above.

Your controls

  • Pause or stop watching, or switch Auto off, at any time on the dashboard.
  • Removing the extension deletes what it stored on your computer.
  • Disconnect Gmail in ClassAdd, and remove ClassAdd at myaccount.google.com/permissions to withdraw Google's permission completely.

Who runs ClassAdd

ClassAdd is an independent project by a USC student. It isn't made, endorsed, or run by USC. Because it has no server and collects nothing, there is no data about you held by ClassAdd to access or delete. For questions about this policy, use the Support tab on ClassAdd's Chrome Web Store listing.

If this policy changes, the date at the top changes, and the new version is what the extension's listing links to.