Privacy Policy

1. Who We Are

Moxaim is a product of Riverton Solutions LLP, a limited liability partnership registered in India. We operate the website and platform accessible at this domain ("the Platform"). References to "we", "us", or "our" mean Riverton Solutions LLP, which is the data fiduciary for the personal data described here.

For any privacy-related query, contact privacy@moxaim.com.

2. Information We Collect

2.1 Information you give us

• Account details: your email address and name, via email sign-up or through Google or Microsoft sign-in. Passwords are handled by our authentication provider and are never visible to us.
• Your CV: if you upload a CV, the file (PDF or DOCX) is sent to our server and the text is extracted. The file itself is deleted from our server within seconds of being parsed: we never keep the original document. What we do keep, saved to your account, is the text extracted from it, the details parsed out of that text (name, contact details, skills, experience), the CV analysis if one has been run, and the file's name and format so we can show you which CV is on file. This is what lets your CV follow you to a new device instead of having to be re-uploaded, and it is what your interview questions are tailored from. You can replace it, or delete it outright, at any time from your account page. See section 8.
• A CV you build with us: if you use the CV builder, everything you type into it is saved to your account so you can come back and keep editing. That is your name, the headline under it, your email address, phone number, location, any profile links you add (GitHub, LinkedIn, a portfolio), your summary, skills, roles, projects, education, and achievements. It is stored separately from any CV you upload, so the two never overwrite each other, and it is visible only to you. You can delete it at any time from the builder, and deleting your account deletes it too. See section 8.
• Your answers: what you type during an interview, MCQ, discussion, or coding round. If you answer by voice, a recording of that answer is captured and transcribed (see section 4).
• Contact and feedback: your name, email, and message if you write to us through the Contact page; and your rating, tags, and comments if you complete the post-assessment feedback survey.

2.2 Information generated when you use the Platform

These are saved to your account so your history and progress work:

• Date, role, target company, duration, and number of exchanges for each assessment.
• The AI-generated feedback report, including scores and written commentary on your performance.
• A question-by-question breakdown: each question you were asked, a short written summary of how you answered it, an assessment of that answer, and what a strong answer would have covered. The summary is written by the model. It is not a word-for-word record of what you said, which is only kept if you ask us to (see section 8).
• Per-topic scores: how you performed on each skill the interview tested, and whether it was tested at all. This is what your readiness plan and practice drills are built from.
• Speech and presence measurements: counts of filler words, how long you spoke, how many long pauses you left, and, if your camera was on, what proportion of samples showed you facing the screen. These are numbers derived during the session. No audio or video is kept.
• Per-round summaries: score, questions passed, and time taken. Your submitted code is not stored, only the outcome.
• Your MCQ paper: the questions you were given, which option you chose for each, and the correct answer. This is what lets you re-open a past report and still see which questions you got wrong and why, rather than only a score out of twenty-five.
• Round breakdowns: for a group discussion, system design, or case study round, the scored dimensions and the written assessment. The conversation itself from those rounds is not kept (see section 2.2.1).
• The list of questions you were asked, so a repeat interview doesn't re-ask them.
• The number of proctoring violations recorded during the session (see section 3).
• The name and years of experience you gave at the time of the assessment.
• An internal record of AI processing cost per session, used for our own capacity planning.
• Which model produced your report, and the version of the report format. We keep this so an old report can still be read correctly after the format changes.

2.2.1 Your interview transcript (only if you turn it on)

The word-for-word transcript of an interview is not kept by default. It is used to generate your report and is then discarded. The same is true of the conversation in a group discussion, system design, or case study round, and of any notes you write in the scratchpad during one.

While an assessment is still open, it is held on our servers. An assessment can be paused between rounds and picked up later, for up to seven days, and that is only possible if we keep your progress somewhere you can reach from any device. So from the moment an assessment starts until it finishes or its window closes, we store an in-progress record of it: which round you are on, the results of the rounds you have finished, and the conversation so far. It is deleted when your report is generated or when the assessment closes, whichever comes first. This is separate from the 90-day setting below, and it applies whether that setting is on or off. See section 8.

You can choose to keep it. On your account page there is a setting called Keep my interview transcripts. It is off unless you switch it on. With it on, the full transcript of each interview from that point onward is stored against your account for 90 days and then deleted automatically. Turning the setting back off deletes every transcript we are holding for you immediately, and stops any more being kept.

It exists because the summary in your report is the model's account of what you said rather than your own words. If you want to re-read an answer, or question a score you think is wrong, the transcript is the only thing that can settle it. That is worth having and it is also more personal data than most people need us to hold, which is why the choice is yours and the default is to keep nothing.

2.3 Information collected automatically

