Account details

Your email address, name, username and a hashed password if you sign up with one. Signing in with Google or GitHub gives us the name, email and avatar those services share; we do not receive your password there and do not keep their access tokens. Profile fields — institute, location, gender, birthday, website and social links, a short bio — are optional and stay empty until you fill them.

What you are preparing for

If you answer the question we ask after sign-up, or later on your profile: your goal — campus placements, product-company interviews, learning a language or just practising — how comfortable you are with coding problems, and the target companies or the language you pick. It is optional: skipping it leaves all of that empty, and you can change it whenever you like. The time you say you have each day, if you set it on the home page, is kept too, with each day's mission — the items it set and the ones you ticked or skipped by hand. If you save a placement target on the readiness page — or give a drive date when you answer the question — the company, the test and the date of the drive or interview are kept until you clear them.

What you do on the site

Every submission you make and the code in it, your saved drafts, bug-hunt fixes, duel results, pair-room sessions (the shared code and the chat), aptitude attempts, placement-test sittings, and the standing all of that gives you — XP, rating, streaks, roadmap progress and chests. When you are signed in we also note the first time you open each problem, and the first time its hints and its editorial are shown to you, so your skill profile can tell a solve you worked out from one you read first. When a coding submission fails, the explanation written for it (the judge's reading and the AI review) is kept with the submission. Your conversations with the workbench's tutor are kept per problem, with how far up its help ladder you went, until you clear them. On a bug hunt we also note the first time you open it and when you start its incident clock (so the time to your first accepted fix can be measured), keep the explanation written for each failed fix and the tutor conversation on that hunt, and keep the root-cause write-up you add after an accepted fix with its score. If you use the application tracker, we keep the applications you enter — company, role, stage, dates, the posting's link and your notes. If you start or join a study cohort, we keep its name, its invite code, its weekly goal, who is in it and since when, and which pair rooms were its group sessions; the cohort's progress is worked out from your accepted solves, not stored. Each system design you send for review on System Design Practice is kept with its review and score. Each virtual contest you start is kept — its problems, when it started and ended, its result and the CP rating it moved; the attempts on its board are your ordinary submissions. On a timed study-plan checkpoint we note when you started its clock.

Resumes

A resume you upload to your account is kept as its text, its sections, its analyses and the versions you save, until you delete it; the file itself is not kept. A resume you check on the resume page without an account is read in memory to score it and then discarded — neither the file, its text nor the report is stored; we count only that a check happened, its score and how long it took, with nothing that identifies you or the resume.

Mock interviews

The answers you type, the questions asked, and the scores and feedback produced. In a voice round your microphone audio is streamed live to the interviewer model; we keep the transcript of what was said, not the recording. If you start an explain-your-solution round after an accepted submission, the interviewer is given that problem's statement and your accepted code. If you choose one of your resumes for a Resume Deep Dive round, a copy of its content — without your name, email, phone, location or links — is kept with that round and given to the interviewer and the scoring model. A company simulation's interview round that covers your projects does the same with your most recently edited resume. If you run a company simulation, we keep the run — which of its rounds you opened and when, and whether its HR rounds are written or spoken — and its interview rounds tell the interviewer which company you are practising for.

Skill tests, placement tests and the webcam

Your answers and code, the score, and how the sitting was proctored: how many times it left full screen, the tab or the window, and what the webcam check found — no face in view, another person, a phone, looking away, or the camera switched off. A skill test or a placement test needs your webcam on, and the check runs entirely in your browser: no video, photo or face data is recorded, stored or sent to us or anyone else — only the name of what it found, when it found something.

The assistant

The questions you ask the site assistant and its replies, so a conversation can be picked up later.

Community

Posts, comments, polls, reactions, saves and follows. These are public by design — see "What is public" below.

Payments

Your plan, order references, amounts, currency and payment status, and your credits — the packs bought and what each spend paid for. Card, UPI and bank details go directly to Cashfree, our payment processor; they never reach our servers.

Technical data

Page views and feature events (a problem submitted, an interview started), error reports with the browser and page they happened on, and your IP address for rate limiting and abuse prevention. When a visit starts we also note how you arrived — the address of the site or app that linked here (only its name, such as google.com or linkedin.com), any campaign tags on the link, the first page you opened, and whether the device is a phone, a tablet or a computer — and when you sign in, how this browser first found CodeKairo is linked to your account, so we can see which sources bring people who join. If you allow it in the cookie banner, Google Analytics also counts visits: the pages opened, how you arrived, your device and browser, and an approximate location that Google works out from your IP address without storing the address. It is given a page's address without its query string (campaign tags excepted), and never your name, email or account.

Cookies and storage

A session cookie (__session) that keeps you signed in, a cookie and local-storage entry for your theme, and local-storage entries for your session token, editor preferences, unsent drafts, and the badges this browser has already celebrated (so each badge's animation plays once; it never leaves your browser). Those are all essential, so the site does not ask about them. Our own measurement keeps four more (traffic-first, traffic-last, traffic-active-at, traffic-attributed): where this browser first and most recently arrived from, when it was last used, and which accounts have already been credited, so a new account can be credited to what brought it. They are read only by this site and sent only to our own servers, never to anyone else. When that first arrival was a company's problem list or a placement test, one more (traffic-first-path) keeps that page's address, so the "What are you preparing for?" question can suggest the company — it never leaves your browser. Google Analytics is the one optional part: it runs only after you choose "Accept analytics" in the cookie banner, and then sets two cookies of its own on this site (_ga and _ga_<id>), holding a random number that tells one visitor's visits apart from another's. Your answer is kept in local storage (cookie-consent), and "Cookie settings" at the foot of every page changes it — choosing "Essential only" later stops Google Analytics and deletes its cookies. There are no advertising or cross-site tracking cookies.

Running the product

Judging your code and explaining a submission that failed, scoring interviews, keeping leaderboards, drawing the roadmap, matching duels — the things you came for.

Personalising it

Your dashboard and the plan on it that suggests where to start, built from what you told us you are preparing for; your skill profile, worked out from your own submissions, answers, tests and mock-interview scores and shown only to you, and the daily mission built from it — and, when you have a placement target (one you saved, or the first company you named in answer to the question), from your readiness for it and the days to its date, with a line on your home page showing that readiness, and the occasional suggestion to try a feature you have not used yet; the roadmap's standing, and which of its stages open early and in what order to work, from the same profile; reminders about a streak at risk or a skill due for review, and the weekly digest's suggestion for your goal; and the assistant's answers about your own account.

Talking to you

Verification codes when you sign up, password resets when you ask, and reminder emails (streak, daily problem, weekly digest) — each of which you can switch off from your profile.

Billing

Creating and honouring a plan, a pass or a credit pack, and matching a payment to your account.

Keeping it safe

Rate limits, spotting abuse of the judge or the community, and revoking sessions when a password changes.

Improving it

Aggregate analytics, from our own records and Google Analytics, about which features are used, how people find the site and where errors happen. We look at patterns, not individuals.

Hosting

Cloudflare serves the site from its edge network and, like any host, sees request logs. The API, the database, the cache and their backups run on Amazon Web Services, on one server in Mumbai, India.

Code execution

The code you run or submit, with the test input, is sent to Paiza.IO, a code-execution service operated from Japan, which compiles and runs it and returns the output to be judged. Nothing else about you goes with it.

AI models

Written interview questions, marking, transcript scoring, the review of a failed coding submission or bug-hunt fix, the scoring of a bug hunt's root-cause write-up, the review of a design on System Design Practice (the text you wrote and the components you chose), the workbench's tutor and the site assistant run on NVIDIA's hosted models: your answers, transcripts and assistant messages are sent to them for processing, and so is a failed submission's code with the problem's statement, its visible examples, the verdict and the error output, a bug-hunt fix's edited files with the hunt's report, logs and visible check results, a root-cause write-up with the accepted patch it explains, and, when you ask the tutor, your message, the conversation so far and — unless you untick sharing — the code in your editor (never the hidden test cases, and nothing that identifies you). Voice interviews run on Google's Gemini: your microphone audio is streamed to Google for the length of the round, and in an explain-your-solution round the problem's statement and your accepted code are sent with the round's brief.

Payments

Cashfree Payments processes subscriptions. They receive what a payment needs — amount, an order reference, and the details you enter on their form.

Sign-in

Google and GitHub, when you choose to sign in with them.

Push notifications

If you switch on notifications on a device (your profile → Edit → Reminders), your browser's own push service — Google's for Chrome and Edge on Android, Mozilla's for Firefox, Apple's for Safari, Microsoft's for Windows — gives us an address and two keys for that browser. A notification's title and text go to that service encrypted, so only your browser can read them. Switching it off or signing out on that device removes them.

Email

Brevo, a transactional email service, delivers verification codes, resets and reminders to the address on your account, and, if you apply to the ambassador programme, carries your application to our team's inbox.

Analytics

Google Analytics measures visits to the site, if you accept it — the technical data and cookies described above. It receives no account details, and its advertising features are not used.

See and correct

Most of your data is visible on your profile and dashboard, and the profile editor changes what you have told us. Your submissions, interviews and results are all listed on the site.

Opt out of email

Each reminder (streak at risk, daily problem, weekly digest) has its own switch on the profile page. Verification and password-reset emails cannot be switched off, because they exist to protect the account.

Opt out of analytics

Google Analytics runs only if you choose "Accept analytics" in the cookie banner; "Cookie settings" at the foot of any page turns it off again. It also stays off if your browser blocks it, and Google's opt-out add-on turns it off on every site. The site works the same either way.

Export or delete

On your profile, Edit → Privacy and your data: Download my data gives you, at once, one file with everything we hold about the account — your profile, code, queries, interviews and their transcripts, test scores, resumes, posts and activity. Test papers, answer keys and the proctor's integrity checks are part of the tests rather than your data, and are left out. Delete account removes the account and everything attached to it, at once, after you confirm with your username (and your password, if the account has one). You can also ask us to do either.

Withdraw consent

Stop using a feature and its data stops being collected; delete the account and it stops entirely. Where processing rests on your consent — the voice round's audio, for instance — you can end it at any time by ending the round.

Complain

If you think we have handled your data badly, tell us first and we will put it right. You also have the right to raise it with the data-protection authority in your country; for users in India, the rights under the Digital Personal Data Protection Act, 2023 apply.