Mascot for macOS · Last updated 6 September 2026
Mascot processes your coursework and deadlines on your Mac and does not upload them to Mascot’s servers. Connecting Classroom sends requests directly to Google. Apple Calendar and Reminders may already sync through iCloud or another account you chose; Mascot reads their local copies. Typed deadlines stay in Mascot’s local files. You do not need a Mascot account for deadlines or installing packs. Optional creator accounts, pack submissions and website feedback send only the information needed for those features. There is no analytics or usage tracking.
Mascot is a macOS application made by one independent developer. There is no company and no team, so this page says "I" rather than "we". You can reach me at Thanachot10072550@gmail.com.
Only what you connect. Each source is optional and off until you enable it.
| Source | What is accessed | Why |
|---|---|---|
| Google Classroom | Your active courses, their coursework and due dates, and the status of your own submissions. Read-only. | To show your deadlines, and to detect work you have already turned in so Mascot stops reminding you about it. |
| Apple Calendar | Events in the single calendar you choose. | To show deadlines you keep in your calendar. |
| Apple Reminders | Reminders in the single list you choose, including whether each is completed. | To show deadlines you keep in Reminders, and to stay quiet once you tick one off. |
| Deadlines you type in | The title, due date and any link you enter yourself. | To remind you about them. |
Mascot requests three read-only Google Classroom scopes:
| Scope | Used for |
|---|---|
classroom.courses.readonly |
Listing the courses you are enrolled in. |
classroom.coursework.me.readonly |
Reading the coursework assigned to you and its due dates. |
classroom.student-submissions.me.readonly |
Checking whether you have turned a piece of work in, so a finished assignment stops driving reminders. |
Mascot cannot modify, submit, or delete anything in Google Classroom. It has no write access. It cannot see other students' work.
Builds with account-matched assignment links also request openid and
email to identify the Google account connected to Mascot. The app reads
your verified email address directly from Google and keeps it in memory while running.
It includes that address in Classroom links so your browser can select the same account;
those links may appear in your browser history. The address is not sent to Mascot’s servers.
If the account cannot be identified, Google’s account chooser opens instead.
Mascot’s deadline data is handled locally as described below. Google and your calendar or reminders provider keep the data you already store with them. Creator accounts, pack submissions and messages you choose to send are stored separately for those features.
| What | Where |
|---|---|
| Your Google sign-in token | The macOS Keychain, encrypted by the operating system. |
| Deadlines you typed in yourself | A file in your Application Support folder. |
| Preferences: which calendar you chose, what you have ticked off, where the mascot sits |
Standard macOS preferences on your Mac. |
| Your account sign-in token, if you have an account | The macOS Keychain, encrypted by the operating system. Your password is not stored: it is used once to sign in and then discarded. |
| Packs you submit to the store | On my server, privately, until they are accepted or you ask for them to be deleted. Only if accepted do they become public. |
| Mascot packs you install | A folder in your Application Support folder. Deleting a pack in the app removes it. |
| Coursework from Google Classroom, Calendar and Reminders | Held in memory while the app is running and discarded when it quits. It is not written to disk. |
Mascot uses the connections below for the features you choose to enable. The website also accepts optional feedback, described separately below.
These requests go directly from your Mac to Google's servers:
accounts.google.com for signing inoauth2.googleapis.com for renewing your sessionopenidconnect.googleapis.com for identifying the account to use in Classroom linksclassroom.googleapis.com and www.googleapis.com for reading your coursework
Once a day, Mascot asks studymascot.com for a small file saying
which version is current. The request carries no account, no identifier and
nothing about you or your deadlines: it is the same file every visitor to the
website loads. If a newer version exists, Mascot says so and offers a link.
It never downloads or installs anything by itself. You can turn this off in
Settings, under Version.
If Mascot quits unexpectedly, the next time it opens it asks whether to send a short report, and shows you the exact text before you decide. Nothing is sent unless you click Send. The report says which versions of Mascot and macOS you have, what kind of error it was, and the names of the functions inside Mascot that were running when it stopped. It does not include your name, your account, your deadlines, your files, or any identifier for your Mac: macOS keeps those in its own crash files, and Mascot builds its report from a short list of fields instead of sending those files.
Reports are stored on my server and only I can read them. You can turn the question off in Settings, under Version, and ask me to delete a report you sent.
Mascot has a store where you can install mascot characters other people have drawn. Opening it downloads a list of available packs, and installing one downloads that pack. Both are ordinary files on a website:
studymascot.com for the list of packs, and the packs themselvesThis happens only when you open the Store, never when the app starts. The request carries nothing about you: no account, no identifier, no coursework, nothing about your deadlines. Nothing is uploaded. GitHub, which serves that site, sees the request in the same way it sees anyone loading a web page; I am not given access to those logs.
An account exists for one reason: so that a person who draws a mascot pack can publish it, be credited for it, and later be paid for it. You do not need one to use Mascot. Deadlines, the mascot, reminders, the store and installing packs all work signed out, and always will.
If you choose to make one, signing in sends to my account server:
The server keeps your email address and a scrambled form of your password that cannot be turned back into it. Your Mac keeps only the sign-in token it gets back, in the Keychain, never the password itself.
Your coursework is not sent to the account server, whether you have a Mascot account or not. Classroom requests go directly to Google.
You can delete your account at any time by writing to me, and everything held for it goes with it.
This applies only to people who draw a mascot pack and send it in. If you are using Mascot to keep track of coursework, none of it touches you.
Submitting a pack uploads its artwork and a preview image to my server, along with the name, description and creator name you typed. They are stored privately: nobody but you and I can see a pack while it is waiting, which is the point of it being reviewed before anyone can install it.
Your coursework is not part of a submission any more than it is part of anything else. Only the files you chose and the words you typed are sent.
Mascot does not automatically send me your coursework, calendar, deadlines, app diagnostics or usage history. If you include personal details in a feedback message or email, I receive the details you choose to send.
For an iPhone reminder to appear on your Mac, enable iCloud Reminders on both devices using the same Apple Account. Then connect the relevant Reminders list in Mascot and give the reminder a due date. Apple handles the sync; Mascot reads the list on your Mac after the update arrives. It does not send reminders through a separate Mascot sync server. A Calendar or Reminders account from another provider follows that provider’s sync settings. Deadlines typed into Mascot’s quick-add box are local and do not sync to your phone.
Apple’s guide to setting up iCloud Reminders
Sending the feedback form uploads the message you type, optional contact details, and a “website” source label to Supabase, which hosts the feedback database for Mascot. The form does not attach coursework, app diagnostics or a device profile. The service receives ordinary network request information, such as an IP address, to handle the request. I use feedback to understand problems, consider suggestions and reply if you provide contact details.
Messages are not published in a public feed. Please include only information you want to share with me. To request deletion, email me with enough detail to identify the message; anonymous messages may be harder to identify. Sending feedback is optional and does not require an account.
Mascot's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: data obtained through Google APIs is used solely to provide the reminder features described on this site, is never transferred to any third party, is never used for advertising, and is never used to train models.
Right-click the mascot and choose Sign Out of Classroom. This deletes the stored token from your Keychain immediately. You can also revoke access at any time from your Google Account permissions page.
Sign out of Classroom and your Mascot account before uninstalling to remove their
saved sign-in tokens. Delete the app and its ~/Library/Application Support/Mascot
folder to remove installed packs and typed deadlines. macOS preferences are stored separately;
Calendar, Reminders and Google data remain with their respective apps and providers.
Contact me to request deletion of a creator account, submitted pack, feedback message or crash report.
Calendar, Reminders and Accessibility access are granted by you in System Settings and can be withdrawn there at any time. Mascot continues to work without them, with the corresponding features switched off.
Mascot is a study tool and may be used by students under 18. Used as a study tool it collects nothing about anyone and transmits nothing to me, regardless of age, and that is the whole app: no account is needed for any of it. An account is only for publishing a mascot pack, and if you are under 18 you should ask a parent before making one. If you are a parent or school with a question, please write to me. School IT staff will find the scopes, client ID and admin steps on the page for school IT.
If Mascot ever changes how it handles data, I will update this page and the date at the top will change. Material changes will also be noted in the app.
Questions about this policy: Thanachot10072550@gmail.com.