• Server logs: our hosting provider records IP addresses, browser type, and request timestamps for security and diagnostics. These are retained for up to 30 days.
• Local browser storage: your sign-in session and a snapshot of any assessment in progress. Your CV is not among these: it is held on your account, not on your device. Itemised in full in the Cookie Policy.
• Assessment-in-progress snapshot: while an assessment is running we also mirror that snapshot to our database at a few checkpoints, so a crashed browser or a dead laptop does not cost you the session. It contains the conversation so far. It is deleted the moment your report is generated, and any snapshot left behind by an abandoned assessment is deleted automatically within 12 hours whether you come back or not.

2.4 What we do not collect

• We do not see or store your password.
• We do not process payments and hold no card, UPI, or bank details.
• We do not use third-party analytics, build behavioural profiles, or track you across other sites. We count page views on our own servers to see which pages are used; that count holds no cookie, no IP address and no identifier that outlives your browser tab, so it cannot be tied back to you.
• We do not sell, rent, or trade personal data, whether to advertisers, recruiters, or anyone else.
• We do not record or store webcam video, and we do not store your voice recordings.

3. Proctoring, Your Camera, and What Leaves Your Browser

Assessments are proctored to keep results meaningful. Before an assessment begins you are shown exactly what this involves and must explicitly agree; you can decline and simply not take the assessment.

Your camera

Your webcam is switched on for the duration of the assessment and analysed entirely inside your browser. The video stream is never uploaded to our servers, never sent to a third party, and never recorded, not as video and not as stills.

The analysis is face detection, not face recognition. It determines whether a face is present in the frame and roughly where it sits; it does not identify you, does not match you against any database, and creates no biometric template or faceprint. We could not identify a person from what it produces.

What is actually recorded

Only derived signals leave your browser, and only as counts and statistics:

• Number of times you switched tabs, the window lost focus, or fullscreen was exited.
• Number of times no face, or more than one face, was detected in frame.
• Whether camera access was denied.
• Aggregate presence statistics (roughly how often you were centred in frame), which feed the body-language section of your feedback report.

A single violation count is saved to your assessment record. If you decline camera access, the assessment cannot start; if you revoke it mid-way, that is logged as a violation.

4. Voice Answers and Your Microphone

Speaking your answers is optional, and you can type instead throughout. When you do use voice, two things happen in parallel:

• Your browser's built-in speech recognition produces a live transcript and speech statistics (filler words, long pauses) that feed your communication score. This is a browser feature, not ours, and you should know that Chrome and Edge send the audio to Google's speech servers to do it, under Google's own privacy terms. Firefox and Safari behave differently. We never receive that audio.
• A recording of the answer is captured and passed through our server to OpenAI's transcription service, which is materially more accurate. The audio is held in memory only, forwarded straight on, and never written to disk or stored by us. Only the resulting text continues into the interview.

If you decline microphone access, voice answering is unavailable and you type instead. Nothing else about the assessment changes.

The transcribed text of a spoken answer is treated exactly like a typed one. It is discarded with the rest of the transcript when your report is generated, unless you have turned on transcript retention (section 2.2.1).

5. How We Use Your Information

• To generate interview questions tailored to your CV, target role, and company.
• To evaluate your answers and produce your feedback report and scores.
• To run the CV analysis and Career Compass domain-match features.
• To keep your history so you can track progress across assessments.
• To maintain assessment integrity through the proctoring signals in section 3.
• To operate credits and access control, and to prevent abuse of our AI and compute capacity.
• To respond to your enquiries and act on your feedback.
• To diagnose technical problems and keep the Platform secure.
• To meet obligations under Indian law, including the IT Act 2000 and the DPDP Act 2023.

We do not use your CV, answers, or results to train any AI model of our own, and our AI providers do not train their models on data submitted through their APIs.

6. Third-Party Services

Running the Platform means certain data is processed by the following providers, each under its own privacy terms:

Anthropic: question generation, evaluation, feedback

Your CV text, your answers, and your assessment content are sent to Anthropic's Claude models. Anthropic does not train its models on data submitted via its API. See Anthropic's Privacy Policy.

OpenAI: speech synthesis and transcription

The text of each interviewer question is sent to OpenAI to be spoken aloud. If you answer by voice, the audio of your answer is also sent to OpenAI to be transcribed. See OpenAI's Privacy Policy.

Google: browser speech recognition

Not a service we integrate, but worth stating plainly: on Chrome and Edge, the browser's own speech recognition sends microphone audio to Google while you are speaking an answer. This is a function of your browser, governed by Google's privacy policy, and outside our control.

Supabase: accounts and database

Authentication and your saved assessment history are hosted with Supabase, with row-level security so your rows are readable only by your own account. See Supabase's Privacy Policy.

JDoodle: sandboxed code execution

In coding rounds, the code you write is sent to JDoodle to be compiled and run against test cases. Code submissions may be retained by JDoodle under their terms, so please don't put personal or confidential information in code.

Hosting

The Platform is served by a third-party hosting provider, which processes connection metadata (IP address, request headers) to route and protect traffic.

Payments

We do not currently process payments and hold no payment information. If paid plans launch, this policy will be updated to name the payment processor before any such data is collected.

7. Campus and Institutional Programmes

