Legal

Privacy Policy

Last updated November 14, 2026

InterviewOS is operated by Albanda Mursalzade Group, based in Poland.

InterviewOS is built local-first and privacy-first. This policy explains what we collect, what stays on your device, and exactly what leaves it when you use the managed live copilot.

1. Our local-first principle

The desktop application stores your interview materials — your CV, extracted evidence, STAR stories, job descriptions, flashcards, transcripts, and reports — in a local database on your own machine. Any API keys you provide are encrypted at rest. Using cloud AI features sends the relevant audio, prompts, and context for processing as described below; local storage does not mean every feature runs offline.

The desktop app includes controls to exclude its windows from screen capture on supported systems. Behavior depends on your operating system, settings, and recording or meeting tool; verify it before sharing sensitive information. Windows app windows are also kept off the taskbar and Alt-Tab. These controls do not replace recording consent or the rules of your interview.

2. Data we process in the cloud (managed tier)

To deliver the real-time copilot without requiring your own AI key, we operate a managed proxy. When you use a cloud-backed feature, the following data flow applies:

  • What is sent. Only the minimum needed to answer a request — for example, selected audio for transcription, the transcribed question, and the specific snippets of your materials retrieved to ground the answer. We do not upload your entire local database.
  • Where it goes. Our proxy calls third-party AI providers (such as OpenAI) under our organization key to perform transcription and answer generation. Their processing is governed by their terms and privacy policies.
  • What we keep. We record usage metadata needed to operate the credit system (for example, which feature was used, token or minute counts, and timestamps) in an audit-grade ledger. New AI answer and transcript retry-cache entries may be kept on our servers for up to 24 hours to make interrupted requests safe to retry without repeating work or billing. That cached content is then purged. This 24-hour limit applies to the retry cache, not historical audit records, which may contain legacy request or response excerpts and are retained separately under the retention policy below. This cache does not upload or replicate your full local CV database. We do not use your content to train third-party models where avoidable.

2A. App diagnostics and live session quality records

To find and fix problems in the live copilot (for example, transcription that stops while the interviewer is speaking, or slow and failed answers), the desktop app sends us a quality record for each live session. There are two parts, and you control each one in the desktop app under Settings → Privacy.

  • Diagnostics (on by default). Content-free technical information: app version and platform, session start and end times, the transcription mode and model, connection, reconnect and error events, loudness statistics of the captured audio in 10-second windows, and counts and timings such as words per turn, answer length and how long an answer took to start. Diagnostics contain no audio, no transcript or answer text, no CV, job description or take-home files, and no device names. We process them on the basis of our legitimate interest in keeping the Service reliable. You can turn them off at any time.
  • App setup diagnostics. The same diagnostic control covers a limited timeline of app sections opened, resume import outcomes, live-session start and stop, credit interruptions and checkout-window progress. These are fixed action and error categories with timestamps, app version and platform. We do not collect typed text, document names or contents, visited website addresses, individual mouse coordinates, passwords or payment details. These client-reported records are kept for seven days from the action time and can be deleted with the same account-record control.
  • Transcripts and answers (only if you share them). If you choose to share a session, its record also includes the transcribed turns, the questions and the answers the app generated. We process this only with your consent, which you can withdraw at any time; withdrawing stops future sharing. Transcripts include what other participants said, so share them only where your interview's rules and local law allow it.

Shared transcripts and answers are encrypted at rest (AES-256-GCM). Quality records are visible only to authorized InterviewOS administrators in an internal quality tool, are used only to diagnose and improve the Service, and are never sold, used for advertising or used to train third-party models. Audio is never uploaded for this purpose. Every quality record is deleted automatically 7 days after it is first received. You can delete all quality records sent from your account sooner, from the same Settings page or by contacting us.

2B. Requested app downloads and setup

When you request a Windows or Mac installer through our download service, we use a secure, HTTP-only, browser-session cookie to show that download's status, let you retry the same installer, and connect this setup session to your account after you sign in. It is created for the download request, not ordinary page visits, and is not used by advertising, Clarity or website analytics. The server stores only a hash of the random session token and accepts it for status and account linking for up to 24 hours.

