Last updated November 18, 2026
Tuddle is a Chrome extension for University of Toronto students. It keeps your deadlines, marks and plans in your own browser. Mostly it sends course text, not your own data: the text of your syllabi, course pages and announcements, so its AI reader can understand them (see "How Tuddle reads your syllabi" below). The few times it sends your deadlines or marks to the Tuddle team (a one-time check after setup without your name, and feedback you choose to send) are listed below, with how to turn them off.
Tuddle reads your coursework using the sign-ins you already have in Chrome, only to build your to-do list, study plan and grade estimates.
Tuddle never reads your passwords. It only visits a site when one of your courses uses it.
Your deadlines, marks, study plan and settings stay in your browser's extension storage on your own computer. Tuddle has no analytics. The developer doesn't see your deadlines or marks, except in the cases listed on this page: the one-time check after setup (sent without your name or Tuddle code), feedback you choose to send, and pages from course sites you link for Tuddle to read. If you add your name and email in Tuddle, they are sent to Tuddle's server. Your email is only used to email you about opportunities for UofT students, and only if "Email me about UofT opportunities" is ticked. Untick it or clear your email any time in the Account tab, or email [email protected] to have it deleted.
Tuddle sends data in only these directions: back to the site it came from (for example, asking Quercus for your assignments), to Google Calendar or your calendar link when you turn those on, to the Tuddle server (to check whether your Tuddle code is paid up, to send survey answers or feedback, for the daily report and the one-time check described below), and to Tuddle's AI reader, described next.
To get grade weights, "best 3 of 4" rules, test dates, readings and make-up dates right, Tuddle sends the text of your course syllabi and course web pages, and of course announcements that might change a date, to the Tuddle server. The server asks Claude, an AI model made by Anthropic, to read it, and sends the answer back to Tuddle. Your Tuddle code and the course code are sent with the text, only to keep usage within Tuddle's limits. Your name and email are never sent to the AI reader. Your marks and submissions aren't either, except what appears on a page of a course site you linked for Tuddle to read (for example a Pearson page that lists your scores).
Because everyone in a course has the same syllabus, the answer is saved on the Tuddle server by course and reused for other students in that course, so each syllabus is only read once. Only the answer is saved, not the text you sent, and it's about the course, not about you. If you pick a course when you send feedback in the Help tab (for example "quizzes are 10% not 5%"), your message is also sent to the AI reader so it can fix that course for everyone in it, and the change is emailed to the Tuddle team.
Anthropic processes this text to answer Tuddle's request and, under its terms for businesses, doesn't use it to train its models.
If you click Connect, Tuddle asks Google for the calendar.app.created permission. That lets it create one calendar called "Tuddle" and add, change or remove events in that calendar only. It cannot see or change any of your other calendars or events.
If you turn on the calendar link in Tuddle's Account tab, Tuddle sends the deadlines and tests it would put in your calendar (their titles, course codes, dates and links, never your marks) to the Tuddle server after each update. They're kept there only so your calendar app can read them at your private link, and they're replaced each time. Anyone with the link can see those deadlines, so keep it private. Turning the link off in Tuddle deletes them from the server.
Tuddle's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used only to show your deadlines and tests in your own calendar. It is not transferred to anyone, not used for advertising, and not read by people.
Tuddle is free right now. If paid extras are added later, you would pay by Interac e-Transfer to [email protected] and write your Tuddle code (a random code like TD-7KQ4MX that Tuddle makes for your installation) in the message. The developer's Tuddle payments service reads the Interac payment email and records the sender's name as shown by Interac, the amount, the Interac reference number and your Tuddle code in a private Google Sheet. Tuddle and its developer never see your bank details.
To check whether you have paid, Tuddle sends the payments service only your Tuddle code. If you fill in the survey in Tuddle's menu, your answers, your Tuddle code, the Tuddle version and the name you entered in Tuddle's menu, if any, are saved in the same private sheet and emailed to the developer. If you add screenshots to your feedback, they're emailed to the Tuddle team with it, are only used to fix the problem, and are deleted once it's fixed. Screenshots can show your marks, so only add ones you're comfortable sharing. The same goes for anything you type in the "Anything else?" box under "How you like to study", along with your study settings, so popular requests can become new settings. "Tell us about you" is anonymous. If you answer it (your program, year and campus, and if you want, your gender, study hours, grade goal, how you found Tuddle and your major), the answers are saved in the private sheet without your name, email or Tuddle code, with only the week they came in, so the team knows who Tuddle is helping. Your Tuddle code is checked separately, only so the 2 free days for answering are given once, and it isn't stored with your answers. Your other study settings stay on your computer. When you send feedback, Tuddle also sends your list of deadlines (each one's course, title, date and whether it's marked done) and what it read from each syllabus, so the team can see what you see and fix it. You can untick "Share my deadline list" to leave it out. It never includes your marks or passwords, and it's only used to fix Tuddle. If you link a course site Tuddle can't read on its own yet (for example Top Hat or Pearson) from Tuddle's setup page or "Get started", Chrome asks you to allow that one site, and after that Tuddle's AI reads the pages you open there so their due dates and marks can be added to your plan, and those pages are sent privately to Tuddle's team so full support for that site can be built. Once, after you finish setting Tuddle up, it sends what it found to the Tuddle team one time so anything it got wrong can be fixed: your deadlines (course, title, due date, whether it's done and where it came from), what it read from each syllabus (grade weights and drop rules), and your marks with how they're weighted. This one-time check is sent without your name, email or Tuddle code (a random check id is used instead), is only used to fix Tuddle, and never happens again after that. You can turn it off before it happens in the Account tab ("Let my team check Tuddle's work once"). Apart from that, Tuddle never sends your deadlines or marks. To have your payment records deleted, email [email protected].
So that support for more course sites can be added, Tuddle tells the developer which of your course sites it recognizes but can't read yet (for example "Top Hat (ECO101)") which syllabi it couldn't read (the course code, the file's name and the problem), and short error messages from the last week saying which part of Tuddle failed (for example "Connect didn't load"), so problems get fixed even if you never report them. It also sends your course codes (for example "ECO101", never your marks) and how many times you opened Tuddle this week, so the developer can see which courses and programs use Tuddle. Your Tuddle code, Tuddle version and the name you entered in Tuddle's menu, if any, are sent with it. Your deadlines and marks are never sent with it. You can turn this off any time in Tuddle's menu under Account and payments.
If a syllabus file in Quercus can't be read (for example a scanned PDF), Tuddle emails a copy of that file to the developer so it can be fixed. Syllabus files you add yourself in Tuddle stay on your computer.
If you link a course site Tuddle can't read on its own yet, or paste a link to a course page in Tuddle's Help tab, Tuddle sends a copy of the pages you open there to the Tuddle team so full support can be built. It's only used to teach Tuddle how to read that site, it's never shared or sold, and it's deleted once support is added. The pages may show your marks. To stop, remove the site from Tuddle in Chrome's extension settings (Site access).
Your Tuddle code is made from your Quercus account number, scrambled so it can't be turned back into your ID, so you keep the same code, free trial and paid weeks if you reinstall Tuddle or use a new computer. The payments service stores when your code was first seen (so the free trial can't be restarted) and a random number from your installation (so a code works on one computer at a time).
Removing Tuddle from Chrome deletes everything it stored. To remove the calendar too, delete the "Tuddle" calendar in Google Calendar settings.
If this policy changes, the new version will be posted on this page with a new date at the top.
Questions: contact the developer at [email protected].