How Interview Command Handles Your Data

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.

Optional AI answer review

When you choose “Review this answer,” Interview Command sends the answer text, the previous answer to that question when available, and the question’s reference material to OpenAI for provisional coaching. Audio, your account email, and unrelated practice records are not included in this request. Saving an answer alone does not trigger this optional review. Avoid including confidential employer or personal information.

The request disables API response storage. This does not promise zero provider retention; OpenAI’s applicable API data policies still apply. Interview Command processes these answer texts in memory for the review and does not intentionally log them. The returned feedback and review history are saved with your browser’s practice record. A server-side copy of the feedback (which can include answer excerpts), an account identifier hash, request hashes, and usage totals are also retained to reuse existing reviews and enforce review allowances. Full submitted answer texts are not stored in the budget ledger. AI feedback can be wrong and does not establish interview readiness.

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

The launch configuration supports Google and LinkedIn. 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 saved 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.