Delivery records contain the requested platform, installer filename and version, response byte range/counts, transfer state and timestamps. They do not duplicate your IP address, email address or browser fingerprint. Anonymous records are removed after seven days; account-linked records after 30 days from the download. A finished server transfer does not establish that your browser saved the file, that you installed it, or that you signed in inside the desktop app.

3. Account & billing data

Optional card-free first practice sends the role, project notes and answers you submit to our AI provider for feedback. The complete practice is saved locally. The server keeps response excerpts for up to 24 hours for safe recovery, plus account-linked offer assignment, hashed request/device/network identifiers, status, timing and token counts to enforce the limited free allowance and prevent abuse. Administrators see aggregate completion and retry counts; these records are not sent to advertising services. The allowance does not grant a subscription or authorize a payment.

For the web app we process your account information (such as email and authentication identifiers) via our authentication provider (Supabase), and your subscription and payment information via the provider shown at checkout or in Billing. Dodo Payments acts as merchant of record for Dodo purchases. Where Stripe is used, it acts as the payment processor. Card details are entered directly into the provider's secure form; we do not store full card numbers or security codes. We retain provider references, masked card details where available, and your billing-consent record, including the selected plan and automatic-conversion terms. We retain billing records as required for accounting and legal compliance.

4. How we use data

  • To provide, secure, and improve the Service for you.
  • To operate subscriptions, enforce plan limits, and meter credits.
  • To communicate about your account, billing, and support.
  • To comply with legal obligations and prevent abuse.
  • With your permission or, outside the EEA, the UK and Switzerland, by default with a notice (section 4A), to measure advertising visits and verified payment events and to understand how our website is used.

We do not sell your personal information.

4A. How your location affects optional analytics and advertising measurement

  • EEA, UK and Switzerland. Nothing optional runs before you opt in. The Privacy choices banner stays until you choose; it never closes or accepts by itself, and waiting or leaving the page is never treated as consent. We treat EU territories with their own country code (such as Réunion, Guadeloupe, Martinique, French Guiana, Mayotte, Saint-Martin and Åland), Gibraltar, Jersey, Guernsey and the Isle of Man the same way, and also visitors whose country we cannot determine.
  • Other countries. Optional analytics (Microsoft Clarity heatmaps and masked session replays on approved public pages, and first-party product diagnostics on your web dashboard) and advertising measurement (the Google Ads tag and ad click identifiers, Google Analytics 4 and OpenAI ad-click measurement) run by default, as described in sections 5 to 5B. A short notice tells you this when you arrive and closes by itself after it has been on screen for about five seconds (it does not count down while the tab is in the background), or when you choose OK. Closing the notice only stores a cookie for up to 90 days so it does not reappear on every page. It is not recorded as consent, and the measurement stays on the regional default described here.
  • Switching it off. Choose Reject optional or Manage choices in the notice, or open Cookie preferences on public pages or your dashboard at any time, to turn any of these off. A saved choice always overrides the regional default, and declining advertising measurement also keeps any later-added optional measurement off until you choose otherwise. A choice to switch something off is kept in that browser for about 13 months; a permission you give lasts up to 90 days. If you save your choices and leave an item ticked that was on by default, it stays on the regional default and is not recorded as your consent.
  • Browser privacy signals. If your browser sends Global Privacy Control or Do Not Track, none of this default measurement runs and we do not show the notice. When you are signed in, that signal also applies to your account: we stop using any ad-click identifiers linked to your account under the regional default, so they are no longer used to report signups or purchases to Google or OpenAI.
  • We use the country that our network provider (Cloudflare) attaches to each request. Your browser keeps a cookie for up to one day noting that the regional default applies; our servers check the request's country again instead of relying on that cookie.

5. Optional advertising measurement

