Interview Wizard Privacy Policy
Effective date: September 21th, 2026
Operator: Zirui Wang
Website: https://interview-wizard.znivexo.com
Privacy contact: tigerryan21@gmail.com
1. About this policy
Interview Wizard ("we," "us," or "our") provides AI-assisted mock interviews, feedback, transcripts, and a personal performance agent. This policy explains how we collect, use, store, and share personal information when you use the service.
2. Information we collect
- Account information: Email address, account identifier, authentication records, and profile information such as your name and profile picture, where provided.
- Interview materials: Uploaded resume files, filenames, extracted resume text, job descriptions, interview type, and other information you submit. Resumes may contain contact details, education, and employment history.
- Interview activity: Questions, answers, transcripts, session dates and status, assessments, scores, and feedback.
- Performance agent activity: Chat messages, relevant past interview information, generated documents, and stored summaries or memories used to personalize future responses. We may create numerical representations of text to retrieve relevant information.
- Audio and camera access: When you enable your microphone, recorded audio segments are sent for speech transcription. If you enable your camera, the service accesses it for the interview experience. No audio or video will be retained in the database.
- Billing information: If you subscribe, our payment provider processes payment details. We maintain associated customer identifiers, subscription status, and billing-related records.
- Technical information: IP addresses, request details, usage counters, and diagnostic logs used to operate and protect the service. Some logs may contain submitted content, including transcribed responses.
- Support communications: Information you provide when contacting us.
Please avoid submitting sensitive information or other people's personal information that is unnecessary for interview practice.
3. Google Sign-In
If you sign in with Google, we receive the basic identity information authorized through Google Sign-In, such as your Google account identifier, email address, name, and profile picture. We use this information to authenticate you, create or link your account, display your profile, and associate your interviews and subscription with your account.
Google identity information is processed through our authentication provider, Supabase, and stored with your account. Google Sign-In does not give us your Google password. Our sign-in feature does not request access to Gmail messages, Google Drive files, contacts, or calendars.
We do not sell Google user data or use it for advertising. Our use of Google user data is subject to the Google API Services User Data Policy, including applicable Limited Use requirements.
You can revoke access through your Google Account connections settings. Revoking access prevents future authorized access but does not automatically delete information already stored by Interview Wizard. Contact us to request deletion.
4. How we use information
We use information to:
- Operate accounts, authentication, subscriptions, and usage limits.
- Generate interview questions based on your resume and target job.
- Transcribe spoken answers, deliver interviewer speech, and support enabled avatar features.
- Produce assessments, transcripts, and personalized performance guidance.
- Retrieve relevant interview history and maintain performance agent conversations and memories.
- Respond to requests, troubleshoot problems, prevent abuse, and maintain security.
- Meet applicable legal obligations and resolve disputes.
AI assessments are practice guidance and may be inaccurate. You may request correction of inaccurate personal information using the contact above.
5. Service providers and sharing
We send information to service providers as needed to deliver the features you use. Depending on the enabled production configuration, these include:
| Provider or service | Purpose and information involved |
|---|---|
| Google Sign-In and the identity information you authorize. | |
| Supabase | Authentication, account and interview records, uploaded resumes, and generated files. |
| Upstash Redis | Temporary guest interview records and usage or rate-limit identifiers. |
| OpenAI and/or the configured AI API provider | Resume and job-description text, interview content, audio for transcription, and text used for retrieval embeddings. |
| Anthropic and/or the configured Claude API provider | Performance agent messages and relevant interview history or summaries. |
| ElevenLabs | Text and voice settings used to generate interviewer speech. |
| HeyGen, when avatar mode is enabled | Avatar session information and content needed to deliver the avatar experience. |
| Tavily, when online research is used | Search queries generated for performance agent research, which may reflect information from your request. |
| Stripe, when paid subscriptions are used | Payment processing, billing details, and customer and subscription identifiers. |
| Vercel | Hosting, request processing, operational logs, and security. |
Provider processing and retention depend on the relevant service configuration and agreements.
We may also disclose information where required by law or necessary to investigate abuse, protect rights and safety, or respond to valid legal requests. Any transfer involving Google user data remains subject to Google's applicable restrictions.
6. Cookies and browser storage
We use cookies and browser storage to maintain sign-in sessions, recognize guest usage, apply interview limits, and remember interface preferences. Blocking or clearing this storage may affect sign-in or other functionality.
7. Data retention
Original uploaded PDF and DOCX resumes become eligible for deletion after 24 hours and are removed by a daily cleanup job, normally within approximately 24–48 hours of upload. Scheduling delays or failed cleanup runs may extend this period. This cleanup also applies to previously uploaded originals once they exceed the retention period. It does not delete extracted resume text, job descriptions, interview transcripts, scores, or feedback, so saved interview results remain available. Provider backups may follow separate retention schedules.
Guest interview records in Redis are configured to expire after approximately 48 hours. This expiration applies to those Redis records; it does not automatically delete separately uploaded resume files, logs, backups, or provider-held data.
Account information and saved interview history are retained to support your account and ongoing practice. Performance agent conversations, memories, and generated files may have separate retention settings.
Information may be retained where necessary for legal obligations, security, or resolving disputes. Deletion from active systems may occur before expiration from backups and provider systems.
8. Your choices and requests
You can choose what to upload, control microphone and camera permissions in your browser, download available interview transcripts, and revoke Google access.
To request access, correction, or deletion of your account and associated personal information, contact the privacy email above. Please identify the account involved; do not send passwords. We may ask for information needed to verify your identity before acting on a request.
Depending on your location and applicable law, you may also have rights to portability, restriction of processing, objection, withdrawal of consent where processing relies on consent, or a complaint to a privacy regulator. We handle requests in accordance with applicable law.
9. Security and international processing
We use authentication and access controls designed to limit unauthorized access to account information. No online service can guarantee absolute security.
Our providers may process information in countries other than your own.
10. Children's privacy
If you believe a child has submitted personal information in violation of the service's age requirements, contact us so we can investigate and take appropriate action.
11. Changes and contact
We may update this policy as the service changes. We will update the effective date and provide additional notice where required. If we introduce a new use of Google user data requiring consent, we will obtain that consent before that use.
For privacy questions or requests, contact tigerryan21@gmail, addressed to Zirui Wang.
Owner review notes — remove before publishing
This is a drafting aid, not a determination of legal compliance. Resolve every bracketed field and ensure each statement matches production practices before publishing.
- Confirm the operator identity, privacy mailbox, effective date, intended age range, and locations served.
- Verify actual Google OAuth scopes and confirm that Google identity data is not used for advertising or unrelated purposes.
- Verify production AI endpoints and intermediary providers. Do not add a blanket "never used for AI training" claim without checking all applicable provider settings and contracts.
- Confirm media behavior, log contents, hosting providers, retention periods, backup handling, and the process for fulfilling deletion requests. The code currently logs transcription text and stores uploaded resumes separately from expiring guest records.
- Confirm whether anonymous activity, agent memories, generated files, and uploaded resumes are covered by deletion procedures.
- If serving jurisdictions that require additional disclosures, add the applicable legal bases, regulator information, transfer safeguards, or regional rights after reviewing the actual operation.
- Publish the completed policy at a public URL, preferably
https://interview-wizard.znivexo.com/privacy, and link it from the homepage. Put that direct policy URL in Google's privacy-policy field. A PDF should also be publicly accessible without sign-in if used; a normal webpage is easier to read on mobile. - A privacy policy is separate from Terms of Service; do not use this document as the terms link.