1. The short version
- DSAtlas tracks your coding practice from the public profiles you connect. We never ask for a coding profile password and never read source code from those profiles. Code you enter in DSAtlas assignments is saved and evaluated as described below.
- Your profile and leaderboard visibility start off. Nothing about you is shown to other students until you turn it on.
- If your college or training provider adds you to its DSAtlas workspace, its staff can see your own practice progress. See Who can see your data.
- There are no ads, no tracking pixels and no third-party cookies. We count page visits and measure page speed without cookies. We do not sell or rent personal data.
- You can export your data, disconnect a coding profile or delete your account at any time from Settings.
- If you are under 18, a parent or guardian must agree before you use DSAtlas.
2. Who we are
DSAtlas (“DSAtlas”, “we”, “us”) runs this service and decides how and why your personal data is processed. Under India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”), we are the Data Fiduciary. Where the EU or UK GDPR applies, we are the controller.
Contact us about anything in this policy at privacy@dsatlas.in. See Complaints and Grievance Officer for formal complaints.
3. What we collect
When you create an account
- Email address (required) and name (optional).
- If you sign up with email: a password, which we store only as a salted scrypt hash. We never store or see it in plain text.
- If you sign in with Google: your Google account ID, name, email address and profile photo link. We ask Google only for your basic profile and email address, and we do not keep Google access tokens.
- Whether you are 18 or older, or under 18 with a parent’s or guardian’s agreement. We ask only for that answer, never your date of birth.
- A record of each agreement you accepted: its version, its exact wording and the time.
What you choose to add
- A profile photo you upload (stored in our database, at most 150 KB), a short bio (up to 160 characters) and your public handle. The handle is generated for you and you can change it.
- College, graduation year, branch and section. All of these are optional and self-declared. We do not verify enrolment.
- Problems you mark as done or skip, and your practice-sheet progress. Manual completions are shown as self-reported and never count towards leaderboard points.
- Notes you write on problems, questions you save under My questions, contests you bookmark and the goals you set.
- Roadmaps you follow, saved learning plans, progress you report, question collections and review notes. We also store your assigned roadmap targets, your choices about sharing progress, and the practice summaries and transfer challenges used for recommendations. Your data download includes these records and your organization sharing-consent history. It does not include hidden assessment answers or restricted source content.
- Feedback you send us: your message, the page you sent it from and your role.
If an organization adds you
A college or training provider that has an organization on DSAtlas can add you by name and email address, with your department and batch. If you have no account yet, one is created for you and your sign-in details are sent to that address. You are asked to agree to these terms the first time you sign in. If you already have an account, you are invited and nothing is shared until you accept.
From the coding profiles you connect
You can connect GitHub, Codeforces, LeetCode, GeeksforGeeks, Codewars, AtCoder, Topcoder, HackerEarth, Code360, Exercism. When you do, we store your username and profile link, and then read only information the site makes public. HackerRank, InterviewBit profile links are saved as you enter them and never read:
- Solved counts by difficulty and topic, and which problems you have solved.
- Submission results: the problem, the verdict (for example, accepted), the language and the time. We never read your source code.
- Contest history and ratings, your activity calendar, and on LeetCode your public ranking, badges, community statistics, display name and avatar.
- On GitHub: your public profile, links and profile README, which are used to confirm that the profile is yours, and your public repositories’ names, languages, topics, stars and dates.
Private GitHub repositories, only if you choose
If you install the DSAtlas GitHub App on repositories you pick, we also store the same details about those repositories, including private ones: name, languages, topics, stars and dates. We never read their code or files. They stay hidden until you choose to show one, and they are deleted when you remove them or disconnect.
The DSAtlas Connect browser extension, only if you install it
The extension reads your own LeetCode profile and submission results while you view them in your browser, and sends DSAtlas the figures shown there. It never reads page contents beyond those figures, your cookies or what you type. Pairing it stores a hash of its credential, never the credential itself.
For some coding profiles you can sign in to prove ownership instead of pasting a link. When you connect GitHub this way, GitHub shows you the access we ask for (read-only profile and email). We check your verified email addresses once, then discard the access token without storing it or the email list. Codeforces sign-in confirms your handle, and we do not store a Codeforces token either.
To confirm a profile is yours
- Verification codes or markers you place on your coding profile. Codes are stored only as a one-way hash, and a marker links to a DSAtlas page that shows nothing about you.
- When you click “Solve on …” for a problem we recommended: which problem and when. A solve shortly afterwards is one signal that the profile is yours. We keep these records for 30 days.
- If you ask for a manual review: the request, the outcome and any note the reviewer writes.
Generated while you use DSAtlas
- Sign-in sessions, the time you were last active (used to decide how often to refresh your profiles), which recommendations we showed you, and a log of sync attempts and errors.
- Security and audit records of important account events. Examples are connecting, verifying or disconnecting a profile, role changes and account deletion.
DSAtlas coding activities
When you write code in a DSAtlas activity, we save your code, chosen language, submitted attempts, test results and scores. Draft answers also stay in this browser for crash recovery. Authorized faculty can review submissions within their student scope. Released results can contribute evidence to your skill profile and recommendations.
Evaluation sends your code and test input to the isolated execution service configured by DSAtlas. Hidden test input and execution output are withheld from student responses. Assessment answers and execution records are kept with the assignment until the account or organization is deleted. Your data download includes your code and permitted results.
Organization pilot requests
If you ask us about an organization pilot, we store the organization name, your contact name, email address, phone number and any message or source information you provide. Authorized DSAtlas administrators use these details and their follow-up notes to respond and manage the request. They can delete the request and its notes. A workspace or invitation already created from it is a separate record. To ask for deletion, contact privacy@dsatlas.in.
What we do not collect
Coding profile passwords or cookies, source code from external platforms, private profile data (other than GitHub repositories you choose to include), payment details, precise location, contacts or advertising identifiers. Our database never stores your IP address as it is: to limit sign-up and sign-in attempts, it keeps a keyed, one-way hash of it for about a day. Our hosting provider does see IP addresses and browser details when delivering pages (see Who we share it with).
4. Why we use it
We process personal data only for the purposes below. Under the DPDP Act the basis is your consent (section 6), or a legitimate use permitted by section 7 where noted. For readers covered by the GDPR, the equivalent basis is shown in brackets.
| Purpose | Data used | Basis |
|---|---|---|
| Create your account and keep you signed in | Email, name, password hash or Google ID, sessions | Consent (contract) |
| Track your progress over time | Connected usernames, public coding profile data, dated snapshots | Consent (contract) |
| Compare you with your batch and run opt-in leaderboards | Progress figures, college, batch, branch, visibility settings | Consent (contract) |
| Suggest what to solve next | Topics and problems solved, recommendations shown | Consent (contract) |
| Confirm a profile belongs to you, and stop impersonation | Markers, verification results, click-outs, review requests | Consent (legitimate interests) |
| Let an organization you joined support your practice | Name, email, department, batch, progress figures, targets | Consent (contract) |
| Keep your notes, saved questions, bookmarks and goals | What you write or save | Consent (contract) |
| Improve DSAtlas from your feedback | Your message, the page and your role | Consent (legitimate interests) |
| Send account emails, such as sign-in details from an organization | Email address, name, organization name | Consent (contract) |
| Keep the service secure and investigate misuse | Audit records, sessions, sync logs, hashed IP addresses for rate limits | Legitimate use under law (legitimate interests, legal obligation) |
| Comply with the law and respond to lawful requests | Whatever the request lawfully requires | Legitimate use under law (legal obligation) |
We do not use your data for advertising, sell it, build marketing profiles, or use it to train AI models. Recommendations and rankings come from fixed, published rules. No automated decision is made about you that has legal or similarly significant effects.
5. Who can see your data
Other students
By default, nothing. Two separate switches in Settings → Privacy change that:
- Public profile (off by default). Anyone with your link can see your name or handle, photo, bio, college, branch and graduation year, connected usernames, verification status and progress. Public profiles ask search engines not to index them. Your email and section are never shown.
- Leaderboard (off by default). Signed-in students can see your name or handle, rank and points on leaderboards.
With both switches off, your figures still count towards anonymous totals such as medians and your batch’s size, but your name is not shown. Anyone who knows a handle can confirm it exists through a profile badge link. The badge shows a solved count only for public profiles.
College staff
DSAtlas may give verified staff (faculty, placement officers or college administrators) a role at their college. If you select that college, its staff can see:
- Group statistics for its students, such as counts, medians, activity and topic gaps. Groups with fewer than five connected students are hidden.
- Only if you turned on leaderboard visibility: your name, handle and total solved.
- Only if you ask for a manual ownership review, or someone disputes a profile you connected: your name, email address, the coding profile username and its profile link, so they can review it.
Choosing a college does not let it see anything else. If you leave the college blank, no staff see you at all.
Organizations you join
If a college or training provider adds you to its organization on DSAtlas, or you accept its invitation, its administrators, managers, trainers and mentors can see your name, email address, handle, department, batch and your practice progress: solved counts, topics, activity, streaks, targets they set for you and a readiness summary. They can print or export this as a report. This is separate from your public profile and leaderboard switches, which still control what other students see. You can leave an organization at any time in Settings → Privacy, and it stops seeing your progress at once.
DSAtlas administrators
A small number of administrators can see operational data, such as sync health and connected usernames, to run the service and resolve disputes. They are bound by confidentiality.
7. Where it is processed
The application and database run in Mumbai, India. Some of our service providers, such as Google, GitHub, Resend and Vercel’s global network, may process data in other countries, including the USA. We transfer data only as the DPDP Act permits, and never to a country the Government of India has restricted. For readers in the EU or UK, these providers rely on recognised safeguards such as Standard Contractual Clauses.
8. How long we keep it
| Data | Kept for |
|---|---|
| Account, profile, settings and consent records | Until you delete your account |
| Progress history and snapshots | Until you delete your account or that coding profile’s history. Raw copies of site responses are cleared after 14 days |
| A disconnected coding profile | You choose when disconnecting: delete its history immediately, or keep it |
| Sign-in sessions | 30 days with “keep me signed in”, otherwise 12 hours. Expired sessions are deleted nightly |
| “Solve on …” click-outs | 30 days |
| Verification codes | Valid for 15–30 minutes. The one-way hash stays with the verification record until you delete your account |
| Notes, saved questions, bookmarks, goals, sync logs, recommendation history, reviews, feedback and browser-extension pairings | Until you delete them or your account |
| Hashed IP addresses used for rate limits | About a day. Deleted nightly |
| Request replay receipts | A 24-hour retry window; expired receipts are deleted by nightly maintenance. These hold request hashes and response references rather than form contents |
| Organization pilot requests and follow-up notes | Eligible for scheduled deletion after 90 days without an update, or earlier on a confirmed deletion request. Workspace and invitation records created from a request have their own lifecycle |
| Staff invitations addressed to an email | Eligible for scheduled deletion 30 days after expiry or revocation. Email is also removed from the invitation audit entry; membership and other security history remain separate |
| Your place in an organization | Until you leave, the organization removes you or you delete your account |
| Security and audit records, including events about connecting a coding profile, which name its username | 365 days from the event, even if you delete your account sooner. Indian rules require security logs to be kept for a year |
| Colleges you add to the college list | Kept. A college name is shared reference data, not personal data |
We keep a copy of the database for up to 14 days to recover from a failure. Deleted data can remain in that copy until it is replaced. It is not restored from it except to recover from a failure, and deletions are re-applied if that happens.
9. Your rights and how to use them
Under the DPDP Act you have the right to:
- Access a summary of your personal data and how we process it, and know who we have shared it with.
- Correct, complete or update it.
- Erase it, and withdraw consent at any time. Withdrawing is as easy as giving consent.
- Nominate someone to exercise these rights if you die or become unable to. Email us their name and how to reach them; we record it and act on their request once we have confirmed what happened.
- Complain to us, and then to the Data Protection Board of India.
If the GDPR applies to you, you also have the rights to restrict or object to processing, and to data portability. You can complain to your local data protection authority.
Do it yourself, right away
- Settings → Account & data: download a JSON export, or delete your account.
- Settings → My Account: correct your name, photo, bio and college details.
- Settings → Coding profiles: disconnect a coding profile. This stops all further reads, and you choose whether to delete its history.
- Settings → Privacy: turn the public profile and leaderboard off.
The export covers your profile, coding profiles, snapshots, topic statistics, sync history, practice progress, notes, saved questions, bookmarks, goals, feedback, organization memberships, verification records, click-outs, recommendations shown and consent records. For anything it leaves out, such as audit entries, email privacy@dsatlas.in. We will respond within the time the law requires. We may ask you to confirm your identity first, and we won’t charge you.
Withdrawing consent
Disconnect a coding profile to stop us reading it, or delete your account to end all processing. Withdrawing consent does not make earlier processing unlawful. We stop within a reasonable time and delete the data, except records the law requires us to keep (see How long we keep it). Deleting your account also removes the DSAtlas GitHub App from your repositories. Security records that mention your account keep only an internal identifier, not your name or email, until their retention period ends.
10. Children
Anyone learning to code can use DSAtlas. If you are under 18, the DPDP Act treats you as a child. A parent or lawful guardian must agree to these terms and this policy on your behalf. Right after you create your account, the Terms and Conditions window asks your age. If you answer “I am under 18”, you give your parent or guardian’s name, relationship, email and phone number there, and cannot continue until you do. We email them a link to confirm. We rely on that confirmation, because we cannot check it.
We do not show advertising to anyone, and we do not track children or monitor their behaviour. An account whose holder said they are under 18 stays private: its public profile and leaderboard switches cannot be turned on, and its “Solve on …” clicks are not recorded.
A parent or guardian can ask us to review or delete their child’s account at privacy@dsatlas.in. If we learn that a child’s account was created without that permission, we will delete it.
11. How we protect it
We protect your data with:
- HTTPS everywhere, and a strict Content Security Policy.
- Session cookies that scripts cannot read, and salted password hashes.
- Hashed verification codes.
- No stored coding profile access tokens, and database rules that block direct outside access.
- Staff access limited by role.
No system is perfectly secure. If a personal data breach affects you, we will tell you and the Data Protection Board of India as the DPDP Act requires. We will explain what happened and what you can do.
13. What you agree to at sign-up
You create your account with your email or Google first. Before anything else in the app, a “Terms and Conditions” window opens and holds all of it: the Terms of Service, this policy, the Data Use Agreement, and the emails we send and sharing your progress with your college once you add one. You choose whether you are 18 or older (or under 18 with a parent’s or guardian’s agreement) and press Agree, or Reject. Agree is a yes to all of it. Nothing is pre-selected, each statement is recorded on its own with its wording, you can switch any email or the sharing off at any time in Settings, and nothing is read from your coding profiles until you agree. Under 18, you get progress emails only and nothing is shared with a college. If you reject, you can sign out or delete the account.
- Your age. One of: “I am 18 or older.” or “I am under 18. My parent or lawful guardian has read the Terms of Service and the Privacy Policy and agrees to my using DSAtlas.”
- The Terms and this policy. “I have read and agree to the Terms of Service and the Privacy Policy.”
- How we use your data, the Data Use Agreement:
I agree that DSAtlas may store the college details and coding usernames I add, read my public coding activity, and include it in cohort aggregates, which staff of a college I choose can see as group totals. If I join a college's or training provider's DSAtlas workspace, its staff can see my own practice progress. My profile stays private unless I choose to share it.
Agreement version 2026-10-03-v8. Each time you connect a coding profile, you also confirm that it is yours and agree to its public activity being read (version 2026-09-25-v2). We record the exact wording, version and server time of each agreement.
14. Changes to this policy
When this policy changes, we update the effective date above. If a change affects what we collect or who can see it, we will show a notice in the app before it applies, and ask for your consent again where the law requires. Earlier agreements stay on record with their original wording.
15. Complaints and Grievance Officer
Grievance Officer, DSAtlas
Email: privacy@dsatlas.in
We acknowledge complaints within 24 hours and aim to resolve them within 7 days. If you are not satisfied with our answer, you can complain to the Data Protection Board of India.