How Interview Command Handles Your Data
Last updated: September 26, 2026
| Data | Where it goes | Why | Current storage |
|---|---|---|---|
| Onboarding answers | Your browser | Personalize your path | Browser local storage |
| Email you submit | Interview Command server | Access/lead administration and requested updates | Server-side access/lead records |
| Social sign-in identity | Your chosen provider + Interview Command server | Create/find your account and restore eligible access | Provider name, provider-specific subject ID, and provider-returned email/name/avatar or verification signal where supplied |
| Account session | Your browser + Interview Command server | Keep you signed in | Opaque HttpOnly cookie in your browser; SHA-256 hash, account ID, and session timestamps on the server |
| Raw résumé file | Interview Command server | Temporary parsing/extraction | Intended to remain in memory only |
| Extracted résumé facts | Returned to your browser | Risk Map and personalized practice | Browser only if you choose to save |
| Recorded practice audio | Your browser; for eligible signed-in premium attempts, InterviewCommand server transiently | Spoken-practice capture and transient practice evaluation | Browser capture for the current attempt; raw audio is not intentionally written to the application database by the transient evaluation endpoint |
| Browser transcript | Your browser / browser speech service; for eligible premium evaluation, InterviewCommand server transiently | Speech analytics, answer evidence, and practice coaching | Attempt history may be stored locally; the transient evaluation endpoint is designed not to write the raw transcript to the application database |
| Derived acoustic measurements | Your browser; for eligible premium evaluation, InterviewCommand server transiently | Descriptive delivery evidence such as estimated fundamental-frequency range, within-answer loudness variation, and clipping | Derived numeric summaries may remain in browser practice history; they are currently unvalidated for scoring and are not treated as confidence, emotion, accent, personality, employability, or hiring signals |
| Optional Zara Voice calibration contribution | InterviewCommand server and authorized human calibration raters, only after explicit post-run consent | Validate analyzer behavior against independently rated natural spoken answers | Pseudonymous primary-answer voice recording, transcript, server-verified question context, measured delivery/acoustic evidence, consent record, blinded human ratings, and adjudication where needed. Designed to exclude account ID, email, order ID, simulation run ID, and outcome data. A voice recording may still identify the speaker; analyzer predictions, derived acoustic telemetry, and other rater labels are hidden during independent rating. |
| Calibration withdrawal code | Your local practice receipt; SHA-256 hash on the InterviewCommand server | Allow deletion of an opt-in calibration batch without linking the calibration corpus to your account | Plaintext withdrawal code remains in the local receipt; only its hash is stored with the calibration batch |
| Strict Simulation camera frames | Your browser / MediaPipe visual-analysis runtime | Face-presence and visual-attention coaching | Not intentionally uploaded to or stored by the Interview Command server |
| Strict Simulation summary | Your browser | Review environment discipline, timing, and visual-attention coaching signals | Browser local storage; raw camera frames are not included |
| Optional Account Sync telemetry | Interview Command PostgreSQL after explicit opt-in | Merge paid training progress across signed-in devices | Question ratings/attempt counters, delivery metrics, and Strict Simulation summary metrics; excludes résumé data, target-workspace snapshots, transcripts, raw audio, and raw video |
| Human Review submission | Interview Command server + authorized human reviewer | Provide the VIP Priority Pass Human Review service | Submitted response/transcript, optional context/session summary, review status/timestamps, written feedback, and exact pointers |
| Affiliate referral identifier | Your browser → Interview Command checkout → Lemon Squeezy | Preserve approved referral attribution and, when enabled, the referral promotion | Short-lived first-party HttpOnly cookie for up to 30 days; affiliate/referral records are administered by Lemon Squeezy |
| Payment credentials | Lemon Squeezy | Checkout and payment processing | Not stored by Interview Command |
| Order recovery data | Interview Command server | Grant, restore, revoke, or account-link paid access | Purchase email, Order #/identifier mapping, variant, entitlement/account link, and status |
| Outcome survey | Interview Command server | Aggregate efficacy analysis | Hashed anonymous browser ID, reported outcome, practice counts, optional comments |
Before uploading a résumé
Remove information not needed for interview preparation, such as full street address, personal identification numbers, banking details, passwords, or unrelated reference contact information.
Résumé consent control
Resume Lab requires an acknowledgment before analysis. The server also requires a matching privacy-acknowledgment header for résumé-processing requests.
No model-training claim
Interview Command does not currently send Resume Lab uploads to an external AI/LLM API. If that architecture changes, the privacy notice and this page should be updated before the change is available to users.
Human Review
Human Review is deliberately human-delivered. When a VIP Priority Pass customer submits a response, an authorized reviewer can read that submitted content and any optional focus notes or session-summary data sent with it. The reviewer’s feedback is stored with the request so it can be shown back to the matching purchase session. One review is available per verified VIP Priority Pass purchase.
Calibration contribution
Zara Voice calibration is separate from Human Review and Account Sync. Primary-answer audio stays in browser memory through the completed Zara run and is discarded unless the learner explicitly opts in. A contributed voice recording may identify the speaker, so the server stores it as pseudonymous calibration evidence rather than claiming it is anonymous. Blind raters do not receive the analyzer prediction or other rater labels while scoring. Finalized corpus export excludes raw audio and outcome data. The server-held contributed batch can be deleted with its private withdrawal code; a corpus export already downloaded by an authorized operator cannot be automatically recalled.
Outcome survey privacy
The outcome survey is optional and does not require your email. The random browser ID is hashed on the server before storage. Survey data is intended for aggregate product evaluation, not for identifying candidates.
Social sign-in
Available social sign-in options are shown on the account page. Social login requests only identity-oriented permissions needed for authentication. Interview Command does not intentionally persist social-provider access or refresh tokens after login. The provider-specific subject identifier is used as the durable external identity key; display names are never used as an account-linking key.
Strict Simulation and visual analysis
Strict Simulation requests camera and microphone access only after you start its system check. Camera frames are processed in the browser for coaching signals such as face presence, multiple-face detection, head position, and sustained visual-attention drift. The current implementation loads MediaPipe Face Landmarker code/model assets from third-party hosting. MediaPipe's package documentation states that usage or performance metrics may be sent to Google. Interview Command does not intentionally upload raw simulation video to its own server and does not use these signals for biometric identification or to declare that a user cheated.
Browser data and cross-device access
You can remove browser-stored Resume Lab plans, onboarding choices, progress, attempt history, and Strict Simulation summaries by using product reset tools or clearing site data in your browser. Account login can restore account-linked access on another device. For active paid accounts, Account Sync is optional and off by default; after explicit opt-in it can merge question progress, delivery metrics, and Strict Simulation summaries across signed-in devices. Résumé Lab facts/plans and Mastery target-workspace snapshots remain browser-local in the current version. Turning sync off stops future transfers while retaining the existing cloud copy; the Account Sync control also provides a separate delete-cloud-data action.
Generated coaching feedback
We retain a private owner quality-review copy of generated AI coaching and free-practice receipt coaching, with the role pack, question, access category and creation time. This archive excludes answer and previous-answer quotation fields, recordings, transcripts, account identifiers and session activity. Selected answer quotations, email addresses and links are removed from generated prose where detected; coaching can still describe the substance of an answer. The owner copy is not a complete session record or a hiring assessment. Existing account-sync, AI review caching and optional Human Review features follow their separate handling described above. Feedback copies are retained for product quality review; contact support about deletion.
Adam voice, saved practice and deletion
Adam voice is separate from browser-only practice: after consent, microphone audio goes to OpenAI for conversation and transcription. Account-linked transcripts, exercises, coaching observations, Practice Receipts and checkpoints are saved for 30 days. Your optional Adam Profile is stored separately until you remove it.
Pause Adam, open Manage this practice and choose Delete this practice to remove that selected conversation and its receipt from the current browser. Other browsers, separately submitted reviews, calibration contributions and downloaded exports need separate cleanup. Deleting a practice does not delete your account, Adam Profile, purchase records or usage allowances. Request account deletion or help with other copies through support.
Supervised tester screen evidence needs separate consent and is kept for 30 days. Payment records, pseudonymous cohort commitments and usage/allowance journals have separate retention for financial accountability and cost controls.