Contents
Last updated: 25 October 2026. Effective: 25 October 2026.
This Privacy Policy explains how Clozo FZE LLC ("Clozo", "we", "us", "our") handles personal information in connection with the Interview Clozo macOS application, the website at interview.clozo.ai, and related services (together, the "Service"). It uses some defined terms that also appear in our Terms of Service: "You", "your" and "User" mean the individual who downloads, creates an account for, or pays for the Service; "Session Content" means the audio, transcripts, screenshots, résumé/CV text, job descriptions, notes and answers processed when you use the Service; and "Other Participants" means any person other than you in a meeting or call in which you use the Service (for example, an interviewer).
Please read this alongside our Cookie Policy, our Acceptable Use Policy and our Disclaimer. This Policy describes our practices; it is not a claim of certification under, or compliance with, any particular law.
The short version
- We are Clozo FZE LLC, a free-zone company in Ajman, United Arab Emirates. Contact us at info@clozo.ai.
- To run a live session, the app captures two audio streams on your Mac — your microphone and your Mac's system audio — and your Mac's system audio includes the voices of Other Participants. See Other people in your interviews.
- Session Content is sent to third-party AI providers to transcribe speech and generate suggestions. We do not use Session Content to train our own models, and we create no voiceprints or other biometric identifiers.
- Some Session Content is written to your own Mac; account and billing data are stored on our servers.
- In Mock Meetings, the app’s practice feature, your microphone is transcribed as in a live session, an AI model writes what the practice interviewer or prospect says, and an AI model scores the transcript of your answers on our servers, which then discard it (the app keeps it on your Mac in History); we keep a record of each practice round and its scores, as numbers only. See section 9D.
- On our website, Microsoft Clarity records how our pages are used — including the pricing, sign-in and subscription-management pages — for every visitor, without waiting for your cookie choice; what you type into forms is masked, and the recordings are not linked to your account. Your account page, the payment-confirmation page, the cancellation pages and the affiliate portal run only code from our own website, so Clarity, PostHog analytics and advertising tools never run there. The payment pages themselves are hosted by Stripe on its own site, where Clarity does not run either. When you are signed in, our website also always sends our servers content-free records of what you do there, such as the pages you open and the account buttons you press. Advertising technologies and PostHog analytics run only if you allow them, and we honour Global Privacy Control for them. See Analytics, session recordings, error reports and cookies.
- Newer versions of the Mac app always send us usage analytics (which screens and features you use, repeated or unanswered clicks, how far you scroll long screens, how sessions start and end, error and crash codes). They cannot be switched off in the app. They never include your interview audio, transcripts, answers, résumé or other text you type, with one exception: the title you give a role (for example “Senior Product Manager”), which we record with the kind of role it is.
- When you start to cancel, we record that you did, and we ask you why — typed or as a voice note. A reason you give is kept even if you then keep your plan or leave the cancellation steps. OpenAI transcribes voice notes; we keep the audio for 1 year and the text for as long as your account exists. See When you cancel.
- Once error reporting is switched on, errors and slow responses in our servers, website and app are reported to Sentry so we can fix them, without Session Content or anything you type.
- If you have not yet finished the steps to our free book, Never Take the First Offer, we email you what is left; you can unsubscribe from those emails in one click. See Our free book.
- You are responsible for using the Service lawfully, including obtaining any notice or consent the law requires from Other Participants.
- Your rights, and how to exercise them, are in Your rights by region.
- If you reached us through one of our affiliates’ links, a value in your browser’s local storage (
clozo_via) remembers that for 90 days so we can credit the affiliate when you buy. It is strictly functional, holds no personal information, and the affiliate sees only the status of the referral and the amounts their commission is based on — never your name, email address or anything that identifies you. See section 9C.
1. Who we are and how to contact us
Interview Clozo is operated by Clozo FZE LLC, a limited liability company registered as a free-zone company in Ajman, United Arab Emirates.
- Business registration number: 2629114574888
- Registered address: CWS-1V-226222, 26th Floor, Amber Gem Tower, Ajman, United Arab Emirates
- Contact: info@clozo.ai
For the personal information described in this Policy we are the controller (the business responsible for it), except where we say otherwise. Please direct all privacy questions and requests to info@clozo.ai.
Regional contacts.
- European Economic Area (EEA): Individuals in the EEA may contact us about their personal information at info@clozo.ai. If you are in the European Economic Area and need our EU representative’s details, contact us at info@clozo.ai.
- United Kingdom: Individuals in the UK may contact us about their personal information at info@clozo.ai. If you are in the United Kingdom and need our UK representative’s details, contact us at info@clozo.ai.
- Canada (including Quebec): Our Privacy Officer, who also acts as the person in charge of the protection of personal information for Quebec, can be reached at info@clozo.ai.
- India: Individuals in India may contact us about their personal information at info@clozo.ai. If you are in India, you may contact us about your personal data or raise a grievance at info@clozo.ai.
- Everywhere else: info@clozo.ai.
We have not appointed a Data Protection Officer, because the scale of our processing does not require one; if this changes we will name one here.
2. What this Policy covers
This Policy covers the Interview Clozo website, the macOS application, account creation, checkout, billing and cancellation, our free book offer, and our support communications. It does not cover the separate services and privacy practices of third parties, including: your meeting platform (for example Zoom, Microsoft Teams, Google Meet, Cisco Webex) and any assessment platform; the payment processor Stripe (which handles your card details under its own policies); and the advertising platforms named in Advertising, pixels and "sharing" or "sale", which use data they receive for their own purposes under their own policies. The Service is intended for use only by people aged 18 or over (see Children).
This Policy also covers our affiliate program: the affiliate portal at interview.clozo.ai/affiliates/, the referral links our affiliates share, and the personal information of the people who join the program as affiliates (section 9C). The Affiliate Program Terms govern that program.
3. The personal information we collect
We collect the following categories of personal information.
| Category | Examples | Source |
|---|---|---|
| Account information | Username, email address, password (stored only as a hashed value), and an optional full name; your marketing preference. | You, when you create an account in the app; or, if you start a Trial or buy a plan on our website without being signed in and no account uses that email address, the email address you give at checkout, from which we create your account; or on our create-account page (interview.clozo.ai/join.html), where you give a username, email address and password and save a payment method with Stripe (nothing is charged). |
| Purchase information | Plan purchased, price, currency (US dollars), dates, the IP address from which the purchase was made, and the transaction and customer identifiers held by Stripe. We never receive or store your full card number. Where you have allowed advertising cookies, we also record — on our own servers, against the record of your purchase, and at our payment processor — the advertising click identifier of the advertisement you arrived from (for example a Google gclid or a Meta fbclid) and the campaign parameters in the link you clicked, so we can tell which advertising produced the sale and so we can answer a payment dispute. If you do not allow advertising cookies, no click identifier is recorded, stored or attached. The terms shown to you next to the button you pressed before you paid or started a Trial (the exact text and its version), with the date, time, IP address and browser or app version; the same record each time you press a button in the Service that charges you, pauses your plan or turns automatic renewal back on. Your billing history with us: Trial start and end, charges, renewals, plan changes, pauses and resumptions, failed payments, cancellations, retention discounts offered, accepted and applied, and refunds. The type of payment method on your subscription and, for a card, its brand and last four digits, as Stripe reports them (never the full number). If you choose to save your payment details at checkout, Stripe stores them, not us. | You and our payment processor, Stripe. |
| Payment-method summary | For each payment method on your account: its type (for example a card, Apple Pay or Link) and, where our payment processor gives them, the card brand, the last four digits, the expiry month and year and the country that issued the card (for Link, a masked email address); which method is your primary one; and whether it has been verified. Never the full card number or the security code. | Our payment processor (Stripe), when you add, change or remove a payment method. |
| Email delivery records | For each email we send you: the address, the subject, the kind of email, when it was sent and whether it was delivered, bounced, refused or reported as spam, with the email provider’s reference for it — never the content of the email. If your address bounces, or you unsubscribe or report our email as spam, the address goes on our do-not-mail list. | Our servers and our email providers. |
| Security and device information | Your IP address; a device identifier (a hash of your Mac's hardware ID); your macOS login (short account) name; your Mac model and operating-system version; your browser or app version; and sign-up, sign-in, session-start and purchase-access events; one-time codes we email you when you sign in again to cancel, single-use links that take you from the app to the cancellation page, and single-use codes that sign the app in from your browser (all stored only in a scrambled, hashed form); failed sign-in and code attempts on the cancellation page; and whether a private download link you used was valid, expired or refused. | Collected automatically from your device and network when you sign up, sign in and start a session. |
| Usage, session and quota information | Sessions started and ended; their length; whether each was a live, practice or tutorial session and how it ended (for example ended by you, by the 50-minute Trial limit, or by an error); counts of questions detected, answers shown, errors, failed answers, transcription failures and slow responses in each session; the outcome of an interview, if you answer the app's optional question about it (offer landed, moved to the next round, rejected, or no result yet) — only that choice, nothing about the company or what was said; the number of answer generations counted against your plan and the AI model used; errors, refusals and slow responses from our AI services, recorded against your account; each time a download of the app starts through your private download link — when, which page or email the link came from (for example the payment-confirmation page, your account page or an email) and whether it started automatically or when you clicked, but not your IP address or the link itself — and each use of an expired or refused link; sign-in, checkout and account-page actions recorded by our servers. These records contain no Session Content. | Generated as you use the Service, by our servers and by the app. |
| Mock Meetings records (practice rounds) | For each practice round: the scenario and its version, its length and mode (assisted or unassisted), the units it used and any units returned, when it started and ended and how it ended, and how many questions were asked and answered; which questions you have been asked, how often and when, so that later rounds do not repeat them; and the scores its Debrief produced — a number and a confidence level for each skill and, for some rounds, how far a second scoring differed — never the words you said, your answers or your audio. Your practice units and their history. | Generated by our servers when you practise in Mock Meetings (see section 9D). |
| App usage analytics | Events such as the app opening and closing and how long it is in front; the screens you open and how long you stay; onboarding steps completed or skipped; permission prompts and their result; whether you imported a résumé (file type and size band only); whether you created, edited or deleted a role, its type or built-in template, and the title you typed for the role (for example “Senior Product Manager”) with the category we derive from that title (for example “product management”) — never the role's job description, company or notes; how many questions and answers you created or edited; which features you use; interview start requests and why a start was refused; the Trial charge screen and your choice on it; notifications shown and opened, and which of their buttons you pressed; settings you change (for example turning reminders or celebration sounds off); celebrations shown; your answer to the optional question about how an interview went; error, failed-action and crash codes; repeated, rapid or unanswered clicks, recorded as the app's own name for the control or only its type (for example “button”), never its label; how far you scroll on long screens such as History, Questions, Roles and Settings, as a percentage and a page count; a once-a-day summary of counts (résumés, roles and their categories, questions, answers); and the app version, macOS version and language setting. Never Session Content, other typed text, names, file names, company or interviewer names, or window titles. | The app, always (newer versions of the app); there is no setting to turn it off. |
| Error and crash reports | The type and code of an error or crash, a stack trace with personal values removed, how long pages, requests and some app actions took, the app, browser and operating-system versions, the device model, the page or screen, your internal account ID and the ID of the session concerned. We strip request bodies, cookies, email addresses, query strings and anything that could hold Session Content or what you type before a report is sent. | Our servers, website and app, once error reporting is switched on. |
| Cancellation records | That you pressed “Cancel subscription”, when, and whether in the app or on our website (or that your subscription was cancelled outside these steps); each step you reached and when (your reason, signing in again and whether by password or code, the “Before you go” step, the final confirmation); whether you were offered the 25% discount and whether you took it, whether you were offered a pause of 1 or 2 months and chose one, asked our founder for help, kept your plan, left the steps, cancelled, or later chose “Keep my plan”; your plan, price and subscription status at that moment; a snapshot of your usage at that moment (the kinds of counts listed above, never content); and, from the app, counts of your résumés, roles, questions, answers and onboarding steps, with the titles and categories of your roles. | Generated when you use the cancellation steps (see section 9A). |
| Cancellation reasons | The reason you type, a voice note if you record one, the transcript of that voice note, and the topic labels, severity and one-line summary we derive from them (for example “transcription quality” or “price”). A reason is kept even if you then choose “Keep my plan”, close the steps or leave them without finishing. | You, when you cancel (a reason is required to continue cancelling; a voice note is optional). |
| Book records | Whether you qualify for our free book, Never Take the First Offer, and which of its steps you have completed (a Trial or a plan, signing in on your Mac, an email address that accepts mail); which step and reminder emails we sent you, and whether and how you unsubscribed from them; when the book was granted and sent; how many times you downloaded it; and, if more than one Interview Clozo account has signed in from the same browser, the link between those accounts described in section 9B. | Generated by our servers as you use the Service and our emails (see section 9B). |
| Session Content | Your microphone audio; your Mac's system (meeting) audio, which includes the voices of Other Participants; transcripts of both; text extracted from screenshots you choose to capture; your résumé/CV text (up to about 60,000 characters) and its filename; job descriptions, role and company notes, saved questions and answers, and answers from earlier interview rounds; and the suggestions generated for you. In Mock Meetings, also your practice profile (target role, seniority, skills, goals, highlights and any résumé you add) and what the AI interviewer or prospect says. | Captured on your Mac while you use the Service, at your direction. |
| Support information | The content of emails and support requests you send us (including a request for our founder's help made while cancelling), and our replies. | You. |
| Website activity | Pages you view on our website; recordings of how you use our pages, made by Microsoft Clarity for every visitor on every page except the four listed in section 10 (clicks, taps, scrolling, mouse movement, page layout and the text a page shows, with what you type into forms masked), not linked to your account; when you are signed in, content-free events our own servers record, always — for example the pages you open, which account, checkout and book buttons you press and whether they worked, repeated or unanswered clicks, and errors shown; the tags in links from our book emails (section 9B); where you allow them, analytics (PostHog) and advertising identifiers and events. See our Cookie Policy. | Microsoft Clarity, our own website code and servers, and cookies and similar technologies on the website. |
| Referral information | If you opened an affiliate’s referral link: the affiliate’s code, which link you opened and when, kept in your browser’s local storage (clozo_via) for 90 days; when you open the link, a record on our servers of the code, the page, the time, the site that referred you and a one-way hash of your IP address and browser, kept for 30 days and then only as daily counts; and, once you complete a checkout, a record on our servers linking your account to that affiliate (the code, the link, the first and the last click), kept with your purchase records and copied into the metadata of your Stripe checkout records so a purchase can be credited correctly. | Your browser, when you open a referral link; our servers, when you open the link and when you complete a checkout. |
| Affiliate information (people who join our affiliate program) | Name, email address, password (stored only as a hashed value), country, the payout method you connect (the bank details you give us for a bank transfer, a USDT wallet address and its network, or a USDC wallet address and its network), the results of the sanctions checks on your wallet address and your name, tax details and identity documents where we ask for them, the version of the Affiliate Program Terms you accepted with the sentence shown, the date, time and IP address, your referral links and codes, every referral, commission and payout on your account, your sign-in records, IP address and device information, and content-free events from the portal pages you use. | You, when you join and use the affiliate portal; our systems, as referrals and payments occur; the payout provider you choose, which tells us whether a payout succeeded. |
You do not have to give us a full name or marketing consent. You must give an email address to hold an account (and, where you create an account in the app or on our create-account page, a username and a password), and the Service cannot run a live session without capturing the audio described above. Cancelling requires you to tell us why, in writing or by voice note; the rest of the cancellation works the same whichever you choose.
4. Other people in your interviews
Interview Clozo runs during live conversations, so it necessarily processes information about people other than you — usually an interviewer. This section is our notice to those Other Participants, and it is also our commitment to you about how we treat their information. It is a public notice for anyone who was in a conversation with a user of the Service.
What we process, and why
When you run a session, the app captures two audio streams on your Mac: your microphone, and your Mac's system audio. Because your Mac's system audio is the sound of your meeting, it includes the voices of everyone else on the call. If you use screen capture, the app also processes images of your screen, which may show other people's names, faces or shared documents. We call all of this "Session Content".
We process this Session Content only to transcribe what is said and to show you suggestions during that session, and, in Mock Meetings, to write and voice what the practice counterpart says and to score your practice round (see section 9D). We do not use Session Content about Other Participants to identify them, build a profile of them, contact them, advertise to them, or train any AI model. As explained in Voice and biometric data, we create no voiceprints or other biometric identifiers, and we do not attempt to recognise who is speaking beyond distinguishing the two audio streams by the input channel each arrives on.
Where it goes
On all plans — free and paid alike — both audio streams (your microphone and your Mac's system audio, which includes Other Participants' voices) are streamed in real time from your Mac, through a relay that Clozo operates, to our third-party speech-to-text provider (OpenAI) to be transcribed. The relay passes this data through in memory to complete your request and does not store it on our servers. Text (including transcripts, your notes and text read from your screen) and screenshot images are sent to the AI providers listed in AI providers and sub-processors. Those providers act on our instructions and may keep limited logs for abuse-monitoring for a short period, as that section explains.
What is kept, and where
Transcripts and suggestions from your recent sessions, and a limited number of recent audio recordings, are stored on your Mac, not on our servers. Screenshot images are held only in the app's memory during a session and are never written to disk or stored on our servers; only the text read from them is kept. See How long we keep information. We do not receive a copy of this local content.
Your responsibility
You decide when to run a session and whose conversation it processes. The Service acts as your tool, at your direction. In many places the law requires the consent of every person to a conversation before it may be recorded, or before certain information may be processed, and the law of an Other Participant's location may apply to you. You represent that you are a party to each conversation, and you are solely responsible for giving any notice and obtaining any consent that the law requires of you before you capture any audio. These obligations are set out in our Acceptable Use Policy and Terms of Service.
If you spoke with a user of Interview Clozo
We usually cannot link Session Content to you, because it is not stored on our servers and is not organised by any identity other than the user's. If you believe your information was processed and you wish to exercise a right, please write to info@clozo.ai. We will tell you what, if anything, we hold, and help you with the rights available to you. Because we act on the user's behalf and cannot ordinarily identify Other Participants, we may need to refer some requests to the user who ran the session.
5. Sensitive information
We do not ask for sensitive information and we do not need it. However, a live interview can surface it — for example, a question about your visa or immigration status, or a health matter you mention — and it then becomes part of Session Content. We use Session Content only to provide the session you started, never for advertising, profiling or training AI models, and we do not store it on our servers. The same applies to the reason you give us when you cancel: please leave out health or other sensitive details. If you include them, we use them only to understand your feedback, and only the people at Clozo who work on the product can see them.
You accept our Terms of Service when you start a Trial, buy a plan or create an account (see Section 1 of our Terms of Service), and that acceptance covers our processing, as this Policy describes it, of the audio, screen images and text of your sessions — which may include sensitive information about you — solely to generate your suggestions.
We use this information only to provide the session you start, never to infer characteristics about you, and we do not store it on our servers. You control what you upload and what you say, and you may withdraw any marketing or privacy consent, or ask us to stop non-essential processing, by emailing info@clozo.ai or using the "Your Privacy Choices" control on our website.
California residents: we use sensitive personal information solely to perform the Service you request and never to infer characteristics about you. If you wish to limit the use of your sensitive personal information, you may exercise the "Limit the Use of My Sensitive Personal Information" right by emailing info@clozo.ai or using the "Your Privacy Choices" control on our website, and we will restrict our use of that information to what is necessary to provide the Service you requested.
6. How we use information, and our legal bases
We use personal information for the purposes below. Where the EU or UK GDPR applies, the legal basis for each purpose is shown in brackets.
- To provide the Service — to run sessions, transcribe speech, generate suggestions, store your account and settings, and deliver the plan you bought. (Performance of our contract with you.)
- To process Session Content — solely to provide the session you start, at your direction. (Performance of our contract with you.)
- To run Mock Meetings — to write and voice what the practice interviewer or prospect says, to score your practice rounds and show your Debrief and progress, to count practice units, to avoid asking you questions you have already been asked, and to check that the scoring is consistent before the app shows any readiness number (see section 9D). (Performance of our contract with you; our legitimate interests in making sure the scores we show you are consistent.)
- To take payment and manage subscriptions — including renewals, cancellations and refunds. (Performance of our contract.)
- To show you, before you pay, exactly what you are agreeing to, and to keep proof of it — the renewal and Trial terms shown next to each pay button and every charge you confirm in the Service, recorded with the text, time and IP address. (Legal obligation; our legitimate interests in being able to show what you agreed to.)
- To send you service emails about your account and subscription — the Trial terms when a Trial starts; reminders 7 and 3 days before a Trial becomes a paid plan; a note when you have used your 3 trial interviews; a reminder 30 days before a Yearly plan renews; receipts; a notice when a payment fails or your bank asks you to approve it; cancellation and “Keep my plan” confirmations; a confirmation when you accept the retention discount; a confirmation when you pause your plan, and reminders 7 and 3 days before a paused plan resumes and is charged; an acknowledgement of a support request; a notice when a password is set on your account; the codes you use to sign in again when you cancel; the email that sets up an account created by a purchase, with a private download link for the app; and an email when we change our Terms, this Policy or our Refund Policy. Some of these contain a sign-in link that takes you straight to one action on your account page (for example “Start your plan now”, “Update your card” or “Keep my plan”). These are not marketing and are sent even if you have unsubscribed from marketing. (Performance of our contract; legal obligation.)
- To understand why people cancel and to improve the Service — recording each time someone starts to cancel and what happened next, with a usage snapshot, and analysing the reasons people give (including reasons given before keeping the plan or leaving the steps, and voice notes, transcribed by OpenAI) into topics. We do not use this to make any decision about you, and we do not use your reason for marketing. (Our legitimate interests in finding and fixing what does not work.)
- To offer you something before you cancel — our founder's help, the 25% retention discount (which can be accepted at most once in any 12 months, which is why we record when it was offered and accepted) and, on a Monthly plan, a pause of 1 or 2 months (we record its dates). (Performance of our contract; our legitimate interests in keeping customers.)
- App usage analytics — to see which features are used, where people get stuck and what fails, always on in newer versions of the app, including the titles of your roles and their categories, so that we can see which kinds of roles people prepare for. (Our legitimate interests in understanding how the app is used and fixing what fails.)
- Our own website events — to see how signed-in visitors use our account, checkout, cancellation and book pages and what fails, always on for signed-in visitors. (Our legitimate interests in understanding and improving our website.)
- Error and crash reports — to find and fix failures and slow responses in the website, the app and our servers, once error reporting is switched on. (Our legitimate interests in keeping the Service working and secure.)
- Website session recordings (Microsoft Clarity) — to see where our pages confuse people or fail, for every visitor, on every page except the four listed in section 10. (Our legitimate interests in understanding and improving our website.)
- To run our free book offer — to work out whether you qualify for our free book, Never Take the First Offer, to send it to you, and to email you the steps you have left (see section 9B). (Performance of our contract for the book once you qualify; our legitimate interests in telling you about the offer — you can object to the step emails at any time by unsubscribing.)
- To keep the Service secure and prevent abuse — including detecting and limiting misuse of the free Trial, protecting accounts, and investigating fraud. (Our legitimate interests in securing the Service and preventing abuse.)
- To keep records for disputes and to defend claims — including logs of access, IP addresses, timestamps and usage that help us respond to payment disputes and chargebacks. (Our legitimate interests; and legal obligation where applicable.)
- To communicate with you — to send service messages (such as verification, password reset, billing-portal and activation emails) and to answer your support requests. (Performance of our contract; our legitimate interests.)
- To send you product news and offers — marketing emails about the Service and our other products for interview candidates, where you have allowed marketing on your account, allowed it through our website, or otherwise asked us to contact you. Every marketing email includes an unsubscribe link. The step and reminder emails about our free book are sent differently, as section 9B explains. (Your consent, which you can withdraw at any time.)
- For PostHog analytics and advertising on our website — only where you have allowed the relevant cookies. (Your consent.)
- To meet legal obligations — including tax and accounting records. (Legal obligation.)
- To credit our affiliates — to remember, for 90 days, which affiliate’s link you opened, to record that referral against your account when you complete a checkout, and to calculate the affiliate’s commission from the amounts you pay us. (Our legitimate interests in running an affiliate program and paying affiliates correctly; performance of our contract with the affiliate.)
- To run our affiliate program — to operate the affiliate portal, verify affiliates, calculate and hold commissions, pay affiliates through the payout provider they choose, prevent self-referral and other fraud, and keep the records tax and accounting law require. (Performance of our contract with the affiliate; our legitimate interests in preventing fraud; legal obligation.)
We do not use Session Content, or any personal information, to train or fine-tune AI models.
7. AI providers and sub-processors
To operate the Service we rely on the third parties below, who process personal information on our behalf or, where noted, as independent controllers.
| Provider | Purpose | Data involved |
|---|---|---|
| OpenAI | Real-time speech-to-text; generation of suggested answers; understanding of the screenshots you capture; a fallback for answer generation; in Mock Meetings, turning what the practice interviewer or prospect says into speech when your Mac’s built-in voice cannot (section 9D), and a fallback for writing it and for scoring practice rounds; and, for the reason you give when you cancel, transcribing voice notes and sorting reasons into topics. | Session Content (audio, transcripts, text and screenshot images); in Mock Meetings, the practice counterpart’s words; cancellation reasons (your typed reason, your voice note and its transcript) with a content-free usage summary. |
| OpenRouter, which routes requests to model hosts including Cerebras, Groq and BaseTen, and, for Mock Meetings, OpenAI and Google | Routing of answer-generation requests to AI models, with the hosts listed as preferred providers; in Mock Meetings, routing the requests that write what the practice counterpart says (to OpenAI models) and that score practice rounds (to Google models). | Session Content (text, including transcripts and notes). |
| Vercel AI Gateway | Backup routing for answer generation, and for the Mock Meetings requests above. | Session Content (text). |
| Stripe (independent controller for payments) | Processing payments and subscriptions. | Purchase and payment details, including your card details, which it holds under its own policies. |
| Fly.io | Hosting of our website and backend. | Account, security, usage and purchase data; request logs. |
| Supabase | Our database. | Account, security, usage and purchase data. |
| Resend, with Brevo and SendGrid as backups where we have them set up | Sending our emails: sign-in links and codes, verification, password reset, activation, Trial terms and reminders, receipts and payment notices, cancellation, “Keep my plan” and pause confirmations, pause reminders, policy-change notices, and our free book and its step and reminder emails. | Your email address and the message content. |
| PostHog | Website product analytics (only where you allow analytics cookies). | Website activity and an anonymous identifier. Never Session Content. |
| Microsoft (Clarity) | Recordings and heatmaps of how the pages of our website are used, for every visitor (every page except the four listed in section 10). Our pages tell Clarity that consent is granted for every visitor, and never tell it who you are. Microsoft may also use Clarity data for its own purposes, as described in the Microsoft Privacy Statement and Clarity's terms. | Clicks, taps, scrolling, mouse movement, page layout and the text a page shows, device and browser information, IP address and Clarity's own identifiers; what you type into form fields is masked in your browser and is not recorded. Never your account, email or user ID. |
| Sentry (Functional Software, Inc.) | Error, crash and performance reporting for our servers, website and app, once error reporting is switched on. | Error details, scrubbed stack traces, timings, versions, device model, page or screen, internal account ID. Never Session Content or anything you type; our Sentry project is set not to store IP addresses. |
| For bank transfers, our bank or Mamo (a payment service provider regulated by the Dubai Financial Services Authority); for USDT and USDC, the exchange we send from, TronGrid and our Ethereum and Base node provider (to send and confirm transfers: wallet addresses and transactions), TRM Labs (sanctions screening: the wallet address only), and the public TRON, Ethereum and Base networks; Payoneer when an affiliate chooses it — independent controllers for affiliate payouts | Paying commissions to our affiliates. | An affiliate’s name, email address, country, the payout details they connect, and the amount and reference of each payout, which each provider holds under its own policies. A USDT or USDC transfer is recorded permanently on a public ledger (the address and amount, never a name). Never customer data. |
Retention at our AI providers, and our no-training commitment
Our AI providers process Session Content on our instructions under contract. Their retention is governed by their own terms; based on those terms:
- OpenAI does not use data sent through its API to train its models by default, and keeps a limited amount of real-time and chat data for up to 30 days for abuse-monitoring, unless the law requires it to keep data longer. We do not claim that no data is retained anywhere.
- Cerebras does not retain session content.
- Groq does not retain data by default, but may keep logs for up to 30 days when troubleshooting or investigating abuse.
- OpenRouter does not retain prompts by default.
- We are confirming the retention terms of BaseTen, Vercel AI Gateway and Google (which hosts the models that score Mock Meetings practice rounds) and will describe them here. Each of these providers processes this data only to return a result to you and retains it only as its own data-processing terms allow.
We do not use your personal information, including Session Content, to train or fine-tune any AI model, and our contracts do not permit our providers to do so. If we ever wish to change this, we will ask for your consent first and will not apply the change to information we already hold. Suggestions are generated by AI and can be wrong; they are for you to judge, and are not professional advice — see our Disclaimer.
8. Where Session Content goes
To make the flow clear:
- Audio (both your microphone and your Mac's system audio, which includes Other Participants' voices) is, on all plans, streamed in real time from your Mac, through a relay we operate, to OpenAI for transcription. The relay processes it in memory and does not store it on our servers.
- Transcripts, your résumé/CV text and filename, job descriptions, notes, saved questions and answers, prior-round answers, and text read from your screen are sent to the AI providers above to generate suggestions. Your résumé/CV text is sent when you import it, or ask the app to read it again, not only when a suggestion is generated.
- In Mock Meetings, your microphone audio is streamed through our relay to OpenAI for transcription, as in a live session (there is no system-audio channel: the only other voice is the app’s own); the conversation so far and parts of your practice profile go to the AI providers above to write what the practice counterpart says; the counterpart’s words are turned into speech on your Mac, or by OpenAI when your Mac’s built-in voice cannot do it (section 9D); and the questions, your transcribed answers, the text of the panes you were shown, your target role and skills and a few timing measurements go to the AI providers above to score the round. Section 9D sets out what is kept.
- Screenshot images are sent to AI vision models to read the on-screen content. Screenshot images are not stored on our servers; the text extracted from them is kept in the session on your Mac.
- Session audio, transcripts and suggestions are written to your own Mac by default for a limited number of recent sessions (see How long we keep information). There is currently no in-app switch to turn off local audio recording. The app does not display a recording indicator of its own; this is simply how the Service works.
- Account, security, usage, analytics, purchase, cancellation and book records, and cancellation voice notes, are stored on our servers (Fly.io and Supabase).
There is no cloud history backup and no synchronisation of your Session Content between devices. Your local session history stays on the Mac where it was created.
9. Voice and biometric data
We do not create voiceprints, speaker-identification templates, or any other biometric identifiers, from you or from Other Participants. The Service distinguishes speakers only by which input channel their audio arrives on (your microphone versus your Mac's system audio); it does not analyse voice characteristics to recognise or identify a person. On-device text processing turns text into numeric vectors for search; it does not process audio into a biometric identifier.
9A. When you cancel: your reason, voice notes and the retention offer
What we always record. When you press “Cancel subscription” — in the app or on your account page — we record that you did, when and where, at the moment you press it, together with your plan and subscription status and a snapshot of your usage at that moment (the counts described in section 3, and from the app the titles and categories of your roles, never Session Content).
We then record each step you reach and when: your reason, signing in again (and whether with your password or an emailed code), the “Before you go” step, and the final confirmation; and how it ended — whether you kept your plan, took the 25% discount, paused your plan, asked our founder for help, left the steps, cancelled, or later chose “Keep my plan”. If your subscription is cancelled outside these steps, we record that too. We record all of this whether or not you finish cancelling, because the moment someone considers leaving is when we most need to understand why.
Your reason. To continue cancelling, you tell us why — by typing a reason, recording a voice note, or both. What you type is saved when you press “Submit”, when you press “Keep my plan” or close the steps with × instead, and also if you leave the page, or close the app's window, with a typed reason you have not submitted. A voice note is saved when you press “Submit”, “Keep my plan” or ×. Saving a reason never cancels anything: if you kept your plan, we record that you kept it. Before you submit, you can play back, re-record or delete a voice note.
Voice notes. A voice note is recorded only while the recording indicator is shown, for at most two minutes. In newer versions of the Mac app, your words appear as text while you speak, using Apple's speech recognition, which runs on your Mac where the Mac supports it and otherwise uses Apple's servers under Apple's privacy policy. When a voice note is saved, the recording is uploaded to our servers and transcribed by OpenAI; OpenAI's handling of it is described in section 7. We do not use voice notes to identify you or anyone else and we create no voiceprint from them (see section 9).
How we analyse reasons. We send your typed reason and the transcript, with a content-free usage summary (for example your plan and how many interviews you ran), to OpenAI to sort them into topics such as “transcription quality”, “price” or “hard to set up”, with a severity and a one-line summary; names, companies and contact details are removed from that summary. The topics help us decide what to fix, and a reason that reports a serious failure is flagged to our founder. This never changes your plan, your price or your cancellation, and we do not use your reason, or the fact that you started to cancel, for marketing.
Who sees it. Only the people at Clozo who work on the product, through an access-controlled internal tool. Your reason, voice note and transcript are never sent to Stripe, advertising platforms or Sentry, and never written to our server logs. Our cancellation pages never show your reason back to you as page text, and Microsoft Clarity does not run on them.
The retention offer. Everyone who reaches the “Before you go” step is offered our founder's help. The 25% discount is offered too, unless a discount was accepted on your account in the last 12 months (a discount you were shown but did not take does not count). If you accept it, it reduces one payment — normally the next automatic payment of the plan you have at that moment; our Terms of Service explain the exceptions — and we email you a confirmation. We record when we showed the discount, whether you accepted it and which payment it applies to.
On a Monthly plan the same step also offers a pause of 1 or 2 months instead; if you choose one, we record its dates and the terms shown to you, email you a confirmation, and remind you 7 and 3 days before your plan resumes and is charged. If you ask for our founder's help, we create a support request linked to your cancellation, so the founder can see your reason and reply to your account email, and we email you an acknowledgement.
How long we keep it. The audio of a voice note: 1 year from upload, then deleted; our database backups never contain it. The reason you typed and the transcript: for as long as your account exists (deleted with your account). The record of the click, the steps and the outcome, and the discount record: while your account exists.
9B. Our free book: step emails, download links and your browser
What we record. Our free book, Never Take the First Offer (The Salary Negotiation Book), is sent to accounts that have a Trial or a plan, have signed in to the Mac app, and have an email address that accepts mail. For each account we record which of these steps are done, which step and reminder emails we sent, when the book was granted and sent, how many times it was downloaded, and whether and how you unsubscribed from the step emails. We keep this record while your account exists, because it is how we make sure the book is sent only once.
Step and reminder emails. Until you have finished the steps, we email you what is left: one email when you reach each new stage, and reminders one day and three days later — whether or not you have allowed marketing email. Accounts created before the offer started that have neither a Trial nor a plan at that time may receive one email about it.
These are marketing emails: each has an unsubscribe link, and your email app can unsubscribe you in one click. Unsubscribing, or turning off marketing email on your account page, stops every later step and reminder email about the book, whatever your situation; the book itself, an email you ask for (such as the link to download the Mac app), and every email about your account, Trial, plan, payments and cancellation continue.
Links. Links from these emails to our website carry a short tag naming the email and the button (for example bk=eb3.d1.cta) and standard campaign parameters (utm_…), so that we can count which emails and buttons are used; the tags contain nothing about you. The link to download the book is private to your account and expires (a link in our email after 90 days; a link from your account page or the app after 10 minutes). The link to download the Mac app is also private to your account and expires. We record that a download started, not what you do with the file.
Your browser: a functional identifier. When you sign in to our website, your browser stores a random identifier (clozo_bid, in the browser's local storage for interview.clozo.ai; it is not a cookie). It is made from nothing and contains no personal information. It is sent to our servers only when you sign in and when our website shows the progress of your book, and our servers keep only a scrambled (keyed-hash) form of it, linked to the Interview Clozo accounts that sign in from that browser.
Its only purpose is to show which of your accounts has the Trial and the book: if you sign in with a different account in the same browser, the book's progress panel can show a masked form of the email address of your other account that has the Trial or plan (for example a•••@b.com).
A link between the identifier and an account is deleted after 180 days without use, and deleting an account deletes its links. Clearing your browser's site data for interview.clozo.ai removes the identifier. It is functional and always on, like the website records described in section 10: our cookie banner does not control it, it is never used for advertising or analytics, and Microsoft Clarity does not read it.
9C. Our affiliate program: referral links, what affiliates see, and affiliates’ own information
The referral value. Some people reach interview.clozo.ai through a link shared by one of our affiliates — a creator, a coach or a community that we pay a commission when someone they referred buys a plan. When you open such a link (it carries ?via=, ?ref= or ?aff= and the affiliate’s code), your browser keeps the affiliate’s code, which link you opened and when, as a value named clozo_via in its local storage (not a cookie). It lasts 90 days; if you later open another affiliate’s link, that code replaces the earlier one.
It contains no personal information and is never sent to the affiliate. It is not used for advertising; the page address that carried the link, like every page address, is visible to the session-recording and analytics tools described in section 10. It is strictly functional and always on, like the website records described in section 10: our cookie banner does not control it and Global Privacy Control does not switch it off. Clearing your browser’s site data for interview.clozo.ai removes it.
When the referral is recorded. The code is sent to our servers when you open the link (the click record described in section 3) and when you complete a checkout, including a checkout that creates your account. It is also sent when you open “Have a code?” on our pricing page and press Apply, and a code you enter there is recorded the same way.
We then record on our servers that your account was referred by that affiliate — the code, the link and the first and last click — and keep that record with your purchase records for as long as we keep them (section 15). We also copy the code into the metadata of your Stripe checkout records, so that a purchase completed later can still be credited correctly. After that, the browser value no longer matters for your account.
What the affiliate sees. The affiliate’s portal shows, for each referral, its status (lead, customer or churned), the plan, the dates, and the amounts in US dollars on which the affiliate’s commission is based, together with the commission and payout records. It never shows your name, your email address, your payment method, your IP address, your usage, your Session Content or anything else that identifies you, and affiliates agree not to try to identify you. We do not share your personal information with affiliates, and affiliates never contact you on our behalf.
If you are an affiliate. When you join our affiliate program we collect the information listed under “Affiliate information” in section 3 and use it as section 6 describes: to run the portal, calculate and hold commissions, pay you, prevent fraud and meet our legal obligations. To pay you we share your name, email address, country and the payout details you connect with the payout provider for your payout method — our bank or Mamo for a bank transfer; for USDT and USDC, the providers listed in section 7 — which handles them under its own privacy policy as an independent controller; we keep only a reference to the payout account and the result of each payout.
USDT and USDC payouts are not available to residents of the United Arab Emirates. We may ask you for tax details and proof of identity before paying you, and we keep those with your payout records. Affiliate records are kept as section 15 describes. If you join the optional leaderboard, your chosen display name, level and the number of customers you referred in the month are shown to other affiliates; leaving it is one press in Settings.
You have the rights in section 17 over your affiliate information; to exercise them, or to close your affiliate account, email info@clozo.ai or use the portal’s Settings page. The affiliate portal itself (interview.clozo.ai/affiliates/portal.html) runs only code from our own website: Microsoft Clarity, advertising technologies and PostHog analytics do not run there (section 10).
Every account has an affiliate code set aside from the start — usually your username, otherwise one we generate; nothing is attributed to it, and it is not used anywhere, until you turn on your affiliate link.
9D. Mock Meetings: practice rounds with an AI interviewer or prospect
Mock Meetings. When you practise with the app’s AI interviewer or prospect, your microphone audio is transcribed as in a live meeting: it is streamed from your Mac through our relay to OpenAI, and our servers do not store it. To write what the counterpart says next, the app sends our servers the conversation so far and parts of your practice profile (your target role, seniority, skills and highlights); an AI model writes the counterpart’s words from them and from the practice scenario you chose, and they come to your Mac one at a time.
To produce your Debrief, the app sends the questions, the written transcript of your answers, the text of any answer panes it showed you, your target role and skills, and a small set of timing measurements (for example how long you spoke and paused) to our servers, where an AI model scores them against the scenario’s criteria.
That text is held in our servers’ memory while the Debrief is made and for up to 15 minutes afterwards, so the reply can be sent again if the app misses it, and is then discarded; neither it nor the conversation is stored in our database, written to our logs, or used to train any model. For some rounds, our servers score the same answers a second time and keep only how far apart the two scores were, so we can check that the scoring is consistent. The Debrief itself is stored on your Mac in History.
We keep a record that the session took place (which scenario, its length and mode, the units it used, how it ended and how many questions were answered), which questions it asked, so that later rounds do not repeat them, and the scores it produced — as numbers only, never the words — so the app can show your progress and so we can check that our scoring is consistent, for as long as your account exists; deleting the session in History deletes those scores from our servers too, and the record that it took place stays.
The words the AI interviewer or prospect speaks are turned into speech on your Mac by a built-in voice model (Kokoro), which the app downloads once from a public model repository the first time you practise; while that download is still running, on an Intel Mac, or on a version of macOS the model cannot run on, they are turned into speech by OpenAI’s text-to-speech service instead, and if that cannot be reached, your Mac’s own system voice speaks them.
Only the counterpart’s own words are ever sent to OpenAI (they may briefly acknowledge what you said) — never your voice or your transcript. The audio of each line is kept in a cache on your Mac; a line voiced by OpenAI is also kept in a cache on our servers, not linked to any account, so the same line need not be voiced twice.
Your delivery. Your pace, your pauses and how long you spoke are measured on your Mac; only those numbers, not your audio, go into the scoring, and they are not used to recognise or identify you (see section 9).
On your Mac. Each practice round’s record (its questions and the transcript of your answers), its Debrief, its recording and its diagnostic trace, your practice profile, your practice progress (skill bands, personal bests, weekly target and milestones) and the cached voice lines are kept on your Mac. Deleting a round in History deletes its record, Debrief, recording and trace from your Mac and its scores from our servers; “Delete all” for Mock reports in the app’s Settings deletes every Debrief on your Mac and their scores on our servers; resetting your practice progress clears it on your Mac.
The scores are an AI evaluation. Every score in a Debrief is an AI model’s evaluation of a practice round, tied to what you said; it is for you to read, it is not a decision about you, we do not share it with anyone, and it does not predict the result of any real interview or meeting.
10. Analytics, session recordings, error reports and cookies
On our website. Microsoft Clarity runs on every page of our website except four — including the pricing, sign-in, subscription-management and legal pages — for every visitor, starting shortly after the page loads. The four exceptions are your account page, the payment-confirmation page, the cancellation pages and the affiliate portal: they run only code from our own website, so Microsoft Clarity, PostHog analytics and advertising technologies never run there, whatever you choose in our cookie banner, and the payment-confirmation page sends no purchase event to any advertising platform.
The payment pages themselves are hosted by Stripe on its own site, where our code, and so Clarity, does not run. Clarity does not wait for your cookie choice: for every visitor, whatever you choose in our banner and whether or not your browser sends Global Privacy Control, our pages tell Clarity that consent to its analytics and advertising storage is granted, so Clarity sets its cookies and records complete visits.
Clarity records how our pages are used — clicks, taps, scrolling, mouse movement, the page's layout and the text it shows — so that we can replay and study visits; what you type into form fields is masked in your browser and is not recorded. Before Clarity starts, any sign-in, checkout or cancellation code in the page's address is removed. We never tell Clarity who you are: recordings are not linked to your account, your email address or your user ID.
When you are signed in, our website also sends our own servers content-free events from the pages you use — for example the pages you open, which account, checkout and book buttons you press and whether they worked, repeated or unanswered clicks, and errors shown. These events are always on for signed-in visitors: they do not wait for your cookie choice, and neither the cookie banner nor Global Privacy Control switches them off. They set no cookie and never include what you type.
Our other analytics (PostHog) and all advertising technologies load only if you allow them in our cookie banner, and never on our account, sign-in, password-reset, verification, subscription-management, cancellation, payment-confirmation, welcome, app sign-in or support pages. Once error reporting is switched on, our pages report script errors and how long pages take to load to Sentry, which sets no cookie and never receives what you type. For the full list, the categories, durations and how to change your choices, see our Cookie Policy.
The referral value clozo_via, which credits one of our affiliates when you reached us through their link, is strictly functional and always on in the same way; section 9C describes it.
In the Mac app. The app sets no cookies and runs no advertising or session-recording technology. Newer versions of the app always send us the usage analytics described in section 3 — including repeated or unanswered clicks and how far you scroll long screens, which show us where people get stuck in the app, as Clarity does on our website — and, once error reporting is switched on, crash reports and how long some actions take.
This is part of how the app works; there is no setting to turn it off. It never includes Session Content, other text you type, résumé text or file names, the words shown on the app's buttons or screens, or the audio or transcript of an interview. The one exception is the title you type for a role, which we record with its category; only the people at Clozo who work on the product can see it.
During a Trial, newer versions of the app can also show you notifications about your Trial (at most one a day, never during an interview and never at night). They are created on your Mac from your Trial's status, and the app reports which ones were shown and opened. You can turn them off with “Trial and billing reminders” in the app's Settings, or in macOS System Settings; that choice affects notifications only, not the usage analytics described above.
On our servers. Our servers keep technical logs of requests, errors and response times, with sign-in and cancellation codes removed from them, and record AI errors and slow AI responses against your account, without Session Content.
11. Advertising, pixels and "sharing" or "sale"
We advertise Interview Clozo on other websites and apps. To measure whether our ads work and to show our ads to people who have visited our website, we use advertising and measurement technologies from Google, Meta, Microsoft, LinkedIn, Reddit and X. Where you allow advertising, Microsoft Advertising's tag also links Microsoft Clarity's recordings of your visit to Microsoft's advertising measurement. These technologies run only on our marketing website, and only after you accept advertising cookies in our banner.
When you allow them, each platform may receive: the pages you view on our website; the ad you clicked (including click identifiers); your IP address, browser and device information; cookie identifiers; and events such as starting a checkout (the plan and its value, never your card details). A platform may combine this with information it already holds, including across devices where you are signed in to it, and may use it for its own purposes under its own privacy policy.
Some US state laws describe allowing an advertising platform to receive this information — through cookies, pixels or server-side events — as "sharing" for cross-context behavioural advertising, as "targeted advertising", or as a "sale", even when no money changes hands. We do not sell personal information for money.
Categories shared for advertising in the 12 months before the date at the top of this Policy: When you accept advertising cookies, we share online identifiers (cookie identifiers, your IP address and any ad click identifier), your activity on our website, and the fact and value of a sign-up, checkout or purchase, with the advertising platforms named above. Under some US state privacy laws this counts as “sharing” for cross-context behavioural advertising, and may be treated as a “sale”.
You can stop it at any time through “Your Privacy Choices” or Global Privacy Control. Separately, Microsoft receives Microsoft Clarity's recordings of every visitor's use of our pages, whatever your cookie choices — our pages tell Clarity that consent is granted for every visitor — and may use Clarity data for its own purposes; some US state laws may treat that as “sharing”. Global Privacy Control and “Your Privacy Choices” do not switch Clarity off.
We have not sold or shared Session Content, passwords, payment-card data, cancellation reasons, book records, our own website events, or any information from the macOS app (including its usage analytics), and we never will for advertising. We do not knowingly sell or share the personal information of anyone under 16.
You can opt out of this sharing at any time using the "Cookie settings" and "Your Privacy Choices" links in the footer of every page of our website, by rejecting advertising cookies in our banner, by sending a Global Privacy Control signal (see below), or by emailing info@clozo.ai. You do not need an account to opt out. These choices cover advertising and PostHog analytics; they do not switch off Microsoft Clarity or our own website events (section 10).
12. Global Privacy Control and other opt-out signals
If your browser or an extension sends a Global Privacy Control ("GPC") signal, or another opt-out preference signal recognised by law, we treat it as a request to opt out of the sale and sharing of your personal information and of targeted advertising. We apply it to that browser and device and, where you are signed in, to your account, automatically and without asking you for anything further. When we detect the signal, our cookie-settings panel shows that your opt-out request has been honoured, and the signal overrides any earlier acceptance on that browser.
We honour these signals for visitors from every location. If you later want to allow advertising cookies again, you can do so in "Cookie settings". We do not require you to verify your identity or to create an account in order to opt out. Global Privacy Control does not switch off Microsoft Clarity, our own events for signed-in visitors (section 10) or the functional browser identifier described in section 9B.
13. International transfers
Clozo FZE LLC is based in the United Arab Emirates. Our servers run on Fly.io, and most of our service providers operate in the United States. Wherever you live, your information will be processed in the United Arab Emirates, the United States, and the other countries where our providers operate. Those countries may not have data-protection laws equivalent to those where you live, and their authorities may be able to access information under local law.
When you give information to us directly, we collect it in the United Arab Emirates. Where we transfer personal information protected by the EU or UK GDPR to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (with the UK Addendum where relevant) or, for recipients certified under the EU–US Data Privacy Framework and its UK Extension, on that certification.
Where the UAE Personal Data Protection Law applies, we transfer information under contractual safeguards requiring the recipient to protect it to the standard that law requires, or where the transfer is necessary to perform our contract with you. You can ask for more information about these safeguards at info@clozo.ai. We put in place appropriate safeguards for these transfers, including standard contractual clauses where required.
14. Automated decisions
We do not make decisions about you based solely on automated processing that produce legal effects or similarly significant effects on you, and we do not use automated decision-making technology to make significant decisions about you. The suggestions the app generates are for you to read and judge; they are not decisions about you, and we do not use them to assess you. The same is true of the scores in a Mock Meetings Debrief: they are an AI model’s evaluation of a practice round, for you to read.
One automated control does affect access: to prevent misuse of the free Trial, our systems can automatically refuse to create a new account from a device or network that has already used its free allowance or that shows signs of automated abuse, and an account or email address that has already had a free Trial cannot start another (a checkout that tries to starts the paid plan at once, as our Terms of Service explain). If this happens and you believe it is a mistake, email info@clozo.ai and a person will review it within 10 business days.
We use an AI model to sort cancellation reasons into topics (section 9A). The result informs what we fix; it never changes your plan, your price or your cancellation. Whether we offer you the 25% retention discount depends only on whether a discount was accepted on your account in the last 12 months and whether your plan is one it can apply to — never on a profile of you.
15. How long we keep information
We keep personal information for the periods below, unless the law requires us to keep it longer or we need it to establish, exercise or defend a legal claim.
- Account information (username, email, optional name, password hash, marketing preference): while your account exists, and deleted within 30 days of account deletion; backups are overwritten within a short cycle thereafter.
- Sign-up records from our create-account page (the username, email address and name you gave, the sentence you agreed to and the version of the Terms it names, the time, the IP address, browser, device identifier and country, the referral value if you arrived through an affiliate’s link, and the Stripe references of the payment method you saved): while your account exists, as the record that you accepted our Terms; deleted within 30 days of account deletion. A sign-up that was not finished, or was refused: deleted 90 days after its last change.
- Sign-in sessions: app sessions for 90 days from last use; web sessions for 30 days; or sooner when you sign out.
- Security and anti-abuse records (IP address, device identifier, macOS login name, Mac model and OS version, and sign-up, sign-in, session-start and purchase-access events): 24 months from each event, to prevent fraud and abuse and to answer payment disputes.
- Usage, session and quota records (section 3): while your account exists.
- Mock Meetings records on our servers (section 9D): while your account exists. A round’s scores are deleted when you delete the round in History, or every Debrief in the app’s Settings; the record that the round took place and the questions it asked stay. When your account is deleted, its scores and the list of questions you were asked are deleted; the records of its practice rounds and their units, which hold no words, audio or scores, are kept with your billing history.
- Mock Meetings text on our servers: what is sent to write the counterpart’s words is not stored; what is sent for a Debrief is held in memory for up to 15 minutes, then discarded.
- Voiced practice lines: on our servers, in a shared cache that holds no account information, until newer lines replace them (the cache is kept to a fixed size); on your Mac, in a cache of up to 150 MB, oldest first.
- Mock Meetings on your Mac: each practice round’s record and Debrief, until you delete the round (they are not removed automatically); your practice profile and practice progress, until you change, reset or delete them.
- App usage analytics and our own website events: individual events for up to 90 days (sometimes less, to save space); daily counts, by app or website version, for 25 months; a record of first-time milestones (for example the first role you created, with the title you typed for it, or finishing onboarding) and your latest daily summary while your account exists.
- Error and crash reports at Sentry (once error reporting is switched on): up to 90 days.
- Website session recordings (Microsoft Clarity): kept by Microsoft for 30 days, unless we mark a recording to keep, when Microsoft keeps it for up to 13 months; heatmaps are aggregated. Because recordings are not linked to your account, we cannot find or delete the recordings of one person; they expire on Microsoft's schedule.
- Billing history (Trial start and end, charges, renewals, plan changes, pauses, failed payments, cancellations, retention discounts, refunds): as purchase records, 7 years. If you delete your account, we keep only what the law requires, without the details of those events.
- Records of the terms shown to you and the charges you confirmed: while your subscription runs, and then 3 years from when they were shown or 1 year after the subscription ends, whichever is later — even if you delete your account sooner, because the law requires us to be able to show them.
- Cancellation records (the click, the steps, the outcome, the usage snapshot and the retention-discount record): while your account exists. Your typed reason and voice-note transcript: for as long as your account exists (deleted with your account). Voice-note audio: 1 year from upload, then deleted.
- Book records (section 9B): while your account exists. Links between your browser's identifier and your accounts: deleted 180 days after they were last used, or when the account is deleted.
- One-time sign-in codes and single-use links: deleted 7 days after they expire.
- Records of which celebration animations were shown to you: up to 90 days.
- Database backups: kept for 14 days; they never contain voice-note audio or app and website usage events.
- Purchase records (plan, price, dates, purchase IP address, our payment provider’s transaction identifiers, billing country): 7 years, as required by UAE tax and accounting law, for tax, accounting and dispute purposes.
- Payment-method summaries (section 3): while your account exists, and deleted within 30 days of account deletion. A method you remove leaves your account at once; we keep only its Stripe reference, so that it cannot be added back by mistake. Stripe keeps the payment method itself under its own policy.
- Session Content on our relay: not stored; held in memory only while a request is processed.
- Session Content at AI providers: governed by each provider, as described in section 7 (OpenAI up to 30 days for abuse-monitoring; Cerebras none; Groq none, or up to 30 days in limited cases; OpenRouter prompts none).
- Session history on your Mac (transcripts and suggestions): your most recent sessions (currently the newest 40, subject to a size limit), kept until you delete them from History or newer sessions replace them.
- Diagnostic traces on your Mac: a separate technical record of each session, which includes the text of the prompts sent and the answers returned, kept for your recent sessions (currently the newest 25 real sessions and every one from the last 7 days, plus the newest 25 very short ones) and removed when newer sessions replace them. Deleting a session from History deletes its diagnostic trace.
- Your résumé/CV on your Mac: the text the app read from it and, in app versions that let you open the original, a copy of the original file, kept until you replace or delete it.
- Session audio on your Mac: written by default for each session (each recording capped at three hours a side); there is currently no in-app switch to disable this. The app keeps the recordings of your recent real sessions (at least the newest three, and every one from the last 7 days) and of the newest three very short ones, within 2 GB for all session records; when a new session starts, older recordings are removed, the very short ones first. Deleting a session from History deletes its recording and its diagnostic trace.
- Support emails and support requests (including a request for our founder's help made while cancelling): for up to 3 years after the request is closed (a request that is never marked closed: 3 years after it last changed), or until your account is deleted, if that is sooner.
- Website analytics (PostHog): up to 12 months; the analytics cookie lasts up to 365 days, or is not set if you reject analytics.
- Advertising click identifiers and campaign parameters recorded against a purchase (for example a Google gclid or a Meta fbclid, where you allowed advertising cookies): kept as part of the purchase record, for the same period as that record. We do not apply a separate, shorter retention period to them. You can ask us to erase them at any time using the contact details in section 1.
- Advertising data held by the platforms: retained by each advertising platform under its own policy; see the Cookie Policy.
- Consent and opt-out records: up to 5 years, so we can show what you chose.
- Privacy-request records: 24 months.
- Email delivery records (section 3): 24 months from each email, to answer delivery problems and payment disputes; deleted within 30 days of account deletion. The counters we use to spot repeated temporary failures (a full mailbox, for example): 7 days.
- Email unsubscribe and do-not-mail list (addresses that unsubscribed, bounced or reported our email as spam): kept indefinitely, so that we do not email you after you unsubscribe, even after your account is deleted. A record that an address was taken off that list is an opt-out record: 5 years.
- Referral value (
clozo_via, in your browser): 90 days from the last referral click, or until you clear your browser’s site data. The click record on our servers: 30 days, then daily counts only. The referral record on our servers (which affiliate referred your account, the link and the clicks): as part of your purchase records, for the same period as those records. - Affiliate profile information (the names, company, website and audience you give for the program, the details of the payout methods you connect, and the IP address and browser recorded with your acceptance of the Affiliate Program Terms and with your activity in the portal): while your affiliate profile is open; deleted 30 days after it is closed or, if a balance, commission or payout is still open on that day, once it is settled — except what the next item requires us to keep. Closing your affiliate profile does not delete your account: its username, email address and password are account information (above).
- Affiliate commission, payout, tax and identity records (every commission, hold, reversal and payout with its provider reference; tax details and your country; identity documents; the version of the Affiliate Program Terms accepted): 7 years from the payout or the closure of the account, whichever is later, as required by UAE tax and accounting law and to defend claims.
- Sanctions check results (the screening of an affiliate’s wallet address and name): We keep the results of sanctions checks for as long as the law requires, including after an account is closed.
To delete individual sessions from History, use the app's history controls; this removes the session's transcript and suggestions from History together with its diagnostic trace and any audio recording of it. Session records are kept in the session-traces folder inside the app's Application Support folder (~/Library/Application Support/Interview Clozo), one folder per session, and you can also delete any of them there at any time. To remove all local files, delete the app's Application Support folder from your Mac. To request deletion of your account and the data we hold on our servers, email info@clozo.ai.
Deleting your account deletes your cancellation records, reasons, transcripts and voice notes, your usage analytics and website events, your support requests, your book records and your browser links, your sign-up record, your payment-method summaries and your email delivery records; we keep your billing history without its details, and the records of the terms shown to you, for the periods above, and your address on our do-not-mail list if it is there, and we ask Sentry to delete the error reports that carry your account ID. We handle account-deletion and data-export requests manually: email info@clozo.ai and we will complete your request within the response times in section 17.
16. Security
We protect personal information with measures appropriate to its sensitivity, including encryption in transit, hashed passwords, access controls limited to staff who need access, session tokens, and keeping Session Content off our servers. No system is completely secure, and we cannot guarantee absolute security. If a breach affects your personal information, we will notify you and the relevant authorities where the law requires, without undue delay, and will tell you what happened and what you can do.
17. Your rights by region
Depending on where you live, you may have some or all of the following rights: to know what personal information we hold about you and to receive a copy; to correct it; to delete it; to receive it in a portable format; to restrict or object to certain uses; to opt out of the sale or sharing of personal information and of targeted advertising; to withdraw consent (without affecting processing already carried out); and to object to processing based on our legitimate interests, including profiling. Wherever you live, we will extend these rights to you, except where the law allows us to decline (for example, records we must keep for tax purposes).
How to exercise your rights. Email info@clozo.ai. We will verify your request using information we already hold, usually by confirming control of your account; we will not require verification simply to opt out of sale or sharing. You may use an authorised agent with your written permission. We will not treat you differently for exercising your rights. You can withdraw consent to website advertising and PostHog analytics at any time in “Cookie settings”; Microsoft Clarity, our own website events for signed-in visitors, the functional browser identifier and the app's usage analytics do not depend on those settings (sections 9B and 10).
Response times. We respond within the time your law requires — generally 45 days in the United States (extendable once by a further 45 days), one month in the EEA and UK (extendable by two further months for complex requests), and, in India, within the periods that apply once those rights are in force.
United States
Residents of California and of other US states with comprehensive privacy laws have the rights described above, including the right to opt out of sale, sharing and targeted advertising, and (where applicable) the right to appeal. To appeal a decision on your request, reply "appeal" to our response and a different member of staff will review it; if you remain dissatisfied you may contact your state Attorney General. California residents may also see the Notice at Collection below and the "Your Privacy Choices" link in our website footer. Provisions of any agreement that purport to waive or limit your rights under the CCPA, including any representative-action waiver, do not apply to those rights.
EEA and United Kingdom
Individuals in the EEA and UK have the rights above under the GDPR and UK GDPR, including the right to lodge a complaint with a supervisory authority (in the UK, the Information Commissioner's Office). You may contact us at info@clozo.ai. We do not route privacy complaints into any arbitration clause.
India
Once the relevant provisions of India's Digital Personal Data Protection Act are in force, individuals in India will have the rights above, may contact us at info@clozo.ai, and may complain to the Data Protection Board of India.
United Arab Emirates
Where the UAE Personal Data Protection Law applies, you have rights of access, correction, deletion, restriction, portability and objection (including to automated processing), which you may exercise at info@clozo.ai.
Canada (including Quebec)
Individuals in Canada may exercise the rights above and may contact our Privacy Officer at info@clozo.ai, or complain to the Office of the Privacy Commissioner of Canada or, in Quebec, to the Commission d'accès à l'information. Your personal information is processed outside Canada and may be accessible to authorities in those countries under their laws.
Australia
Individuals in Australia may seek access to and correction of their personal information and may complain to the Office of the Australian Information Commissioner. Your personal information may be disclosed to recipients overseas, including in the United States and the United Arab Emirates.
18. Children
Interview Clozo is for adults. You must be at least 18 years old to create an account or buy a plan. Our website and app are not directed to children, and we do not knowingly collect personal information from anyone under 18. If we learn that we have, we will delete it and close the account. If you believe a child has provided us with information, contact info@clozo.ai.
19. Changes to this Policy
We will update this Policy when our practices change, and at least once a year. We will post the new version with its date and keep the previous version available on request. When we change this Policy, we email every account holder when the new version is published, and it applies from that day — the date shown at the top of this Policy. We will never use information we already hold to train AI models, or share it in a new way for advertising, unless you agree.
20. Notice at Collection (short form)
We collect your account details, purchase and billing details (including the terms shown to you when you paid), device and security information, usage and session records, the app's usage analytics (including the titles of your roles), our own website events when you are signed in, records of our free book offer, and, when you run a session, the audio, screen images and text of that session, and, when you practise in Mock Meetings, a record of each practice round and its scores as numbers, in order to provide Interview Clozo, keep it secure, improve it and meet our legal obligations.
On our website, Microsoft Clarity records how our pages are used (every page except your account page, the payment-confirmation page, the cancellation pages and the affiliate portal), for every visitor, with what you type masked and without linking the recordings to your account; advertising and PostHog analytics run only if you allow them. When you start to cancel, we record that you did and collect your reason, which may include audio information from a voice note that OpenAI transcribes.
Session Content and cancellation reasons are not sold, are not shared for advertising, and are not used to train AI models. How long we keep each category, and your choices, are set out above in How long we keep information, Analytics, session recordings, error reports and cookies, Advertising, pixels and "sharing" or "sale" and Your rights by region.
If you reached us through an affiliate’s link, we also collect the referral value and click record described in section 9C and record which affiliate referred your account, to pay that affiliate; affiliates see only the status of the referral and the amounts their commission is based on. If you join our affiliate program, we collect your affiliate account, payout, tax and identity information to run the program and pay you.
21. Contact and complaints
For any question or request about this Policy or your personal information, contact us at info@clozo.ai. You also have the right to complain to your data-protection authority, including your EEA supervisory authority, the UK Information Commissioner's Office, the Office of the Privacy Commissioner of Canada or Quebec's Commission d'accès à l'information, the Office of the Australian Information Commissioner, the UAE Data Office, or the Data Protection Board of India once it accepts complaints.