DSA/Visual
LessonsProblemsConceptsMock interview
← Back to the site

Help & policies

PrivacyTermsRefundsContact

Policy

Privacy Policy

Last updated 16 November 2026

DSA Visual is a study site for data structures, algorithms, C++, Python and C#. This page explains what we store and why.

What we collect

  • Your sign-in identity. When you continue with Google or GitHub, we receive your email address, name and profile picture from that provider. We do not get your password, and we do not ask for access to your repositories, contacts or files.
  • Your study progress. Lessons you mark as learned, problems you mark as solved, drill answers and mock test best scores.
  • Your code. The latest code you write in the editor (C#, C++ or Python), saved per problem and language so you can continue on another device. Project Challenge submissions are also temporarily uploaded to run their tests.
  • AI features. What you type into the AI mock interview, the AI Interviewer, the Roadmap or the help assistant is sent to Google's Gemini API to produce a reply. For the AI Interviewer this includes the resume or project summary you paste, the interview transcript and your coding results. If Gemini is not available, the same text may be sent to Groq instead. We do not store the conversation or your resume; we keep only a count of AI requests per account (and per interview), to enforce the limits.
  • Your roadmap. The answers you give on the Roadmap page (goal, level, weeks, hours and the optional note) and the AI tips are saved to your account so they follow you to other devices. The note is also sent to the AI to write the tips.
  • Voice input. If you switch on voice in the AI Interviewer, your browser's own speech recognition turns speech into text. In Chrome and some other browsers, the audio is sent to Google (or your browser's maker) for that. We only receive the text.
  • Emails we send. When you join, we may send a one-time welcome email to the address you signed in with. We also use Resend to forward new contact messages to our support inbox so we can respond. That notification includes the message, the page you were on and the reply email you provided, if any. We do not send marketing emails.
  • Messages you send us. Contact us messages, with the email you give and the page you were on. You need to be signed in to send one, and the message is linked to your account. If you provide an email, an authorized DSA Visual admin may reply from [email protected]. We store sent replies with the original message in Supabase and use Resend to deliver them; replies come from the site’s support address, not an admin’s personal email address.
  • Visit statistics. We use Google Analytics and Cloudflare Web Analytics to count visits: the pages viewed, the referring site, the device, browser and approximate location (country or city). Google Analytics does not store IP addresses, and we have switched off its cross-device tracking (Google Signals) and ad personalisation. It sets cookies to tell repeat visits apart, and Google processes the data under its privacy policy. We do not send your name, email or code to analytics.
  • Plus payments. The Razorpay order and payment IDs, amount, date and how long your Plus lasts. Payments are handled by Razorpay; we never see or store your card, UPI or bank details.

How we use it

To sign you in, show you your own progress and code, run the AI features, give you Plus after a payment and answer your messages. We do not sell your data or show ads. Analytics is used only to understand which parts of the site are useful.

Where it is stored

Accounts and saved data are stored with Supabase, our database and sign-in provider. Database rules allow each signed-in learner to read and change only their own rows. Your browser also keeps your sign-in session and a copy of your progress and drafts in local storage; signing out removes the session and the account's copy from that browser.

Code you run

C# code in Solve and the personal compiler runs in your browser. C++, Python and Java code in Solve or Playground is sent with the test inputs to Judge0, an online code runner, and the result is returned to your browser.

When you choose Run tests in Project Challenges, the editable files and your signed-in account ID are temporarily stored in the DSA Visual Supabase project. The source is encrypted before it is stored and transferred. A GitHub Actions job decrypts it on an ephemeral runner and tests the fixed .NET project inside a resource-limited Docker container with network access disabled; no credentials are mounted in that container. The workflow artifacts contain encrypted data only. We delete the source and encryption key when the run completes, or within 24 hours if a run fails to finish. The test summary is kept with your run for up to 14 days. Project Challenge code is not sent to an AI model.

Deleting your data

To delete your account and everything saved with it, email [email protected] or use Help → Contact us from the email you sign in with. Payment records may be kept as long as the law requires. You can also revoke DSA Visual's access at any time from your Google or GitHub account settings.

Changes

If this policy changes, the date at the top of this page will change too.

DSA/VisualAnimated DSA lessons in C++, Python and C#.All topicsPrivacyTermsRefundsContact