OpenAI Ads measurement is a separate, optional choice in Cookie preferences. Existing Google Ads, product analytics and Clarity choices do not enable it. Where it is enabled, it is on by default outside the EEA, the UK and Switzerland (section 4A) unless you switch it off, decline advertising measurement or your browser sends Global Privacy Control or Do Not Track. After you opt in (or under that regional default), we can retain an OpenAI ad-click identifier for up to 30 days and associate it with your account. We send OpenAI only verified registration and paid-plan purchase events, their time, a generated deduplication identifier, the ad-click identifier and, for a successful paid purchase with an activated plan, its actual amount and currency. Free credits, opening checkout and closing payment are not paid purchases. This integration is server-side; it sends no email address, phone number, card data, CV, interview content or browser session recording. Pending measurement records are kept for up to 90 days. You can withdraw the OpenAI choice at any time to stop future events and clear the associated click identifier. Essential account and billing records follow their separate retention rules.

When advertising measurement is configured, in the EEA, the UK and Switzerland we use Google Ads only after you enable Advertising measurement in Cookie preferences or choose Allow optional. Before that choice, we do not load the Google Ads measurement tag or set its advertising cookies. In other countries it runs by default with a notice (section 4A) unless you switch it off or your browser sends Global Privacy Control or Do Not Track. This choice is separate from account access, payment processing, and essential security functions.

With your permission, or under the regional default in section 4A, we store advertising click identifiers (gclid, gbraid, or wbraid) and the time and version of your consent, or, under the regional default, the capture time and the fact that no explicit consent was given. If you sign in, we can associate that attribution with your account so a verified payment can be connected to the visit that led to it. The attribution cookie and an advertising permission last up to 90 days; a choice to switch it off is kept about 13 months. Conversion matching is limited to eligible events within the measurement window; this is not a promise that every advertising or billing record is deleted after 90 days.

Measurement data can be sent to Google through its website tag or an upload of verified events. It includes the click identifier where available, event type and time, currency, conversion value, consent signals, and a generated transaction identifier used to avoid counting the same event twice. Google also receives technical browser and request information, such as the page address and IP address, when its tag runs. Verified refund or dispute information can be used to correct a previously reported conversion.

Where an earlier checkout included a refundable $1 activation payment, that capture is a separate, zero-revenue measurement event. It does not mean trial credits have been granted; that earlier offer still waits for a successful refund. Cardless free-credit grants and earlier card-setup trials capture no activation payment and are not reported as a paid subscription. Paid subscription events use the amount of a verified successful invoice payment. We do not send card numbers, security codes, CV content, interview audio, or transcripts to Google Ads. We do not use enhanced conversions that send hashed email addresses, phone numbers, or other customer-provided personal details. Advertising personalization is disabled for this measurement.

Choose Reject optional to decline, or Manage choices to decide per purpose. You can revisit Cookie preferences on public pages or your dashboard to change your choice or withdraw permission. Withdrawing advertising permission stops future optional measurement from that browser and revokes the attribution associated with your signed-in account; it does not automatically erase information already received by Google. Declining does not affect your account, trial eligibility, or ability to buy a plan. For information about Google's processing, see Google's Business Data Responsibility information and Google's Privacy Policy.

5A. Optional product analytics

Product analytics has its own choice in Cookie preferences. A previous permission for Google Ads does not enable it. Outside the EEA, the UK and Switzerland it is on by default for your web dashboard (section 4A); the checkout privacy option on the desktop app's billing page still needs your own choice. If product analytics is on and you sign in, we keep basic events about viewing the dashboard, billing or checkout, clicking a Windows or Mac download or setup guide, choosing to continue, mounting the payment form, and broad setup-error categories. These events are associated with your account inside InterviewOS and help us diagnose account and app setup. A download click does not tell us whether installation completed.

Event data includes only the step, a plan category, a fixed error category where relevant, the server-recorded time, your account reference, and whether the event was recorded with your permission or under the regional default (section 4A). It does not include typed text, CVs, interview content, card details, raw provider errors, or page addresses containing query parameters. These diagnostics are not sent to Google Ads or an external analytics service. These first-party diagnostics do not record your screen or session.

Diagnostic events are retained for up to 30 days; a permission in your browser lasts up to 90 days and a choice to switch it off about 13 months. You can turn product analytics off independently in Cookie preferences. This stops new optional events from that browser; earlier events remain subject to the retention period. We also respect Do Not Track and Global Privacy Control for these diagnostics. Your choices do not change account access, billing agreements, trial eligibility, or essential billing and security records.

