Privacy Policy

Last updated:

DSA Tracker (“DSA Tracker”, “we”, “us”, or “our”) operates dsatracker.tech (the “Service”), an interview-preparation tool that tracks your progress across a curated set of coding problems. This policy explains, in plain language, what data we collect when you use the Service, why we collect it, who else ever sees it, and the controls you have over it. It applies to every visitor and account holder, including guest sessions.

We wrote this policy to be read, not skimmed past. It comes from the people who actually run the product. If something here is unclear, write to support@dsatracker.tech and we will explain it plainly or fix the policy if it is wrong.

1. Information we collect

We collect the minimum needed to run the Service. Everything below is either something you gave us directly, something the Service generates as you use it, or something a third-party platform returns when you ask us to fetch your own public stats from it.

1.1 Account information

  • Email address and password (if you sign up directly), or your email and name as shared by Google or GitHub if you use one of those sign-in options.
  • Display name and an optional public username.
  • Optional profile details you choose to add: college, social links (GitHub, LinkedIn, X/Twitter, personal website).

1.2 Progress and learning activity

  • Which problems you mark solved, starred, or flagged for revision, and when.
  • Free-text notes you attach to a problem.
  • Study sessions, streaks, and calendar activity generated as you use the tracker.

1.3 Preferences

Target role, experience level, focus topic, daily problem goal, and display settings (theme, layout density). These are synced to your account so they follow you across devices; for a guest session they stay only in your browser.

1.4 Third-party platform sync (optional, you control it)

If you choose to connect a username for LeetCode, Codeforces, CodeChef, GeeksforGeeks, AtCoder, or HackerRank, we fetch that platform’s own public profile data (solve counts, rating, badges) to show alongside your progress here. We never ask for or store a password for those platforms, and you can disconnect any of them at any time from your Profile.

1.5 Payment information

If you purchase Pro, payment is handled entirely by Razorpay, our payment processor. We never see or store your card, UPI, or bank details. We keep only the payment identifier Razorpay gives us (to match a receipt to a refund request) and the dates your Pro access starts and ends.

1.6 Support communications

If you contact us through the Support or Contact form, we keep the message and your email address so we can reply and so we have a record of the request.

1.7 Technical and log data

Like any web service, our servers and infrastructure providers automatically log standard request data (IP address, browser/device type, page requested, response status, and timestamp) for security, abuse prevention, and diagnosing errors. These logs rotate automatically and are not used to build an advertising profile of you.

1.8 Code you write and run

Python and JavaScript run inside your own browser and are not sent anywhere. Code in the other languages is sent, with the input you gave it, to a public code-running service so it can be compiled and run; only the code and the input are sent, with nothing that says who you are. When you press Submit on a graded problem while signed in, we keep that attempt (your code and the result) in your account so you can look back at it. Do not put passwords, keys or personal details in code you run here.

1.9 What other people can see

  • Leaderboard: your solved count, streak and level are shown to everyone using the app, including visitors without an account. Your username appears beside them only if you have switched your public profile on. Otherwise you are listed under a handle made from a number, such as @user126.
  • Public profile: only if you switch it on. It shows the sections you choose, and you can switch it off again.
  • Your email address, notes and code are never shown to other users.

2. How we use it

We use the information above only to:

  • Provide the Service: track your progress, render your dashboards, and keep your preferences.
  • Authenticate you and keep your account secure.
  • Process a Pro purchase and respond to a refund request.
  • Send you email about your account: a sign-in or password message, a purchase confirmation, a reply to your support message.
  • Occasionally ask how the product is working for you, by email. Every such email has a one-click unsubscribe link.
  • Send a practice reminder to your browser, only if you turned reminders on. You can turn them off in your browser or in the app.
  • Diagnose bugs, prevent abuse, and keep the Service reliable.
  • Understand, in aggregate, which pages and features are actually used, so we build the right things next.

We do not use your data to build an advertising profile, and we do not sell it to anyone. See Section 4 for the specific, named third parties we work with.

3. AI features

AI tools run only when you press their button, and only for signed-in accounts. Each one sends what it needs for that one answer to an AI provider named in Section 4: for skill analysis and insights, your selected role and level, a description of your skills if you wrote one, and a summary of what you have solved; for code review and mock-interview feedback, the code or answer you asked it to look at and the problem it belongs to. We never send your email address, password or payment details to an AI provider.

We keep the result, not what was sent. These providers handle each request under their own terms, which we do not control, so do not put personal details in text or code you send to an AI tool.

4. Who we share it with

