Privacy policy

Account and sign-in information

We store the email address, name and account settings you provide. Email/password accounts use a hashed password rather than storing the password in readable form.

If you choose Google or Microsoft sign-in, we request basic identity information: an account identifier, name and email address where the provider supplies it. We use identity-token claims to validate the sign-in and connect the provider identifier to your InterviewRep account. Provider identity tokens can also contain a profile-picture reference and other validation claims; this sign-in integration does not save provider photos. Microsoft may require an additional email-verification step.

These sign-in permissions do not give InterviewRep access to your Gmail or Outlook mailbox, messages, contacts, calendar or files. We do not request those permissions or ongoing offline access. Provider access and refresh tokens are not retained by this sign-in integration.

We use sign-in information to create, authenticate and secure your account and provide account-related service, not to sell that information or build advertising profiles. Account name and email may also be used for service messages and payment administration when you use those features.

Interview information you choose to provide

InterviewRep processes supported live audio to produce transcripts. When you request AI answer suggestions, it processes the relevant transcript and context you supply, which can include resumes and job descriptions. Saved transcripts, resumes, settings and session information can remain in your account for later use.

Only capture audio or share information you have permission to use. Interview participants may have their own rules or privacy expectations. You control when to start, pause or stop a live session.

Service providers

Our infrastructure and processors help deliver the service. These include DigitalOcean for hosting and database infrastructure, Deepgram for transcription, OpenAI for requested AI processing, Stripe for payments and subscriptions, and our email provider for account messages. Information sent to a processor depends on the feature you use.

Stripe may receive your account name and email to manage a payment customer, together with the payment information you submit through its payment interface. InterviewRep stores billing references and invoice/credit information; the application does not store complete card details. Google or Microsoft receives the information needed to handle a sign-in you initiate.

Service providers have their own applicable privacy and retention practices. Data processing may occur outside your country, depending on the provider and feature.

Browser storage and security

We use necessary browser storage for your sign-in session and preferences. Social sign-in also uses a short-lived cookie to bind its security checks to the browser that started the request. Signing out clears the application’s stored sign-in token; expired tokens are rejected by the service.

We use HTTPS, access controls and restricted backend credentials to protect information. Operational information used to deliver and secure the service can include connection details, errors and account activity. No service can promise absolute security.

Your choices, saved data and deletion

You can use email/password access instead of provider sign-in. You can review and edit available profile settings and use the application’s transcript deletion and export tools. You can also remove InterviewRep’s authorization in your Google or Microsoft account settings; doing that does not itself delete your InterviewRep account or saved interview data.

Saved account and interview information remains associated with the service until removed through supported deletion tools or an account-deletion request. Payment records held by Stripe follow its own retention practices. If you want to request access, correction or deletion, email the privacy contact above. We verify account ownership before disclosing or changing account information and explain any limitations that apply to your request.

Google user data is handled in accordance with the Google API Services User Data Policy. If we introduce a new use of provider data or request additional permissions, we will explain that use and request the necessary consent before using the new access.