Privacy Policy
Last updated 11 September 2026
Who this covers
This policy explains what Rehearsal ("we", "us") collects from students, lab incharges/administrators, and site visitors on rehearsal-app.com, why, and how it's handled. It's written to be accurate to what the product actually does, not boilerplate — if something here looks wrong for how you use Rehearsal, tell us at the contact below.
What we collect
Account & identity. Name, email address, and password (handled by our authentication provider — we never see or store your plaintext password). If your college has onboarded you, we also hold your roll number, department, year of education, and section, and your college/organization affiliation.
Practice content. The text, code, and spoken answers you submit in a practice or graded session — this is the core of what the product grades and gives feedback on. Spoken answers are transcribed to text for grading; we don't keep the raw audio beyond what's needed to produce that transcript.
Performance & usage records. Scores, verdicts, attempt history, and session timestamps, so you (and, where applicable, your lab incharge) can see progress over time. We also log AI-usage volume per account internally, to keep the service within its cost limits — this is operational, not shared or sold.
Device information. A random token generated in your browser (not a hardware ID) and your browser's user-agent string, used to enforce the "one mobile + one laptop" device limit on a license. We don't fingerprint you across other sites.
Location. Two separate things, both narrow in scope: (1) a coarse, country-level signal from standard web-hosting infrastructure, used only to decide which payment provider and currency to show you; (2) if — and only if — your lab incharge has set up a physical-attendance check for exam-mode sessions, your browser's precise location at the moment you start a Real attempt, to confirm you're on campus. This is captured once per attempt, only with your browser's own location permission prompt, never tracked continuously, and never used for anything else.
Payments. We do not store your card, UPI, or bank details. Payments are handled directly by our payment processors (Razorpay for India, Stripe internationally) — we receive confirmation that a payment succeeded, not the underlying instrument.
Why we collect it
To run the practice/grading product itself (that's most of the above), to enforce the access and licensing terms a student or institution has actually paid for (device limits, attempt limits, exam-mode checks), to bill correctly, to keep the service secure and within operating budget, and to respond when you contact us. We don't use your data for advertising, and we don't sell it.
Who we share it with
We use a small number of service providers to run Rehearsal, each processing only what their function needs:
- Supabase — our database, authentication, and file storage.
- Vercel — hosting.
- Anthropic (Claude) — evaluates and generates feedback on practice-session text. Session content is sent for that purpose; Anthropic's own API terms govern retention on their side.
- OpenAI — transcribes spoken answers to text where a module uses voice.
- Azure Cognitive Services / ElevenLabs — generate the spoken prompts you hear; they don't receive your answers.
- Judge0 (via RapidAPI) — executes code you submit in a sandboxed environment, for grading.
- Razorpay / Stripe — process payments.
- Resend — sends transactional email (password resets, invitations).
If you're a student at a partner college, your lab incharge/institution admin can see your performance records and attempt history within their own organization — that's the point of the institutional product. We don't share your data across unrelated institutions.
We don't sell your personal data, and we don't share it with anyone for their own marketing purposes.
How long we keep it
We keep account and performance data for as long as your account is active, plus a reasonable period after (so a returning student doesn't lose their history, and an institution can review a completed cohort). If you ask us to delete your account, we delete or anonymize the personal data tied to it, other than what we're required to retain for legal, tax, or dispute-resolution purposes.
Your rights
You can ask us to access, correct, or delete the personal data we hold about you, or to export it. If you're a student whose account was created by your college on your behalf, some of these requests may need to go through your institution as well as us, since they hold the underlying enrollment relationship. Email the address below and we'll respond as quickly as we can.
Cookies & local storage
We use essential cookies/local storage to keep you signed in and to remember a few per-device preferences (like your device token). We don't use third-party advertising or cross-site tracking cookies.
Children's privacy
Rehearsal is built for college students preparing for placements, not for children. We don't knowingly collect data from anyone under the age our region's law sets for independent consent to an online service.
Changes to this policy
If we make a material change to what we collect or how we use it, we'll update the date at the top of this page and, where the change is significant, let institutions and students know directly.
Contact
Questions, requests, or concerns about your data: info@rehearsal-app.com.
This policy describes our practices in plain language. See also our Terms of Service.