Some students reach Moxaim through a programme arranged with their college or institution. If that applies to you, we additionally hold your institutional email, the organisation you belong to, your assessment credits, and a log of which rounds you started and completed with their scores.

8. Retention and Deletion

• Your CV file: deleted from our server within seconds of being parsed. We never retain the original PDF or DOCX.
• Your CV text, parsed details, and analysis: kept on your account until you replace it with a newer CV or delete it. Uploading a new CV overwrites the old one, and we do not keep previous versions. To delete it, open your account page and use Remove CV; that erases it from your account, not just from the device you are using. Deleting your account deletes your CV with it.
• A CV you build with us: kept on your account until you delete it, because it is a document you come back to and edit rather than a one-off upload. We keep only the current version, not a history of your edits. Deleting your account deletes it with everything else.
• Voice recordings and webcam video: never retained. A voice answer is transcribed and the audio is discarded; camera frames are analysed in your browser and never uploaded at all.
• An assessment still in progress or paused: the in-progress record described in section 2.2.1, including the conversation so far, is kept until your report is generated or the assessment's seven-day window closes, whichever comes first, and is then deleted. Abandoning an assessment and starting over deletes it immediately. A copy is also held in your own browser so the round you are sitting survives a reload or a lost connection; itemised in the Cookie Policy.
• The record of the assessment itself: which rounds you started and finished, when, whether a report was issued, and when the window closes. This is what lets you pause and return, stops one credit producing two reports, and lets us answer you if something goes wrong. It is kept with your account history and is deleted when you delete your account.
• Your interview transcript: discarded when your report is generated, unless you have switched on Keep my interview transcripts on your account page. With that on, transcripts are kept for 90 days and then deleted automatically. Switching it off deletes the ones we hold straight away. See section 2.2.1.
• Assessment history and feedback reports: kept on your account until you delete them from your account page or ask us to delete your account. This includes the question-by-question breakdown, the per-topic scores, and the speech measurements described in section 2.2. Clearing your history removes all of it together, including any transcripts attached to those sessions.
• Assessment-in-progress snapshots: deleted when the assessment completes. An abandoned one is deleted automatically within 12 hours.
• Server logs: up to 30 days.
• Contact enquiries and survey responses: up to 2 years, so we can follow up and act on patterns in the feedback.

To delete your account and everything associated with it, email privacy@moxaim.com from your registered address with the subject "Delete My Account".

9. Your Rights

Under the Digital Personal Data Protection Act, 2023 and the IT (Reasonable Security Practices) Rules, 2011, you may:

• Access: obtain a copy of the personal data we hold about you.
• Correct: have inaccurate or incomplete data fixed.
• Erase: have your data deleted, subject to any legal retention duty.
• Withdraw consent: at any time, and as easily as you gave it. Every one of these is a control on your account page, under Your consent: stop transcripts being kept and delete the ones we hold, delete the CV you uploaded, delete a CV you built here, or delete your account and everything in it. Proctoring is asked for per assessment, so declining it there withdraws it. Withdrawing does not undo processing already carried out lawfully.
• Nominate: name someone to exercise these rights on your behalf if you are unable to.
• Complain: to our Grievance Officer, and thereafter to the Data Protection Board of India.

Email privacy@moxaim.com with the subject "Data Rights Request". We respond within 30 days.

10. Children's Privacy

Moxaim is intended for users aged 18 and over, and we do not knowingly collect personal data from anyone younger. Under the DPDP Act 2023, processing a child's data requires verifiable parental consent, and behavioural monitoring of children is restricted, which is why under-18s should not use a proctored assessment. If you believe a minor has used the Platform, contact us and we will delete the data.

11. Security

We encrypt all traffic in transit over HTTPS, keep every AI and service key on the server so none is exposed to your browser, gate sensitive endpoints behind authentication and rate limits, enforce row-level security so accounts cannot read each other's data, and execute submitted code in an isolated sandbox. Details are on the Data Security page.

No system is perfectly secure. Please avoid putting sensitive personal information (identity numbers, financial details, health information) into your CV, your answers, or your code.

12. Changes to This Policy

We may update this policy as the Platform changes. The "Last updated" date at the top always reflects the current version. Where a change materially affects how your data is handled (a new category of data, a new recipient, or sharing results with a third party), we will make that clear rather than relying on the date alone.

29 July 2026, what changed: your CV is now saved to your account rather than only to your browser. Previously the extracted text sat in your device's local storage and never reached our database; it now lives on your account so it follows you between devices and does not have to be re-uploaded. The uploaded file itself is still deleted from our server within seconds of being parsed. That has not changed, and we still never keep your original PDF or DOCX. You can delete the stored CV at any time from your account page, and any copy previously held in your browser has been cleared. See sections 2.1 and 8.

13. Grievance Officer

In accordance with the Information Technology Act, 2000 and the rules made thereunder, and the DPDP Act 2023:

If your complaint is not resolved to your satisfaction, you may escalate it to the Data Protection Board of India.