Cookie Policy · DSAtlas

1. The short version

DSAtlas uses only strictly necessary cookies, to sign you in and protect sign-in forms. It also uses local storage in your browser to remember display preferences, such as dark mode, that you choose yourself.

We use no analytics, advertising, social media or other third-party cookies, and no tracking pixels or fingerprinting.

The law requires consent for cookies that are not needed to provide a service you asked for, such as analytics or advertising. It exempts cookies that are strictly necessary for that service, and storage that keeps a setting you chose. Everything DSAtlas stores falls under those exemptions, so a banner would ask you to approve nothing.

If we ever want to use a cookie that is not strictly necessary, we will ask first. Refusing will be as easy as accepting, and nothing will be set until you choose.

3. Cookies we set

Cookies (all first-party, strictly necessary)
Name	Purpose	Duration
`authjs.session-token`	Keeps you signed in. Holds a random token that points to your session. It cannot be read by page scripts.	30 days with “keep me signed in”, otherwise until you close the browser (the session itself ends after 12 hours). Demo sessions last 4 hours
`authjs.csrf-token`	Protects sign-in and sign-out forms from cross-site request forgery.	Until you close the browser
`authjs.callback-url`	Remembers which page to return to after signing in with Google.	Until you close the browser
`authjs.pkce.code_verifier`	A one-time secret that proves a Google sign-in was started by you (PKCE).	15 minutes
`dsatlas-signup-consent`	Carries your sign-up agreement across the redirect to Google, so we can record it when you return.	15 minutes, deleted on return
`dsatlas_connect`	Links a GitHub or Codeforces connection back to your account and stops forged connection attempts. Signed, sent only to our connection endpoints.	10 minutes, deleted on return

On secure (HTTPS) connections, some names carry a __Secure- or __Host- prefix. That prefix tells your browser to protect the cookie further.

4. Preferences stored in your browser

These values stay in your browser’s local storage and are never sent to us. Most are written only when you change a setting away from its default.

Local storage (your preferences)
Key	What it remembers
`dsatlas-theme`	Light, dark or system theme, including your answer to the one-time dark mode question
`dsatlas-density`	Your density setting in Settings → Appearance
`dsatlas-sidebar`	Your sidebar setting in Settings → Appearance
`dsatlas-accent`	Your accent setting in Settings → Appearance
`dsatlas-text`	Your text setting in Settings → Appearance
`dsatlas-font`	Your font setting in Settings → Appearance
`dsatlas-motion`	Your motion setting in Settings → Appearance
`dsatlas-contrast`	Your contrast setting in Settings → Appearance
`dsatlas-links`	Your links setting in Settings → Appearance
`dsatlas-spacing`	Your spacing setting in Settings → Appearance
`dsatlas-accent-hex`	A custom accent colour, if you pick one
`dsatlas-tour`	That you finished or skipped the welcome tour, so it isn’t shown again

5. Third-party content

DSAtlas embeds no third-party scripts, iframes, videos, fonts or social widgets. The only outside content is images: Google profile photos and LeetCode avatars load directly from Google and LeetCode. As with any image on the web, those services receive your IP address and basic browser details when your browser fetches them. DSAtlas sets no cookies for them.

6. How to control them

Signing out ends your session. Deleting your account removes every session.
Settings → Appearance lets you reset your display preferences. Clearing this site’s data in your browser also removes them.
You can block cookies in your browser settings, but you will not be able to sign in without the session cookie.

7. Questions

Ask us at privacy@dsatlas.in. See the Privacy Policy for how we handle personal data generally.