5A-1. Google Analytics 4

If you allow Website analytics in Cookie preferences, we also load Google Analytics 4 (Google LLC) on our website to measure page views and key steps such as signing up, starting checkout, completing a server-confirmed subscription purchase and downloading the app. This is a separate choice: earlier advertising, product analytics or Clarity permission does not enable it. In the EEA, the UK and Switzerland, Google Analytics does not load without that permission; in other countries it runs by default with a notice (section 4A) unless you switch it off. It sets first-party cookies (_ga, _ga_*) that last up to 90 days. We send page addresses without query parameters (except campaign tags such as utm_* and gclid), turn off Google signals and ad personalization, and never send names, email addresses, account identifiers, CVs or interview content. A confirmed checkout event includes the invoice reference, actual amount and currency for deduplication. Google receives technical browser and network information when its tag runs. We exclude admin and desktop-billing pages and respect Do Not Track and Global Privacy Control. Withdrawing website analytics consent stops new events and removes these cookies from this browser; it does not erase earlier data already received by Google. See how Google uses data from sites that use its services.

5B. Optional public-page session analytics

Microsoft Clarity has a separate Public-page session analytics choice in Cookie preferences. In the EEA, the UK and Switzerland it is off until you enable that choice or choose Allow optional. In other countries it runs by default on the approved public pages below, with a notice (section 4A), unless you switch it off or your browser sends Global Privacy Control or Do Not Track. Previous Google Ads or product analytics permission does not enable Clarity. We use its heatmaps and masked session replays to understand navigation and improve public pages.

When Clarity runs, Microsoft receives public-page interaction and technical data, such as clicks, scrolling, page layout, browser and device information, page addresses, and network information including your IP address. Clarity uses cookies and similar technologies. We configure strict text masking and do not send account identifiers, email addresses or custom customer information to Clarity.

Clarity is limited to approved public pages. It does not run on sign-in, registration, account, dashboard, admin, payment or desktop-billing screens. Pages with query parameters or a query-bearing referrer are excluded. We do not use Clarity to record CVs, interview content, passwords or card details. Its permission is independent of the first-party trial diagnostics described above.

You can withdraw this permission, or switch off the regional default, in Cookie preferences. We stop future recording in that browser and reload the document to unload the SDK; withdrawal does not automatically erase data already sent to Microsoft. A permission lasts up to 90 days in that browser and a choice to switch it off about 13 months. Microsoft applies its own processing and retention practices, described in the Microsoft Privacy Statement and Clarity retention documentation. We respect Do Not Track and Global Privacy Control for Clarity. Declining does not change your account, trial or billing agreement.

6. Sharing

We share data only with service providers that help us run the Service (such as hosting, authentication, payments, AI providers, and optional advertising measurement and public-page analytics as described above), under appropriate contractual safeguards, and where required by law. A list of subprocessors is available on request.

7. Security

We use industry-standard measures including encryption in transit, server-side enforcement of access (row-level security on our database), and least-privilege access to keys. Server secrets such as AI provider keys are never exposed to the browser or the desktop client. No system is perfectly secure, and you are responsible for safeguarding your own device and credentials.

8. Your choices & rights

  • Local data. You can delete your local materials at any time from the desktop app.
  • Account data. You may access, correct, or delete your account information, subject to records we must retain by law.
  • Depending on your location, you may have additional rights under laws such as the GDPR or CCPA. Contact us to exercise them.

9. Data retention

Local content persists on your device until you remove it. Cloud-side usage and billing audit metadata are retained for as long as your account is active and thereafter as needed for legal, accounting, and audit purposes. Live session quality records (section 2A), including any shared transcripts, are deleted automatically after 7 days.

10. Children

The Service is not directed to children under 18, and we do not knowingly collect their personal information.

11. Changes & contact

We may update this policy; material changes will be communicated through the Service or by email. For privacy questions or requests, contact [email protected]. See also our Terms of Service and Acceptable Use Policy.