1. Why there is no cookie banner
Consent banners exist because most sites set cookies that are not needed to deliver the service — advertising, analytics, and cross-site tracking. Those require your consent before they may be set.
Schollar sets none of them. The only cookies we use are strictly necessary to sign you in and keep you signed in. Cookies of that kind do not require consent, because without them the service you asked for cannot function. That is why you see no banner — not an oversight.
2. Cookies we set
| Name | Purpose | Type |
|---|---|---|
sb-<project>-auth-token(may be split across numbered parts, e.g. .0, .1, when the session is too large for one cookie) | Holds your authentication session so you stay signed in between page loads, and lets the server verify who you are. Without it you would be signed out on every navigation. | Strictly necessary. First-party. Set with SameSite=Lax and, in production, Secure so it is only ever sent over HTTPS. Cleared when you sign out or the session expires. |
That is the complete list. We set no other cookies of our own.
3. Other storage on your device
Cookies are not the only way a site can store data in your browser. For completeness, Schollar also uses the following. All of it stays on your device — none of it is transmitted to us or to anyone else.
| Key | What it stores |
|---|---|
sidebar-collapsed(local storage) | Whether you collapsed the sidebar, so it stays that way next visit. |
schollar:study-timer(local storage) | The state of a running study timer, so it survives a page reload instead of resetting. |
schollar-v2(cache storage / service worker) | Copies of pages and files so the app loads faster and can work offline. |
4. What we do not use
- No advertising or re-targeting cookies.
- No analytics cookies. Schollar loads no analytics script of any kind — not Google Analytics, not a privacy-friendly alternative, none.
- No social media pixels or share-button trackers.
- No device fingerprinting.
- No cross-site tracking, and no sharing of your activity with anyone.
5. Third-party cookies
Schollar embeds no third-party content, so no other company can set cookies through our pages.
The one exception is if you choose Sign in with Google. You are then sent to Google's own website to authenticate, and Google sets its own cookies on its own domain during that visit. Those cookies are controlled by Google under its own policies, not by us, and we cannot read them. Once you are returned to Schollar, only the session cookie in section 2 applies.
6. How to control cookies and storage
You are in charge of what your browser keeps:
- Delete or block cookies in your browser settings — usually under Privacy, Cookies, or Site data.
- Clear this site's data to remove the cookie, the local storage keys and the offline cache in one step. In most browsers: the padlock icon in the address bar → Cookies and site data → Delete.
- Sign out to clear your session cookie without touching anything else.
What happens if you block them: because our only cookie is the one that carries your session, blocking cookies for this site means you will not be able to sign in. Clearing site data signs you out and resets your sidebar and timer preferences; none of your tasks, notes or other content is affected, because that lives in your account, not on your device.
7. Changes to this policy
If we ever introduce a cookie that is not strictly necessary, we will update this page and ask for your consent before setting it. The “last updated” date at the top always reflects the current version.
8. Related policies and contact
This page expands on the cookies section of our Privacy Policy, which explains everything else we collect and your rights over it. See also our Terms of Service.
Questions about cookies: scholar.thimral@gmail.com