We do not sell your personal data, and we do not share it for anyone else’s marketing. The only parties who ever see any of it are the infrastructure and processing services below, each of which handles only what it needs to do its one job:

  • Clerk runs sign-in and sign-up. It handles your email address, your password if you set one, and the Google or GitHub sign-in you choose. See Clerk’s privacy policy.
  • Supabase stores your account record, progress data, and preferences. See Supabase’s privacy policy.
  • Cloudflare hosts and serves the Service, and provides basic bot/abuse protection at the network edge. See Cloudflare’s privacy policy.
  • Razorpay processes Pro purchases. We never receive your raw card/bank details; see Razorpay’s privacy policy.
  • Resend delivers the emails we send (purchase confirmations, feedback requests, support replies). See Resend’s privacy policy.
  • Render runs the server that answers the app’s requests. See Render’s privacy policy.
  • Compiler Explorer, Judge0, Wandbox and JDoodle compile and run code in languages that cannot run in your browser. They receive the code and its input, nothing else; see Section 1.8.
  • Your browser’s push service (run by Google, Mozilla or Apple, depending on the browser) carries practice reminders, only if you turned them on.
  • Groq, Google Gemini, OpenRouter, and NVIDIA NIM process the specific, limited AI-feature payload described in Section 3, only when you trigger an AI feature.
  • Google Analytics provides aggregate, cookie-based usage analytics (which pages get used, roughly how many visitors), only after you accept our cookie-consent banner. You can decline it, or later change your choice, at any time; see Section 5.

We may also disclose information if required by law, to enforce our Terms of Service, or to protect the rights, property, or safety of DSA Tracker, our users, or the public.

5. Cookies & local storage

The full list, with lifetimes, is on the Cookie Policy page.

Strictly necessary (always on): sign-in cookies and a guest-session cookie, set purely to keep you signed in. Page scripts cannot read them and they are never used for tracking.

Local storage: your display preferences, guest-trial progress, and some cached responses are kept in your browser’s localStorage/sessionStorage so the app feels fast. This data stays on your device and is never transmitted to a third party.

Analytics cookies (optional): Google Analytics only runs after you accept our cookie banner, and only to measure aggregate usage. It is not used to identify you personally. You can decline it when the banner first appears, or clear your browser’s cookies at any time to withdraw consent.

6. Data retention

We keep your account data for as long as your account exists. If you delete your account (see Section 7), your progress, notes, and preferences are permanently removed immediately. This is not a soft delete with a recovery window. Payment records we are legally required to retain for accounting/tax purposes are kept only as long as that obligation requires, independent of your account’s existence. Standard request logs roll off automatically after a short, fixed window. Two things are kept apart from your account and are not removed when you delete it: messages you sent to support (with the email you wrote from), and survey answers (the link to your account is removed, the email you typed into the survey stays). Write to us and we will delete those too.

7. Your rights

You do not need to email us to exercise most of these: they are self-service, in the product.

  • Access & export: download everything you have tracked, as CSV or JSON, from Profile → Preferences.
  • Correction: edit your profile, preferences, and notes directly at any time.
  • Deletion: permanently delete your account and all associated data from the same Preferences screen, no email required. It takes effect immediately.
  • Disconnect a synced platform: remove a connected LeetCode/Codeforces/etc. username from Profile → Connections at any time.
  • Withdraw analytics consent: decline or later revoke the analytics cookie as described in Section 5.

Under India’s Digital Personal Data Protection Act, 2023 you can also ask us for a summary of the personal data we process and who we share it with, and nominate someone to use these rights for you if you die or cannot act yourself. If we do not resolve a complaint, you can take it to the Data Protection Board of India.

For anything not covered above (including a formal data-access or deletion request made on someone else’s behalf), write to support@dsatracker.tech and we will respond directly.

8. Security

We use industry-standard practices to protect your data: passwords are never stored in plain text, session credentials are kept in cookies inaccessible to page scripts, connections to the Service are encrypted in transit (HTTPS), and access to production data is restricted. No method of transmission or storage is 100% secure, so while we work hard to protect your information, we cannot guarantee its absolute security. If you believe your account has been compromised, contact us immediately at support@dsatracker.tech.

9. Children’s privacy

The Service is for adults preparing for technical interviews. You must be 18 or older to create an account, and we do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has given us personal information, contact us and we will delete it.

10. International use

DSA Tracker is built primarily for students in India, and our infrastructure providers may process and store data outside your own country: for example, Supabase and Cloudflare operate global infrastructure. By using the Service, you understand that your information may be processed in a country with different data-protection laws than your own.

11. Changes to this policy

We will update the “Last updated” date at the top of this page whenever this policy changes, and for a material change we will make a reasonable effort to flag it on the Service itself. Continued use of the Service after a change indicates acceptance of the revised policy.

12. Contact us

Questions about this policy, or a data request of any kind: email support@dsatracker.tech, or use the Contact page. We read every message ourselves.

DSA Tracker is an independent student project run by one person in India, who decides how your data is used and is the contact for any complaint about it. Complaints go to the same address; we aim to reply within 5 business days.