ScholarOS is a browser extension that copies your upcoming assignments off your college's learning management system and into a planner. This page explains what it reads, what it keeps, and the only two situations in which anything leaves your computer.
The short version: there is no ScholarOS server. No account, no sign-up, no analytics, and nowhere for your data to be sent, because nothing was ever built to receive it. Everything ScholarOS knows about you sits in your own browser's storage on your own machine.
ScholarOS requests no access to any website when you install it. The install prompt asks for no websites at all, because at that moment ScholarOS is allowed to read nothing.
It asks for one school at a time. When you pick your school, your browser asks whether ScholarOS may read that school's web address, and only that address. Nothing else on the internet is included: not your email, not your bank, not your search history. Settings lists every school you have granted, and removing one there hands the access back to your browser.
On a school you have added, and only after you have signed in yourself, ScholarOS picks out:
That is the whole list. On Brightspace and Moodle, ScholarOS reads the assignment listing already on your screen. On Canvas and Blackboard, it asks your school's own planner or calendar feed for the same details, at the same school address, using the session you are already signed into. It does not crawl your course or follow links to other sites.
cookies permission, so the browser does not give it access to them.history permission.calendar.events. It has no access to Google Drive, Gmail, or your contacts, and it never asks for them. It never requests the name, description, location, or guest list of any event on your calendar (section 4). If you never connect Calendar, there is no consent screen because there is nothing to consent to.On your device, in your browser's own extension storage. Three places:
| Store | What is in it |
|---|---|
chrome.storage.local | The import review queue, your import-window setting (how many days ahead to scan), your Gemini API key if you have entered one, the schools you have added, your licence key and the date your trial started. Google Calendar: whether it is connected, its two switches, when due dates last synced and whether that worked, whether this copy of ScholarOS has written any due dates, whether your Calendar was connected before version 0.11.0, and a random ID for this copy of ScholarOS. Notifications: the switches and morning time, a list of notifications already shown with the item and time each was for (each entry is dropped a week after that time), a copy of your Smart Plan study session times, titles and task numbers, and whether you pressed Not now on the dashboard card |
IndexedDB, database ScholarOS_DB | Your saved tasks, reminders (with their time, if you set one), and class folders, including any document links you have pasted, plus the completion timings described below |
| Local storage for the ScholarOS dashboard | Smart Plan: your preferences, the latest plan, your note for the planner, the assignments you picked to start early, and any assignment plan you saved from a chat. A plan built around your calendar records how many busy stretches it avoided; the busy times themselves are not kept. Assignment chats: one conversation per assignment. Clearing a chat deletes it, and chats for deleted assignments are removed the next time the dashboard opens |
Completion timings. When you mark an assignment finished, ScholarOS records four numbers: which task it was, which class it belonged to, when it was due, and when you finished it. That is the whole record: no title, no notes, no content. It exists so Smart Plan can notice that you finish one class's work the night before and another's three days early, and schedule accordingly. Marking a task unfinished again, or deleting it, deletes its timing record. "Forget all of it" in Smart Plan erases the lot at once.
Nothing is uploaded or backed up by ScholarOS. If your browser profile syncs across your own devices, your browser does that under your own account. The only copies outside your browser are the calendar entries described in section 4, and only if you connect Google Calendar.
There is no ScholarOS account, no ScholarOS login, and no ScholarOS server holding a copy.
ScholarOS has two outbound network paths, and both go to Google. Both are optional and both are off until you switch them on: the Gemini API, under an API key you supply yourself, and Google Calendar, if you connect it.
This powers four optional features: Smart Plan, the chat inside each assignment, pasting text or a link to turn it into a task, and pasting a syllabus to fill the Import Inbox. All are off until you paste your own free Gemini key into Settings. Without a key, the features tell you so and do nothing. No request is made.
When you do use them, and only at the moment you click the button:
Those requests go to Google under your API key, so they are governed by your own agreement with Google and by Google's API terms and privacy policy. ScholarOS has no server to receive the response on. Nothing is sent to Gemini in the background, on a schedule, or without you starting it.
This is off until you press Connect in Settings. Nothing about Calendar happens before that.
When you press Connect, two things are asked for and both are shown to you by your browser: permission for ScholarOS to reach Google's API (www.googleapis.com and oauth2.googleapis.com), and a Google sign-in asking only for the calendar.events scope. That scope lets an app see and change events on your calendars. ScholarOS uses it to write two kinds of entry to your calendar and to read when your other events start and end, as described below. It never changes or deletes an event it did not create. It gives no access to your contacts, your email, or anything else in your account.
What ScholarOS writes. Every entry it writes carries a private tag marking it as ScholarOS's, and ScholarOS only ever changes or deletes entries carrying that tag.
Due dates are written whenever your task list changes while the ScholarOS dashboard is open, and study blocks when a plan is made, as long as “Add due dates and plans to my calendar automatically” is on. With it off, nothing is written until you press Sync due dates now in Settings or Send to Google Calendar on a plan.
What ScholarOS reads. When you make a Smart Plan with “Plan around my calendar” on, ScholarOS asks Google for the events on your main calendar between now and the end of the plan. For each event it requests only Google's ID for it, its start and end time, whether it is cancelled or marked free, whether you declined it, and ScholarOS's own tag if it has one. The name, description, location, and guest list are never requested, so they never reach your computer. ScholarOS leaves out cancelled, free, declined and all-day events and its own entries, merges the rest into busy stretches, and sends those start and end times to Gemini under your key, as described above. The busy times are not saved. ScholarOS also looks up its own tagged entries before writing, so it updates them instead of adding duplicates.
Google Calendar is part of the $2.99 unlock and is included in the 14-day trial (section 8).
Pressing Disconnect in Settings first asks whether to remove the due dates ScholarOS added, from today onward. Then it stops all of this, tells Google to forget the grant so it stops showing in your Google account's connected-apps list, and hands Google's web addresses back to your browser. Study blocks, past due dates, and due dates you chose to keep stay on your calendar until you delete them in Google Calendar. Each one says “Added by ScholarOS.” or “Scheduled by ScholarOS.” in its description.
ScholarOS's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used only to put your due dates and study plan on your calendar and to plan around the times you are already busy. It is never sold, never used for advertising, and never read by a person.
Your key is stored in your browser's extension storage, on your device, in plain text. That is the same way any browser extension setting is stored. It is sent to Google, and to nowhere else, as part of the API requests above. You can clear it at any time by emptying the field in Settings. You can also revoke it entirely at Google AI Studio, which takes effect regardless of what ScholarOS does.
ScholarOS can remember which documents belong to which class. A document reaches it as a link you paste in yourself. ScholarOS stores that link with the task or class, on your device, and opens it in a new tab when you click it.
ScholarOS never fetches, downloads, reads, or previews the contents of a linked document. It stores a string of text and opens it in a tab, which is the same thing a bookmark does.
Notifications are off until you press Turn on notifications, on the dashboard card or in Settings, and your browser asks whether ScholarOS may display notifications. After that, each kind has its own switch in Settings: a morning summary of what is due and overdue, a heads-up 24 hours and 2 hours before an assignment is due, reminders at their time, and study session starts from your Smart Plan, which stays off until you switch it on.
ScholarOS decides what to show on your own computer, with a check once a minute while your browser is running. Your operating system displays the notification through the browser. Nothing about notifications is sent anywhere, and there is no push service. What ScholarOS keeps to avoid showing the same notification twice is listed in section 3.
| Permission | Why |
|---|---|
sidePanel | Shows the planner in the browser's side panel next to your LMS page |
storage | Saves your tasks, settings, and review queue on your device (section 3) |
scripting | Points ScholarOS at a school the moment you add it, instead of at the next browser restart. It is never used on a site you have not added |
alarms | Wakes ScholarOS once a minute, on your device, to check whether a notification is due (section 6). It adds nothing to the install prompt and sends nothing anywhere |
identity | Signs you in to Google, only if you connect Google Calendar. Requests the calendar.events scope and nothing else |
notifications, asked for when you press Turn on notifications | Shows the desktop notifications you switched on (section 6). Never requested at install |
| Access to the school you choose | Reads your assignments from the school you are signed into (section 1). Granted by you, one school at a time, and revocable in Settings |
Access to www.googleapis.com and oauth2.googleapis.com, asked for when you press Connect | Reaches Google Calendar (section 4). Handed back when you press Disconnect |
There are no others. In particular there is no tabs, no activeTab, no cookies, no history, and no OAuth scope beyond calendar.events, which is requested only if you connect Google Calendar. ScholarOS has never had a server, and adding Canvas, Blackboard and Moodle did not change that: those systems are read through your own school's web address, using the session you are already signed into, and nothing is sent anywhere else.
ScholarOS costs $2.99 once, after a 14-day trial, with no account and no subscription. Payment is handled by Stripe on Stripe's own hosted page in your browser. You receive a license key and paste it into Settings, where it is stored locally like any other setting.
Card numbers, billing addresses, and payment details never pass through the extension and are never visible to it. ScholarOS's entire relationship with a paying student is one license key sitting in their own browser storage.
The license key is checked on your own device and is never sent anywhere. Validation is a signature check performed in your browser, so it works with no internet connection and produces no network request. ScholarOS learns nothing about when or whether you use it.
The trial starts the first time you open ScholarOS and needs no card, no email address, and no sign-up. When it ends, the planner keeps working in full and only the paid extras stop, Google Calendar among them. If your Google Calendar was connected when version 0.11.0 first ran, you keep sending study plans to it free.
ScholarOS is built for college students and is not directed at children under 13. It collects no personal information from anyone, of any age, on any server. See section 3.
Uninstall the extension. Your browser deletes the extension's storage with it, which is every piece of data described in section 3.
If you connected Google Calendar, press Disconnect in Settings first so Google forgets the grant, and choose to remove the due dates ScholarOS added if you want them gone. You can also remove ScholarOS later from the third-party access page of your Google account. Anything ScholarOS wrote that you kept stays on your calendar until you delete it in Google Calendar (section 4).
There is no account to close and no data-deletion request to file. If you entered a Gemini key and want to be thorough, revoke it at Google AI Studio as well. That is a key Google issued to you, not to ScholarOS.
If this policy changes, the date at the top of the page changes with it, and the updated version replaces this one at the same public address. Material changes to what leaves your device will be called out in the extension's release notes.
Questions, corrections, or anything in this policy that does not match what you observe the extension doing: