Skip to main content
CareerVerse
CareerVerse
Career TwinAI MentorPractice
EarnSign inStart free
Home
Practice
Ask
Career
Community
CareerVerse
  • Career Twin
  • AI Mentor
  • Practice
  • Courses
  • Community
  • Refer and earn
  • Contact
  • Privacy
  • Terms
  • Delete your account

© 2026 CareerVerse. All rights reserved.

  • Privacy Policy
  • Terms
  • Referral terms

Privacy Policy

Last updated 17 November 202617 sections

On this page17 sections
  1. 1 Who we are
  2. 2 Information we collect
  3. 3 How and why we use your data, and our legal bases
  4. 4 AI processing, your Career Twin, and on-device proctoring
  5. 5 Cookies and local storage
  6. 6 How we share your data
  7. 7 International data transfers
  8. 8 How long we keep your data
  9. 9 How we keep your data safe
  10. 10 Your privacy rights
  11. 11 Third-party links
  12. 12 Grievance Officer (India)
  13. 13 Children
  14. 14 Content you post in public areas is public
  15. 15 Changes to this Policy
  16. 16 YouTube
  17. 17 Contact us

On this page

  1. 1 Who we are
  2. 2 Information we collect
  3. 3 How and why we use your data, and our legal bases
  4. 4 AI processing, your Career Twin, and on-device proctoring
  5. 5 Cookies and local storage
  6. 6 How we share your data
  7. 7 International data transfers
  8. 8 How long we keep your data
  9. 9 How we keep your data safe
  10. 10 Your privacy rights
  11. 11 Third-party links
  12. 12 Grievance Officer (India)
  13. 13 Children
  14. 14 Content you post in public areas is public
  15. 15 Changes to this Policy
  16. 16 YouTube
  17. 17 Contact us
Back to top

In short: This policy explains what personal data CareerVerse collects, why, and the rights you have. We use passwordless sign-in — an emailed one-time code, or "Continue with Google" or, in our iPhone app, Sign in with Apple if you choose one (note that Google's sign-in button loads on our home page, so Google sees your visit even if you never use it — Section 2(a1); and if you create your account that way, we start your profile with the name and photo from your Google Account — Section 2(a2)) — store your content to run the Service, and send some content to a third-party AI provider (OpenAI, etc.) to power AI features. If you sit a mock interview, the audio of your spoken answers is sent to a speech-to-text provider so it can be graded, and the text of each question is sent to a speech-synthesis provider so it can be read aloud — Section 4 sets out exactly who receives what, names the provider that transcribes your voice — which processes it in the European Union — together with the browser fallback (in the app, your phone's own speech service) that takes over when it cannot run, and is blunt about the one localisation promise we cannot make. We also build a Career Twin for you automatically from work you complete here — it shows the skills on your record and the work behind each, gives each skill a standing that your graded results move, and, against a target you choose, shows how far your record reaches it. We never lower a standing because of results that did not pass without asking you first. Those standings and figures decide nothing, and we do not send them to employers or anyone else, except to our AI provider, only to write your own AI Mentor replies, and only while you let the mentor read your Career Twin (Section 4). You can switch off any source of it at any time in your account settings, which also deletes what we derived from that source (Section 4). On our website we use optional third-party analytics (Google Analytics, and PostHog, which also records replays of your visits to our website with all text and typed input hidden and, once you sign in, links what it records in that browser to your account by a pseudonymous id, including what it recorded there before you signed in) and advertising-measurement (Google Ads and Meta Pixel) tools that load only if you consent, and — again only with your consent — record which channel or campaign brought you to us (Section 2(l)). We also set, without asking, a small cookie that only remembers which of our campaign links your browser has opened, so we count each browser once; it is never linked to your account and never used to credit a sign-up (Section 5). We also keep your browser's time zone in a cookie, without asking, so our pages can show you dates and times in it; it holds nothing else and is never linked to your account (Section 5). We advertise CareerVerse and measure which ads lead to visits, sign-ups, and free-trial starts — including sharing a hashed (SHA-256) version of your email with Google to match those results and page-visit/browser signals with Meta — but we do not sell your data or show third-party ads on CareerVerse. Anything you post in the public Community is visible to anyone and can appear in search engines (see Section 14). Our app for iPhone and Android differs from the website in three ways you should know about: it sends usage data to Google Analytics for Firebase, and crash reports and a note of each time you use it to Sentry, as soon as it opens, without asking first, until you turn off its Send analytics and crash reports switch, and it also sends Google your phone's advertising ID, to measure our own ads, on an iPhone only if you agree and on Android unless you turn off its Ad measurement switch, and sends that ID and a few events to Meta too: from version 1.0.1 of our Android app once the app has shown you its short line about our partners or you turn on Meta ad measurement, until you turn it off, and without asking for your consent, in Europe as elsewhere, and from version 1.0.3 of our iPhone app only once you allow tracking in Apple's prompt or later in your iPhone's Settings, until you turn it off; Meta may use them for the ads it shows you, though on a phone the app treats as being in Europe the app asks Meta not to; from version 1.0.1 of our Android app and version 1.0.3 of our iPhone app it also sends PostHog how you use it while you are signed in, linked to your account: on a phone the app does not treat as being in Europe, once the app has shown you its short line about our partners saying that one of them links app use to your account, until you turn it off, and on a phone it treats as being in Europe only if you say yes; it can send you the push notifications you turn on, through Expo's push service; and it keeps some things on your phone, including unsent drafts that your phone's own backup can include (Section 2(r)). Google explains how it uses the data it receives from our website and app at business.safety.google/privacy.

What changed on 17 November 2026: from version 1.0.3, our iPhone app also measures our own ads on Meta (Facebook and Instagram), but only once you allow tracking in Apple's prompt (whose words now name Google, Facebook and Instagram and say that Meta may also use it for its own ads) or later in your iPhone's Settings, and, if the prompt you answered was the earlier one, which named only Google, only once you also turn on the app's new Meta ad measurement switch: what Meta then receives from it, including your phone's advertising identifier (Apple's IDFA), details of your phone and the app, and when the app is installed and opened, how long it stays open and roughly how long since it was last open, when you sign up and when you start a trial or buy Premium, but never your name, email address or account ID; that Meta may also use it for its own purposes, including to personalise the ads it shows you, and that we may also use it, from phones the app does not treat as being in Europe, to choose who sees our ads; that it never starts while Send analytics and crash reports or that switch is off; how to turn it off, and that this does not delete what Meta already has; that, whether or not you allow tracking, the app also tells Apple's own ad attribution that it has been opened and, through Google Analytics for Firebase or, once it has started, Meta's kit, may tell it which steps you reached, so that Apple can tell an ad network what its ads led to, in a report whose signed contents, Apple says, include no data about you or your phone; and that, from version 1.0.3, our iPhone app also sends PostHog how you use it while you are signed in, linked to your account by the same pseudonymous id as our website and our Android app, under the same rules as our Android app, with a shorter line about our partners on its sign-in screen that says nothing about ads, except that an iPhone, which does not tell apps the country of its mobile network or SIM, is treated as being in Europe by its time zone, its region setting and the country or region of its App Store, and PostHog is the first of the app's partners on an iPhone that links how you use it to your account (the opening paragraph and Sections 2, 2(j), 2(r), 3, 5, 6, 7, 8 and 10).

What changed on 16 November 2026: that, from version 1.0.1 of our Android app, Meta's kit, once it has started, takes the install referrer Google Play gives the app, and that the app reads that referrer for the labels of where your sign-up came from and for your referral once, the first time it opens (Section 2(r)).

What changed on 16 November 2026: that, from an update of version 1.0.1, our Android app shows its short line about our partners to a member already signed in for whom it has not yet fully taken effect on that phone, and that once it has been on your screen there, ad measurement, Meta's included, and, on a phone the app does not treat as being in Europe, PostHog start as they would after that line on the sign-in screen, until you turn them off in Privacy and data (the opening paragraph and Sections 2, 2(r), 3, 5 and 6).

What changed on 16 November 2026: that the list of references we keep to the pages your mentor conversations belonged to stays after your account is closed until the clean-up that removes it runs, and, if that clean-up fails or is skipped, until we run that clean-up again, and so, rarely, does anything connected with the mentor that a request still running as your account was closed, or made in the seconds after, saved after we first deleted that kind of data (Sections 8 and 10); that, rarely, anything else still being saved for your account as it was closed, or in the seconds after, can also stay after your account is closed, if it arrives after we have deleted that kind of data, even where we say that kind of data goes with your account (Sections 2(m) and 8); and that one sub-section of India's data protection law, s.6(9), which requires every consent manager to be registered with the Data Protection Board of India, commenced in November 2026, before the rest of ss.3 to 17, and that we do not use a consent manager (Sections 3 and 7).

What changed on 15 November 2026: that the running count of your mentor messages that we keep to apply your plan's limits now normally goes about 15 minutes after your account is closed, whether you close it or ask us to erase your data (until now, neither removed it any sooner); in any case it still clears itself within about six weeks of its last update (Sections 8 and 10); and that, beside our ordinary server logs, the rate limits we keep to secure the Service can also stay after your account is closed (Section 8).

What changed on 14 November 2026: more on the reports our app sends Sentry: that it has also been sending one when it stops responding; that, from version 1.0.1 of our Android app, on Android 11 and later, such a report also carries Android's own record of that moment, which our app sends as Android wrote it, so what we say a report never carries does not cover that record, and which, on Android 14 and later, can name other apps' processes; and that, on Android 11 and later, once Send analytics and crash reports is on again, the app can send a report of the latest time in the past 91 days that it stopped responding, even one from while the switch was off (Section 2(r)).

What changed on 14 November 2026: from version 1.0.1 of our Android app, the app sends PostHog which screens you open and which features you use while you are signed in, linked to your account by the same pseudonymous id as our website, so the two join. On a phone the app does not treat as being in Europe it does not ask: it starts for your account once you have signed in after the app's sign-in screen showed you its short line about our partners in the form that says one of them links app use to your account (PostHog is that one; Section 6 names the partners), and runs until you turn it off in the app's Privacy and data. On a phone it treats as being in Europe it asks you first and sends nothing unless you say yes. From 13 April 2027 it asks on every phone. Turning it off asks PostHog to delete what it holds about you, website history included. Our iPhone app sends PostHog nothing before version 1.0.3 (the opening paragraph and Sections 2, 2(j), 2(r), 3, 5, 6, 7, 8 and 10).

What changed on 14 November 2026: that PostHog, which our website uses only if you consent, now also receives, with your plan, whether you are on a free trial or paying, from our website and, from version 1.0.1, from our Android app; that the approximate location PostHog works out from your network address can include a postal code; and that the profile PostHog keeps with no time limit also holds technical details of your browser, device and visits from our website and of the app and your phone from our Android app (Sections 2(j), 2(r) and 8).

What changed on 13 November 2026: that, from version 1.0.1, the short line our Android app shows under "By continuing" says what our partners get, why, and that you opt out in Privacy and data, without naming them, and which partners it means and what each gets (Sections 2(r) and 6); where Google explains how it uses the data it receives from our website and app (the opening paragraph and Section 6); and that Meta also collects information from other apps that use its technology, and uses what it gets to provide measurement services and to target and deliver ads (Section 2(r)).

What changed on 13 November 2026: more on what our app has been sending Sentry: that its crash reports carry a random identifier for the app's installation; that the app also sends Sentry a note each time you use it, under that identifier, of when the use began, how long it lasted, how many errors it met and how it ended, so that we can see how often the app crashes; that Sentry works out your approximate location from the network address a report comes from and keeps it with the report, though our Sentry project is set not to store the address; and that Sentry keeps those notes of each use for as long as its own rules allow (the opening paragraph and Sections 2(r), 3, 5, 6, 7 and 8).

What changed on 13 November 2026: from version 1.0.1, our Android app also measures our own ads on Meta (Facebook and Instagram): what Meta receives from it, including your phone's advertising ID, details of your phone and the app, what Google Play tells the app about where it was installed from, and when the app is installed and opened, when you sign up and when you start a trial or buy Premium, but never your name, email address or account ID; that Meta may also use it for its own purposes, including to personalise the ads it shows you, and that we may also use it, from phones the app does not treat as being in Europe, to choose who sees our ads; that it never starts while Send analytics and crash reports, Ad measurement or Meta ad measurement is off, or before the app has shown you its short line about our partners, which names none of them (Sections 2(r) and 6 do), unless you turn on Meta ad measurement; that the app does not ask for consent for it, in Europe too, and on a phone it treats as being in Europe asks Meta not to use it to choose who sees ads; how to turn it off, and that this does not delete what Meta already has; and that our iPhone app sends Meta nothing before version 1.0.3 (the opening paragraph and Sections 2, 2(r), 3, 5, 6, 7, 8 and 10).

What changed on 11 November 2026: how long we keep a mock-interview recording, and the proctoring events, integrity signal and composure summary figures from a mock interview (Section 8), and which readings the face check sends with its events, and what it notes instead on a device too slow for it, in your browser and in the app (Section 4).

What changed on 11 November 2026: if grading a mock interview fails when you submit it, we may now finish grading it in the background, and send you one email saying its result is ready, as we already could when grading it took longer than our time limit allows (Sections 2(f) and 3).

What changed on 11 November 2026: we now use PostHog, from its cloud in the European Union, on our website, only if you accept our cookie banner, so Google Analytics is no longer the only third-party analytics tool there: it records the pages you view, with the parts of each address that point to a record of yours removed, a short list of named events, and session replays of your visits with all text and typed input hidden; once you sign in, it links what it records in that browser, including what it recorded there before you signed in, to your account by a pseudonymous id, never your email address, name or account ID; it is kept off our staff pages and the pages that open an emailed sign-in link; and deleting your account, or withdrawing your consent while signed in, deletes what it holds under that id. Because this changes what our cookie banner asks about, everyone who answered it before is asked again (the opening paragraph and Sections 2, 2(j), 2(r), 3, 5, 6, 7, 8 and 10).

What changed on 11 November 2026: we no longer use Microsoft Clarity on our website, so it no longer records session replays of your visits or sets its cookies, and nothing from your visits is sent to Microsoft for it; Google Analytics is now the only third-party analytics tool on our website (the opening paragraph and Sections 2, 2(j), 2(r), 3, 5, 6 and 7).

What changed on 10 November 2026: if you are signed in and choose Open in my browser in an app's built-in browser, we can now carry your sign-in to the browser that opens, with a one-time link that works for ten minutes at most, only from the same network and only after you press Continue; that the app you were in can see that link; the record we keep of it; and the cookie that holds it in your browser for those ten minutes (Sections 2(a) and 5). Also, two more technical details we keep for each spoken answer in a mock interview: how quickly the speech detection started on your device, and why it could not start if it did not (Section 2(f)). Also, the app's entry in Section 3's list of where we rely on consent is now headed for both phones, not an iPhone alone, as it already said that on Android we do not rely on consent for it (Section 3). Also, where we said on 30 October that on Android the app tells you that ad measurement is on "instead of asking first", we mean without asking first: on Android the app does not ask (Section 2(r)). Also, that on Android the app reads your phone's advertising identifier only while analytics are on, as Section 2(r) already said that turning off Send analytics and crash reports stops it too (Section 5).

What changed on 30 October 2026: that, once the Data Protection Board of India can hear complaints, you may approach it about a grievance we have not resolved; Section 3 says it cannot yet (Section 12). Also, that the app's Google sign-in sends nothing to Google until you choose "Continue with Google" (Sections 2(a1) and 6). Also, each fingerprint we keep to spot someone referring themselves is now deleted when the account it belongs to is closed, including the one from a sign-up with a referral code, which we used to keep with our record of that referral after that account was closed (Sections 2(a) and 8). Also, the CareerVerse app now asks, with Apple's tracking prompt on an iPhone, whether it may use your phone's advertising ID to measure our own ads on Google; it records a Premium purchase you make in it, and we import its sign-ups, first opens and purchases into Google Ads to see which of our ads lead to them; ad personalisation stays off; and the app no longer sends your Android ID (Sections 2, 2(r), 3, 5, 6 and 10). Also, that on Android the CareerVerse app uses your phone's advertising ID to measure our own ads on Google unless you turn off Ad measurement in the app's Privacy and data, telling you that ad measurement is on in a short line on its start page and sign-in screen instead of asking first, and that for this we rely on our legitimate interests, which you can object to with that switch; on an iPhone it still asks first, with Apple's tracking prompt (Sections 2, 2(r), 3, 5, 6 and 10). Also, we now describe the service that fetches the public details of a LinkedIn profile you import as an outside profile-lookup service that receives the username you give and works under its own terms, not a service provider that works for us (Sections 2(g), 3, 6 and 7).

What changed on 27 October 2026: what we keep after you close your account, and why: the records of a plan bought on our website, kept as financial records with no time limit and still carrying your account's identifier and the customer reference our payment processor gave you, and that a message our payment processor sent us on or before 26 September 2026 may have been kept whole, with any name or email address it held; that for each payment on our website we receive the type of payment method and, for a card, its brand, last four digits and expiry date; that withdrawing your cookie consent does not delete an advertising click identifier a checkout on our website carried, which those records keep; the record of what our staff did on your account, kept with no time limit so that we can account for it; and what our record of a referral still holds once an account is closed; and that what we delete can remain in our routine backups for up to 35 days, a time we did not state before (Sections 2(a2), 2(i), 2(l), 6, 8 and 14). Also, who receives two things the app sends: statistics about how the vision library behind the app's face check ran, which Google receives under its own terms (Sections 6 and 7), and the app's requests for updates to its own code, which Expo receives for us (Section 6); that AssemblyAI, which turns the audio of your mock-interview answers into text, does not use that audio or its transcripts to train its models, as our account has been opted out of its model improvement program since we began using it, and that AssemblyAI says it offers zero data retention of them for an account opted out as ours is (Sections 4 and 6); and the name of our Grievance Officer and our company's postal address (Section 12).

What changed on 27 October 2026: the CareerVerse app for iPhone and Android, and what it collects, keeps on your phone and shares, including the analytics and crash reports it sends and the push notifications you can turn on, what each request from the app tells us, and that where you signed up can be the app on an iPhone or an Android phone (the opening paragraph and Sections 2, 2(h), 3, 5, 6, 7, 8 and 10); the app's Send analytics and crash reports switch, on until you turn it off, which stops the app collecting analytics and crash reports on that phone, though what it had already gathered may still be sent (the opening paragraph and Sections 2, 2(j), 2(r), 3 and 6); signing in to the app with "Continue with Google", and in our iPhone app with Sign in with Apple: what Google and Apple receive when you do, including a relay address if you hide your email from Apple, the name the app passes on the first time, the token we keep only to end CareerVerse's access to your Apple Account, what Apple can tell us later, what stopping Sign in with Apple or deleting your account does, and what we keep (the opening paragraph and Sections 2(a1), 2(a2), 2(b), 2(r), 3, 6, 7, 8, 9 and 10); how mock interviews work in the app: that it asks for your camera and microphone, that when our speech-to-text provider cannot take an answer, your phone's own speech service (Apple, Google or your phone's maker) turns it into text instead, that in an interview you start under the app's current consent wording the face check runs on your phone, whose vision library sends Google statistics about how it ran, and you can switch on the composure estimate there too, the other events the app notes, the timing it measures on your phone, its own consent screen, the microphone test that starts by itself, your phone's own voice reading a question aloud, how long a recording stays on your phone, and that the proctoring events from an interview in the app go to our AI provider with your answers as part of grading it, while the face analysis that notes the face events still rests on your consent (the opening paragraph and Sections 2(f), 2(r), 3, 4, 6, 7 and 8); that your voice stays on your phone in conversation practice in the app (Section 2(r)); the consent screen you tick before each mock interview, on our website and in the app, which now names AssemblyAI as the provider that turns your answers into text and Google Cloud Text-to-Speech as the one that voices the interviewer, and asks you to confirm you are 18 or older, no longer accepting a guardian's consent in its place (Sections 3 and 4); that Google Cloud Text-to-Speech also receives the text of the interviewer's greeting and sign-off, which use your first name, and that your browser's own voice, or in the app your phone's own voice, reads them when that service is unavailable (Sections 4 and 6); in the app, the reminders it sets on your phone and does not send to us, among them the end of a focus timer you start in a lesson and a reminder an hour before an expert call you booked, when it uses your photos, camera and microphone, the Python runtime it loads from jsDelivr, a public content-delivery network, when you run Python in a lesson, and what Expo's push service receives, including a random identifier the app keeps on your phone and a label naming each notification's kind (Sections 2(r) and 6); that when you create your account in the app, it records where your sign-up came from, as up to four short labels (source, medium, campaign name and campaign id) and a channel we work out from them, with no consent choice, which our website's cookie choice does not cover, and that we keep it on your account until you close it (Sections 2(l), 2(r), 3 and 8); buying Premium in the app, through the App Store or Google Play: what we receive from the store and keep, the random token that ties a store purchase to your account, who processes the payment, what a copy of your data holds about it, that deleting your account while a plan renews also turns off a renewal in Google Play, while an App Store subscription keeps billing through Apple until you cancel it there, that we keep a store purchase as a financial record after you close your account, and that restoring it on a new account works (Sections 2(i), 2(r), 3, 6, 8 and 10); in the app, sending us a report, with any screenshot you attach, and reporting an answer our AI wrote for you, which sends us that answer's text, where it appeared and why you reported it, and with an AI Mentor reply your question too, unless you turn that off (Sections 2(r) and 3); blocking a member in the Community: the list of who you blocked that we keep, how a block made from an anonymous post works, and what it can and cannot tell anyone about who wrote it, that we check the text of a post, reply or edit, and of your public profile, against a list of words we don't allow before it is saved, and the record we keep that you agreed to our community rules (Sections 2(e), 3 and 14); when you open the AI Mentor from your own public page, the description of the page sent with your message carries what anyone can see on it, and, while your Courses and practice switch is on, the proof it shows, never your name, photo, links or page address (Section 4); the wait a new Free account may have before its first practice conversation, and before its first mock interview when the network it signed up from had already started many accounts that day, what we keep about it, and that your data export lists it (Sections 2(a) and 3); the projects you send for grading, with their links and screenshots, and the code, write-up and screenshots our AI provider receives to grade them (the opening paragraph and Sections 2(e) and 4); what a code-host lookup keeps, including a usage count and, when we check whether a username exists, the answer for up to 10 minutes (Section 4); and that we require every service provider to protect your data to the same or an equal standard as this Policy, while the companies that receive data under their own terms apply their own policies, Expo among the service providers and Apple's and Google's push services among those companies (Sections 3, 6 and 7).

What changed on 26 October 2026: importing your own LinkedIn profile: you confirm that the profile is yours before each import, a service provider that works for us fetches its public details, nothing on your profile changes until you tick what to keep and save, and a contact email the profile lists is discarded (Sections 2(b), 2(g), 3, 6, 7 and 8).

What changed on 26 October 2026: the code our website loads from jsDelivr, a public content-delivery network, including the Python runtime, and the fonts the system-design canvas on our website may load from esm.sh, another one; GitHub, which receives from our server the username you type into the journal's recall panel and the dates you chose, and from which our server downloads the public repository of a project you send for grading; and that these three answer under their own terms, not as our service providers (Section 6).

What changed on 26 October 2026: the network address your sign-up came from, which we look up with IPinfo, a service provider in the United States, for its country, region, city, time zone and network; the fingerprint of it we keep when you sign up with a referral code, and the one we may keep of an address we have confirmed a referrer opened their Refer & Earn page from; who at CareerVerse can see what it finds; and how long we keep each (Sections 2(a), 2(h), 3, 6, 7 and 8).

What changed on 26 October 2026: we no longer promise that AssemblyAI, which turns the audio of your mock-interview answers into text, does not keep that audio or its transcripts after the session and does not use them to improve its models, because we have not confirmed that our account is on the arrangement under which it makes both promises (Sections 4 and 6).

What changed on 24 October 2026: that a resume-builder draft can be saved to your account, where we keep one, the latest you saved, until you delete it or close your account, and include it in a copy of your data (Section 8).

What changed on 23 October 2026: the kind of device you signed up on, and where, which we keep on your account (Section 2(h)); that a person reads your resume when you ask for a recruiter review, and our AI provider turns their written review into the report card you receive; what the person arranging an expert call sees, including any note you add to your booking, that when you book from a job you saved, we start that note with the job's role and company, and that the expert who takes the call receives your name, email address and note, and the call's area, reason, length and time (Sections 2(s), 3 and 6); that the proctoring events from a mock interview, sometimes with a short reading, go to our AI provider with your answers as advisory input to grading, which we do as part of grading the interview you asked for (Sections 3 and 4); and that you can now delete your account while a plan renews, which turns off its renewal so you are not charged again (Section 10).

What changed on 23 October 2026: adding a Google sign-in to your account from your account settings, after you confirm a code we email you, with a Google Account that may use a different email address from your CareerVerse one; that a Google sign-in added this way keeps working if its Google address changes; and that we keep that Google address, show it in your sign-in methods and include it in your data export, and keep a stopped Google sign-in's address until you delete your account (Section 2(a1)).

What changed on 18 October 2026: four more technical details we keep for each spoken answer in a mock interview: if you opened the interview inside another app's browser, which app it was; how many times the speech-to-text connection was stopped before it opened; and whether the question's voice played and how many times you asked to hear it again (Section 2(f)).

What changed on 17 October 2026: hands-free answering in mock interviews on our website: the speech detection that runs in your browser to tell when you have stopped talking or started talking over the interviewer, and what we record about how hands-free answering behaved for each answer (Sections 2(f) and 4); and on a day your Career Twin has no free step for it, the daily reminder now points you to a mock interview, or else to conversation practice, that you still have (Sections 2(o), 3 and 4).

What changed on 9 October 2026: the microphone test before the first question of a mock interview, which sends one sentence you say to our speech-to-text provider, and that this provider may still receive your answer audio while your browser stands in for a slow or broken connection (Sections 3 and 4); the technical details of the speech-to-text connection we keep for each spoken answer (Section 2(f)); and the microphone test you can run once more during a mock interview in which none of your answers come through as words, and that the sentence you say for it is part of that interview's recording (Sections 3 and 4).

What changed on 7 October 2026: a day now counts toward your streak when you roll or check in for your daily CVTokens (Section 3); and a sign-up or trial start you make before answering the cookie banner is now reported to Google, as it already was to Meta, if you then accept (Sections 2(k) and 5).

What changed on 5 October 2026: what your AI Mentor can read about you and how to switch each part off, and what more a page description can carry, including on your job tracker and competency ladder (Sections 3, 4 and 10); which suggestion each Done for you action came from, and the record we keep of each tap on a mentor suggestion (Sections 4 and 8); deleting one AI Mentor conversation yourself (Sections 8 and 10); asking for a mock-interview question in plainer words (Section 4); what a tailored résumé rewrite sends to our AI provider when you let it use your Wins, and the note we keep of which Win a rewrite's figure came from (Sections 4 and 8); the demo on our home page (Sections 2(m1) and 3); what conversation practice keeps, what goes to our AI provider from a rehearsal and where your voice goes in it, and the sound files we keep of spoken questions and practice lines (Sections 4, 6, 7 and 8); that when your browser's own voice reads a question aloud, some browsers send the question's text to the browser's maker (Sections 4 and 6); the short list of names our speech-to-text provider receives with your answer audio (Sections 4, 6 and 7); code-editor drafts saved to your account, and your theme kept in your browser only (Sections 5 and 8); a few first-run markers and a weekly note of where your skills stand (Section 2); the opt-in daily reminder email (Sections 2, 3 and 4); your daily CVToken allowance and what we keep to run it, and check-in days counting toward your streak (Section 3); and the coded form of your email address we keep when an email bounces, and the hashed one we share with Google, both plain SHA-256 hashes that we no longer call one-way or irreversible (Section 2).

This Privacy Policy explains how ASOasis Tech Private Limited ("ASOasis", "we", "us", or "our") collects, uses, shares, and protects personal data when you use the CareerVerse website, the CareerVerse app for iPhone and Android (the "app"), and related features (together, the "Service"). It is designed to meet India's Digital Personal Data Protection Act, 2023 ("DPDP Act") — the statute that will be our primary data-protection law once its main provisions commence in May 2027, and which we are already building towards — as well as the EU and UK GDPR and the California Consumer Privacy Act (CCPA/CPRA), where applicable. The Indian law that binds us today is the Information Technology Act, 2000 and the 2011 Rules made under it. Section 3 sets out both, and is honest about which is which. Read this policy together with our Terms of Service.

The Service is intended only for individuals aged 18 or older (see Section 13).

1. Who we are

ASOasis Tech Private Limited, a company incorporated in India, is responsible for your personal data. We are the Data Fiduciary for the purposes of the DPDP Act, the Controller under the GDPR, and the Business under the CCPA/CPRA.

  • Email: support@careerverse.tech
  • India DPDP Grievance Officer: see Section 12.

2. Information we collect

In short: The information you give us, the content you create, and a little technical data to keep you signed in — plus, if you create your account with "Continue with Google", the display name and profile photo Google hands us at that moment — profile data that reached us from a company rather than from you (Section 2(a2)). If you consent, we also collect pseudonymised product-analytics through third-party tools (Google Analytics, and PostHog, which also records session replays with all text and typed input hidden and, once you sign in, links what it records in that browser to your account by a pseudonymous id, including what it recorded there before you signed in), use advertising tools (Google Ads and Meta Pixel) to measure which ads bring people to CareerVerse, and record which channel or campaign your own sign-up came from. Separately, and regardless of that choice, we keep aggregate counts of how often things happen across the Service with no identifying data attached (Section 2(m)); and every email we send carries open and click tracking added by our email provider, which keeps a per-recipient history we can look up (Section 2(q)). In the app, analytics and crash reports are collected without a consent choice until you turn them off there, and on an iPhone the app's analytics reads the identifier Apple gives our company's apps; the app sends your phone's advertising ID, to measure our own ads, on an iPhone only if you agree and on Android unless you turn it off, and from version 1.0.1 our Android app also sends it, with a few events and your phone's details, to Meta, as our iPhone app does from version 1.0.3 only once you allow tracking in Apple's prompt or later in your iPhone's Settings, and Meta may use them for the ads it shows you, though on a phone the app treats as being in Europe the app asks Meta not to; and from version 1.0.1 of our Android app and version 1.0.3 of our iPhone app the app sends PostHog how you use it, linked to your account by the pseudonymous id: on a phone the app does not treat as being in Europe once the app has shown you its short line about our partners saying that one of them links app use to your account, until you turn it off, and on a phone it treats as being in Europe only if you say yes (Section 2(r)).

This section was added to on 26 September 2026, to describe the email saying a mock-interview result is ready, and the one follow-up email after your first mock interview; and on 27 September 2026, to describe the answer timing behind the delivery notes on your mock-interview results; and on 28 September 2026, to describe what we count for our campaign links and what we keep when your sign-up came through one of them; and on 30 September 2026, to name the skill names from your profile that we keep beside a match we made for them; and on 5 October 2026, to describe the opt-in daily reminder email, the demo on our home page, the first-run markers we keep with your profile, and the weekly note of where your skills stand, to describe the coded form of your address we keep when an email bounces, and to stop calling the one we send Google irreversible; and on 7 October 2026, to say that a sign-up or trial start you make before answering the cookie banner is also reported to Google if you then accept; and on 27 October 2026, to describe the CareerVerse app for iPhone and Android; and again on 27 October 2026, to say that for each payment on our website we receive the type of payment method and, for a card, its brand, last four digits and expiry date, that withdrawing your cookie consent does not delete an advertising click identifier a checkout on our website carried, and that what we delete can remain in our routine backups for up to 35 days.

a. Account and authentication data. Your email address, used for one-time-passcode (OTP) sign-in, and an authentication token kept in a secure session cookie. We do not collect or store passwords. When you request a sign-in code, your IP address may be forwarded to our backend for rate-limiting and abuse prevention.

If you are signed in and choose Open in my browser in an app's built-in browser, we make a one-time sign-in link for your account and hand it to your phone to open your normal browser. The app you were in passes it on, so it can see it, as it can see everything in its own built-in browser. We keep a record of it (a one-way code of the link and of your network address, your account identifier, the sign-in it came from, the page it opens and when it was made) and delete it automatically, usually within a few days of the link expiring after ten minutes. It signs you in only from the same network and only once you press Continue, as a new sign-in on that browser that you can end like any other. When it starts, it is set to expire no later than the sign-in it came from.

New-account wait. When a new Free account is created, we may record on it a time, up to 24 hours after sign-up, before which its first practice conversation cannot start. If the network your sign-up came from had already started many CareerVerse accounts that day, your first mock interview waits until then too. A free trial or Premium never waits. Our website and the app show you when each opens. We keep that time, and whether the network check applied, on your account until you close it, and your data export lists both, as new_account or network_check.

The network you signed up from. When a sign-in creates your account, whichever way you sign in, we record the network (IP) address the request came from. We send that address, and nothing else about you, to IPinfo, a service provider in the United States, which tells us the country, region, city and time zone the address is registered to and the name and number of the network it belongs to, such as your mobile or internet provider. If IPinfo does not answer, we keep the address alone, and if we cannot tell which address your sign-up really came from, we record nothing. We do this once, when the account is created, never on a later sign-in, and never with your phone's location service, so it shows where that network was, not where you live; a mobile network can place you in another city. We use the country to decide which country's rates apply to you in Refer & Earn and, for a sign-up made on our website, whether the weekly win prompt and the monthly growth digest may start on (Section 3). Our admin tools show the people at CareerVerse who look into fraud and abuse the country, region, city, time zone and network name, but not the address itself. We keep the address and those details on your account until you close it. They are not in the copy of your data you download yourself (Refer & Earn's export does show the reward country we worked out from it); write to support@careerverse.tech and we will send them to you.

If you sign up with a referral code. We also keep a fingerprint of that network address on the referral. It is a hash of the address, which can be matched back to it, so it does not hide the address. We use it only to spot someone referring themselves, by comparing it with a fingerprint the person who referred you may have on their referral profile. If you refer people yourself, we may keep the same kind of fingerprint on your referral profile, of an address we have confirmed you opened your Refer & Earn page from, replace it only when we confirm a new one, and use it only for that comparison. Each fingerprint is deleted when the account it belongs to is closed: a referrer's own when they close their account, and the one from your sign-up when you close yours. Our record of the referral and of any reward it earned stays, also after either account is closed.

a1. Sign in with Google (optional). If you choose "Continue with Google", Google confirms your identity to us and sends us a signed assertion containing your email address, whether Google has verified it, a stable identifier for your Google Account, and — in most cases — your Google display name and a link to your Google profile picture. We use that identifier to recognise you on later sign-ins, and we store it alongside your account; what we do with the name and picture is set out in Section 2(a2) below. We never receive your Google password, and we do not request access to your Gmail, Drive, Contacts, or any other Google data — the name and the picture link are simply fields inside the signed assertion, not access to your account. Because CareerVerse issues its own session, signing out of Google does not sign you out of CareerVerse. If you stop using Google sign-in in your account settings, this does not affect your Google Account: we disable the identifier in CareerVerse, end CareerVerse sessions created through it, and retain the disabled record so ordinary Google sign-in cannot silently restore that access. It does not remove a name or photo that was copied onto your profile when the account was created (Section 2(a2)) — by then they are ordinary profile fields, and yours to change or clear. You can also add a Google sign-in to an existing account from your account settings, and that Google Account may use a different email address from your CareerVerse one. To add one, you must first confirm a one-time code we email to your CareerVerse address; we then send that address an email saying a Google sign-in was added. A Google sign-in added this way recognises you by Google's stable identifier, not by its email address, so it keeps working if the Google address changes; we keep that Google address, show it in your sign-in methods and include it in your data export, together with when it was added. A Google sign-in not added this way still works only while Google's verified email matches your current CareerVerse sign-in email. If you stop using a Google sign-in, we keep the disabled record, including its Google email address, until you delete your account, so that ordinary Google sign-in cannot silently restore that access; to use it again, add it again with a fresh code. Active and disabled Google sign-in history is visible in your account settings.

A "Continue with Google" button appears on our home page and on our sign-in screens. It appears in account settings only after you choose "Add Google sign-in" and confirm a code we email you. Drawing that button loads Google's sign-in code, and when it loads Google receives your IP address, basic device and browser information, the page address, and any Google cookies your browser already holds — so if you are signed in to Google, Google can recognise you at that moment. On the home page this happens as soon as the page loads, whether or not you ever use the button; on a sign-in screen it happens when that screen opens. To us, however, nothing about your Google account is revealed unless you actively choose "Continue with Google" — and we do not use Google's automatic "One Tap" prompt, so no Google sign-in prompt ever appears on its own. (Drawing the button also makes one request to our own backend to mint a single-use security token; as described in 2(a), your IP address may be processed for rate-limiting and abuse prevention.) See Google's Privacy Policy.

"Continue with Google" in the app. The app's Google sign-in sends nothing to Google until you choose "Continue with Google". (This is about signing in only: the app's analytics, which run from the moment the app first opens unless you turn them off (Section 2(r)), and the push notifications you turn on (Section 7) reach Google separately.) When you choose it, the app hands you to Google's own sign-in for apps (on Android, your phone's Google account chooser; on an iPhone, a Google sign-in screen the app opens), where Google receives what it needs to sign you in, under its own privacy policy. Google then sends us the same signed assertion as on our website, described above, and Section 2(a2) applies in the same way. The app keeps your Google email address, name and picture link on your phone only until that sign-in finishes.

Sign in with Apple (optional, in our iPhone app only). Our iPhone app also offers "Sign in with Apple"; our website and our Android app do not. If you choose it, Apple confirms your identity to us and sends us a signed assertion containing a stable identifier that Apple gives your Apple Account for our apps, your email address, whether Apple has verified it, and whether it is a private relay address. If you choose Apple's "Hide My Email", that address is one Apple creates for us and forwards to your own inbox, so we do not learn your own address. The first time you sign in to CareerVerse with Apple, Apple also gives the app the name you choose to share; the app sends it to us, and we use it only to fill in the name on your profile if that is empty, after which it is an ordinary profile field (Section 2(a2)). We use the identifier to recognise you on later sign-ins, and we store it alongside your account. If Apple has verified the address and a CareerVerse account already uses exactly that email, signing in with Apple signs you in to that account and adds Sign in with Apple to it; if Apple has verified it and no account uses it, we create a new account with that address, a relay address included. If Apple has not verified it, we first ask you to confirm a one-time code we email to it, whether or not it belongs to a CareerVerse account, and add Sign in with Apple only once you have: to the account that uses that address, or to the new account that confirming the code creates if none does. When you sign in, Apple also gives the app a one-time code, which we exchange with Apple for a token that we keep, encrypted, only so that we can later ask Apple to end CareerVerse's access to your Apple Account; we never use it to read anything from your Apple Account, and we never receive your Apple Account password. Apple can tell us when you stop using Sign in with Apple with CareerVerse in your Apple Account settings, or delete your Apple Account; we then turn Sign in with Apple off for your CareerVerse account and delete that token, but we do not delete your CareerVerse account. Apple can also tell us when you turn email forwarding from a relay address off or on. While it is off and that address is your account's email, we do not send it the codes that confirm it's you before you download a copy of your data, delete your account or add a sign-in method, or our security notices about your sign-ins and sessions, because they would not reach you, and we start again when you turn it back on or stop using Sign in with Apple (if you add the same Apple Account again later, we go by what Apple last told us about that address); in the iPhone app you can still confirm a download or a deletion with Sign in with Apple. Our other email, including the code to sign in, still goes to that address. Sign in with Apple is shown in your sign-in methods in your account settings, and you can stop using it there: we disable it, ask Apple to end CareerVerse's access, delete the token, keep the disabled record until you delete your account, and sign you out on every other device, and on this one too if you signed in with Apple. To use it again, add it again in the iPhone app with a fresh code we email you. When you delete your account, or we delete it for you at your written request, we ask Apple to end CareerVerse's access and delete the token; if Apple cannot be reached, we still delete your account, and you can remove CareerVerse yourself in your Apple Account's Sign in with Apple settings. Your data export lists Sign in with Apple among your sign-in methods, with its email address and when it was added, but not the identifier Apple gives us. Apple processes this under its own terms and privacy policy, potentially outside India. See Apple's Privacy Policy.

a2. Starting your profile from Google (new accounts only). If your CareerVerse account is created by "Continue with Google", we start it with the display name and profile picture from that signed assertion, so you do not begin with an empty profile. Profile information reaches us from a company rather than from you in two other places — a LinkedIn import you start yourself (Section 2(g)), and the name you choose to share the first time you use Sign in with Apple in our iPhone app, which fills your profile's name only if it is empty (Section 2(a1)). This one is different because you never asked for a profile change at all: it happens as a side effect of creating your account. That is why we set it out on its own. It happens once, at the moment the account is created, and only then:

  • It never runs on a later sign-in, and never when Google is connected to an account that already existed — that is an existing account gaining a sign-in method, and nothing about your profile changes.
  • It never writes over anything already filled in. If a field already has a value, we leave it exactly as it is.
  • It is best-effort. If Google sends no name or picture, or the picture cannot be fetched, that field is simply left empty and your sign-in carries on normally.

For the picture, our server fetches the image from Google once and keeps our own copy, on our storage in India (Section 6). We do not keep Google's link to it on your profile — only our copy — so displaying your photo on CareerVerse makes no request to Google, and a page showing your avatar never tells Google you were there. From that moment it is an ordinary profile photo in every respect: it appears wherever a profile photo appears, and you can replace or remove it in your account settings exactly like one you uploaded yourself.

Because it is a one-time copy, it is a snapshot, not a mirror: changing or deleting the picture on your Google Account later does not change or delete ours, and neither does disconnecting Google sign-in (Section 2(a1)). Editing or clearing the fields yourself is what changes them here. On the one sign-in path that asks you for an emailed code before finishing, we hold the name and the picture link on a server-side record tied to that attempt. It is never sent to your browser, and it expires automatically — though, like our other records, a copy can survive in our routine backups for up to 35 days after it is deleted (Section 8).

b. Profile data. Name, headline, summary, phone number, location, profile photo, skills, languages, work experience, education, and LinkedIn/GitHub/portfolio URLs. You give us most of it directly. Three things can arrive another way: on an account created through "Continue with Google", the name and profile photo are filled in from your Google Account at that moment (Section 2(a2)); the name you share the first time you use Sign in with Apple in our iPhone app fills your name if it is empty (Section 2(a1)); and a LinkedIn import writes the fields you tick into them (Section 2(g)). In each case they are ordinary profile fields afterwards, yours to change or clear. We also keep a few markers with your profile about the first-run steps you have already been through (the tour, your first question to the mentor, the first-win card, the daily-reminder offer, the trial offer shown after a win, and whether you hid the Get started card), so another device neither repeats them nor skips them. They are included in a copy of your data and deleted with your account.

c. Resume. A resume file you upload (e.g. PDF), and information derived from it when you use AI resume features.

d. Job-application records you create in the application tracker — including the status you set on one, which is where an outcome such as an offer or a rejection is recorded if you choose to record it, and, where you paste a job description, the set of skills you accept from it (Section 4).

e. User-generated content. Forum posts, comments, and images; code submissions; system-design canvases; the projects you send for grading, with their repository and live-demo links, write-ups and screenshots; and the text you enter into AI features (including job descriptions and mentor-chat messages). Content you post in the public Community is visible to anyone and may be indexed by search engines — see Section 14. If you block a member, we keep a list of who you blocked so we can hide their posts and comments from you; for a block made from an anonymous post, we keep a link to that post's author, which we never show you. We also keep a record that you agreed to our community rules (which version, and when). Section 14 says more about both.

f. Mock-interview data. Camera video and microphone audio recordings; the transcript of your spoken answers (which is produced by sending that audio to a provider as you speak — Section 4 says who, and what we can and cannot promise about it); and derived proctoring events with timestamps (for example, "face not detected", "multiple faces", "gaze away", tab switch, window blur, full-screen exit, camera or microphone disconnect, or attempted copy/paste), from which an integrity signal is derived. If you switch on the optional composure estimate during an interview, we also store the summary figures it produces — one per answer and one for the session — which are worked out on your device, so that your account page can show you your own trend; we do not use them in grading. We do not receive or store the underlying facial-landmark data, or any image from the face check or the composure estimate — that is computed and stays in your browser, or in the app on your phone (see Section 4); the interview's own recording is the video and audio described above. In the app, in an interview you start there under the app's current consent wording, the same face check runs on your phone and you can switch on the composure estimate, also worked out on your phone; besides the face events, the app records that you left the app or locked your phone, that something such as a call came over the app or took its sound, or that the camera or microphone stopped (Section 4). An interview started on our website, or in the app under its earlier wording, runs no face check in the app. For each spoken answer, we also record timing measured in your browser (in the app, on your phone) — how long you spoke and how soon you began after the question finished — and show it to you on your results as delivery notes; they are not used in your score. For each spoken answer, we also keep technical details of how our speech-to-text connection behaved: which way the answer was turned into text, your browser type (in the app, whether it is a phone or a tablet) and, if you opened the interview inside another app's browser, which app it was, how often the connection dropped or reconnected, how many times the connection was stopped before it opened, and how much audio was sent and how many replies came back. These are numbers and short labels only, never your words or your voice. We use them to find and fix lost answers, they are not used in your score, and they are deleted with the interview. For each spoken answer, we also record how hands-free answering behaved: how the answer ended (you submitted it, it was submitted automatically after you stopped talking, or the interview ended), the hands-free settings in effect and why automatic submitting was off if it was, how many automatic countdowns started and how many were cancelled, the lengths of the pauses in your answer, how long a pause a countdown waited for and how long you had been quiet when the answer was sent, whether you were still speaking in the seconds after an answer was sent, which voice read the question, whether the question's voice played and how many times you asked to hear it again, how often speech was heard on your microphone while the interviewer was speaking, how many times talking over the interviewer began an interruption and whether one was confirmed or was a false start, and how quickly the speech detection started and ran on your device, and why it could not start if it did not. Where we are still testing automatic submitting in your browser, we count the countdowns it would have started, and whether you kept talking after one would have sent your answer, without showing them to you. These are numbers and short labels only, never your words or your voice, are not used in your score, and are deleted with the interview. If we finish grading an interview in the background — because grading it took longer than our time limit allows or failed when you submitted it, or because you answered every question but the interview was never submitted — we may send you one email for that interview saying its result is ready, with a link to it. It carries no score, figure, verdict or standing (Section 4). We record against that interview that we sent, or tried to send, that email, so it is never sent twice; the record is deleted with the interview.

g. LinkedIn import data. If you choose to import your own LinkedIn profile, you give us its link or username and confirm that the profile is yours. We send that username to an outside profile-lookup service, which fetches that profile's public details from LinkedIn — name, skills, work experience and education — and we show them to you. It works under its own terms, not as our service provider (Section 6). Nothing changes on your profile until you tick what to keep and save; what you save becomes ordinary profile fields (Section 2(b)), and if you have no headline yet, one is set from your most recent role. If the profile lists a contact email, the service may return it; we discard it at once and never store or show it.

h. Limited technical data. Information necessary to operate and secure the Service, such as the IP address forwarded for rate-limiting, the network address your sign-up came from (Section 2(a)), and standard server logs. When you use the app, each request also tells us that it came from the app, the app's version, and whether the phone runs iOS or Android and which version. When you create your account, we also keep two labels on it, worked out from how your browser or the app described itself on that request: the kind of device you signed up on (for example a computer, a phone, a tablet, or a browser inside another app) and where you signed up (our website, or the app on an iPhone or an Android phone). We keep only the two labels, never that description itself. They stay on your account until you close it, and we use them to see which devices, and which of our website and app, people sign up on, which shapes what we build (Section 3, "Maintain, debug and improve CareerVerse"). Until 23 October 2026 this page did not mention these labels, although we already kept them for accounts created on our website; this paragraph is the correction.

i. Billing data. If you purchase a paid plan on our website, your payment is processed by a third-party payment processor acting as the merchant of record (see Section 6). We receive your email address and limited transaction and subscription data (such as plan, amount, currency, status, and renewal dates) needed to provision your access and keep our records, and, for each payment, the type of payment method and, for a card, its brand, last four digits and expiry date (Section 8 says how long we keep them). We do not receive or store your full payment-card number — card details are handled by the payment processor. If you buy Premium in the app, through the App Store or Google Play, that store processes your payment (see Section 6). The app sends us the purchase so that we can check it with the store, and the store then sends us notices when it renews, is refunded or otherwise changes. From the store we receive, and keep, the purchase's transaction or purchase identifiers, the product, its status, its renewal and expiry dates and whether it will renew, whether it is in a free trial, the price and currency you paid, and the store environment (whether it was a real or a test purchase), with a short record of each notice the store sends us about it. We give your account a random store-account token, which the app hands to the store when you buy, so that a store purchase is tied to your account and to no other. We never receive or store the card details, name or email address of a store purchase.

j. Product-analytics data (only with your consent). If you accept analytics cookies, we use two third-party analytics tools (Google Analytics and PostHog) to understand how the Service is used. Google Analytics (GA4) measures pseudonymised usage — pages viewed, events (such as starting an interview or completing a lesson), approximate location inferred from IP, device/browser type, and site-performance (Core Web Vitals) and error signals; GA4 does not log or store your IP address, and we do not enable Google Signals, advertising features, or cross-site ad profiling. Neither tool is loaded at all unless you consent, and you can withdraw consent at any time via "Cookie preferences" in the site footer. See Sections 5–7. This paragraph is about our website: the app's analytics work differently, as Section 2(r) sets out.

PostHog is our service provider, under its data processing agreement, and runs from its cloud in the European Union. It receives the pages you view, each address stripped of the part that points to a record of yours (such as a saved job or a mock interview) and of every query value other than campaign tags and the tag our own links carry to say where they were placed; the page you came from, stripped the same way, or only its site if it is another site; a short list of named events, such as signing in or signing up, starting a mock interview, finishing a lesson, seeing a Premium offer, and opening or completing a checkout with its plan and whether it is a free trial, never a payment reference; session replays of your visits, which record how each page changes and where you click and scroll, with all text, everything you type, anything drawn on a canvas, and the parts of a page we mark as yours hidden; your device and browser type, the full description of itself your browser sends (its name, version and system), its language and time zone, and the size of your screen and window; and the approximate location PostHog works out from your network address (such as your country, region, city and postal code, with rough coordinates and a time zone), after which it discards the address. While you are signed in, it also receives a pseudonymous id, a one-way code our server works out from your account, together with your plan (Free or Premium, and whether you are on a free trial or paying) and, for our own staff, a mark that lets us keep their visits out of our figures. When you sign in, PostHog also links to that id what it recorded in the same browser before you signed in, since PostHog was first accepted in that browser or since someone last signed out of CareerVerse or withdrew consent there, whichever is later; on a browser that others also use, that can include their visits. It never receives your email address, name, account ID or payment details. PostHog is never started on our staff pages or on the pages that open an emailed sign-in link. If you move to one of them from another of our pages, a staff page is loaded afresh without it, and on a sign-in page the session replay stops and nothing captured there is sent; the one exception is the split second of the move itself, whose page changes, with all text hidden, the replay may already have recorded and can send once you have left. Our app sends PostHog what Section 2(r) describes, from version 1.0.1 on Android and 1.0.3 on an iPhone, under the app's own switches rather than this consent and with the same pseudonymous id, so what PostHog records from the app and from our website joins under one profile. We may use service providers, including AI tools, to analyse pseudonymised usage data to improve the Service and our marketing; we do not sell this data.

k. Advertising-measurement data (only with your consent). If you accept, we use Google Ads and Meta Pixel to measure and optimise our own advertising. When you arrive from a Google ad, Google adds a click identifier to the URL; we store it in a first-party cookie and later send it to Google to attribute a resulting sign-up, trial, or purchase (a "conversion"). To improve matching we also send Google a hashed (SHA-256) version of your email — not your raw email — using Google's "Enhanced Conversions". Meta Pixel sends Meta the pages you view, the page address and referrer, the time of the visit, browser/device and network information (including IP address), and Meta cookie/browser identifiers so Meta can measure and optimise our ads. When you arrive from a Meta ad, Meta adds its own click identifier to the URL; if you accept, we store it and provide it back to Meta (in Meta's _fbc cookie, together with the time of the click) so a resulting sign-up can be matched to the ad you clicked — the purpose that identifier was put on your link for. When a consented visitor creates a new CareerVerse account, or starts a free trial of Premium, the Pixel also sends Meta the corresponding standard event (registration or trial started), carrying at most one opaque event identifier — issued by our systems for a registration, and by our payment processor for a trial — so the same action can be deduplicated if server-side measurement is added later. Those events contain no email, CareerVerse user id, authentication method, plan, amount, profile data, form values, or other custom data. If you create your account or start your trial before answering the cookie banner and then accept, that one event identifier is held in your browser's memory only — never written to your device, never sent anywhere — and the event is sent once you accept, for up to 30 minutes; if you decline, close the tab, or reload the page first, it is discarded and nothing is ever sent. The same applies to Google: if you create your account or start your trial before answering the cookie banner and then accept, the fact that you signed up or started a trial, how you signed in or, for a trial, whether it is monthly or annual and our payment processor's transaction reference, and a hashed (SHA-256) form of your email address are held in your browser's memory only — never written to your device, never sent anywhere — and the sign-up or trial start is reported to Google Analytics and Google Ads once you accept, for up to 30 minutes; if you decline, close the tab, or reload the page first, it is discarded and nothing is ever sent. This implementation does not enable Meta Advanced Matching or send your email, profile data, resume, application records, or the text you enter into CareerVerse to Meta. Meta may associate Pixel activity with a Meta account and use it according to its privacy and advertising settings, including for ad personalisation. Neither advertising tag is loaded, and no advertising-measurement cookie is set by us, unless you consent; you can withdraw consent at any time via "Cookie preferences" in the footer. We do not show third-party ads on CareerVerse.

l. Sign-up source on our website (only with your consent). If you accept, we record where your sign-up came from and keep it on your account: the marketing "channel" (for example paid search, organic social, email, or direct), the campaign name or id, the website that linked you (the domain only — never the full address or what you searched for), the page you first landed on, the time, and any advertising click identifier that was on the link. If that source is one of our own campaign links (Section 5), we also record when you later start a free trial and when you first pay, if you do, so we can see which of our campaign links lead to trials and payments. We use this only to understand which of our own channels and campaigns bring people to CareerVerse, and which of our campaign links lead to trials and payments. It is first-party — recorded by us, kept by us, and not shared with any advertising platform for this purpose. (The advertising click identifier is the one exception, and only for a different purpose: it is separately used to measure our advertising, as Section 2(k) describes, which is what the ad platform put it on your link for.) Nothing is recorded unless you consent, the first source we record for you is never overwritten, and withdrawing consent via "Cookie preferences" in the footer permanently deletes it — a later change of mind cannot bring it back. It does not delete an advertising click identifier that a checkout on our website carried, which stays in our records of that plan (Section 8). This paragraph is about accounts created on our website. When you create your account in the app, the app records a shorter sign-up source instead, with no consent choice, as Section 2(r) sets out, and withdrawing consent on our website does not delete it.

m. Aggregate activity counts (no identifying data). We keep plain running totals of how often certain things happen across the whole Service — for example how many accounts were created, how many signed-in visitors reached the pricing page or opened checkout, how many free trials began, and how many lessons were completed. These are counts only: each records that something happened once, with no user id, email, device identifier, cookie, or IP address attached, and nothing about you is stored beside them. That includes how many times each of our campaign links is opened, and by how many different browsers; to tell one browser from another we read the campaign-link cookie described in Section 5, which holds only link codes, and nothing from it is stored beside the count. It also includes how many times the demo on our home page is started and finished, which visitors who are not signed in report (Section 2(m1)), and how many new accounts were created after it. The counts themselves therefore cannot be traced back to you, filtered to you, or used to single you out; they are held in our own cloud infrastructure, and may be copied — still as counts only, with nothing about you attached — to other systems and tools we use to run and report on our business; they are not shared with any advertising platform, and are not sold. To be precise about what that does and does not cover: it is a statement about the counts, not a claim that no record of your request exists anywhere — our ordinary server logs, described in Section 2(h), record requests as they do for the rest of the Service, and are kept and deleted on the same basis. The counts are not derived from those logs and cannot be joined back to them by us. We use them to see whether the Service — and the journey from signing up to upgrading — actually works. Because they contain no personal data, they are not part of the optional cookie consent and are unaffected by withdrawing it; the third-party analytics and advertising tools in Sections 2(j) and 2(k), which do involve personal data, remain consent-only.

One more thing this paragraph is not. Everything above is a statement about these counts — it is not a claim that we never measure anything against your account. Separately from them, and not part of them, we mark which days your account was active, and record which growth lens you chose, and we roll those up into cohort figures to see whether people come back and whether a feature is worth keeping (Section 3). Those markers sit on your account rather than in the counts, are never shared with any advertising platform, and go when your account goes, with the rare exception Section 8 names. We also read them for one account at a time for the follow-up email in Section 2(p1): to decide whether to send it, and to record whether you came back.

m1. The demo on our home page. You can try CareerVerse on our home page without an account: a sample Career Twin, a sample interview report, and one interview question you can answer yourself. The demo runs in your browser. What you type or say in answer to its question stays on that page: it is never sent to us, and we don't keep it. If you choose Speak, your browser's own speech recognition turns what you say into text; in some browsers (notably Chrome) that recognition sends your audio to the browser's maker, under its policies rather than ours (Section 4). When you first open the demo, and when you submit an answer in it, your browser tells us so, and the report says only which of the two it was: no answer, no cookie, no account and no device identifier. We add each report to a running count (Section 2(m)). So that nobody can flood those counts, we limit how many reports one network can send. For that we keep a small record keyed by the network address a report came from (an IPv4 address; for an IPv6 address, its first half, and a wider block that contains it), holding only how many more reports that network may send and when that was last updated. Each report it lets through updates it, and it is deleted automatically once seven days pass without one, though the deletion can take a few more days. Our log of these requests records neither your address nor which report it was, with two exceptions: if a report cannot be added to its count, a warning says which of the two counts it was, without your address; and if that rate-limit record itself cannot be read or written, a warning names the network it belongs to, as for every rate limit we keep (Section 2(h)). Your browser also remembers, in that tab only, that you tried the demo, so that if you then create an account we count one more sign-up after the demo, again with nothing about you stored beside the count. If you have accepted analytics cookies, opening the demo, submitting an answer in it and signing up after it are also reported to Google Analytics (Section 2(j)), never what you wrote or said.

n. Your Career Twin (what we work out from your own activity). CareerVerse builds a Career Twin for you: a list of the skills on your record — the ones you added or ticked yourself, and the ones your work here evidences — what evidences each one, a standing for each skill, and — once you set a target — how far your record reaches it. We assemble it automatically, from activity you have already carried out — your achievement-journal entries; your profile headline, summary, work history and the skills you have listed; mock interviews you have sat; coding solutions you have submitted; projects you have submitted; system-design sessions you have completed and the notes recorded during them; courses and course exercises you have finished; a résumé you upload; and a profile you import from LinkedIn. A journal entry you write up from a merged public pull request we found for a code-host username you typed reaches it as well, as the journal entry it is (Section 4). Two further sources are treated differently and are named here so the list stays complete: interview transcripts, which need a separate permission you must grant and can withdraw, and a job description you paste, which is held against the application it belongs to and deleted with it, along with the set of skills you accept from it. What we store is mostly pointers and labels: which skill, which piece of your own work supports it, when that work happened, whether the link was chosen by you or worked out by us, and — for graded work — whether that attempt passed, judged by the same pass rule the page that graded it uses. From those we work out each skill's standing. Alongside them we store your answer whenever we asked whether to record a lower standing, together with the attempts that question was about; the figures described in Section 4; and a record of when one of those figures was shown to you. Each week, the first time we show you your Career Twin skill standings, we note how each skill stands that week, so your Sunday summary can show how it moved. We keep each weekly note for about four weeks after that week, include it in your data export, and delete all of them when you delete your account or turn an activity source off or back on. There is free text alongside those pointers, and it is worth being exact about who wrote it: the only prose we generate is a short factual note about a completed session — an observation, never a judgement (Section 4). The rest comes from you: the target role you type in if you set a goal, any comment you add to an item, and the skill names you type — the ones you set as a target's skills, the ones you set against a job description, and a skill name from your profile that we matched to a skill on our list, which we keep beside that match (Section 4). Every entry says where it came from, and you can remove or detach it. Section 4 explains how it works, how to stop it, and how long each part is kept.

o. Email reminder settings. If either the weekly win prompt or the monthly growth digest is — or has been — switched on for your account, we store what those sends need: which of the two you are getting, the day and hour you want the weekly one, your timezone, and, only if you fill it in, the month your performance review falls in. We also count how many prompts in a row drew no journal entry, so that we can ease off automatically rather than keep mailing into silence.

The daily reminder. If you turn on the daily reminder, we email you on days your quest is still open, around the time you chose. It is off unless you turn it on. A day is still open when nothing you have done that streak day yet counts toward your streak; if something has, no reminder is sent. When you turn it on we store that you did and when, the hour you want it (7 pm in your timezone unless you choose another) and your timezone. The email carries your streak count, when your streak day ends in your time, and one next step, picked when it is sent: a free step from the ranked next steps on your Career Twin; or, if your Career Twin has no goal with a free step you can open that day, a mock interview you still have, or else a conversation practice you still have. To choose between those two, we read how many of each you have used in your current allowance; nothing new is stored. It never carries a standing, a readiness or match figure, a price or an offer. If none of these is open to you that day, nothing is sent. After 7 reminders in a row go unanswered we pause it, and your account settings show the pause with a way to resume. If you turn it off, we keep the hour you chose, so turning it back on in your account settings restores it. Every reminder carries a one-click link that stops it. Like every email we send, it carries the open and click tracking set out in Section 2(q).

The timezone is the one your browser reports. It reaches us when you sign in, and we record it when any of these emails is switched on for your account — including where we switched the weekly and monthly ones on for you at sign-up (Section 3). We use it for nothing but working out when to send. We keep it after you switch all of them off, so that turning one back on later restores the schedule you had rather than silently resetting it to a default hour you never chose; it is deleted when your account is deleted. We are listing it separately, rather than leaving it unmentioned inside a scheduling setting, because it is a rough indication of where in the world you are. All of it is visible and changeable in your account settings.

Separately from those settings, for each of these emails we send you we keep a record of when it was sent and, for a weekly prompt, whether a journal entry was filed from the link in it. Each of those records is kept for about 180 days from the send, except the daily reminder's, which record the day it was for and are kept for at most about 60 days. If the weekly win prompt carries a note from your career twin, it is built at send time from your target and the skills on your career twin, and nothing new is stored for it.

If one of these emails bounces. If a reminder in this section, or the win-back message (Section 2(p)), bounces because it cannot be delivered to that address, or you report it as spam, we keep the same note described in Section 2(p1), against a coded form of your address and not your account. A bounce like that stops every one of these emails to that address; a spam report stops at least that kind of email. The note is not deleted with your account.

p. The one win-back email, and whether it arrived. Separately from the reminders above, we may send you a single message — once, ever — if you opened an account and never took a paid plan. It is not a stream and there is no switch left on for it: each account may receive one of these for the lifetime of the account, and once it has gone it cannot be sent again. Every copy carries a one-click unsubscribe link; using it stops this message and takes you out of the campaign permanently, and you can ask us to do the same at support@careerverse.tech.

We measure that one send, and it is worth being exact about which parts of it are attached to you and which are not. Against your account, we record that the message was sent and which version of it you got, and afterwards whether you signed back in, started a free trial or took a paid plan, or why you left the campaign — on the same record that enforces the once-ever limit. Separately, if a copy bounces or you report it as spam, we act on that against your account too: it stops any further mail of this kind reaching you.

Whether it was delivered and whether it was opened, we count for the campaign as a whole. We count how many of these messages our email provider delivered, how many were opened, and how many had a link in them clicked — the first two described on this page since 8 September 2026, the third since 17 September 2026. The open count works because the message carries a small tracking image: it loads when you open the message, which is what reports that a copy was opened — and, as any image in any email does, it discloses to the host serving it your network address and basic information about the mail client that fetched it. That image is not special to this message: every email we send carries one, and any web link in it is tracked as well (Section 2(q), which sets out the one exception). Our own databases hold no per-account record of deliveries, opens or clicks. Ours are counted in aggregate only: running totals for the campaign, with no user id, email address or device identifier stored beside them, so that we can tell whether the message arrives and is read at all. Our email provider does keep one, for this message as for every other: a per-recipient history of its delivery and of any open or click, which we can look up (Section 2(q)). The image is served from a host operated by our cloud provider (Section 6) rather than by us. If you would rather it never loads, most mail clients can be set not to load images automatically; the unsubscribe link stops the message itself.

p1. One follow-up email after your first mock interview. About a day after we grade a mock interview that is the only graded mock interview on your account — normally your first — we may send you one email inviting you back for your next one — but only if you have not been back on CareerVerse on a later day, and only while your account is active and its email address is verified. It is sent once, ever: each account can receive it at most once for the lifetime of the account; once it has been sent or held back (below) it is never sent for a later interview, and if the moment to send it passes we do not send it late. It never carries a score, figure, verdict or standing, or anything else about how your interview went (Section 4).

For the first 4 weeks after we start sending it, about half of the accounts that qualify are picked at random and not sent it, so that we can compare whether the people who got it came back more often than the people who did not. Being in that half is final too: an account picked for it is never sent this email later. After those 4 weeks, every account that qualifies is sent it.

Against your account, we record when that interview was graded, and whether you used the unsubscribe link. If we decided not to send it before choosing a group, we record why (for example, that you had already come back), and when. Otherwise we record which of the two groups your account was placed in, and when; when the email was sent, if it was; and whether your account was active on CareerVerse in the 7 days after the day it was graded, and when we checked. To tell whether you came back, we read the markers of which days your account was active, described in Section 2(m); nothing new is collected for that. The record holds no email address and does not say which interview it was. We keep it until your account is deleted, because it is what makes sure this email is only ever sent once. It is included in the copy of your data you can download (Section 10).

Every copy carries an unsubscribe link, and the one-click unsubscribe some mail apps show at the top of a message. The email is sent only once, so it will not come again either way; using the link records that you did not want it. You can object to the record above by writing to support@careerverse.tech. Like every email we send, it carries the open and click tracking set out in Section 2(q); our own databases hold no per-account record of whether it was delivered, opened or clicked. If a copy bounces because it cannot be delivered to that address, or you report it as spam, we keep a note of that against a coded form of the address (a plain SHA-256 hash of it), not your account, so this email is not sent to it again. The note holds no address and no account, but the same address always gives the same code, so anyone who already knows an address can work out its code and find the note: it is pseudonymous, not anonymous. A copy that bounces because the address does not exist also stops our other reminder emails to that address. That note is not deleted with your account, so that a new account on the same address is not emailed against it.

q. Open and click tracking in every email we send. Every email we send you is delivered by our cloud provider (Section 6), and it adds tracking to each one as it goes out — the tracking is not in the email we write. That covers all of them: sign-in codes; the codes that confirm an account action, and the security notices we send about your account (for example when your other sessions are signed out, or Google sign-in is linked, turned on or removed); a notice that a payment failed; emails about an expert session or a recruiter review; a notice that a mock interview result is ready (Section 2(f)); the weekly win prompt, the monthly growth digest and the daily reminder (Section 2(o)); the win-back message (Section 2(p)); and the one mock-interview follow-up email (Section 2(p1)). It works in two ways:

  • An open-tracking image. A tiny, invisible image, unique to that one message, is added to the email. When your mail client loads it, the request tells our provider that this message was opened, and when.
  • Click-tracking links. Each web link in the email is replaced by a link, also unique to that message, to a host our provider operates, which sends you straight on to the page the link was for. Clicking one tells our provider which link in which message was clicked, and when. There is one exception: the sign-in button in an email carrying a sign-in code. We mark that one link so our provider leaves it as it is, and it does not record a click on it.

Both are served from hosts operated by our cloud provider, not by us, and as any image or link fetched over the internet does, each request also discloses to that host the network address and basic mail-client or browser information of the device that made it — yours, or that of a mail service that loads images on your behalf. Only the formatted (HTML) version of an email is tracked: each of these emails also carries a plain-text version, in which nothing is tracked and no link is replaced.

Who holds the result. Our provider keeps a delivery and engagement history for each message and each recipient: your email address, the subject and sender, the mail service that received the message, and when it was sent, delivered, opened or clicked, or bounced or reported as spam. We can look that history up, by recipient address, for messages sent in the last 30 days. The provider's open and click events are not copied into our own databases; separately, if you file a journal entry from the link in a weekly prompt, we note against that send that it led to an entry (Section 2(o)). None of the provider's history goes to any advertising platform, and what reaches our own monitoring from it is totals, with no address or account attached.

Why, and on what basis. We use it to see whether the emails we send arrive and are read, and to catch problems delivering to the mail services our users rely on. The basis is our legitimate interests in that (Section 3). It is not consent, and we do not call it that: nothing asked you to switch it on.

How to object. Set your mail client not to load images automatically, and the tracking image does not report an open unless images are loaded anyway — by you, or by a mail service that fetches them in advance; a link you click in the formatted version is still tracked, so if your mail client can show the plain-text version instead, use that. Where an email carries an unsubscribe link, using it stops that kind of email, and the tracking that comes with it — the link in the formatted version itself passes through a tracking link, while the one in the plain-text version, and the unsubscribe option some mail apps show at the top of a message, do not. You can also write to support@careerverse.tech. We cannot yet switch tracking off for a single recipient, so for emails without an unsubscribe link, such as sign-in codes, turning off image loading and reading the plain-text version are the ways to avoid it.

Until 17 September 2026 this page described only a tracking image, and only in the win-back message; the tracking set out above was already applied to the emails we send, and this paragraph is the correction.

r. The CareerVerse app. Everything above also applies when you use CareerVerse through the app, except what is about our website alone: the app has no cookie banner, signs you in with an emailed code, with "Continue with Google" or, on an iPhone, with Sign in with Apple (Section 2(a1)), records where your sign-up came from in a shorter form and with no consent choice (below), and loads none of the website's analytics or advertising tools (the website's Google Analytics tag, Google Ads and Meta Pixel); it loads PostHog from version 1.0.1 on Android and 1.0.3 on an iPhone, as below. It does help us measure our own ads on Google, as below: on an iPhone only with your agreement, and on Android unless you turn it off. It also helps us measure them on Meta (Facebook and Instagram), as below: from version 1.0.1 on Android, and from version 1.0.3 on an iPhone only once you allow tracking in Apple's prompt or later in your iPhone's Settings. These are the other differences and additions.

  • Analytics, until you turn them off in the app. The app we publish on the App Store and Google Play sends usage data to Google Analytics for Firebase, which reports into the same Google Analytics property as our website. It sends an identifier Firebase creates for this installation of the app; on an iPhone, the identifier for vendor (IDFV) that Apple gives our company's apps on that phone, which Firebase reads by default (the app no longer sends your phone's Android ID); the screens you open, named by their type and never by the record on them (for example "a job", never which job); events we define, such as finishing a lesson or opening a notification, which can name the course, lesson, coding problem or system-design session they concern but never carry what you wrote, what you searched for, an interview's ID or your account ID, and the ones Firebase records itself, such as the first time the app opens, how long you use it and, where Google can tell, how the app was installed (for example from a store search or a link); your device model, operating-system version, app version and language; and your approximate location, which Google works out from your network address. Unlike our website, the app does not ask first: it runs from the moment the app first opens, until you turn off Send analytics and crash reports in the app's Privacy and data. Turning it off stops the app collecting this usage data, and the crash reports and notes of each use below, on that phone straight away and, unless the phone could not keep your choice (the switch says so when it could not), every time the app opens afterwards, though what it had already gathered may still be sent, and if the app is stopped just as you turn it off, the usage data Firebase records by itself may still be sent the next time it opens; turning it back on starts them all again and, on Android 11 and later, can also send one report of the app not responding from while it was off (Crash reports and notes of each use, below). The choice belongs to the phone, not to your account, so it stays as you left it when you sign out, and the app's sign-in screens say whether it is on. Even while it is off, Firebase may still register or refresh the identifier it created for this installation with Google, without the usage data above. We do not send Google your CareerVerse account ID, and Google signals is off. We import the app's sign-ups, first opens and Premium purchases from Google Analytics into Google Ads, to see which of our own ads lead to them. Advertising storage and ad user data are turned on, on an iPhone only after you agree, and on Android once the app has shown you a short line saying so, until you turn them off (below); Google's ad personalisation stays off, so Google does not use the app's data to build advertising audiences; Meta's use is different (Meta, in our Android app, and Meta, in our iPhone app, below). If you do not agree on an iPhone, or turn it off on Android, the app still sends this usage data, without the advertising ID, and Google may use it to estimate, in aggregate, how our ads perform. Whatever you choose about the app's advertising measurement, Apple's and Google's stores may also tell Google Ads how many installs and purchases our ads led to, without telling us who you are. On an iPhone, Apple does this through its own ad attribution: whether or not you allow tracking, Google Analytics for Firebase tells it that the app has been opened and may tell it which steps you reached in the app. Copies of the app built for our test servers send Google no analytics.
  • Advertising ID. On an iPhone the app asks, using Apple's prompt, whether it may track you. From version 1.0.3, Apple's prompt says that this measures which of our ads on Google, Facebook and Instagram brought you here and led to signing up or subscribing, and picks who sees our Facebook and Instagram ads, that Meta may also use it for its own ads, and that the app works the same either way. It asks when you first tap Get started free, Sign in or Look around first, or later on Home if you have not answered yet. On Android it does not ask: a short line on its start page and sign-in screen, or while you are signed in, tells you that our partners get your advertising ID for ads, and you turn it off with Ad measurement in the app's Privacy and data, which opens once you sign in (until then, you stop it by signing in and turning it off, or by removing the app). If you allow it on an iPhone, or on Android once that line has been shown and until you turn it off, Firebase reads your phone's advertising identifier (Apple's IDFA or Google's advertising ID) and sends it with the usage data above, so that Google Ads can tell which of our ads brought you to the app and led to signing up or subscribing. Meta's kit reads it too: in our Android app from version 1.0.1, under the same switches and the further conditions below, and in our iPhone app from version 1.0.3, only once you allow tracking and while Meta ad measurement is on (below). Nothing in the app depends on your choice. You can stop it at any time: on an iPhone in Settings > Privacy & Security > Tracking, on Android with Ad measurement in the app's Privacy and data, and turning off Send analytics and crash reports stops it too. From version 1.0.1, the short line on our Android app says what our partners get, why, and that you opt out in Privacy and data, without naming them; on its sign-in screen, or while you are signed in, on a phone where PostHog may run without asking (PostHog, in our app, below), it also says that one of them links app use to your account. The partners it means are Google, which gets your advertising ID and app use through Google Analytics for Firebase, for analytics and our ads; Meta, which gets your advertising ID and app use for our ads (Meta may also use them for the ads it shows you, though on a phone the app treats as being in Europe the line, unless you have turned Meta ad measurement off, says that we ask our partners not to target ads, and the app asks Meta not to use them to choose who sees ads); Sentry, which gets crash reports and a note of each use, for analytics: to find and fix what breaks in the app and see how often it crashes; and, where the line says that one of them links app use to your account, PostHog, which is that one: it gets which screens you open and which features you use, linked to your account by a pseudonymous id, for analytics. From version 1.0.3, on an iPhone where PostHog may run without asking, the app's sign-in screen shows a shorter line in place of its usual one: that our partners get your app use for analytics, that one of them links it to your account, and that you opt out in Privacy and data; it says nothing about ads, which Apple's prompt asks about, and the partners it means are Google, through Google Analytics for Firebase, Sentry and PostHog, which is the one that links app use to your account. Version 1.0.0 of our Android app names Google in its line, and elsewhere our iPhone app's line names no partner: it says whether analytics and crash reports are on. The app shows no ads.
  • Meta, in our Android app. From version 1.0.1, our Android app contains part of Meta's software kit for apps, so that we can see which of our ads on Facebook and Instagram bring people to the app and lead to signing up, to free trials and to buying Premium. It never starts in copies of the app built for our test servers, while Send analytics and crash reports, Ad measurement or Meta ad measurement is off in the app's Privacy and data, or before the app has shown you its short line about our partners, unless you have turned on Meta ad measurement yourself. The app does not ask for your consent for this, in Europe or anywhere else: that line is a notice, not a request for consent. We rely on our legitimate interests (Section 3), and you can object by turning it off in Privacy and data, at any time once you sign in (without an account, see below). On a phone the app treats as being in Europe, the line is written for Europe, and the app also asks Meta not to use what it sends to choose who sees ads, ours included; whether and how Meta acts on that is for Meta to decide under its own terms. The app treats a phone as being in Europe when it is set to a time zone in Europe, in a European Union territory elsewhere (such as the Canary Islands or Réunion) or in Saint Barthélemy, to UTC or GMT under any of their names, to a time zone named only by its offset from GMT (such as those in the Etc group), to the "Factory" zone (which means none has been set) or to a time zone it cannot read, or when its mobile network or SIM is from the European Union (its territories included), the European Economic Area, the United Kingdom, Switzerland, or a few other places in Europe or tied to a European country (such as Andorra, Monaco, Gibraltar, the Channel Islands or the Faroe Islands). It goes by your phone's time zone and the countries of its mobile network and SIM, which it reads on your phone each time the app starts, not by where you are, and it sends what it reads for this nowhere (Meta's kit reads the time zone itself and sends it as one of your phone's details below). No feature of the app depends on whether it is on or off. Once it has started, it sends Meta: your phone's advertising identifier (Google's advertising ID), with whether you have asked your phone to limit ad tracking; an identifier Meta's kit creates for the app on your phone (Android's backup of the app's data can carry it, with the rest of what the kit keeps on your phone except its unsent events (Section 5), to a reinstall or a new phone, where the kit, once it starts, sends them on as before); that the app was installed (only in the first days after you install it, unless the app cannot tell when that was), and when it is opened, when Meta's kit first starts while it is open, or when you come back to it after more than a minute away from it or behind another screen (such as Google Play's); when you create your CareerVerse account in the app; when you start a free trial of Premium or buy it in the app, without the plan, the price or the store's identifiers; details of your phone and of the app, such as the phone's model, operating-system version, language and region setting, time zone, mobile network, screen size, number of processor cores and storage space, and the app's version and the store that installed it; whenever Google Play's note about where the app was installed from contains the letters "fb" or the word "facebook", that note exactly as Play gives it; when a Meta ad or link opens the app, or Google Play's note carries Meta's click identifier, the ad-click and campaign identifiers Meta put there, which the kit keeps and sends with the install and every event it sends afterwards; if the Facebook app is on your phone and lets it, the identifier the Facebook app keeps for this, and, if Meta turns this on, the same events handed to the Facebook app on your phone; and, as with any request, your network address. It never sends Meta your name, email address or CareerVerse account ID, anything you write, search for or record, anything from a mock interview or its face check, your scores or your Career Twin. Meta uses this to tell us which of our ads led to installs, sign-ups, trials and purchases, and, under its own terms, may also use it for its own purposes, including to link it to a Meta account you have and to choose and personalise the ads it shows you on and off Facebook and Instagram; on a phone the app treats as being in Europe, the app asks Meta not to use it to choose the ads it shows you, and whether and how Meta acts on it is for Meta to decide. From other phones, we may also use what the app sends Meta to choose who sees our ads on Facebook and Instagram, for example so that people who already have the app are not shown an ad to install it. Through Meta's technology in our Android app we share information from our app with Meta, which also collects information from other apps that use its technology, and Meta uses it to provide measurement services and to target and deliver ads (on a phone the app treats as being in Europe the app asks it not to use ours for targeting ads); you opt out in the app with Meta ad measurement or Ad measurement in Privacy and data. Turning off Meta ad measurement, Ad measurement or Send analytics and crash reports stops it on that phone straight away and, unless the phone could not keep your choice (the switch says so when it could not), every time the app opens afterwards: what it had already sent stays with Meta, a request it was already sending may still arrive, and until the app restarts Meta's kit may still fetch its own settings from Meta, which tells Meta your network address, your phone's language and region setting, and the versions of its operating system and of Meta's kit, but no advertising identifier and no event. If you look around the app without an account, you can turn it off only once you sign in, or by removing the app. To limit how Meta uses what it already has for ads, use the ad settings in your Meta account (Meta's privacy policy says where); on Android you can also delete or reset your advertising ID in your phone's settings. We cannot delete what Meta has received; Meta's own privacy policy says how to ask Meta, and you can also write to support@careerverse.tech and we will pass your request on. See Meta's Privacy Policy.
  • Meta, in our iPhone app. From version 1.0.3, our iPhone app contains part of Meta's software kit for apps too, for the same purpose, but starts it only once you allow tracking in Apple's prompt or later in Settings > Privacy & Security > Tracking, for example after choosing Ask App Not to Track in a prompt that named Meta (an Allow there takes effect from the moment you are back in the app). It never starts in copies of the app built for our test servers, before you allow tracking, after you choose Ask App Not to Track until you allow tracking in Settings, or while Send analytics and crash reports or Meta ad measurement is off in the app's Privacy and data. Allowing tracking, in Apple's prompt or in Settings, is the consent we rely on for it, in Europe as elsewhere (Section 3); Meta ad measurement, on while you allow tracking until you turn it off, turns off Meta alone and leaves the measurement of our ads on Google as it is. But if the tracking prompt you answered was the one our iPhone app showed before version 1.0.3, whose words named only Google, Meta ad measurement is off until you turn it on, and Meta's kit starts only once you do, which, with tracking allowed, is then the consent we rely on. On a phone the app treats as being in Europe, the app asks Meta not to use what it sends to choose who sees ads, ours included; whether and how Meta acts on that is for Meta to decide under its own terms. An iPhone does not tell apps the country of its mobile network or SIM, so the app treats an iPhone as being in Europe when it is set to a time zone the test above counts, or when its region setting, or, once the phone has told the app, the country or region of its App Store, is one of the places that test lists; it goes by these settings, which it reads on your phone each time the app starts, not by where you are, and it sends what it reads for this nowhere (Meta's kit reads the time zone and the language and region setting itself and sends them as details of your phone below). Once it has started, it sends Meta: your phone's advertising identifier (Apple's IDFA), with whether you have allowed tracking; an identifier Meta's kit creates for the app on your phone; that the app was installed, and when it is opened, how long it stays open, how often it is interrupted and roughly how long it had been since it was last open, with a random identifier for each spell of use; when you create your CareerVerse account in the app; when you start a free trial of Premium or buy it in the app, without the plan, the price or the store's identifiers; details of your phone and of the app, such as the phone's model, operating-system version, language and region setting, time zone, mobile network, screen size and number of processor cores, and the app's identifier, version and build; and, as with any request, your network address. The app never hands Meta's kit a link that opened it, so the kit sends Meta no ad-click or campaign identifiers, and the app turns off the parts of the kit that Meta could otherwise switch on to read what you type, the buttons you tap or your screens. It never sends Meta your name, email address or CareerVerse account ID, anything you write, search for or record, anything from a mock interview or its face check, your scores or your Career Twin. Meta uses this to tell us which of our ads led to installs, sign-ups, trials and purchases, and, under its own terms, may also use it for its own purposes, including to link it to a Meta account you have and to choose and personalise the ads it shows you on and off Facebook and Instagram; on a phone the app treats as being in Europe, the app asks Meta not to use it to choose the ads it shows you, and whether and how Meta acts on it is for Meta to decide. From other phones, we may also use what the app sends Meta to choose who sees our ads on Facebook and Instagram. Once it has started, Meta's kit also tells Apple's own ad attribution (SKAdNetwork) which steps you reached in the app, such as signing up, so that Apple can tell Meta how far the installs from our ads went, in a report whose signed contents, Apple says, include no data about you or your phone. Separately, whether or not you allow tracking, from version 1.0.3 the app (never a copy built for our test servers) tells Apple's ad attribution once, while Send analytics and crash reports is on, that it has been opened, as Apple asks of an app whose installs it attributes to ads, so that Apple can tell Meta, or another network whose ad led to the install, that its ad did, in the same kind of report; the app sends nothing to Meta for this. Through Meta's technology in our iPhone app we share information from our app with Meta, which also collects information from other apps that use its technology, and Meta uses it to provide measurement services and to target and deliver ads (on a phone the app treats as being in Europe the app asks it not to use ours for targeting ads); you opt out in the app with Meta ad measurement in Privacy and data, or by turning off tracking for CareerVerse in Settings > Privacy & Security > Tracking. Turning off Meta ad measurement or Send analytics and crash reports stops it on that phone straight away and, unless the phone could not keep your choice (the switch says so when it could not), every time the app opens afterwards, and turning off tracking for CareerVerse in Settings > Privacy & Security > Tracking stops it from the moment you are back in the app, with or without an account: what it had already sent stays with Meta, a request it was already sending may still arrive, and until the app restarts Meta's kit, which stays loaded, may still fetch its own settings from Meta, which tells Meta your network address and the versions of your phone's operating system and of Meta's kit, and can tell it your phone's language, but no advertising identifier and no event. To limit how Meta uses what it already has for ads, use the ad settings in your Meta account (Meta's privacy policy says where). We cannot delete what Meta has received; Meta's own privacy policy says how to ask Meta, and you can also write to support@careerverse.tech and we will pass your request on.
  • What our app sends PostHog

    PostHog, in our app. From version 1.0.1 of our Android app and version 1.0.3 of our iPhone app, the app sends PostHog, our analytics service provider (Section 2(j)), how you use the app while you are signed in: the screens you open, named by their type and never by the record on them, each with the part of the app it belongs to, its time and an identifier of its own; these named events, each also with its time, an identifier of its own and the type of the screen you had last opened: signing in (and whether with an emailed code, Google or Apple), each step of the app's welcome, choosing your first quest (which kind, or that you skipped it or went on to the page you had opened, and whether on the welcome or on Home), seeing your first-win card (and what the win was: a mock interview, a coding problem, a lesson, a system design or a project), starting a mock interview (and whether it is your first), a mock interview you sat being graded, solving a coding problem, enrolling in a course, finishing a lesson, a project you sent being graded, opening your Career Twin, logging a win (and how it came in and through which part of the app), adding a job (and how you added it), seeing a Premium offer (and whether it was the mock-interview limit card, a Premium feature's wall or the purchase sheet), and opening, completing or failing to complete a purchase, with its billing period, where the offer or purchase was opened from and whether a completed one is a free trial, never what you wrote, a score, the id of a record of yours or the store's purchase reference (an event about a course, lesson, coding problem or project names which one); your phone's system and its version, the app's package name or, on an iPhone, its bundle identifier (the same on every phone), version and build, whether that copy of the app is built for our live or our test servers, the name and version of PostHog's software in the app, our PostHog project's public key and the time each batch of events is sent, two marks that the event comes from a signed-in member and belongs on that member's profile, and your screen's size; a random identifier for each spell of use, which groups its events; your plan (Free or Premium, and whether you are on a free trial or paying), sent each time the app starts sending for your account, with its time and an identifier of its own, and, for our own staff, the mark in Section 2(j); where the app asked you and you said yes, when you said it and to which version of its question; and the approximate location PostHog works out from your network address, after which it discards the address. It is linked to your account by the same pseudonymous id as on our website, so what PostHog records from the app and from our website joins under one profile. It never receives your email address, name or account ID, and the app sends it nothing before you sign in and nothing it records after you sign out. Each time the app starts sending for your account, and never before, PostHog's software in the app also fetches its settings from PostHog, a request that carries our PostHog project's public key, the software's name and version and, as any request does, your network address, and nothing about how you use the app. Whether the app asks first depends on where your phone seems to be. On a phone the app does not treat as being in Europe (the test in the two Meta bullets above, which for PostHog the app also applies again each time it would send) and, from version 1.0.1 on Android or 1.0.3 on an iPhone, has never treated so, the app does not ask: it starts for your account once you have signed in on that phone after its sign-in screen showed you its short line about our partners in the form that says one of them links app use to your account (the line names none of them; Section 6 says PostHog is that one; on an iPhone it is the shorter line in Advertising ID, above; the same line on the app's start page leaves those words out and does not count), or once the app has shown you that line while you were signed in there, and sends this until you turn off PostHog product analytics in Privacy and data. If that line was not on your screen as you signed in, for example because you signed in before scrolling down to it, or you were already signed in when the app updated to version 1.0.1 (1.0.3 on an iPhone), it does not start until you sign in again with the line shown, the app has shown you the line while you are signed in, or you turn on PostHog product analytics yourself. On a phone it treats, or from version 1.0.1 on Android or 1.0.3 on an iPhone has once treated, as being in Europe, the line never says that, and the app asks you once, on its own screen, and sends nothing unless you say yes, wherever the phone is later. From 13 April 2027 the app asks on every phone and stops for anyone who has not said yes. Turning off PostHog product analytics stops it on that phone at once and asks PostHog to delete what it holds about you, including what it recorded on our website. Turning off Send analytics and crash reports stops it too, for every account on that phone, and asks for the same deletion for each account the app has sent PostHog anything for from that phone: at once for the account signed in, and for any other the next time it signs in there (deleting that account also deletes it). Saying no on the app's own screen after it has already sent PostHog anything for your account from that phone stops it and asks for the same deletion for your account. If the app cannot reach us, it tries again each time you open it signed in to that account. Your choice is kept on that phone only: on another phone, or if you remove and reinstall the app on Android, the app sends nothing until it has shown you that line there as above, you say yes where it asks, or you turn on PostHog product analytics there, and you turn it off there too; an iPhone can keep what the app noted for this after you remove the app, so a reinstall there can carry on as before. Our website's cookie choice does not change what the app does, and the app's choice does not change our website's.
  • Purchases in the app. If you buy Premium in the app, Google Analytics for Firebase also records that purchase from Apple's or Google's store: which plan, its price and currency, and the store's identifiers for that purchase. We use it to see how the app is used and to measure which of our ads lead to purchases: with your advertising ID on an iPhone only if you agree and on Android unless you turn it off, and otherwise only in Google's aggregate estimate (above). The app also tells Meta that you started a free trial of Premium or bought it, without the plan, the price, the currency or the store's identifiers (above): our Android app from version 1.0.1, and our iPhone app from version 1.0.3 once you have allowed tracking. The store, not CareerVerse or Google, takes your payment.
  • Crash reports and notes of each use, until you turn them off in the app. When the app crashes, meets an error or stops responding, it sends a report to Sentry: what failed and where in our code, the type of screen it happened on (never the record on it), the steps that led there on screens where we allow that, technical details such as your device model, operating-system version and language, the app version, and a random identifier that Sentry's software creates for this installation of the app; from version 1.0.1 of our Android app, on Android 11 and later, a report that the app stopped responding also carries Android's own record of that moment: what each part of the app was doing, how much processing time and memory it was using, and technical details such as your phone's Android build. On Android 14 and later, that record also holds Android's reason for the freeze and its short list of recent serious events on the phone, such as an app crashing or not responding, which can name other apps' processes: as Google builds Android, it names those of Android itself and of apps built into the phone's system software, with Android's own words for what went wrong, and gives numbers in place of the name of any other app's process. Apart from Android's own record, which our app sends as Android wrote it, a report never carries your name, email address, account ID, a picture of your screen, or what you typed. The app also sends Sentry a note each time you use it, under that same identifier, of when the use began, how long it lasted, how many errors it met, how it ended (for example in a crash), and the app version, so that we can see how often the app crashes. As with any server, Sentry, in the United States, also receives the network address a report or one of these notes comes from, and our Sentry project is set not to store it, but Sentry works out from it your approximate location (the country, and sometimes the region or city) and keeps that with the report. The same Send analytics and crash reports switch stops crash reports, and these notes, on that phone, apart from any it had already gathered (above); but on Android 11 and later, once the switch is on again, the app can send Sentry a report of the latest time in the past 91 days that it stopped responding, even one from while the switch was off.
  • Push notifications, only if you turn them on. If you allow notifications and turn one on in the app, the app gets a push token for your phone from Apple or Google through Expo's push service, giving Expo the token Apple or Google issued and a random identifier the app keeps on your phone, and sends the push token to us with whether the phone runs iOS or Android and the app's version. We use it to send the notifications you chose: the daily quest reminder, the weekly win prompt, and a note that a mock interview result, a review draft or promotion packet, a project grade or a recruiter review is ready, that a project could not be graded, or that an expert call you booked is confirmed or could not be scheduled. Each notification is a fixed sentence, a link to the page it is about and a label naming its kind. It never carries a score, a verdict, a note, a title, a skill area or a reason. To send one, we give the token, that sentence, the link and the label to Expo, which hands them to Apple's or Google's notification service to deliver. We keep at most ten phones per account. We delete a phone's token when Apple or Google tell us it no longer accepts notifications, when another account turns notifications on for that phone, when a newer phone takes its place among your ten, or when you close your account. Signing out of the app does not always delete it: the app asks us to only if it has sent us the token since it last started, and that request can fail to reach us, so a phone you have signed out of can go on receiving the notifications you turned on. You can turn each kind off in the app, which stops it on all your phones, or turn off notifications for CareerVerse in a phone's settings, or delete the app from it, which stops them on that phone.
  • Reminders that stay on your phone. Some reminders, such as one before a key date on your job tracker, the clock for a system-design session, the end of a focus timer you start in a lesson, or one an hour before an expert call you booked, are set by the app on your phone with your phone's own notification system. They are not sent to us.
  • App lock. If you turn on the app lock, your phone checks your face, fingerprint or passcode with its own system, and the app learns only whether the check passed. Your biometric data never leaves your phone, and we never receive it.
  • What stays on your phone, and your phone's backup. The app keeps your sign-in in your phone's secure storage (the iPhone keychain, or Android's equivalent), and keeps some settings and unsent drafts on the phone, such as a system-design canvas you are still working on. Drafts are deleted when you sign out or another account signs in on that phone. Like other app data, unsent drafts can be included in your phone's own backup (iCloud, or Android's device backup), depending on your backup settings, which are between you and Apple or Google.
  • Conversation practice in the app turns what you say into text on your phone, and only that text, and how long you spoke, is sent to us: your voice is never recorded and never leaves your phone. Where your phone cannot do that on its own, the app asks you to type instead.
  • Python in lessons. When you run Python in a lesson, the app loads the Python runtime (Pyodide) from jsDelivr, a public content-delivery network, which receives your network address, basic device information and the files requested, including any Python package your code imports, and nothing about your account (Section 6).
  • Files you make in the app. When you export or share something from the app, for example your resume as a PDF or a prep sheet as text, the app makes it on your phone and hands it to the app you choose from your phone's share menu. We do not see where it goes.
  • The camera, the microphone and your photos. The app opens your photo library only when you choose to pick a profile photo, an image for a community post, screenshots for a project you send for grading, or a screenshot for a report you send us (Reports you send from the app, below), and asks for your camera only when you choose to take a profile photo or a photo for a community post or a project, or start a mock interview. It asks for your microphone for a mock interview (next), or when you choose to speak your side in conversation practice. When you agree to a mock interview's consent screen, the app asks for your camera and then your microphone, because the interview is recorded and your spoken answers are turned into text. On an iPhone it also asks to use speech recognition, for the backup Section 4 describes.
  • Referral codes in the app. If you install the app on an Android phone from a Google Play link that carries a friend's referral code, Google Play keeps that code, and the app reads it for your referral once, the first time it opens. The app keeps that code on your phone until you first sign in, or for 90 days at most. It is sent with your first sign-in and counts only if that sign-in creates a new account. You can also type a friend's invite code when you sign up; a code you type is used instead of one the app found (see the Refer & Earn Terms).
  • Where your sign-up came from, with no switch in the app. The app may find up to four short labels: the source and medium of what brought you (for example google-play and organic), and the campaign name and campaign id, if a link carried them. It finds them in a link that opens it before you sign up, or, on Android, in the install referrer Google Play gives the app, which the app reads for this once, the first time it opens. For an ordinary install from the Play Store that referrer says only that you came from Google Play; a Play link of ours can add a campaign. On an iPhone the app reads no install referrer, so an iPhone sign-up records labels only if a link opened the app first. Labels from a link are held in the app's memory only; labels from Google Play are kept on your phone until you sign in, or for 90 days at most. The labels are sent with every sign-in attempt from that phone while the app holds them, even one that fails or that signs you in to an account you already have, and we keep them only if a sign-in creates your account. Any sign-in or sign-out ends both. We store the labels on your account together with a channel we work out from them by the same rules our website uses (for example organic search or paid social), and use them only to understand which of our own channels and campaigns bring people to the app. We never take a search term, an ad's wording or an advertising click identifier, a later sign-in never changes what we stored, and we do not share these labels with any advertising platform; but from version 1.0.1 of our Android app, Meta's kit, once it has started, takes the install referrer Google Play gives the app and, whenever it contains "fb" or "facebook", sends it to Meta whole, with any labels in it (Meta, in our Android app, above). There is no switch for this in the app, and our website's cookie choice does not cover it, so withdrawing consent on our website does not delete it. It is included when you download a copy of your data, and deleted when you close your account.
  • In-app purchase. If you buy Premium in the app, you pay through the App Store or Google Play, which processes the payment under its own terms and privacy policy; we never see your card details. As you buy, the app gives the store your account's random store-account token, and afterwards it sends us the purchase so that we can check it with the store. When the app opens, and when you choose to restore your purchases, it sends us your store purchases again so that your Premium stays up to date. Section 2(i) lists what we keep.
  • Reports you send from the app. You can send us a report from the app, such as a bug, a suggestion or a question, with any screenshot you attach. With it, the app sends the email address you leave for a reply, which starts as your account's; the address of the screen you sent it from, never with a search you typed, a referral code, a public page's name, a certificate ID or a share link in it; whether the phone runs iOS or Android, its operating-system version and the app's version. Until you send it, the app keeps what you typed on your phone as an unsent draft. You can also report an answer our AI wrote for you. Choosing Report this answer under it sends us, with the same details, the answer's text as you saw it (cut at 8,000 characters if it is longer), which part of the app showed it, the reason you choose, any words you add, whether you had changed the text, and the IDs of the record it belongs to, such as the conversation or the mock interview, so that we can look into it. If you report an AI Mentor reply, your question goes with it too, unless you turn off Include my question before you send. An AI answer can repeat what you gave us, such as parts of your resume or a review, so the report can carry those words too. An AI-answer report never carries a screenshot, and the app keeps no draft of it. The people at CareerVerse who handle reports read them; we never send a report to our AI provider, and we keep every report until you delete your account. A copy of your data includes your reports.

s. Recruiter reviews and expert calls. When you ask for a recruiter review, a person acting for CareerVerse reads the resume saved on your profile and writes a review of it. Our AI provider (OpenAI) then turns that written review, not your resume itself, into the report card you receive, and a person acting for us checks the card before it is sent to you. When you book an expert call, the person who arranges it for us sees your name and email address, the area and reason you chose, any note you added, the length and time you picked, and the time zone you were in, so that they can find an expert and set the call up. They pass your name, your email address and the length and time you picked to the expert who takes the call, so that you can be invited to it, and the area and reason you chose and any note you added, so that the expert can prepare. If you book from a job you saved, we start that note with the job's role and company, which you can change or delete before you book.

What we do not do. We do not sell your personal data or show third-party ads on CareerVerse. Our advertising is limited to running and measuring our own campaigns on platforms such as Google and Meta (Section 2(k)); those platforms may use the advertising signals they receive under their own policies (Sections 2(k) and 2(r)). The third-party tools we use on our website include Google Analytics, PostHog, Google Ads, and Meta Pixel, each loaded only with your consent (see Sections 5–7). In the app, Google Analytics for Firebase and Sentry run without a consent choice until you turn them off there, PostHog runs in the app, from version 1.0.1 on Android and 1.0.3 on an iPhone, without a consent choice on a phone the app does not treat as being in Europe, once the app has shown you its short line about our partners in the form that says one of them links app use to your account and until you turn it off, and only with your yes on a phone it treats as being in Europe, the app's advertising measurement runs on an iPhone only if you agree (apart from what the app tells Apple's own ad attribution whether or not you allow tracking: that it has been opened and, through Google Analytics for Firebase, possibly which steps you reached, so that Apple can tell an ad network how many installs and purchases its ads led to, as Section 2(r) describes, in a report whose signed contents, Apple says, include no data about you or your phone) and on Android unless you turn it off, which includes Meta, from version 1.0.1 on Android and, only once you allow tracking in Apple's prompt or later in your iPhone's Settings, from version 1.0.3 on an iPhone, and the app records where your sign-up came from with no switch, as Section 2(r) sets out.

3. How and why we use your data, and our legal bases

In short: To run CareerVerse for you, keep it working and honest, and meet our legal duties. Each use below gets its own line, and each answers two separate questions: the basis under the EU and UK GDPR, and the ground we expect to rely on under India's DPDP Act once its main provisions commence. Those are not the same list and we have not pretended they are. Where a line says consent, there is a real switch and we tell you where it is; where there is no switch, we do not call it consent.

A note on how we cite. Everywhere else in this policy, "Section 5" means a section of this document. In the tables below we are citing statutes, so we write those as DPDP s.7(a) or GDPR Art. 6(1)(b). If you see "s." or "Art.", we mean the Act named in that column, not this policy.

Your account, and the Service you asked for

What we doWhyEU/UK GDPR basisIndia — DPDP ground (from May 2027)
Sign you in by one-time email code, or with Google or Apple if you choose either (Section 2(a1)), and keep your sessionGive you access to your accountPerformance of a contractDPDP s.7(a) — you gave us your email in order to be signed in
Rate-limit sign-in, the home-page demo's reports (Section 2(m1)) and other sensitive requests, using the network address the request arrived fromStop credential-stuffing and abuse of the sign-in system, and keep the demo's counts from being floodedLegitimate interests: keeping accounts and the sign-in system safe, and our counts honestNothing on the s.7 list squarely fits — see "Security, and a gap we are not papering over" below
Record, when you sign up, the network address the request reached us from, look it up with IPinfo for its country, region, city, time zone and network (Section 2(a)), and count how many accounts that network has started that day, which can make a new account's first mock interview wait (Section 2(a))Keep our own sign-up records, look into fraud and abuse, and keep one network from taking the free allowances meant for many peopleLegitimate interests: keeping accurate records of our own service, and keeping it free of fraud and abuseDPDP s.7(a)
Draw the "Continue with Google" button, which loads Google's code and lets Google see your visit even if you never use it (Section 2(a1))Offer you a sign-in methodLegitimate interests: offering a sign-in method. Google and we are jointly responsible for what the button sends as it loads — see belowConsent — a step we have not built yet. This is separate from the cookie banner, which does not cover the sign-in button (Sections 5 and 6)
Start a new account's profile with the display name and photo from the Google Account you signed up with, including fetching that image from Google once and keeping our own copy (Section 2(a2))Give a new account a usable profile instead of an empty oneLegitimate interests: sparing you from re-entering what you have just signed in with. You can object by clearing either field in your profile — we never put them backThe s.7 list does not cover this either: you gave this data to Google, not to us, so it was not "voluntarily provided" to us for this purpose. We will ask properly before those provisions commence
Store and display your profile, resume, job applications, journal entries, notes, bookmarks and other content you createProvide the core ServicePerformance of a contractDPDP s.7(a) — you gave it to us to be stored and shown back to you. For how a name or photo can arrive on your profile without you giving it to us, see the row above
Fetch the public details of your own LinkedIn profile through an outside profile-lookup service when you ask, show them to you, and save the ones you tick (Section 2(g))Fill your profile from your own LinkedIn profilePerformance of a contract — you asked for the import and confirmed the profile is yoursDPDP s.7(a) — you gave us the link for exactly this
Run and grade the coding problems, projects, system-design sessions and course exercises you submitProvide the practice features you usePerformance of a contractDPDP s.7(a)
Send the text you give us to our AI provider (Section 4) to power resume, interview, mentor, conversation-rehearsal and grading featuresProvide the AI features you ask for, at the moment you askPerformance of a contractDPDP s.7(a) — you supplied the text for exactly this
Meter your usage against the limits of your plan — CVTokens, mentor turns, interviews, code runs, conversation simulations and job-description readings each count separately — and run your daily CVToken allowance, for which we keep your CVToken balance, the day you last checked in and that day's roll, the streak gifts added, and this month's spend, while your account exists, deleting them when you delete it; and hold a new Free account's first practice conversation, or first mock interview, until the time we recorded at sign-up (Section 2(a))Keep the Service usable and priced fairlyPerformance of a contractDPDP s.7(a)
Take payment and manage your subscription, renewals and refundsBill you for a plan you boughtPerformance of a contractDPDP s.7(a)
Check a Premium purchase you make in the app with the App Store or Google Play, keep it up to date from the notices the store sends us, and tie it to your account, and to no other, with a random store-account token (Section 2(i))Give you the Premium you bought in a store, wherever you use CareerVersePerformance of a contractDPDP s.7(a) — the app sends us the purchase to check
Have a person acting for us read your resume for a recruiter review you asked for, and our AI provider turn their written review into your report card; share your booking with the person arranging an expert call, and your name, email address and note, and the call's area, reason, length and time, with the expert who takes it (Section 2(s))Provide the review and the call you asked forPerformance of a contractDPDP s.7(a)

Mock interviews

What we doWhyEU/UK GDPR basisIndia — DPDP ground (from May 2027)
Record camera video and microphone audio during a mock interviewLet you practise and watch yourself backConsent, taken before recording starts; and performance of a contract for the practice session you asked forConsent (DPDP s.6)
Send the audio of your answers to a speech-to-text provider so it can be turned into the transcript you are graded on, and — where that provider is unavailable — fall back to your browser's own transcription or, in the app, your phone's own speech service (Section 4). Before your first question you can test your microphone: one sentence you say is sent to the same speech-to-text provider and turned into text so you can see it works; it is shown only to you and is not saved or graded; if none of your answers in an interview come through as words, you can run the test once more during that interview, and that sentence, though never graded, is part of that interview's recording and, whenever we keep that recording, is kept and deleted with it; in the app, if no test has run for that interview since the app was last started, the camera and microphone check before you begin starts one by itself once your microphone hears you, unless a screen reader is on, when it waits for you to start it, and never while the app is asking whether you want to begin without a test.The transcript is the graded artefact; without it there is no mock interviewConsent, taken on the same screen, which names AssemblyAI as the provider that turns your answers into text in the European Union, and names the backup that takes over when it cannot: your browser's vendor on our website, or in the app your phone's own speech service (Apple, Google or your phone's maker); and performance of a contract for the practice session you asked for. Section 7 covers the transfer positionConsent (DPDP s.6)
Send the text of each question to a speech-synthesis provider so the interviewer can read it aloud (Section 4)Make the exercise a spoken interview rather than a reading exercise. Your own voice is never sent to itPerformance of a contractDPDP s.7(a)
Capture proctoring events during a mock interview — for example face not detected, multiple faces, looking away, tab switch, window blur, full-screen exit, camera or microphone disconnect, blocked right-click and blocked copy/paste — and derive an integrity signal from them. In the app, the face events come from a face check that runs on your phone, in an interview started in the app under its current wording, and the other events are leaving the app or locking your phone, something such as a call coming over the app or taking its sound, and the camera or microphone stoppingMake the exercise a fair test of you, so the result means somethingConsent, taken on the same screen; and legitimate interests in the exercise being honestConsent (DPDP s.6)
Send those proctoring events, with your answers, to our AI provider as advisory input to grading (Section 4)Grade the mock interview you asked for. The face analysis that notes some of those events still rests on your consent (the row above)Performance of a contract: grading is part of the mock interview you asked forDPDP s.7(a)
Work out an optional composure estimate on your device from your camera — in your browser, or on your phone in the app — and store the per-answer and whole-session summary figures it produces (Section 2(f))Give you optional coaching on how you came across. We do not use it in gradingConsent — off unless you turn it on during the interviewConsent (DPDP s.6)
Measure the timing of your spoken answers in your browser (in the app, on your phone) and show it back as delivery notes (Section 2(f))Give you feedback on how you spoke; not used in gradingPerformance of a contractDPDP s.7(a)
Finish grading a mock interview in the background — when grading it took longer than our time limit allows or failed when you submitted it, or when you answered every question but the interview was never submitted — and email you once that its result is ready (Section 2(f))Give you the result of the practice session you asked forPerformance of a contractDPDP s.7(a)

Community, and anything you choose to make public

What we doWhyEU/UK GDPR basisIndia — DPDP ground (from May 2027)
Host Community discussions and comments, and publish the ones you choose to make public — to anyone, and to search engines (Section 14)Run the community, and publish what you chose to publishPerformance of a contract — hosting and publishing to the audience you chose are both part of the Community service you signed up for. Where a post contains special-category data, you have manifestly made it public (Art. 9(2)(e))Hosting: DPDP s.7(a). Once it is public, the Act does not apply to data you have yourself made publicly available (DPDP s.3(c)(ii)(A))
Keep your blocked list and hide blocked members' posts and comments from you (Section 14)Let you stop seeing a member you don't want to seePerformance of a contract — it is part of the Community service you signed up forDPDP s.7(a)
See which account posted anonymously, act on reports, and moderate contentKeep the Community safe and enforce our TermsLegitimate interests: safety, moderation, and enforcing our TermsNothing on the s.7 list squarely fits — see below
Publish a public profile at a handle you claim, or a share link for a promotion packet you choose to sharePublish the page you asked us to publishPerformance of a contract, carrying out your instructionDPDP s.7(a); and the Act does not apply to data you have yourself made publicly available (DPDP s.3(c)(ii)(A))

Your Career Twin

What we doWhyEU/UK GDPR basisIndia — DPDP ground (from May 2027)
Build your Career Twin automatically from work you complete here, including a standing for each skill worked out from your graded results, and keep a record that a profile import ran (Section 4)Provide the Career Twin featurePerformance of a contractConsent — a step we have not built yet. Today the per-source switches in your account settings are how you stop it
Read a journal entry, or your profile headline or summary, that you select, and suggest skills from itProvide a feature at the moment you ask for itPerformance of a contract, at your requestDPDP s.7(a) — you chose the text and asked us to read it
Read work you completed before the feature existed, so your record is not emptyMake the feature useful from your first visitLegitimate interests: making the feature useful immediatelyConsent — a step we have not built yet

Keeping the Service working, and knowing whether it works

What we doWhyEU/UK GDPR basisIndia — DPDP ground (from May 2027)
Keep the Service secure, investigate abuse, keep server logs, and enforce our TermsProtect you, other users, and usLegitimate interests: preventing fraud and abuse, and keeping the Service availableNothing on the s.7 list squarely fits — see below
Keep streaks, mastery points, badges and your activity heatmap from the work you do here. A day counts toward your streak when you roll or check in.Show you your own progressPerformance of a contract — it is a feature on your account pageDPDP s.7(a)
Count each account's active days, and which growth lens you chose, and report those to ourselves as cohort figuresSee whether people come back, and whether a feature is worth keepingLegitimate interests: understanding whether the Service worksConsent — a step we have not built yet
Maintain, debug and improve CareerVerseFix faults, and decide what to build nextLegitimate interests: keeping the Service running, and deciding what to buildConsent — a step we have not built yet
Receive crash reports from the app through Sentry, and a note of each time the app is used (Section 2(r))Find and fix what breaks in the app, and see how often it crashesLegitimate interests: keeping the app working. You have a right to object: turn off Send analytics and crash reports in the app's Privacy and data, which stops both from that phone, apart from what Section 2(r) says may still be sentConsent — a step we have not built yet: the app's switch is on until you turn it off, which is not consent
Send the push notifications you turn on in the app, through Expo, Apple and Google (Section 2(r))Tell you what you asked to hear aboutConsent: each is off until you turn it on, and you can turn it off in the app or your phone's settingsConsent (DPDP s.6)
Keep aggregate, non-identifying counts of product activity (Section 2(m))See whether the Service, and the journey from signing up to upgrading, actually worksThe stored counts are not personal data. But a request is what increments one — usually a signed-in request, though the campaign-link counts and the home-page demo's two counts are also incremented by requests from visitors who are not signed in (Sections 2(m) and 2(m1)) — and that observation rests on our legitimate interests in measuring the ServiceThe stored counts are not personal data. For the request that increments one, the position is the same as the line above
Send you the weekly win prompt and the monthly growth digest by emailKeep your achievement journal alive, and show you what it added up toConsent — the switch in your account settings — except where we resolved your sign-up as coming from India or the United States, in which case both may start on and the basis is our legitimate interests in helping you get value from the journal and the career twin you keep with us. You can switch them off at any time, and you have a right to object (see below)Consent — a step we have not built yet, and one we will have to ask for before ss.3–17 commence. Sign-ups we resolve as Indian may start with both already on
Send you the daily reminder email, only after you turn it on, on days your streak day is still open, with one next step: a free step from your Career Twin, or else a mock interview or conversation practice you still have (Section 2(o))Help you keep practising on a day you have not yetConsent: it is off unless you turn it on, and you turn it off in your account settings or with the link in any reminderConsent (DPDP s.6)
Use the same resolved sign-up country to decide which country's rates, currency and payout method apply to you in Refer & Earn, and record that answer against your referral profileWork out what a referral pays you, and in which currency, without asking you for anythingPerformance of a contract — it is what decides the amount and the currency of a commission you are owed under the Refer & Earn Terms. Where we could not resolve it, we ask you instead and record your answerDPDP s.7(a) — it is necessary to work out and pay what we owe you under a programme you chose to take part in

Measurement and marketing

What we doWhyEU/UK GDPR basisIndia — DPDP ground (from May 2027)
Measure product usage with third-party analytics tools (Google Analytics and PostHog, including PostHog's session replays)Understand how the Service is used, and fix problems; analyse that pseudonymised usage data, including with AI tools, to improve the Service and our marketingConsentConsent (DPDP s.6)
Measure how the app is used with Google Analytics for Firebase, including the identifier for vendor on an iPhone (Section 2(r))Understand how the app is used, and fix problems; Google may also use this usage data, without the advertising ID, to estimate in aggregate how our ads performLegitimate interests: understanding how the app is used, and, in aggregate and without the advertising ID, how our own ads perform. This is not consent and we do not call it that — the app's switch for it is on until you turn it off. You have a right to object: turn off Send analytics and crash reports in the app's Privacy and data, which stops it from that phone, apart from what Section 2(r) says may still be sent; we cannot turn it off for an installation from our sideConsent — a step we have not built yet, and one we will have to ask for before ss.3–17 commence: the app's switch is on until you turn it off, which is not consent
Measure how the app is used with PostHog, from version 1.0.1 on Android and 1.0.3 on an iPhone, linked to your account by the pseudonymous id and joined with what PostHog records on our website (Section 2(r))See where people get stuck and what helps them, across the app and our website, and fix problemsOn a phone the app does not treat as being in Europe: legitimate interests: understanding how the app is used. This is not consent and we do not call it that — the app runs it once it has shown you its short line about our partners in the form that says one of them links app use to your account, until you turn it off. You have a right to object: turn off PostHog product analytics or Send analytics and crash reports in the app's Privacy and data on each phone you use, which stops it from that phone and, as Section 2(r) sets out, asks PostHog to delete what it holds about you. On a phone it treats as being in Europe: consent, asked on the app's own screenOn a phone the app does not treat as being in Europe: consent, which the app asks every member for from 13 April 2027, before the Act's main provisions commence; until then it runs on notice and you object with the switch. On a phone it treats as being in Europe: consent (DPDP s.6)
Measure our own advertising with Google Ads and Meta Pixel, including sending Google a hashed version of your email (Section 2(k))See which of our ads bring people to CareerVerseConsent. For what those tags collect and send as they load, Google and Meta are each jointly responsible with us — see belowConsent (DPDP s.6)
Measure our own app advertising with Google Ads: the advertising ID and the usage and purchase data in Section 2(r)See which of our ads bring people to the app and lead to sign-ups and purchasesConsent: Apple's tracking prompt on an iPhone. On Android, legitimate interests: knowing which of our own ads bring people to the app and lead to sign-ups and purchases. This is not consent and we do not call it that — the app's Ad measurement switch is on until you turn it off. You have a right to object: turn off Ad measurement in the app's Privacy and data, which stops it from that phone, as turning off Send analytics and crash reports does; before you sign in, Section 2(r) says how. For what the app sends for it, Google is jointly responsible with us — see belowOn an iPhone, consent (DPDP s.6). On Android, consent — a step we have not built yet, and one we will have to ask for before ss.3–17 commence; until then, notice and opt-out
Measure our own app advertising with Meta, in our Android app from version 1.0.1 and, once you allow tracking, our iPhone app from version 1.0.3: the advertising ID, the phone and app details and the install, open, sign-up and trial or Premium events in Section 2(r)See which of our ads on Facebook and Instagram bring people to the app and lead to sign-ups, trials and purchases, and, from phones the app does not treat as being in Europe, choose who sees themLegitimate interests, on every Android phone, Europe included: knowing which of our own ads bring people to the app and, from phones the app does not treat as being in Europe, choosing who sees them. This is not consent and we do not call it that — Meta's kit runs once the app has shown you its short line about our partners, or once you turn on Meta ad measurement, until you turn it off. On a phone the app treats as being in Europe, the app also asks Meta not to use what it sends to choose who sees ads, ours included. You have a right to object: turn off Meta ad measurement or Ad measurement in the app's Privacy and data, which stops it from that phone, as turning off Send analytics and crash reports does; before you sign in, Section 2(r) says how. For what the app collects and sends to Meta, Meta is jointly responsible with us — see below; what Meta then does with it, including personalising ads, Meta decides alone. On an iPhone: consent, which you give by allowing tracking in Apple's prompt or later in Settings > Privacy & Security > Tracking (and, if the prompt you answered was the one our iPhone app showed before version 1.0.3, which named only Google, by also turning on Meta ad measurement) and withdraw there, or for Meta alone with Meta ad measurementOn an iPhone, consent (DPDP s.6). On Android, consent — a step we have not built yet, and one we will have to ask for before ss.3–17 commence; until then, notice and opt-out
When you sign up on our website, record on your account which channel or campaign your sign-up came from, and, for a campaign link, when you started a trial or first paid (Section 2(l))See which of our own channels and campaigns bring people to CareerVerse, and which of our campaign links lead to trials and paymentsConsentConsent (DPDP s.6)
When you sign up in the app, record on your account the source, medium, campaign name and campaign id the app found, and the channel we work out from them (Section 2(r))See which of our own channels and campaigns bring people to the appLegitimate interests: knowing which of our own channels and campaigns bring people to the app. This is not consent and we do not call it that — there is no switch in the app. You have a right to object by writing to support@careerverse.tech, and we will remove these labels from your accountConsent — a step we have not built yet, and one we will have to ask for before ss.3–17 commence
Count how often each of our campaign links is opened, and — using the campaign-link cookie in your browser (Section 5) — by how many different browsers (Section 2(m))See how many people each of our own posts and campaigns reachesLegitimate interests: knowing how many people open our campaign links. This is not consent and we do not call it that — there is no switch you turned on. You have a right to object: delete the cookie in your browser at any time, which makes no difference to using CareerVerse, though opening another of these links while signed out sets it again; to stop that too, block cookies for this site, which also stops you staying signed in. It is never read or set while you are signed inThe counts are not personal data, and the cookie holds only link codes. For reading that cookie: consent — a step we have not built yet
Keep the choice you made at the cookie banner on your account, and — when you are signed in on a device where the cookie recording it is missing — put your own last answer back rather than asking you again (Section 5)Be able to show what you agreed to and when, and honour an answer you have already given — including a refusal — on every device you sign in onLegal obligation to be able to demonstrate the consent you gave (GDPR Art. 7(1)) for keeping it; legitimate interests in not re-asking a question you have answered, for reading it back. This is not a second consent and we do not call it one: it only ever restores a decision you made, it never turns a refusal into an acceptance, and it never restores one you withdrewDPDP s.7(a) — you gave us the answer so that we would act on it
Send you the one win-back email, record against your account that it was sent, which version you got, and whether you then signed back in, started a free trial, took a paid plan or left the campaign, and count deliveries, opens and clicks for the campaign in aggregate — the opens through a tracking image and the clicks through tracked links (Section 2(p))Reach an account that never took a paid plan, once, and know whether that one message arrives and is read at allLegitimate interests: telling our own existing users about our own service, and knowing whether a message we sent them worked. This is not consent and we do not call it that — there is no switch you turned on. You have a right to object: the one-click unsubscribe in the message stops it permanently, or write to support@careerverse.tech. Our own databases hold no per-account record of deliveries, opens or clicks; the per-recipient history our email provider keeps of every email, this one included, is the row after nextConsent — a step we have not built yet, and one we will have to ask for before ss.3–17 commence. The unsubscribe link is how you stop it today
Send you one follow-up email about a day after a mock interview is graded, if it is the only graded one on your account (normally your first) and you have not already come back; for the first 4 weeks, hold about half of the accounts that qualify back at random so the two groups can be compared; and record against your account when that interview was graded and either why it was not sent before a group was chosen, or which group it was in, whether it was sent and whether you were active in the 7 days after it was graded; and whether you unsubscribed (Section 2(p1))Help someone who has just sat their first mock interview carry on practising, once, and know whether that message helpsLegitimate interests: helping an existing user carry on practising, and knowing whether the message helps. This is not consent and we do not call it that — there is no switch you turned on. You have a right to object: use the one-click unsubscribe in the message, or write to support@careerverse.tech. Our own databases hold no per-account record of deliveries, opens or clicks; the per-recipient history our email provider keeps of every email, this one included, is the next rowConsent — a step we have not built yet, and one we will have to ask for before ss.3–17 commence. The unsubscribe link is how you stop it today
Track opens and clicks in every email we send — sign-in codes, account-action codes and security notices, payment-failed notices, expert-session and recruiter-review emails, mock-interview result notices, the weekly win prompt, the monthly growth digest, the daily reminder, the win-back message and the one mock-interview follow-up email — through an invisible tracking image and click-tracking links our email provider adds, which leave it a per-message, per-recipient history we can look up (Section 2(q))Know whether the emails we send arrive and are read, and catch problems delivering to the mail services our users rely onLegitimate interests: knowing whether the emails we send you reach you and work. This is not consent and we do not call it that — there is no switch you turned on. You have a right to object: set your mail client not to load images automatically and read the plain-text version, use the unsubscribe link where an email has one, or write to support@careerverse.tech. We cannot yet switch this tracking off for a single recipient, so for emails with no unsubscribe link, such as sign-in codes, those mail-client settings are the way to avoid it todayConsent — a step we have not built yet, and one we will have to ask for, or stop tracking these emails, before ss.3–17 commence. The routes in the previous column are how you object today
Publish our own videos to our YouTube channel, and once a day find recent public YouTube videos about careers, keeping their video IDs, channel IDs, titles and publish dates; titles may be sent to an AI provider to suggest a draft comment that a person reviews (Section 16)Promote CareerVerse on our own channel, confirm our uploads went live, and pick videos our team may watch or comment on by handLegitimate interests: promoting our own service, and taking part by hand in public conversations about careersThe Act does not apply to data a creator has themselves made publicly available (DPDP s.3(c)(ii)(A)); for publishing our own videos, and for anything a title says about someone other than the creator who posted it, nothing on the s.7 list squarely fits

Support, and the law

What we doWhyEU/UK GDPR basisIndia — DPDP ground (from May 2027)
Answer support requests, and handle in-product feedback reports including any screenshot you attach, and any AI answer you choose to reportHelp you, and fix what you reportPerformance of a contract if you have an account; otherwise legitimate interests in answering people who contact usDPDP s.7(a) — you contacted us for this
Meet legal, tax and regulatory duties, and respond to lawful requests, judgments and court ordersComply with the law we are subject toLegitimate interests in complying with the Indian law that governs us. Art. 6(1)(c) covers only obligations laid down by EU or UK law, so we do not claim it for our Indian duties; where an EU or UK obligation genuinely applies, Art. 6(1)(c)DPDP s.7(d) where Indian law requires us to disclose something to the State, and s.7(e) for a judgment or order. A duty simply to retain records is not squarely covered by either

Two legal systems, two different answers

The two right-hand columns differ because the two laws are not built the same way, and copying one across to the other would be inaccurate.

The EU and UK GDPR offer six lawful bases, two of which — performance of a contract, and legitimate interests — carry most of what a service like ours does.

India's DPDP Act offers only two kinds of ground: your consent (s.6), and a closed list of nine "certain legitimate uses" (s.7). That list is fixed. There is no contract-performance ground and no legitimate-interests ground in the DPDP Act at all — "legitimate uses" looks like the GDPR's "legitimate interests" but works differently, because there is no balancing test and nothing can be added to the list.

  • Where the India column says s.7(a), that is the ground for "the specified purpose for which you voluntarily provided your personal data" and in respect of which you have not told us you do not consent to that use. That second half is part of the ground itself: the data you handed us, used for the thing you handed it over for — and if you tell us you object to a particular use, that ground stops being available to us for it. Write to support@careerverse.tech.
  • Where it says s.7(d) or s.7(e), those are the grounds for a legal duty to disclose something to the State, and for complying with a judgment or order.
  • Where it says consent — a step we have not built yet, we mean it literally: when those provisions commence we will need your consent for that use, and the screen that asks for it does not exist today. We would rather say so than claim a consent we never asked you for.

What governs your data in India today

Most of the DPDP Act is not yet in force. The sections that set out lawful grounds, the notice we must give you, and your rights as a Data Principal (ss.3 to 17) commence eighteen months after the Government's commencement notification of 13 November 2025 — that is, in May 2027, except s.6(9) (below). The India column above therefore describes the position from that date. It is not a description of today. The one sub-section that commenced sooner, s.6(9), requires every consent manager to be registered with the Data Protection Board of India; it commenced one year after that notification, in November 2026, and we do not use a consent manager.

The Data Protection Board of India was established in law by that same notification, but as at the date of this policy no Chairperson or Members have been appointed, so it cannot yet hear anything. We are not going to point you at a redress route that does not yet function.

Until then, the Indian law that actually governs this is the Information Technology Act, 2000 — in particular s.43A — together with the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 ("the 2011 Rules"). Those survive precisely because the provision of the DPDP Act that removes them (s.44(2)) sits in the same deferred tranche and does not take effect until May 2027 either. Under those Rules:

  • We treat your mock-interview camera video and microphone audio as sensitive personal data.
  • We ask for your consent before any recording starts, on a screen that lists each item separately, and we use that data only for the purposes stated there. Rule 5(1) speaks of consent "in writing through letter or fax or email"; an in-product consent screen with a versioned record of what you agreed to is the accepted modern reading of that requirement, and it is the reading we rely on.
  • You can withdraw that consent at any time by writing to support@careerverse.tech, and you can delete any interview and its recording yourself. If you withdraw it, we will not be able to offer you recorded mock interviews.
  • We publish this policy, describe the security measures we take (Section 9), and provide a Grievance Officer (Section 12).

We are setting this out now rather than waiting, because it is the law that binds us today.

Security, and a gap we are not papering over

Three lines above — rate-limiting sign-in, moderating the Community and acting on reports, and keeping the Service secure — are things any service has to do. Under the GDPR they rest on our legitimate interests, which you can object to.

The DPDP Act's list of nine legitimate uses contains no general security or fraud-prevention ground. The one clause that mentions protecting against loss or liability applies to employers and their employees, which is not our relationship with you. We could have written "consent" in that column, but we do not ask you to consent to being rate-limited, and it would not be true. So we have written that nothing on the list squarely fits, and we will follow whatever rules the Central Government makes under s.40 of the DPDP Act, and any direction of the Data Protection Board that applies to us, before those sections commence.

Where we say "consent", here is the switch

Consent means nothing without a real way to refuse, so here is every place we rely on it and the control that goes with it. If a use is not on this list, consent is not what we rely on for it.

  • On our website: analytics, advertising measurement, and recording your sign-up source. One banner, one choice, covering all three together — accepting or declining applies to all of them, and there is no separate switch per purpose today. You can change it at any time from "Cookie preferences" in the site footer. Nothing loads and no such cookie is written until you accept.
  • In the app: advertising measurement. On an iPhone, Apple's tracking prompt; withdraw it in Settings > Privacy & Security > Tracking. Whether or not you allow tracking, while Send analytics and crash reports is on, the app tells Apple's own ad attribution that it has been opened and may tell it which steps you reached (Section 2(r)); the signed contents of Apple's report on it, Apple says, include no data about you or your phone. Your advertising ID is not read on an iPhone until you agree; without it, Google may still estimate in aggregate how our ads perform (Section 2(r)). On Android we do not rely on consent for it: the app measures our ads with your advertising ID unless you turn off the Ad measurement switch in Privacy and data, which is how you object to it (see the table above). The same holds for Meta, in our Android app from version 1.0.1, on every Android phone, Europe included: we do not rely on consent for it; once the app has shown you its short line about our partners, or once you turn on Meta ad measurement, it runs while Ad measurement and Send analytics and crash reports are on too, and you object to it by turning off any of the three in Privacy and data (Section 2(r)). From version 1.0.3 of our iPhone app, allowing tracking, in Apple's tracking prompt or later in Settings > Privacy & Security > Tracking, covers Meta too, and Meta ad measurement in Privacy and data turns Meta off alone; if the prompt you answered was the one our iPhone app showed before that version, which named only Google, Meta runs only once you also turn Meta ad measurement on.
  • In the app: PostHog product analytics, on a phone the app treats as being in Europe. The app, from version 1.0.1 on Android and 1.0.3 on an iPhone, asks on its own screen and sends PostHog nothing unless you say yes. Withdraw it with PostHog product analytics or Send analytics and crash reports in Privacy and data, which also asks PostHog to delete what it holds about you. On any other phone we do not rely on consent for it until 13 April 2027: the app runs it once it has shown you its short line about our partners in the form that says one of them links app use to your account, until you turn it off, which is how you object (see the table above).
  • Mock-interview recording, proctoring, event capture, and sending your audio to be transcribed. A consent screen before the interview starts, listing each item separately so you can see exactly what each one covers, and saying who receives your audio: it names AssemblyAI, our speech-to-text provider, and the backup that takes over when AssemblyAI cannot (your browser's vendor, or in the app your phone's own speech service: Apple, Google or your phone's maker). It also asks you to confirm you are 18 or older (Section 13). All of them are required for a recorded mock interview, so the interview cannot start until each is ticked. The screen is shown every time you start an interview, so you always tick the current wording rather than a remembered one, and we record which version of it you agreed to: the wording changed on 27 August 2026, when transcription moved from your browser to a provider acting for us, and again on 2 September 2026, when a second such provider was switched on, and again on 27 October 2026, when our website's screen began naming AssemblyAI and Google Cloud Text-to-Speech and stopped accepting a guardian's consent in place of being 18 or older. The app's screen has its own wording, which describes what the app does rather than what our website does, and it too names AssemblyAI and Google Cloud Text-to-Speech and asks you to confirm you are 18 or older; it too is shown every time you start an interview, and we record which version of the app's wording you agreed to.
  • The composure estimate. Off by default, and turned on inside the interview only if you want it. It is genuinely optional: everything else about the interview works identically without it. The app asks the same way, on its camera and microphone check before each interview, and it starts off every time.
  • The weekly win prompt and the monthly growth digest. Both are off unless you switch them on in your account settings — that switch is the consent — except where we resolved your sign-up as coming from India or the United States, in which case both may start on instead, and consent is not what we rely on for them (see Section 3). "May", because that also requires your browser to have told us your timezone at sign-up: where it did not, both stay off, so the only way to know your own setting is to look. We work the location out from the internet connection you signed up on, so it reflects where you were at that moment rather than where you live; if it put you on the wrong side of that line, switching them off in your account settings is the fix, and it sticks. Every one of these emails also carries a one-click unsubscribe link. No existing account was changed by this — nothing that was already off has been switched on.
  • The daily reminder. Off unless you turn it on, in your account settings or by choosing Yes, remind me the one time we offer it after your first win. We never turn it on for you, and no existing account was changed by it. Turn it off in your account settings or with the one-click link in any reminder.
  • Push notifications in the app. Each kind is off until you turn it on in the app. Turn any of them off in the app, or turn off notifications for CareerVerse in your phone's settings.

Withdrawing consent stops that processing going forward; it does not make what we already did unlawful. Where you withdraw a consent you previously gave, we also permanently delete the record of where your sign-up came from (Section 2(l)), so a later change of mind cannot bring it back. That holds even if we have changed what we ask you to consent to in the meantime: if we re-ask and you decline, we treat it as withdrawing the consent you gave before, not merely as a fresh "no".

Where we say "legitimate interests", you have a right to object

You have the right to object, on grounds relating to your particular situation, to processing we base on our legitimate interests, including profiling. We must then stop unless we can show compelling legitimate grounds that override your interests, rights and freedoms. We are setting this out separately from the other rights in Section 10 because the law requires us to bring it to your attention on its own. Where we ever process your data for direct marketing, you can object at any time with no reason needed and we must stop — that one is unconditional.

Your Career Twin is profiling in the GDPR's sense — automated processing that evaluates aspects of how you perform at work — and it now produces figures about you: a readiness figure against a target you accepted, a match percentage against a job description you paste, and a completeness figure for the career twin itself. It also gives each skill on your record a standing, which your graded results move. Section 4 sets out exactly what each one measures.

Profiling is not the same as a decision, and the difference is what matters here. Those figures and standings decide nothing: nothing is withheld from you because of them, no access, price or eligibility turns on them, and no third party — no employer, no recruiter — ever receives them. Our AI provider, which acts on our instructions, receives them only to write your own AI Mentor replies, and only while you let the mentor read your Career Twin (Section 4). They are shown to you, to help you choose what to work on. A lower standing because results did not pass is recorded only if you confirm it, and your next pass on that skill lifts it again. On that basis they do not engage the rules on solely automated decisions producing legal or similarly significant effects, and Section 10 sets out the rights that do apply. If that ever changes — if a figure of ours were to drive a decision about you, or travel to someone who makes one — this section changes with it, before it ships.

We give you more than the law requires here. Two of the three Career Twin lines above rest on performance of our contract, which carries no statutory objection right at all. We apply the per-source switches to all three anyway: under "What builds your record" in your account settings there is a switch for each source, you do not need to give a reason, and we do not weigh your objection against our own interests. Section 4 sets out exactly what turning one off deletes, and Section 10 notes that on a large account the deletion takes more than one step.

For anything else we base on legitimate interests, write to support@careerverse.tech and tell us what you object to. For PostHog in the app you object in the app itself, by turning off PostHog product analytics on each phone you use: the choice is kept on that phone, so writing to us cannot switch it off on your phone. You can also ask us how we weighed our interests against your rights for any of those lines, and we will tell you.

One thing those per-source switches are not. They let you stop processing that has already started. They are not a consent step, and we do not present them as one — Career Twin building is on unless you switch a source off. When the DPDP Act's main provisions commence that will no longer be enough, and we will ask you properly.

The one place we do ask first. Reading your interview transcripts is a separate, explicit permission that is off until you grant it, and withdrawable at any time (Section 4). That is a genuine consent step, and we keep it visibly apart from the switches above so the two are never mistaken for each other.

Who else is responsible alongside us

For three things described on this page, another company decides things about the data alongside us rather than simply acting on our instructions. We name them here because you should know who else holds a piece of this; the essence of each arrangement is set out in Section 6.

  • Google, for what its sign-in button collects and sends when it loads on our pages (Section 2(a1)).
  • Google, for the advertising measurement you consent to on our website (Section 2(k)), and for the advertising measurement in the app described in Section 2(r).
  • Meta, for what the Pixel collects and sends once you consent (Section 2(k)), and for what its kit in our app collects and sends (Section 2(r)).

There is also a third kind of relationship, which the two categories above do not describe. When Google hands us your display name and picture as you create an account (Section 2(a2)), Google is not acting on our instructions and is not deciding jointly with us — it is a separate company disclosing data to us under its own terms, and what happens to that data afterwards is our decision alone.

For everything else, our service providers act on our instructions, and the other companies Section 6 names receive data under their own terms — see Section 6 for who they are and what each receives.

4. AI processing, your Career Twin, and on-device proctoring

In short: To power AI features, we send the relevant content to a third-party AI provider (OpenAI, etc.) through our backend. Your Career Twin is built automatically from work you have already done here and from what you have put on your profile — you can switch off any source of it at any time, and doing so deletes what we derived from that source and does not undo. It gives each skill a standing that your graded results move, and those results never move it lower without your confirmation. It produces figures about how far your record reaches a target you have chosen; those standings and figures decide nothing, and leave the product only for our AI provider, to write your own AI Mentor replies while you let the mentor read your Career Twin. Reading your interview transcripts needs a separate permission you must grant. Face proctoring runs on your device, in your browser or in the app on your phone: no image from it leaves your device, and the events it notes go to our AI provider with your answers as advisory input.

AI features

This part was added to on 5 October 2026, to describe the switch that keeps the page you are on out of every mentor message, what the mentor does for you when you tap a button and which suggestion each tap came from, what your AI Mentor can read and how to switch it off, what more a page description can carry, including on your job tracker and competency ladder, what goes to our AI provider from a conversation-practice rehearsal, what a tailored résumé rewrite sends when you let it use your Wins, and asking for a question in plainer words during a mock interview.

When you use an AI feature, the relevant content is sent through our backend to a third-party AI provider (OpenAI, etc.) to generate the output — including your resume text, the job descriptions you provide, your interview answers and transcripts, short-answer submissions, system-design solutions, the projects you send for grading (your repository's code, your write-up and your screenshots), mentor-chat messages, what you type or say in a conversation-practice rehearsal, together with the journal entries and the career ladder you choose to ground it in, and — when you ask us to read one for your Career Twin — your achievement-journal entries and your profile headline or summary; and, for the AI Mentor, the sources you leave switched on in The Mentor sees (below). Only while your Use my Wins in rewrites switch is on (it is on the Resume tailor and on each job's Resume tab, and it starts off), we also send the title and the before/after figure (with its label) of up to your 30 most recent Wins (your achievement-journal entries), with your résumé when you ask for a tailored rewrite and again when we check that rewrite against your own sources. Never what you wrote under a Win, its employer, skills or evidence. We send only the content needed to provide the feature you requested. AI usage is metered as "CVTokens". OpenAI may process this data outside India, including in the United States (see Section 7).

What travels with a mentor message when you open the AI mentor from a page. So that the mentor can answer about what is in front of you, a short description of the page you are on is sent to the AI provider alongside your message. What that description holds depends on the page, and the most it ever carries is this: on a coding problem, the problem and the code in your editor at that moment; on a résumé analysis, the overall score we gave it, the job role and the skills we extracted from your résumé; on a tailored résumé, the fit score; on the community pages, what you searched for and the titles, text and top replies of the discussions on your screen, with the authors' names left out; on a course or a lesson, the titles of the course, the module and the lesson, and on a lesson also the text of the part you are reading; on a system-design brief, the brief and the requirements on your screen; on your design canvas, the brief's title, the names on its shapes and the arrows between them, with any label you gave an arrow (never a free-standing note you typed), and the time left; on the coding problem list, your filters, what you searched for and the problem titles on your screen. Some pages carry more, each part only while the switch in The Mentor sees (below) that governs it is on: on Home, your Career Twin (a skill on it included) and your journey page, the titles and minutes in today's plan and your next steps, your goal's role and date, the names of the skills still to prove, and a skill's name and what would move it, while your Career Twin switch is on, and your streak, level, XP and the names of your badges, while your Courses and practice switch is on, never a figure or a standing; on Mock interviews and an interview report, while your Interview results switch is on, the role, your scores and the verdict, which competencies you passed, each question with the written feedback on your answer, and what to work on and your strengths, never the recording, the transcript, composure or proctoring figures; on a system-design result, while your Courses and practice switch is on, the brief's title, your score, the verdict and the rubric scores; on your job tracker, while your Jobs switch is on, how many jobs you have open and up to 15 of them, each with its company, role and stage, the date to apply by and the day it last moved, never a closed or archived job, your notes, contacts, salary notes, the job post you pasted or a fit score; on your competency ladder, which only your This page switch governs, the ladder's name and its level names, the level you say you are at and the one you aim at, and each competency's name, the level you marked it at and how many pieces of proof you attached to it, never a note on a mark or which win, piece of graded work or link you attached; on your public page, only when it is your own and you open the mentor from it, what anyone can see on it: your headline and about text, the skills and languages you list, each job's title, company, dates and description, each school, degree, field of study and years, and each project's title, summary and skills, and, while your Courses and practice switch is on, the proof numbers, certificate titles, badge names and project scores the page shows; never your name, photo, links or page address (only whether you have them), where a job was, your activity map, or anything that is not on your public page. On your account page and your achievement journal it carries nothing but which page it is — no profile field, no journal entry. The skill labels on your Career Twin are added at the end of that description (never on your public page), and are the smallest part of it. Before it is sent, the description is capped in size and swept for email addresses, phone numbers and long runs of digits, which are replaced. You can turn this off for every message with the This page switch in Account › The Mentor sees, or leave the page out of any one message. With the switch off, no page description is sent and no audit record is made. The small cross on the page's label above the message box leaves the page out of your next message, so no description is sent with it and no audit record is made for it; the page is attached again automatically after that. Otherwise, what is sent is what you have on screen and in your editor when you send.

What your AI Mentor can read, and how to switch it off. When you send a message to the AI Mentor, it can read the following about you to write its reply. Each item has its own switch in Account › The Mentor sees. Every switch starts on, except Wins, which starts off:

  • Your Career Twin: your target and its date, your readiness range and how it has changed, the standing of each skill on your target, the skills you have not yet shown or that need more work, your ranked next steps and, if you have one, the next two days of your day plan. This includes the figures and standings described in "The figures it produces" below.
  • Your job applications: your most recently active applications (up to six; archived ones are left out): the company, the role, its stage, its deadline and when you last worked on it. Your résumé fit score is read only for an application whose own Let AI Mentor see this application's fit score setting is on. Your skill match for a job, when you ask from that application's own page, is read only while both your Career Twin and Jobs switches are on and that application's own setting is on. Never your notes, contacts, salary notes or the job post you pasted.
  • Your interview results: the role, score and result of your recent mock interviews, the coaching we wrote for you after the newest graded one (strengths, things to work on and next steps, which can quote a few of your own words), and which competencies you passed. Never your recordings, full transcripts, composure signal or integrity score.
  • Your course and practice progress: your courses and how far you are in each, how many problems, designs and projects you have passed, your streak, and your last few coding attempts with their result.
  • Your wins: only if you turn this switch on, and then only their titles and dates, never what you wrote under them.
  • This page: the description of the page you are on, as set out above.

We read these fresh each time you send a message, only for that message, and send them to our AI provider with it so the mentor can answer about your own work. We do not keep a copy of them for the mentor. The one record made is the one Section 8 describes when a readiness or job-match figure is given out, the same record opening your Career Twin makes. We never use them for anyone else's conversation. The mentor's replies and its running summary of your conversation are kept with the conversation and may repeat a figure. Switching a source off stops new reads from your next message. Replies the mentor has already written in a conversation, and its running summary of that conversation, stay in it: the summary and your most recent messages and replies in that conversation are sent with each later message in it, so the mentor can still mention something it read before you switched the source off. If we cannot check your switches for a message, we treat every switch as off for that message.

Your practice conversations are never read by the mentor. There is no switch that could turn them on.

Each time a page description is sent, we also keep an audit record of it, tied to your account. It holds the time it was made, how long the description was, a one-way code computed from it, and a copy of the description after that sweep. The sweep replaces only email addresses, phone numbers and long runs of digits, so the copy can still hold the code in your editor or the discussion text described above. It also notes which of a list of suspicious phrases the description contained, whether the mentor's reply came back normally, and a few technical details of how the request was handled. It does not hold the message you typed. We keep these records so that we can look into attempts to misuse the mentor and check that our safeguards against them work, and each is deleted about 90 days after it was made. They are not part of the copy of your data we put together when you ask for one, but while your account is open you can ask us for these records separately at support@careerverse.tech, and we will send you what they hold about you. If you want them, ask before you close your account. Closing your account or asking us to erase your data does not remove them sooner.

When the mentor does something for you. The mentor changes your data only when you tap a button that says what it will do: add a job to your tracker, save a win, or bookmark a problem, design brief or project. Each change is listed in Done for you with the time and the button you tapped, and can be undone for 7 days. Undo removes what the action created and clears its name from Done for you. If you have changed that item since, Undo leaves it alone and you can delete it where it lives. If the item was already saved before you tapped, Undo leaves your earlier copy in place. A Done for you row also keeps which suggestion it came from, where the button names one: a reference to the conversation's page, the time of the mentor's reply and the suggestion's place in it, never any words from the conversation. That lets a suggestion run only once, even from another tab or device. It stays after Undo, so an undone suggestion does not run again. Nothing the mentor does spends CVTokens, a mock interview or a résumé tailoring without its own tap that says so.

Asking for a question in plainer words during a mock interview. While a question is on screen in a mock interview, you can ask the mentor to put it in plainer words. We then send our AI provider only that question as it was shown to you, which can include your first name or refer back to an earlier answer, and your request. Never your answers, your recording, your transcript or what the question is marked against. The reworded question is shown only to you, uses one of your mentor messages, and leaves no mark on your grade or your report. Your request and the reworded question are kept as a mentor conversation of their own: it appears in your list of mentor conversations, where you can delete it on its own, it is included in a copy of your data, and it is deleted when you delete the interview or close your account.

Your Career Twin: automatic processing of your own activity

This subsection was added to this Policy on 15 September 2026, rewritten on 19 September 2026, when the feature it describes was released, added to on 21 September 2026, when combining two entries on the skill list became something that can happen without a person deciding it, and added to again on 22 September 2026, when you gained a control that takes off a lower standing you had confirmed, and when what happens to your record if we retire an entry from the skill list was set out here for the first time. It changed again on 25 September 2026, to say what the weekly win prompt may carry from your career twin, and on 30 September 2026, to say how we may match a skill you listed under a name we do not use, for your record only, and that switching Profile off deletes those matches. It changed again on 5 October 2026: it used to say that nothing you say in a practice conversation is recorded or readable by us, but a written record of each rehearsal is kept for its debrief until you delete it, and the sentence now says so; it now says that our AI provider receives your figures and standings to write your own AI Mentor replies, while you let the mentor read your Career Twin; and it now says what the daily reminder may carry from your career twin. Two sentences it carried about proctoring were wrong; the correction is below, under "One correction".

What we do. Your Career Twin (Section 2(n)) fills itself in. As you use CareerVerse, we match the work you complete against a list of skills and record that the work evidences them.

How that skill list is built, and why it is shared. The list is not fixed and not written by hand. When we meet a skill name we do not hold — in a job description you paste, in a résumé or profile you import, in a skill name you type, or in your own work — an AI normalises it into a canonical entry and may add it to the list automatically, so the product is not limited to a vocabulary someone wrote in advance. Our team reviews, merges and retires entries afterwards, not before.

Two consequences we would rather state than have you discover:

  • The list is shared across everyone. An entry created from one person's text becomes an entry every other user's work can be measured against. It holds skill names only — never who supplied a name, and nothing about you. A name on it can start from something a person typed, but only the skill name itself is kept, never the text around it.
  • What you supply can therefore affect what others see. The checks on that are the three stated here and no others: new entries are rate-limited; a proposed name that duplicates or closely resembles an entry we already hold is refused — a near-spelling of one, or the same words in a different order, or those words with one more added — and your text is then left unmatched rather than becoming a second name for one skill; and our team reviews, merges and retires them afterwards. We are not going to tell you that what comes back from that AI is drawn from a fixed, closed set of names, because it is not — that is exactly what "may add it to the list automatically" means.

Two entries that turn out to be the same skill can now be combined without a person deciding it. Because the list is built as described above rather than written by hand, the same skill arriving twice under two spellings is ordinary rather than rare, and leaving the pair apart splits the evidence for it in two. So where the same skill appears twice we may combine the entries automatically — and only where the entry being folded away was created automatically in the first place. An entry our team wrote is never combined away without our team doing it. Every automatic combination can be undone for 14 days, and so that it genuinely can be, we first take a copy of the records of yours the change would touch and keep it for that window (Section 8); if it is not undone in those 14 days it becomes permanent, exactly as a combination our team makes is permanent today. Nothing about you is added or taken away by it: your evidence moves from the entry that goes to the one that stays, and a standing is worked out again from what remains — the case named further down, under how a standing can fall without a question.

Matching a skill you listed, for your record only. A skill on your profile may be listed under a name we do not use — a short form, say, or another spelling. When you save the skills on your profile, or when a new account's skills are checked again once it is a week old (Section 8), our AI may match such a name to a skill on our list, or we may reuse the answer it gave earlier for the same name, whoever listed it then. When the answer is a match, we keep it against your account — your name for the skill and the skill on our list we matched it to — and count that skill on your record as one added automatically from your profile, without asking you first. That match is kept for you alone and counts on your record only. The answer about the name itself holds nothing about who listed it, and can be reused for anyone who lists the same name. Your matches are listed under "Skills we matched from your words" in your account settings. If one is wrong, choose Not what I meant beside it: the skill is withdrawn from your record the next time your record is worked out in full, unless you added or ticked it yourself or something else still supports it, and we keep your answer for as long as the match would have lasted, to stop the same match being made for you again in that time. While Profile is switched off, no match is kept for you, and switching Profile off deletes every match and every Not what I meant answer. A match lasts at most about 180 days (Section 8).

Reading your own words, only when you ask. You can also ask us to read a journal entry, or your profile headline or summary, and suggest skills from what it says. This never happens on its own: you choose the text and press the button, and the text is sent to our AI provider as described above. Anything it produces is marked an unconfirmed suggestion until you accept it, and an unconfirmed suggestion is never turned into prose about you — it is not used to draft, summarise or write anything. Nor does it count towards what your record shows you can evidence, and it does not change what we suggest you practise next: a guess nobody has checked should not be able to talk us out of recommending the very thing that would prove it. It starts counting only when you accept it, or when other evidence lands against the same skill — graded work you complete here, a role on your profile, or a journal entry. From then on it is no longer a guess, and it stops expiring (Section 8); if that other evidence later goes, the 180-day clock starts again.

A look back over your earlier work. So your career twin is not empty on day one, we also read work you completed before this feature existed. Today that covers your journal entries, mock interviews and coding submissions; we do not re-import the same history over and over.

Where other people's words can reach it, so you know. Most of what builds your career twin is your own activity. Two sources are not purely yours, and we say so plainly:

  • Imported documents — a résumé or an imported profile can contain text someone else wrote about you, such as a recommendation. We record who a sentence is about by its grammar rather than assuming that appearing in your document makes it your claim, and anything drawn from prose is marked an unconfirmed suggestion until you accept it.
  • A code host — when you type a username into the journal's recall panel, we look up merged pull requests that username authored in public repositories, and show you each one's title, repository, date and link. A title is text that may have been written by somebody other than you. There is no connection, no install and no stored credential: we hold nothing that could reach a private repository, and there is nothing for you to revoke, because there is nothing connected. The lookup files nothing on your record and keeps neither the username nor its results in our database: a lookup that completes counts once against your usage allowance, like any metered feature; a check of whether the username exists also counts toward a limit on how often your account can make such checks, like the other rate limits we keep to secure the Service (Section 2(h)); and when we check whether the username exists on the code host, our server holds the username and the answer in its memory only, for up to 10 minutes, so that a lookup repeated in that time does not ask again. What can reach your career twin is only a journal entry you wrote and filed from one of those results, and it is governed by the Achievement journal switch like any other entry. We never treat a username as proof of anything: you typed it, and we do not check that it is yours. Your employer never agreed to share your work with us, and you cannot agree on their behalf.

How to stop it — the control, and what it costs. Under "What builds your record" in your account settings there is a switch for each source. Turning one off does two things: we stop reading that source straight away, and we delete what we derived from it — the links, the supporting entries, the passed or not-passed results we kept for its graded attempts, and any notes or suggestions that came from it. Its attempts also stop counting in any decision about a lower standing: a lower standing you confirmed or declined stops citing them, and is deleted once fewer than three pieces of graded work remain behind it. Then we withdraw any skill we had worked out that nothing else still supports. Two things correctly stay: a skill other work still evidences, and a skill you confirmed yourself — that one is your statement rather than ours, so it is yours to remove, not ours.

That deletion is permanent. Turning the source back on later starts again from your new work only; it does not bring back what was removed, including anything we had quoted from your own words. One honest exception: if you turn Profile back on, your work-history entries and the skills listed on your profile reappear — not restored from a copy, but simply re-read from your profile, which still says what it said. Anything we quoted from your headline or summary does not come back, and nor does a skill that counted only because we had matched a name you listed to a skill on our list (above): switching Profile off deleted that match, so that skill comes back only if we match the name again later, for example when you next save the skills on your profile.

Your actual work is never deleted by this. Your journal entries, submissions, interviews and profile stay exactly as they are; only what we made of them is removed. And switching a source off never restricts what you can do — adding, confirming, correcting or removing an entry yourself is your statement, not ours, and is never blocked.

You can correct it yourself, item by item. On the Career Twin page you can remove any skill, detach any piece of evidence from a skill it was linked to, and decide whether a lower standing we propose is recorded. Removing a skill is permanent for that item — a later automatic pass cannot quietly bring it back. Where a model has written a short factual note about one of your sessions, you can mark it wrong, which takes it out of your record immediately, with nobody reviewing that decision. Where two things you have told us appear to disagree, you decide: keep one, or say both are true, which keeps both and closes the question. In either case you can also add your own written comment, which is stored with the item, is never sent to any AI provider, and is included if you ask for a copy of your data.

Each skill's standing, and how it moves. Every skill on your record — one you added or ticked yourself, or one your work evidences — has a standing: one of four named steps, which we show beside the graded results behind it. The four are Not shown yet, Shown, Shown consistently and Working on it. A skill starts at Not shown yet, and a skill we first meet through graded work you did here is added at the step that result earns, never below the starting step, even when that result did not pass. Moving up is automatic: one passed piece of graded work puts a skill on Shown, and three put it on Shown consistently. Each piece of graded work counts once however many times you attempt it, and it counts as passed if any attempt passed — a later attempt that does not pass never undoes that. Whether an attempt passed is decided by the same pass rule the page that graded it uses.

We never lower a standing because of results that did not pass unless you confirm it. If three different pieces of graded work on a skill have not passed within the last 90 days, all of them since your last pass on it, we show you those attempts and ask whether to record the skill at Working on it. No lower standing is recorded unless you confirm. If you decline, the skill stays exactly where it was — and we keep your answer, so that we do not ask you again about those same attempts; we ask again only if a different piece of graded work on that skill does not pass. A lower standing you confirmed is not a mark you have to live with, and you can take it back yourself: the skill's own row on your Career Twin page carries a control that takes it straight off, with nothing to do first and nothing to delete — where that skill stands then follows your graded work again, and we will not ask you about that same work again. It also lifts on your next pass on the skill, and it goes altogether if you remove the skill, or delete, detach or switch off the work it cites.

A standing can still fall without a question, when the evidence behind it goes. That happens when you remove a skill, detach evidence from it, or delete the work itself (a mock interview, for instance); when you turn a source off (above); when we correct which skill a piece of our own content evidences — which can take evidence away from a skill you confirmed; when we merge two entries on the skill list that turn out to be the same skill; or when we retire an entry from that list. None of those records anything against you: the standing is simply worked out again from what remains. Evidence growing old never lowers a standing.

Retiring an entry goes further than the rest of that list, so we set it out on its own. Our team retires an entry when it should never have been on the list at all — most often because it means the wrong thing — and a retirement is not a merge: there is no other entry for it to fold into, so nothing moves across. From then on nothing new is ever worked out against it. The next time your record is worked out — and on a large account that can take more than one pass, because each pass walks only part of your work — a skill of yours that we had worked out and that named the retired entry is withdrawn from your record, without your doing anything, and without our asking you first.

Two kinds of entry are left where they are, and only one of them is yours. A skill you added or ticked yourself is left alone: that one is your statement rather than ours. And a skill we only ever guessed from your own words and you never confirmed is left alone too — that one is our guess about you rather than your statement, nothing withdraws it, and it stays on your record naming the retired entry until it expires or you remove it yourself on your Career Twin page. We would rather say that than let you assume anything still there is something you put there.

Nothing else of yours moves — your work, your journal entries and the evidence behind your other skills all stay exactly as they are, and nothing is recorded against you. A target you have set is not edited either: it still asks for the skills it asked for. But if the retired entry is one of them, or if a withdrawn skill was counting towards it, the figure showing how far your record reaches that target goes down, and where the retired entry itself is on the target it can never be evidenced again, so that part of the figure does not come back. A retirement cannot be undone. Unlike an automatic combination it has no 14-day window: there is no before-and-after copy taken at the moment it runs, and nothing to put the entry back from. What does stay is the entry itself — kept on file, marked as withdrawn, with the date we withdrew it and the reason — and because it is still on file, it is included in a copy of your data if you ask for one, and nothing removes it with the passage of time. It stays withdrawn: the retired name cannot be evidenced again, so a skill that leaves your record this way does not come back on its own.

Mock interviews count per competency. An interview can move the standing of each competency it scores that matches a skill on our list, one competency at a time. A competency counts as passed when it averages 6 or more out of 10 across the answers that scored it, and as not passed below that. Answers where we captured no words at all are left out, so an answer we never heard does not count against you; an answer we captured only in part is scored on what we captured. Interviews graded before 07:23:01 UTC on 24 August 2026 stay on your record as practice but carry no passed or not-passed result at all, so they never move a standing.

The figures it produces, and what they mean. Your Career Twin produces three numbers, and we describe them exactly rather than leaving you to guess:

  • a readiness figure against a target you chose and accepted — how far the skills on your record reach that target, with each skill counted by its standing, so a skill on a higher step counts for more. A suggestion counts for nothing until you accept it or other evidence lands against it, and we show no figure at all until at least three pieces of graded work stand behind the target; below that we tell you what would help instead;
  • a match percentage when you give us a job description — the same measurement against the skills that description asks for;
  • a completeness figure for the career twin itself — how much of what we know how to hold, we hold.

These figures and standings measure our evidence about your work, one skill at a time. None of them is a single rating of you as a person, and none predicts what any employer will decide. A standing reflects the graded work you have done here on that one skill, and any lower step you confirmed. A readiness figure is lower when fewer of the target's skills are on your record, or when little graded work stands behind them — which is often a statement about how much you have done here rather than about what you can do. We say so on the page, and we tell you to apply anyway when the role is right.

The figures and standings are automated, and we do not pretend otherwise. But they decide nothing: nothing is withheld from you because of them, no access or price changes, and no employer, recruiter or other person sees them. The one service that receives them is our AI provider, and only to write your own mentor replies while your Career Twin switch is on (Section 4). They exist to show you where to put your effort. You can dispute or remove any evidence behind them at any time (below), which can change them, and you decide whether a lower standing is ever recorded (above).

A job description you paste, and the skills you take from it. Against an application, you can have a job description read into a proposed list of skills — that reading is a paid feature and is metered — or you can set the list yourself, which is free, and the match figure works the same either way. The list you accept is stored beside that job description, on that application, and is deleted with the application, exactly as the description itself is. You can also remove the list on its own at any time, which stops us measuring your record against it and leaves the application untouched. The record that a figure was shown to you (Section 8) keeps which application and which version of the description it was measured against — never the text of the description.

We do not send your Career Twin, any of these figures, or any skill's standing to employers, recruiters, or anyone else. The one exception is our AI provider, which receives them only to write your own AI Mentor replies, and only while your Career Twin switch is on. They are blocked at the source from every place they could leak: they are stripped from promotion packets and review documents you share with a manager, they are never part of a recruiter review you ask for, they never appear in a résumé we generate for you, on your public profile or behind any share link, and no figure or standing is ever included in any email we send. Two emails may carry part of your career twin. The weekly win prompt may name one skill on your target that your work that week included and one skill your career twin suggests you build next, by name only and never with a figure, a count, a standing or the role you are aiming for; or, if you have not set a target or not finished it, it may ask you to; and the daily reminder, if you turn it on, may name one free next step from the ranked next steps on your career twin, by its title only (Section 2(o)). Standings are never sent to our AI provider to draft a résumé or to prepare an interview. They are sent to it for one purpose: to write your own AI Mentor replies while your Career Twin switch is on (Section 4). One qualification, so the sentence is exact: if you open the AI mentor while looking at a page, the skill labels on your career twin are added to the end of the description of that page which goes to our AI provider, so the mentor can answer usefully — labels only, never your evidence, your figures, your standings, your notes or your comments. The labels are the smallest part of what is sent, and the rest of it — which on some pages includes your own code or a score we gave you — is set out in full at the top of this section rather than left for you to infer from this sentence. With your Career Twin switch on, the mentor also receives your figures and standings as Section 4 describes. Your evidence items, notes and comments are never sent. A standing is not a stored value at all: we work each one out afresh from the evidence in front of us every time we show it to you. Your own copy of your data (Section 10) therefore carries what a standing is worked out from rather than the standing itself — every graded attempt and whether it passed, every lower-standing decision you made and the attempts it cited, and, on each record of a figure we showed you, the standings that figure counted.

What is excluded from it by design, and what changed. Mock-interview video and audio recordings, the composure signal and any integrity score are never used to build your Career Twin and cannot become part of it. Practice conversations are excluded permanently — nothing you say in one is ever read into your Career Twin, indexed, read by the AI mentor or shown to anyone else, and that is a property of how it is built rather than a promise we keep by choice. Your voice is never recorded. A written record of each rehearsal is saved for your debrief until you delete it, and if you use Speak, the spoken versions of the other side's lines are kept as Section 8 describes.

One correction, because we published the opposite and would rather name it than quietly delete it. From 15 September 2026 this page said that proctoring events — the on-device signals described below — had become one of the sources that build your career twin, and that they had their own switch under "What builds your record". Neither was true. There is no proctoring switch, proctoring is not one of the sources listed there, and since your career twin is built from the sources in that list, it is not built from your proctoring events. The integrity score derived from them stays excluded too, as the paragraph above says. A control we told you about and you never had is worth correcting out loud.

Interview transcripts are different, and are off unless you turn them on. What you said in a mock interview is more personal than the grade you were given for it, so we do not fold it in with everything else: reading your transcripts to work out skills requires a separate, explicit permission that you can withdraw at any time, and it is off until you give it. Without it, interviews still contribute — through the competency scores the grading already produced, judged per competency as described above, not through your words.

Legal bases. Building and showing your Career Twin is performance of our contract with you (GDPR); the look back over earlier work, and maintaining the skill list itself, rest on our legitimate interests in making the feature useful from the first visit. Under the DPDP Act, the grounds are the per-purpose ones set out in Section 3, and they are deliberately not all the same.

On permissions, exactly. For the ordinary sources we do not ask for a separate Career Twin permission — the per-source switches are how you stop that processing, and they are switches you turn off, not ones you must turn on. One source is the exception: reading your interview transcripts is a separate, explicit permission that is off until you grant it and that you can withdraw at any time. We keep the two apart on purpose, so that "on unless you stop it" and "off unless you ask for it" never get confused.

Whichever basis applies, you get the same per-source control — you do not need to give a reason, and we act on it rather than weighing it against our own interests. For the parts that rest on our contract with you, that is more than the law requires: there is no statutory right to object to contract-based processing at all.

On-device proctoring

On-device proctoring (privacy by design). Mock-interview face/attention detection runs entirely on your device — in your browser on our website, and on your phone in the app — using an on-device vision library (Google MediaPipe, etc.). The detailed facial-landmark data never leaves your device and is never sent to us. Only summarised, derived events (such as "face lost" or "gaze away", sometimes with a short reading such as how far your head turned) and their timestamps are transmitted to and stored on our backend, and our AI provider (OpenAI) receives them with your answers as advisory input to grading. Sending them to our AI provider is part of grading the interview you asked for, while the face analysis that notes the face events runs only with the consent you give before the interview starts (Section 3). The face check's readings are the number of faces seen, how far your head turned, how open your eyes were and how far your eyes looked aside, and, in your browser, the level below which it counts your eyes as closed, worked out from how open your eyes normally look or else set at a fixed level. On a device too slow for the check, an event can instead say that it slowed down, with how long it took to check one picture, or switched off. On your phone, the vision library sends Google statistics about how it ran (such as timings and the app and device version), never an image or a reading.

In the app, the face check runs on your phone. In an interview you start in the app under its current consent wording, the app checks the camera's picture on your phone, up to twice a second, for whether your face is in view, whether more than one face is, and whether your head is turned away or your eyes are closed or looking aside. On the camera and microphone check it also learns how open your eyes normally look, so that holding a phone is not mistaken for closed eyes; nothing from the check is sent. No image or facial-landmark data from the face check leaves your phone; the interview's recording is uploaded separately, under its own consent. The app also notes that you left the app or locked your phone, that something such as a call came over the app or took its sound, or that the camera or microphone stopped. Only the events from while you are answering are sent: they wait on your phone, timed against the recording, and are sent to us only with the finished interview. If you turn on the optional composure estimate on the check, the app works it out on your phone too and sends only its summary figures, which we never use in grading or send to our AI provider. An interview started on our website, or in the app under its earlier wording, runs no face check in the app.

Turning your spoken answers into text, and the interviewer's voice

This is not on-device processing, and it is set out separately for that reason. Until 27 August 2026 answer transcription was done by your browser and this paragraph sat under the heading above. It no longer belongs there.

Speech-to-text. Your mock-interview answers are graded from a transcript, not from the recording, so your speech has to be turned into text. One provider does that for us: AssemblyAI, a specialist speech-to-text provider that processes the audio in the European Union. The consent screen you tick before each mock interview names AssemblyAI too, on our website and in the app. It acts as our processor and returns the text to your browser as you speak. Where it cannot run for a given answer, your own browser transcribes instead (in the app, your phone's own speech service) — a different recipient, described further down this section.

A second provider used to share this work, and no longer does. Until 3 September 2026 an answer could instead be transcribed by Amazon Web Services (Amazon Transcribe), which we called in the India region, and our server decided per answer which of the two handled it. We retired that arrangement: no mock-interview audio is sent to Amazon Transcribe any more, and the two admissions this page owed for that path — that we could not tell you the audio stayed in India, and that we could not tell you it was never used to improve that provider's own services — came off the page with it. AWS is still the provider that hosts the rest of the Service and stores your recordings, in India (Section 6); it no longer turns them into text.

Two things we are not telling you about your answer audio, because we cannot stand behind them. We are not telling you that this audio stays in India: the provider above transcribes it in the European Union, deliberately and on every session it handles, and where your browser transcribes instead your audio goes to your browser's vendor, in whichever country that vendor chooses. And on that fallback path we cannot tell you that your voice is never used to improve someone else's service — that is the browser vendor's decision, under its policies rather than ours. What we can tell you, on every path here, is what we do with it: we do not sell it, we do not show it to other users, and we do not use it to train our own models.

The specialist provider is switched on, and we named it here before it carried anything. The version of this policy published on 1 September 2026 described AssemblyAI in the conditional, because at that point no session had gone to it. That is no longer the conditional: your answer audio is sent to AssemblyAI on every session our server routes there, and it is transcribed in the European Union. It receives the audio of your spoken answers, and, so that it can recognise the words your interview is most likely to contain, a short list of names: your first name, the skills listed on your profile, and the role and the skills the interview is built around. When a mock interview is built from a job post you pasted, that role and those skills are the ones the post names, in its own words, and your profile's are used for them only where the post names none; the rest of the post is never sent. It receives nothing else with your answers — not your recording, not the rest of your profile, not your resume, and not anything else you type. Until 5 October 2026 this paragraph said it received your audio and nothing else; it has received that list of names with the audio since we switched it on, and this is the correction.

The microphone test. Before your first question you can test your microphone: one sentence you say is sent to the same speech-to-text provider and turned into text so you can see it works; it is shown only to you and is not saved or graded. If none of your answers in an interview come through as words, you can run the test once more during that interview. That sentence is turned into text only to show you and is never graded, but because the interview is being recorded, it is part of that interview's recording and, whenever we keep that recording, is kept and deleted with it. In the app, if no test has run for that interview since the app was last started, the camera and microphone check before you begin starts one by itself once your microphone hears you, unless a screen reader is on, when it waits for you to start it; it never starts one while the app is asking whether you want to begin without a test.

That is a transfer out of India, and we are not going to soften it. Everything else about the Service runs in India (Section 6). We pin the European region rather than letting the session be routed to whichever one is nearest, so it is a named place rather than an unknown one — but a named place outside India is still a cross-border transfer, and Section 7 sets out what we rely on for it.

What we can promise about it. Our AssemblyAI account has been opted out of AssemblyAI's model improvement program since we began using AssemblyAI. So AssemblyAI does not use the audio we stream to it, or the transcripts it makes from that audio, to train its models. On keeping them, AssemblyAI says that for an account opted out of model training, as ours is, it offers zero data retention of the audio and transcripts of its streaming service, the one we use. AssemblyAI says it still stores certain information about each transcript for its logging and billing. This promise covers AssemblyAI alone, not the browser or phone backup described below. If our account ever stops being opted out, this paragraph changes the same day and the date at the top moves.

If our own speech-to-text is unavailable or slow, your browser does it instead. Your browser's built-in speech recognition is kept as a fallback, and in some browsers (notably Chrome) it sends your audio to the browser vendor (Google), under that vendor's control and policies rather than ours. That path is used when the provider above cannot run for a given answer — for example on an unsupported browser, or when a limit or an outage means we do not open a stream. Your browser also stands in when our live connection to that provider is slow to connect, or stops working, during an answer. While it does, our speech-to-text provider may still receive the same answer audio: we keep trying to reconnect in the background, a connection that comes through is sent what you said while it was not working (up to the last 30 seconds), and its text then replaces your browser's for the stretch it covers. You are not told which path a given answer took, because there is nothing you can do about it mid-interview; both are described here so that neither is a surprise.

In the app, your phone's own speech service is the backup. In the app, the backup is not a browser but your phone's own speech service (Apple, Google or your phone's maker): Apple's speech recognition on an iPhone, and on an Android phone the speech recognition service the phone is set to use. The app lets it work over the network, so it may send the audio of your answer to Apple, Google or your phone's maker, under their control and policies rather than ours. The app uses it only for an answer our own speech-to-text cannot take: when our server tells the app not to open a stream, for example because of a limit or an outage; when the connection to our provider fails twice in a row, whether it cannot be opened or it breaks, or fails once in a way that cannot be retried; or when the app cannot get from your microphone the sound our provider needs. A slow connection on its own does not hand an answer over. Once your phone's service takes an answer, it hears the rest of that answer, and our provider is not sent it. A later answer can go back to our provider, but after some of the cases above, such as our server's decision or a failure that cannot be retried, your phone's service can take every later answer in that interview. As on the browser path, we cannot tell you where Apple, Google or your phone's maker process that audio, or that they never use it to improve their own services. On an iPhone, the app asks to use speech recognition when you agree to a mock interview's consent screen; if you say no, the interview still runs, without this backup. Android asks no separate question: the backup uses the microphone you have already allowed. The microphone test never uses your phone's speech service.

The interviewer's voice. Each question is read aloud in a synthetic voice produced by Google Cloud Text-to-Speech. We send it the text of the question — which is generated from your profile, your job description and your previous answers — and the text of the interviewer's greeting and sign-off, which use your first name, and it returns audio. Your own voice and your own recording are never sent to it. We keep each spoken question as a sound file (Section 8). Where that synthesis is unavailable, your browser's own built-in voice reads the question, greeting or sign-off instead; in some browsers that voice is made by the browser's maker from the text it reads, which can include your first name, under its policies rather than ours. In the app, your phone's own voice reads the question, greeting or sign-off instead. The app prefers a voice that works on the phone itself, but it cannot always tell which voices do, so the text it reads may be sent to the company that provides your phone's voice (such as Apple, Google or your phone's maker), under its policies rather than ours. This was previously not described here at all; it is, as of 27 August 2026, and conversation practice, the demo on our home page and the browser's own voice were added on 5 October 2026.

Conversation practice works differently. If you choose Speak in conversation practice, your browser's own speech recognition turns what you say into text in the message box, where you can correct it, and only that text, and how long you spoke, is sent to us when you send your turn. We never receive or record your voice there. As with the fallback above, in some browsers that recognition sends your audio to the browser's maker, under its policies rather than ours. In Speak, each line the other side says is read aloud by the same speech-synthesis provider that reads interview questions. We send it the text of that line, which can repeat or answer what you said and mention the work you chose to ground the rehearsal in; your own voice is never sent to it, and we keep the spoken line as a sound file (Section 8). Where that provider is unavailable, your browser's own voice reads the line instead, and in some browsers that means the browser's maker receives the text of the line. If you choose Type, no voice is involved at all. In the app, conversation practice turns what you say into text on your phone itself, so your voice never leaves your phone (Section 2(r)), and a line our speech-synthesis provider cannot voice is not read aloud. The demo on our home page works the same way when you choose Speak: your browser's own recognition writes what you say into the answer box, with the same caveat about the browser's maker. Nothing you say or type in the demo is sent to us (Section 2(m1)).

On-device speech detection

Hands-free answering in mock interviews on our website. On a computer, a speech-detection model runs entirely in your browser on your microphone audio, to tell when you have stopped talking and, in browsers where you can interrupt the interviewer by speaking and unless you switch that off, when you start talking over the interviewer. We serve the model from our own website. It produces only readings of whether someone seems to be speaking and how loud the sound is; nothing it looks at is sent to us or anyone else for this purpose. It runs in every interview where your browser can use it, whatever your hands-free settings, including while the interviewer is speaking, so that the figures in Section 2(f) can be measured. Where it cannot run, such as on a phone or tablet, the same may instead be judged from your words as they are turned into text and from your microphone's sound level. Your answers are still recorded and transcribed as described above. Nothing you say while the interviewer is speaking is added to your answer.

5. Cookies and local storage

In short: Three essential sign-in cookies — one keeps you signed in, one lasts 15 minutes while you sign in with an emailed code, and one lasts ten minutes while Open in my browser carries your sign-in to your normal browser — one that records your cookie choice, one that holds your browser's time zone so our pages can show you dates and times in it, plus one set by Google's sign-in button. Analytics cookies and browser storage (Google Analytics and PostHog), advertising-measurement cookies (Google Ads and Meta Pixel), and two that record which channel or campaign brought you here, only if you consent. We also set, without asking, a cookie that holds only the codes of our campaign links your browser has opened, so we count each browser once; it is never linked to your account. Some drafts live only in your browser until you save; code-editor drafts are also saved to your account. The app uses your phone's storage instead of cookies: your sign-in in its secure storage, and settings and unsent drafts in the app's own storage, which your phone's backup can include (Section 2(r)).

This section was added to on 28 September 2026, to describe the campaign-link cookie; and on 5 October 2026, to say which drafts are saved to your account, and where your theme is kept; and on 6 October 2026, to describe the time-zone cookie; and on 7 October 2026, to say that Google Ads measurement includes a sign-up or trial start made shortly before you accepted; and on 27 October 2026, to describe what the CareerVerse app keeps on your phone.

  • Session cookie (cv_session). A strictly necessary, HttpOnly cookie that keeps you signed in. It is set with SameSite=Lax, marked Secure in production, contains your email and an authentication token, and expires automatically. It is not used for tracking or advertising.
  • Sign-in link cookie (cv_signin). A strictly necessary, HttpOnly cookie we set when you ask for a sign-in code on our website, so that the code, and the sign-in button that may come with it in the email, work only in the browser where you asked for them. It is named __Host-cv_signin in production, set with SameSite=Lax, marked Secure in production, and holds a random value, the email address you are signing in with and, if you were on your way to a particular page, that page. It expires 15 minutes after your latest code request and is deleted once you sign in with the code or the button. It is not used for tracking or advertising.
  • Sign-in hand-off cookie (cv_handoff). A strictly necessary, HttpOnly cookie we set when you open CareerVerse from Open in my browser in an app's built-in browser. It is named __Host-cv_handoff in production, set with SameSite=Strict, marked Secure in production, and holds the one-time sign-in link and the interview page it opens. It expires after ten minutes and is deleted sooner once you press Continue, or once we find the link cannot be used or is no longer needed. It is not used for tracking or advertising.
  • Google sign-in cookie (g_state). Drawing the "Continue with Google" button causes Google's sign-in code to set a first-party g_state cookie on our domain. Google uses it to remember sign-in-prompt state, and it contains a randomly generated identifier for your browser. Because that button is on our home page, this is set for visitors who never use it and never sign in. We treat it as necessary to offering sign-in rather than as analytics or advertising, so it is not covered by the consent banner — see Section 2(a1) — but we list it here so you know it is there. It is not used by us for tracking or advertising, and we do not read it. You can clear it like any other cookie in your browser settings.
  • Time-zone cookie (cv_tz). So that our pages can show dates and times in your own time zone from the moment they load, they have your browser store its time-zone name (for example America/New_York) in a first-party cookie, which our server reads when it draws a page for you. It is set on every visit, whether or not you are signed in. It holds only that name; we never store anything we read from it, never link it to your account, and never use it for tracking or advertising. It is separate from the time zone saved with your email reminder settings (Section 2(o)), which your browser reports to us on its own; this cookie never sets or changes that one. It is set with SameSite=Lax, marked Secure in production, and expires a year after your last visit (sooner in some browsers). We treat it as necessary to show you the Service as you expect, so it is not covered by the consent banner. If you delete or block it, our pages show times in India time for a moment and then switch to your own time zone; a deleted one is set again the next time your browser loads one of our pages in full, as when you open or reload one, but not always when you move from page to page within the site.
  • Campaign-link cookie (cv_go). We put links starting careerverse.tech/go/ in our own posts and campaigns. When a browser that is not signed in opens one, we set a first-party, HttpOnly cookie that remembers which of those links that browser has already opened, so that opening one again is not counted twice in how many people it reached. It holds only those link codes — the 20 most recent at most — and nothing about you. It is set with SameSite=Lax, marked Secure in production, and expires 90 days after the last campaign link it counted. We read it only at the moment such a link is opened, never store what it holds, and never link it to an account; it is not used for advertising, and it is not used to credit a sign-up to a link — that uses the sign-up source cookies below, and only if you consent. It is not covered by the consent banner: we rely on our legitimate interests in knowing how many people open our campaign links (Section 3). To object, delete it in your browser settings at any time — that makes no difference to using CareerVerse, though opening another of these links while signed out sets it again; to stop that too, block cookies for this site, which also stops you staying signed in. It is never read or set while you are signed in, and a browser without it is simply counted as new the next time it opens one of these links.
  • Browser local storage. Some features keep drafts and in-progress work locally in your browser for your convenience (for example, resume-builder and resume-tailoring drafts, application-workspace notes and interview progress markers). This data stays on your device unless and until you save or submit it. One draft goes further: what you write in the code editor on a coding problem is saved to your account as you work, so you can pick it up on another device, and a copy stays in your browser in case a save does not reach us (Section 8). Your theme (light, dark or automatic) is kept in your browser only.
  • On your phone (the app). The app keeps your sign-in in your phone's secure storage (the iPhone keychain, or Android's equivalent) instead of a cookie; your app lock and reminder settings on the phone; and unsent drafts in the app's own storage until you send or delete them. Signing out deletes the drafts, the sign-in, the app lock setting and your reminder settings. Your phone's own backup (iCloud, or Android's device backup) can include unsent drafts, depending on your backup settings. The app also keeps the identifiers that Google Analytics for Firebase and Sentry's software create for the installation (Section 2(r)). On Android it also keeps your Ad measurement choice and whether it has shown you its short line about ad measurement, and, while analytics are on, it reads your phone's advertising identifier once it has shown you that line, until you turn Ad measurement off (Section 2(r)). From version 1.0.1 that line is its short line about our partners, and the app also keeps whether, at a time you had not turned Meta ad measurement off, it has shown you each of that line's two forms (the one for phones it treats as being in Europe and the one for other phones), whether you turned Meta ad measurement on or off, and whether, the last time it set out to start Meta's kit, it was to ask Meta to limit its use of what it sends. Once Meta's kit has started, the kit keeps on your phone the identifier it created, its own settings, any events not yet sent, any Meta ad-click and campaign identifiers from a link that opened the app or from Google Play's note about where the app was installed from, and, when that note contains "fb" or "facebook", its copy of it (Section 2(r)); turning it off deletes only the events it saved to send later. Android's backup of the app's data can copy the rest to a reinstall or a new phone; your choices are not in that backup and stay on this phone (Section 2(r)). From version 1.0.1 on Android and 1.0.3 on an iPhone, for PostHog, the app also keeps on that phone, for each account signed in there, under a coded form of its email address and with its account ID, whether PostHog may run for it and why (your answer, your switch, or when the app's short line about our partners, in the form that says one of them links app use to your account, was shown before that sign-in or while it was signed in), whether the app may already have sent PostHog anything for it and whether a deletion it asked for is still owed; whether the phone has ever been treated as being in Europe; when you last turned off Send analytics and crash reports; and that its sign-in screen showed that line before anyone signed in, which counts for 15 minutes only and is deleted by the next sign-in there, by that screen closing with no sign-in code still waiting to be used or, failing those, when the app next starts after those 15 minutes; none of this is in Android's backup of the app's data, and an iPhone keeps it in its keychain in a form that never moves to another phone, though it can outlast removing the app. On an iPhone, Apple keeps your answer to its tracking prompt, and from version 1.0.3 the app keeps, in the same keychain form, whether you turned Meta ad measurement on or off, whether it has found Apple's prompt there not yet answered (so that the prompt you answer is its own, which names Meta) and whether, the last time it set out to start Meta's kit, it was to ask Meta to limit its use of what it sends, and, in its own storage, whether it has told Apple's own ad attribution that it has been opened. Once Meta's kit has started there, it keeps on your phone the identifier it created, its own settings, a record of how long the app was last open, a record of which steps you reached for Apple's ad attribution and any events not yet sent (Section 2(r)); turning it off deletes the events it had saved to send later and its record of how long the app was last open, and it keeps the rest until you remove the app; the phone's own backup (iCloud, or a computer's) can restore the kit's files, saved events included, and the app's note for Apple's ad attribution, to that phone or another.
  • Analytics cookies — Google Analytics (only with your consent). If you accept, Google Analytics (GA4) sets cookies to measure product usage — for example _ga and _ga_* (persistent, used to distinguish visitors). These are non-essential: GA is not loaded and none of these cookies are set unless you opt in, and you can withdraw consent at any time via "Cookie preferences" in the footer. They are not used for advertising.
  • Analytics cookies and browser storage — PostHog (only with your consent). If you accept, PostHog sets two first-party cookies: ph_<our project's public key>_posthog, which keeps a random identifier for your browser (and, while you are signed in, the pseudonymous id in Section 2(j)), and ph_<our project's public key>_posthog_cpm, which keeps a short code worked out from the first one, that PostHog uses when it reads it. Both last 365 days. PostHog also keeps entries whose names begin ph_ in your browser's storage. These are non-essential: PostHog is not loaded and none of them are set unless you opt in, and withdrawing consent via "Cookie preferences" in the footer removes them from that browser. They are not used for advertising.
  • Advertising-measurement cookies — Google Ads (only with your consent). If you accept, we store the Google click identifier from an ad you clicked in first-party cookies (for example cv_gclid) and load the Google Ads tag (which may set its own _gcl_* cookies), to attribute a later sign-up, trial, or purchase to that ad — including a sign-up or trial start made earlier in the same browsing session, shortly before you accepted (Section 2(k)). These are non-essential: none are set unless you opt in, and you can withdraw consent at any time via "Cookie preferences" in the footer. They measure our own ads' results and are not used to show you third-party ads on CareerVerse.
  • Advertising-measurement cookies — Meta Pixel (only with your consent). If you accept, Meta Pixel records page views and a standard event when a genuinely new account is created or a free trial is started — including one that happened earlier in the same browsing session, shortly before you accepted (Section 2(k)) — and may set/read Meta advertising cookies such as _fbp and _fbc to identify a browser and measure or optimise our Meta ad campaigns. _fbc holds the ad-click identifier that was on your link; where the Pixel cannot record it itself — because it only loads once you accept, by which time you may have moved on from the page you arrived on — we write that cookie for it when you accept, from the identifier your own link carried. Both are deleted when you withdraw consent. These are non-essential: the Pixel is not loaded and no Meta Pixel event is sent unless you opt in, and you can withdraw consent at any time via "Cookie preferences" in the footer. Meta may use this activity under its own privacy policy and your Meta advertising settings; we do not enable Advanced Matching or send your email to Meta in this implementation.
  • Sign-up source cookies (only with your consent). If you accept, we store how you reached us — channel, campaign, the linking domain, the landing page, and any advertising click identifier, and simply "direct" when you arrive with no marketing link at all — in two first-party cookies (cv_attr for your first visit and cv_attr_last for your most recent). They are read only by us, when you create an account, and are deleted when you withdraw consent. One further cookie (cv_consent) records the choice you made here; it is strictly necessary — without it we cannot tell whether you consented, and it is what stops the cookies above from ever being written. We also keep that choice on your account — what you chose, when, and which version of this notice you were shown — so that we can show what you agreed to. From 11 September 2026 we also read it back, for one purpose: if you are signed in on a device or browser where this cookie is missing, we put your own last answer into it instead of asking you the same question again. Only a decision you actually made is ever restored; a refusal is restored exactly as an acceptance is; a choice you have withdrawn is never restored; and if we cannot find a live answer of yours, or the one we find was made against an older version of this notice, you are simply asked again. Signing out clears this cookie from the browser.
  • We set no non-essential cookie (analytics, advertising, or sign-up source) without your consent, other than the campaign-link cookie above, and we do not use cookies to show you third-party ads on CareerVerse. If you consent to Meta Pixel, Meta may use the resulting activity under its own policy, including for ad personalisation.

6. How we share your data

In short: We share data with the service providers that help us run CareerVerse, and with the other companies named below, some of which receive it under their own terms. We never sell your data.

We do not sell your personal data. If you consent, we share limited advertising-measurement data with Google and Meta to measure and optimise our own advertising (Section 2(k)); Meta may use Pixel activity under its own policy, including for ad personalisation. From version 1.0.1 of our Android app, and from version 1.0.3 of our iPhone app once you allow tracking in Apple's prompt or later in your iPhone's Settings, Meta also receives the advertising-measurement data in Section 2(r), under the app's switches rather than our cookie banner, and may use it in the same way; on a phone the app treats as being in Europe, the app asks Meta not to use it to choose who sees ads, and whether and how Meta acts on that is for Meta to decide. We share data with the service providers below, and with the other companies this Section names, some of which receive it under their own terms (see the paragraph after the list):

  • Amazon Web Services (AWS) — cloud hosting, file storage (S3), and compute, in the ap-south-1 (Mumbai, India) region. Your data, including interview recordings, is stored on AWS. AWS also delivers every email we send — sign-in codes, account notices, the reminders in Section 2(o), the win-back message in Section 2(p), the mock-interview follow-up in Section 2(p1) and the rest listed in Section 2(q) — so it receives your email address, and the message itself, in order to send them. It adds open and click tracking to every one of them (Section 2(q), which also names the one link we tell it not to track): the tracking image is fetched from, and every tracked link redirects through, an AWS-operated host, which is where your network address and mail-client or browser information go when a copy is opened or a link in it is clicked. AWS keeps a per-message delivery and engagement history for each recipient, which we can look up, and it reports delivery, open and click totals back to us, with no address attached, across all our email and separately for the reminder emails (together with payment-failed notices, which go out the same way), for the win-back message and for the mock-interview follow-up. AWS does not transcribe your spoken mock-interview answers: it did until 3 September 2026, and that arrangement was retired (Section 4). Hosting, storage and mail delivery are what it does for us now, and the hosting and storage stay in that India region.
  • IPinfo — when a sign-in creates your account, the network address it came from, and nothing else about you, so that it can tell us the country, region, city, time zone and network that address belongs to (Section 2(a)). IPinfo hosts its service in the United States (Section 7).
  • AssemblyAI — in use. It receives the audio of your spoken mock-interview answers for every session our server routes to it, and returns the transcript your answers are graded from (Section 4), processing that audio in the European Union — a transfer outside India, see Section 7. Beside the audio it receives only the short list of names Section 4 describes — your first name, the skills listed on your profile, and the role and the skills the interview is built around, taken from a job post you pasted where there is one — and no other content: not your recording, not your resume, and not anything else you type. We use it under a paid plan, on an account opted out of its model improvement program since we began using it, so it does not use that audio or its transcripts to train its models, and AssemblyAI says it offers zero data retention of them for an account opted out as ours is (Section 4).
  • Google (Analytics for Firebase) — from the app, with no consent choice, until you turn it off there, the usage data, installation identifier, identifier for vendor on an iPhone, approximate location and any Premium purchase described in Section 2(r), which also says what may still reach Google while it is off. Google processes it under its terms and privacy policy, potentially outside India (including the United States). We do not send it your account ID, and we send your phone's advertising ID on an iPhone only if you agree and on Android unless you turn it off, for measuring our own ads (Section 2(r)), for which Google is jointly responsible with us (Section 3); ad personalisation stays off.
  • Sentry — from the app, until you turn them off there, the crash reports and the notes of each time the app is used described in Section 2(r), with the random installation identifier they carry, and the network address each one comes from, which our Sentry project is set not to store (though Sentry keeps the approximate location it works out from a report's address), outside India, in the United States.
  • Expo, Apple and Google (push delivery) — if you turn on a push notification in the app, Expo's push service receives your phone's push token and, when the app gets that token, a random identifier the app keeps on your phone, and then each notification's fixed sentence, link and label, which it passes with the token to Apple's push service (for an iPhone) or Google's Firebase Cloud Messaging (for Android) to deliver. Expo relays them for us, as our service provider; Apple's and Google's push services deliver them under their own terms. Each may process them outside India (including the United States).
  • Expo (app updates) — the app asks Expo's update service whether a newer version of its own code is ready, each time it starts and when you come back to it after some hours, and downloads it from there. Each request gives Expo your network address, basic device information, whether your phone is an iPhone or an Android phone, which version of the app and of its code your phone runs, any version of that code that recently failed to start on it, a random identifier the app keeps on your phone for these requests, and, if the app failed to start the last time, a short description of what went wrong. It receives nothing about your account and nothing you do in the app. Expo does this for us, as our service provider, potentially outside India (including the United States).
  • A person acting for us on recruiter reviews and expert calls — the resume on your profile when you ask for a recruiter review, and your booking details when you book an expert call (Section 2(s)).
  • The expert who takes your expert call — your name, your email address and the length and time you picked, so that you can be invited to the call, and the area and reason you chose and any note you added to your booking, so that the expert can prepare (Section 2(s)).
  • OpenAI — receives the content described in Section 4 to generate the AI outputs you request, and the written review a person makes of your resume when you ask for a recruiter review, to turn it into your report card (Section 2(s)).
  • Google (Sign-in) — on our website, a "Continue with Google" button appears on our home page, our sign-in screens and your account settings, and drawing it loads Google's sign-in script, so Google receives your IP address, basic device and browser information, the page address, and any Google cookies your browser already holds at that moment — on the home page this happens on page load, even if you never use the button. In the app, Google's sign-in receives nothing until you choose "Continue with Google"; then Google's own sign-in for apps receives what it needs to sign you in (Section 2(a1)). If you choose "Continue with Google", Google confirms your identity to us and sends us your email address, whether Google has verified it, a stable identifier for your Google Account, and — in most cases — your display name and a link to your profile picture (Section 2(a1)). If that request creates your account, our server then fetches that picture from Google's image servers, which tells Google the image was fetched and reveals our server's network address and the time; the image itself comes back to our storage in India (Section 2(a2)). Neither the sign-in nor that fetch is analytics or advertising, so neither is part of the optional cookie consent; Section 3 sets out what we rely on for each. Google processes this under its terms and privacy policy, potentially outside India (including the United States).
  • Apple (Sign in with Apple) — in our iPhone app, if you choose Sign in with Apple, Apple confirms your identity to us, and we exchange the one-time code Apple gives the app for a token that we keep, encrypted, only so that we can later ask Apple to end CareerVerse's access to your Apple Account, which we do when you stop using it in your account settings, when you delete your account, and when we delete it at your written request (Section 2(a1)). Apple processes this under its own terms and privacy policy, potentially outside India.
  • Google (Analytics) — only if you consent to analytics cookies, the pseudonymised usage and event data described in Section 2(j) are sent to Google, which provides the Google Analytics service and processes that data under Google's terms and privacy policy, potentially outside India (including the United States). GA4 does not store your IP address. If you do not opt in, no Google Analytics data is shared from our website; the app is different (Google (Analytics for Firebase), above).
  • PostHog — on our website only if you consent to analytics cookies, the usage data, named events, session replays and, while you are signed in, pseudonymous id described in Section 2(j); and from the app, version 1.0.1 or later on Android and 1.0.3 or later on an iPhone, the usage data and pseudonymous id described in Section 2(r), on a phone the app does not treat as being in Europe once the app has shown you its short line about our partners in the form that says one of them links app use to your account and until you turn it off, and on a phone it treats as being in Europe only with your yes. PostHog is our service provider, under its data processing agreement, and stores and processes this data in its cloud in the European Union (Germany). The companies PostHog uses for that cloud receive it too: Amazon Web Services, which stores it, in Germany; Modal Labs, for computing, in Germany; Wiz, for security monitoring, in Germany and France; and Cloudflare, whose worldwide network may carry it on its way (Section 7). PostHog may also have its own companies, Hiberly Ltd in the United Kingdom and PostHog GmbH in Germany, process it to provide its service. On our website, if you do not opt in, nothing is sent to PostHog; Section 2(r) says when the app sends.
  • Google (Ads) — only if you consent to advertising cookies, we send Google the click identifier and a hashed version of your email (Section 2(k)) to measure which of our ads lead to sign-ups, trials, and purchases. Google processes this under its terms and privacy policy, potentially outside India (including the United States). If you do not opt in, no Google Ads data is shared from our website. From the app, Google Ads receives, through Google Analytics, the sign-ups, first opens and purchases described in Section 2(r), to measure which of our ads lead to them: with your advertising ID on an iPhone only if you agree and on Android unless you turn it off, and otherwise only in Google's aggregate estimate (Section 2(r)).
  • Meta (Ads / Pixel) — only if you consent to advertising cookies, Meta receives the page-visit, browser/device, network, referrer, and Meta cookie/browser identifier signals described in Section 2(k), plus a standard event with an opaque server-issued event identifier when a new account is created or a free trial is started, to measure and optimise our ads. We do not enable Advanced Matching or send your email, CareerVerse user id, authentication method, plan, amount, or CareerVerse content to Meta in this implementation. Meta processes this under its privacy and cookie policies, potentially outside India (including the United States). If you do not opt in, Meta Pixel is not loaded and no Pixel event is shared.
  • Meta (in our Android app) — from version 1.0.1 of our Android app, once Section 2(r) allows it (never while Send analytics and crash reports, Ad measurement or Meta ad measurement is off, and never before the app has shown you its short line about our partners unless you turned on Meta ad measurement yourself), your phone's advertising ID, an identifier Meta's kit creates for the installation, the details of your phone and the app, your network address, when the app is installed and opened, when you sign up and when you start a trial or buy Premium, any Meta ad-click and campaign identifiers on a link that opened the app, and the other things Section 2(r) lists, to measure our ads and, from phones the app does not treat as being in Europe, to choose who sees them; Meta may also use them for its own purposes, including to personalise ads, under its own terms and privacy policy, potentially outside India (including the United States); on a phone the app treats as being in Europe, the app asks Meta not to use them to choose who sees ads. We send Meta no name, email address, account ID, price or anything you create.
  • Meta (in our iPhone app) — from version 1.0.3 of our iPhone app, only once you allow tracking in Apple's prompt or later in your iPhone's Settings and while Send analytics and crash reports and Meta ad measurement are on (Section 2(r)), your phone's advertising identifier, an identifier Meta's kit creates for the installation, the details of your phone and the app, your network address, when the app is installed and opened, how long it stays open and roughly how long since it was last open, when you sign up and when you start a trial or buy Premium, and the other things Section 2(r) lists, to measure our ads and, from phones the app does not treat as being in Europe, to choose who sees them; Meta may also use them for its own purposes, including to personalise ads, under its own terms and privacy policy, potentially outside India (including the United States); on a phone the app treats as being in Europe, the app asks Meta not to use them to choose who sees ads. We send Meta no name, email address, account ID, price or anything you create.
  • Payment processor (merchant of record) — if you buy a paid plan on our website, a third-party payment processor acts as the merchant of record: it collects your payment and receives your email and transaction/subscription data to bill you and issue any refund. It handles your card details directly; we do not receive or store your full card number (Section 2(i) says what we do receive, and Section 8 how long we keep it). See the billing and refund terms in our Terms of Service.
  • Apple (App Store) and Google (Google Play) — if you buy Premium in the app, the store you buy it in processes your payment and handles your card details under its own terms and privacy policy, and we never receive them. It receives from the app the random store-account token that ties the purchase to your account, and for an App Store purchase we may also send that token to Apple ourselves. We send the store the purchase's own identifiers to check the purchase and keep it up to date, and, when you delete your account, to turn off a Google Play renewal (Section 10). Whatever you choose about the app's advertising measurement, each store may also tell Google Ads how many installs and purchases our ads led to, without telling us who you are (Section 2(r)). Each store processes this under its own terms, potentially outside India (including the United States). See the billing and refund terms in our Terms of Service.
  • An outside profile-lookup service (LinkedIn import) — when you start an import and confirm the profile is your own, it receives from us the LinkedIn username you gave, and nothing else about you, to fetch that profile's public details, and returns them to us, potentially from outside India. It works under its own terms, not as our service provider. This is not a LinkedIn sign-in and does not use LinkedIn's own API. Only what you tick is saved (Section 2(g)).
  • Google (Cloud Text-to-Speech) — receives the text of each mock-interview question and of the interviewer's greeting and sign-off, which use your first name, and, when you choose Speak in conversation practice, the text of each line the other side says (which can repeat or answer what you said), and returns the synthetic voice that reads it aloud (Section 4). It does not receive your voice, your recording, or your transcript. Google processes this under its terms and privacy policy, potentially outside India (including the United States).
  • Browser speech vendor — as described in Section 4, your browser's built-in recognition transcribes a mock-interview answer when our own speech-to-text cannot run, and everything you say when you choose Speak in conversation practice or in the demo on our home page; and your browser's built-in voice reads a question, the interviewer's greeting or sign-off (which use your first name), or the other side's line, aloud when our own synthetic voice is unavailable. In some browsers either of these sends your audio, or the text being read, to the browser vendor (e.g. Google) under that vendor's own policies.
  • Apple, Google or your phone's maker (your phone's own speech service) — in the app, as described in Section 4, your phone's own speech recognition turns a mock-interview answer into text when our own speech-to-text cannot take it, and may send the audio of that answer to Apple, Google or your phone's maker under their own policies, potentially outside India. When our synthetic voice is unavailable, your phone's own voice reads the question, or the interviewer's greeting or sign-off (which use your first name), aloud instead, and may send its text to the company that provides that voice.
  • Google (MediaPipe) — in the app, the vision library behind the face check (Section 4), which the app starts only in a mock interview in which the face check runs, sends Google statistics about how it ran, such as when it started, how many times it was used and how long that took, with the app's name and version and details of your phone, such as its operating system version and, on Android, its model, language setting, country and network type. It never sends an image or a reading from your face, and nothing about your account, and there is no setting that turns it off. Google uses these statistics to measure, maintain and improve that library, under its own terms and privacy policy, potentially outside India (including the United States).
  • jsDelivr (a public content-delivery network) — our website loads the code editor, the Python runtime (Pyodide) and the face-check library from it, and the app loads the Python runtime when you run Python in a lesson (Section 2(r)). Each request gives jsDelivr your network address, basic browser or device information and the file requested, which for Python includes any package your code imports, and, from our website, which of our sites asked for it; it receives nothing about your account and never the code you write. jsDelivr serves these files to anyone under its own terms, potentially from outside India.
  • esm.sh (another public content-delivery network) — when the system-design canvas on our website needs a font for Chinese, Japanese or Korean characters or for some symbols, such as the rupee sign (₹), or cannot load one of its other fonts from our own site, your browser may fetch that font from esm.sh. Each request gives esm.sh your network address, basic browser information, the font file requested, which reflects the range of characters the canvas needed, and which of our sites asked for it; it receives nothing about your account and never your drawing. esm.sh serves these files to anyone under its own terms, potentially from outside India.
  • GitHub (a code host) — when you type a username into the journal's recall panel, our server sends GitHub that username and the dates you chose, to find the merged pull requests it authored in public repositories, and may ask GitHub whether the username exists (Section 4); and when you send a project for grading, our server downloads from GitHub the public repository at the link you gave, so that its code can be graded (Section 4). These requests come from our server, with no GitHub account or credential of ours or yours, so GitHub receives the username, the dates or the repository named and our server's network address, never yours, and nothing else about you or your account. GitHub answers these requests under its own terms, potentially from outside India.
  • Legal and safety — we may disclose data where required by law or legal process, or to protect the rights, safety, or security of our users, the public, or ASOasis.
  • Business transfers — if ASOasis is involved in a merger, acquisition, or sale of assets, data may be transferred as part of that transaction, subject to this Policy or a successor policy.

We require every service provider that processes your personal data for us to protect it to the same or an equal standard as this Policy, and to use it only to provide its service to us. Some companies named above receive data not as our service providers but under their own terms, as this Section and our Terms of Service say: the payment processor that acts as merchant of record on our website, the App Store and Google Play, Apple for Sign in with Apple, Apple's and Google's push services, Meta for its own use of Pixel activity and of what our app sends it, the outside profile-lookup service behind the LinkedIn import, the speech service of your browser or phone, Google for MediaPipe's usage statistics, jsDelivr, esm.sh and GitHub; and Google, for what its sign-in button sends as it loads, Google and Meta, for what their advertising tags collect, and Google and Meta, for the advertising measurement in the app described in Section 2(r), are each jointly responsible with us (Section 3). For those companies, their own privacy policies also apply to what they do with that data.

Who the app's line about partners means

From version 1.0.1, the partners our Android app's short line about our partners refers to are Google (Google Analytics for Firebase, and Google Ads for measuring our ads), Meta and Sentry, and, where the line says that one of them links app use to your account, PostHog, which is that one; each is described above and, for the app, in Section 2(r). Meta may also use what it gets for the ads it shows you; on a phone the app treats as being in Europe, the app asks Meta not to use it to choose who sees ads, and whether and how Meta acts on that is for Meta to decide. From version 1.0.3, the partners our iPhone app's shorter line refers to (Section 2(r)) are Google (Google Analytics for Firebase), Sentry and PostHog, which is the one that links app use to your account; on an iPhone, Google gets your advertising ID, and Meta's kit runs, only if you allow tracking in Apple's prompt or later in your iPhone's Settings. Google explains how it uses information from apps that use its services at policies.google.com/technologies/partner-sites, and how it processes the personal information it receives from them at business.safety.google/privacy.

7. International data transfers

In short: We host in India. If your data crosses borders, we use lawful safeguards.

Our primary infrastructure and stored data (including interview recordings) are hosted in India (AWS ap-south-1, Mumbai). Some processing involves transfers outside India — in particular, AI inputs sent to OpenAI, the text of mock-interview questions, and of the other side's lines in conversation practice, sent to Google (Cloud Text-to-Speech), the network address a new account signed up from, sent to IPinfo, authentication data sent to Apple (Sign in with Apple) when you use it in our app, authentication data sent to Google (Sign-in) — which, on our website, includes the connection data described in Section 2(a1), sent when the sign-in button loads rather than only when you use it — usage data from the app sent to Google (Analytics for Firebase), advertising-measurement data from the app sent to Meta (from version 1.0.1 on Android, and from version 1.0.3 on an iPhone once you allow tracking), under the app's switches (Section 2(r)), usage data from the app sent to PostHog (from version 1.0.1 on Android and 1.0.3 on an iPhone), under the app's switches (Section 2(r)), whose transfer is described below, crash reports and notes of each use from the app sent to Sentry in the United States, statistics about how the vision library behind the app's face check ran, sent to Google (MediaPipe), and, for push notifications you turn on, your push token sent to Expo, Apple and Google, and the LinkedIn username you give for an import, sent to the outside profile-lookup service that fetches that profile — and, where you consent, interaction data sent to our analytics providers (Google (Analytics), and PostHog, whose transfer is described below) and advertising-measurement data sent to Google Ads and Meta Pixel — which may be processed in the United States or other countries. Your mock-interview audio is missing from that list on purpose, not by oversight: it is the one transfer we will not summarise in a clause, and it has its own paragraph next.

Your mock-interview audio needs its own paragraph, and this is the honest version of it. One provider transcribes it for us, and your own browser is the fallback when that provider cannot run (Section 4). AssemblyAI processes it, and the short list of names sent with it (Section 4), in the European Union — not a "may" and not an accident of routing, but a deliberate transfer outside India on every session that takes that path, which is why it was named here before it carried anything rather than after. We pin that European data zone rather than letting the connection be routed to whichever one is nearest, and one honesty point belongs with that claim rather than buried under it: the short-lived credential your browser (or the app) opens the session with is issued through the provider's global endpoint rather than a European one, so the request for it is not itself EU-resident — it carries no audio and no transcript, only the permission to open a session, and the audio path is the one we pin. Until 3 September 2026 a second provider in the India region took the answers we did not route to the EU one, and this paragraph carried a third leg for it; that provider was retired and the leg went with it, so the EU transfer is now the only one we make for this audio ourselves. On the fallback path — where your browser transcribes instead — your audio goes to your browser's vendor, under that vendor's own policies and outside our control, which is very likely to be outside India. In the app, the fallback is your phone's own speech service instead, which may send your audio to Apple, Google or your phone's maker, also under their own policies and possibly outside India. So every path here does or may involve a transfer outside India. If you would rather not have any of that happen, do not start a mock interview, and choose Type rather than Speak in conversation practice and in the demo on our home page: those are the only three places where your voice is turned into text. Before a mock interview, the consent screen is where we ask; in conversation practice and in the demo, choosing Speak is the choice, and there your voice goes only to your browser's own recognition (Section 4); in the app, conversation practice turns your voice into text on your phone, and your voice never leaves it (Section 2(r)).

PostHog stores what it receives from our website and our app in the European Union, in Germany, and processes it there and, for one of the companies it uses (Wiz, for security monitoring), also in France. PostHog may also have its own company in the United Kingdom, Hiberly Ltd, process it to provide PostHog's service (Section 6). On its way to Germany, that data may pass through Cloudflare's worldwide network.

One flow on this page runs the other way. When we fetch your Google profile picture as your account is created (Section 2(a2)), the image travels into India and comes to rest on our storage there; what leaves is only the request for it, described in Section 6. An inbound copy like that is not a restricted transfer, so the safeguards below are not what protects it — we mention it so the direction is not left to guesswork.

For users in the EEA/UK, where we transfer personal data to a country without an adequacy decision, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (and the UK Addendum/IDTA, as applicable); you may request a copy via support@careerverse.tech.

For users in India the answer has to be given twice, for the reason Section 3 sets out: the DPDP Act's provisions that govern these transfers do not commence until May 2027, so pointing only at that Act would name no safeguard that is operative today. Today, the law that governs these transfers is the Information Technology Act, 2000 and the 2011 Rules made under it. Rule 7 of those Rules permits a transfer only to a recipient that ensures the same level of data protection the Rules require, and only where the transfer is necessary for the performance of a lawful contract with you or you have consented to it. Both of those limbs are what we rely on for your mock-interview audio — the transcript is the artefact the exercise is graded from, and the consent screen before recording starts is where we ask you — alongside the requirement stated in Section 6, after its list, that every service provider protect your data and use it only to provide its service to us. From May 2027, when ss.3–17 commence, these transfers must additionally comply with the DPDP Act, including any restriction on transfer to a particular country that the Central Government notifies under s.16; we will follow whatever it notifies.

8. How long we keep your data

In short: We keep your data while your account is active, then delete or anonymise it within a reasonable period, apart from a few records named below, some of which we keep with no time limit. Your conversations with the AI mentor are kept while your account is open unless you delete one, are deleted when you close it, and are included in a copy of your data.

This section was added to on 25 September 2026, to say how long we keep a word you told us means a skill, and a company you tag on a practice problem; and on 30 September 2026, to add the reminder to look at skills you typed again once your account is a week old, and how long we keep a match we made for a skill you listed; and on 5 October 2026, to say how long we keep your Mentor sees switches, your Done for you list and the record of each tap on a mentor suggestion; how long we keep conversation-practice rehearsals, and the spoken versions of interview questions and practice lines; which drafts are saved to your account; how long we keep the weekly note of where your skills stand; and how long we keep the note of which Win a rewrite's figure came from; and on 27 October 2026, to say how long we keep push tokens, app crash reports and app analytics, and how long a mock-interview recording made in the app stays on your phone; and again on 27 October 2026, to say what we keep after you close your account, among it the records of a plan bought on our website, of what our staff did on your account and of a referral, and how long what we delete can stay in our routine backups.

Some parts of your Career Twin (Section 4) clear themselves on fixed clocks, whether or not you act:

  • A skill we guessed from your own text and you never confirmed is deleted after about 180 days — unless other evidence lands against that skill first (graded work you complete here, a role on your profile, or a journal entry). Then it is no longer a guess: it stops expiring and stays like any other skill with evidence behind it, and if that evidence later goes, the 180-day clock starts again. A guess that expires is genuinely deleted, not hidden.

  • The record of the sentence we read it in — the "your own words" entry that shows you why we suggested a skill — is deleted after about 180 days as well, and this one runs whether or not you confirmed the skill. Confirming the skill keeps the skill; it does not keep the quotation behind it. Any comment you added to that entry is stored on it and goes when it goes, so if you want to keep what you wrote, keep your own copy.

  • A short factual note a model wrote about one of your sessions is deleted after 12 months.

  • A disagreement between two things you have told us that you never settle lapses after about 365 days, and both statements are released.

  • A lower standing you declined is kept for 90 days after the newest attempt it concerned, so that we do not ask you again about the same attempts. It goes sooner if you delete, detach or switch off the work it cites.

  • A record that a figure was shown to you — what the readiness or match figure was, how much lower it could have been, what it was computed from, including the standing of each skill it counted, and, where the figure was measured against a job description, which application and which version of that description — is deleted after 12 months. We keep it so we can tell whether our figures are any good, and we delete it because a permanent log of every number you were ever shown serves no purpose to you. It never holds the text of a job description.

  • A weekly note of how each of your skills stands is kept for about four weeks after its week (Section 2(n)).

  • A job description you paste is held against the application it belongs to and is deleted with that application, and so is the set of skills you accept from it. It is a third party's text, and we have no reason to keep it once the application is gone.

  • A copy of your own records, taken so that an automatic combination can be undone (Section 4) is kept until that 14-day window closes, and clears itself within a week after. It is taken before the change is made, it holds your own records and nothing anyone else supplied, and it exists for one purpose: to put your record back exactly as it was if the combination is reversed. It is included if you ask for a copy of your data, and it goes when you close your account.

  • A record that a skill name has been seen by this account is kept for 90 days after the last time that name was seen. We keep it to tell whether three different people have met the same new name — which is one of the ways a name reaches the shared list, the one that lets a name we were not sure enough about on its own get there after several people have used it. A name we are sure enough about is added without it. It holds a one-way code for the name, computed with a secret only we hold so the name cannot be read back out of it — never the name itself — and nothing about where you typed it or what else you were doing.

  • A reminder to look at the skills you typed again, once your account is a week old, is kept for up to 30 days. For a new account's first week we do not send a skill name we do not hold to an AI to be matched to or added to the skill list, so when you save one in that week we note that your account should be looked at again once it is seven days old, and then we check your saved skills a second time in the same way as described above. The reminder holds no skill name and no text — only that your account is due, on which day, and how many times we have tried — and it is deleted when that check is done, after three tries, or when you close your account. It is included if you ask for a copy of your data.

  • A match we made for a skill you listed — your name for the skill from your profile and the skill on our list we matched it to (Section 4) — ends, and is deleted, within about 180 days of when we made it: sooner if it came from an answer our AI had given earlier, because a match lasts only as long as the answer it came from, and sooner still if you switch Profile off or close your account. If you choose Not what I meant for one under "Skills we matched from your words" in your account settings, we keep that answer, which holds the same two names, until the match would have ended; switching Profile off or closing your account deletes it sooner. When a match ends or you turn it down, the skill it added is withdrawn from your record the next time your record is worked out in full, unless you added or ticked it yourself or something else still supports it; the withdrawn entry stays on file, marked as withdrawn. Matches and answers are both included if you ask for a copy of your data.

Three parts of your Career Twin have no clock at all, and are kept until you act. We are naming them here rather than leaving them out, because a retention section that lists only the things with timers is not a complete answer.

  • A lower standing you confirmed is kept until you take it off from that skill's own row (Section 4), your next pass on the skill lifts it, you remove the skill, or you delete, detach or switch off the work it cites. In those last cases it is trimmed to what remains, and deleted once fewer than three pieces of graded work stand behind it.
  • A skill we no longer ask you about — one you asked us to stop suggesting, or one added for you when two entries on the skill list turned out to be the same skill — is kept until you take it off. All of them are listed under "Skills we no longer ask you about" in your account settings, the ones you did not ask for included, and each is removed from there. Being on that list keeps a skill out of our suggestions and nothing more: nothing is deleted from your record by it, and work you do that shows the skill still counts.
  • A word you told us means a skill — one you used that we did not hold by that name, stored with the skill you picked for it so that we read that word your way — is kept until you take it off under "Your own words for skills" in your account settings or close your account, and taking that skill off your record does not remove it.

Three more are kept for as long as the thing they belong to.

  • The result we keep for a graded attempt — passed or not passed — is kept with our record of that attempt, and is deleted when that record is: when you delete the work, turn its source off, or close your account, with the rare exception we name below. Detaching the attempt from a skill does not delete it.
  • A copy of your target's skill list, kept alongside the target so we can find it again, goes when a skill leaves the target or when you delete the target.
  • A record that a profile import ran — which source (LinkedIn), when it first ran and when it last ran, and nothing it fetched — is kept until you close your account. It stays when you switch Profile off, because it records something you did rather than something we worked out.

A skill you confirmed yourself does not expire — it is your statement, and it stays until you remove it. As the second bullet says, that is true of the skill itself and not of the quoted sentence we first read it in.

A display name or photo copied from Google when your account was created (Section 2(a2)) is kept like any other profile field: it is a one-time copy that we never refresh, so changing or deleting the picture on your Google Account does not change or delete ours, and disconnecting Google sign-in does not remove it either. Editing or clearing it in your profile is what changes it here.

The token we keep for Sign in with Apple (Section 2(a1)) is kept only while Sign in with Apple is on for your account: we delete it when you stop using it, when Apple tells us you have, and when your account is deleted.

The network address you signed up from, and the country, region, city, time zone and network we looked up from it (Section 2(a)), have no clock of their own: they are kept on your account until you close it. The fingerprints we keep to spot someone referring themselves (Section 2(a)) follow the same rule. Each fingerprint is deleted when the account it belongs to is closed: a referrer's own, which we may keep of an address we have confirmed they opened their Refer & Earn page from, when they close their account, and the one from a sign-up with a referral code when that member closes theirs. Our record of the referral and of any reward it earned stays, also after either account is closed. That record has no clock. Once the account that signed up with the code is closed, it no longer holds that member's name or email address, but it still carries the closed account's identifier, the kind of device it signed up on, whether we flagged the sign-up as possibly someone referring themselves, and any reward it earned; and where a payment that member made in the App Store or Google Play earned a reward, we also keep, with that payment, a copy of our record of who referred them, so that a refund of it can still cancel the reward. When a referrer closes their account, we delete their payout details and their own record of rewards and payouts, but our records of the people they referred stay, still filed under the closed account's identifier and showing any reward each earned, and their referral code stays reserved, with no owner, so that it is never given to anyone else.

A company you tag on a practice problem, as one that asks it, is stored against your account and has no clock: it is kept until you remove your tag from that problem, we delete the problem, or you close your account.

When a rewrite made for a job you track uses a figure from one of your Wins, we note which Win it came from and that Win's date beside the rewrite. The note is kept with that job's rewrites and deleted with them.

A mock-interview recording we hold expires automatically at the end of the day (UTC) 30 days after it is uploaded, and is then deleted by AWS, which stores it for us and says the deletion can take days or even weeks; deleting the interview or your account deletes it sooner, and if that deletion fails or misses it, the recording still expires then. The proctoring events we store from a mock interview, the integrity signal derived from them and any summary figures we store from the composure estimate are kept with that interview until you delete it or your account; if you delete an interview while it is being graded or saved, some of them can stay until you delete your account.

Conversation practice. Your voice is never recorded. The written record of each rehearsal — what you typed or said, as text, the other side's replies, its debrief and its prep sheet — is saved for your debrief until you delete that rehearsal, and deleting it removes that written record for good. It has no shorter clock of its own, is included in a copy of your data, is deleted when you close your account, and is never shown to anyone else. If you used Speak, the spoken versions of the other side's lines are kept separately, as the next paragraph describes.

Spoken versions of interview questions and practice lines. When our synthetic voice reads a mock-interview question aloud, or a line the other side says in conversation practice when you choose Speak, we keep the spoken version as a sound file, so that the same sentence can be played again without being made again. The file itself holds no link to your account: while the interview or rehearsal is kept it points to the file, and once you delete it, nothing of yours does. But the file says what the sentence says: an interview question can include your first name or refer to your profile or an earlier answer, and a practice line can repeat or answer what you said. These files have no expiry. They are not deleted when you delete the interview or the rehearsal, or when you close your account, and they are not included in a copy of your data. Any session that produces exactly the same sentence in the same voice plays the same file.

Drafts saved to your account. What you write in the code editor on a coding problem is saved to your account as a draft, one for each problem and language, and has no clock of its own: it is kept until you reset it or close your account. Choosing Reset to starter on a coding problem deletes what you wrote in that language from your account. A resume-builder draft can be saved to your account too, so you can pick it up on another device: we keep one for your account, the latest you saved, with everything in it. It has no clock of its own either, and is kept until you delete it or close your account. The resume builder on our website does not save its draft to your account yet; it keeps it in your browser (Section 5). Saving a draft never sends it to our AI provider, and no one else can read it. Drafts are included in a copy of your data.

What PostHog records on our website and from our app (Sections 2(j) and 2(r)) is kept by PostHog for a limited time, and then deleted: its events for up to two years, and its session replays for up to 90 days. The profile PostHog keeps under your pseudonymous id once you sign in (that id; your plan, and whether you are on a free trial or paying; for our own staff, the mark in Section 2(j); the page and source of the first visit it recorded, and the approximate location it worked out; the technical details it first received and the latest of them it has saved (from our website, your device type, your browser and system and their versions, the full description of itself your browser sends, the size of your screen and window, and the address of the page you were on and of the page you came from, stripped as Section 2(j) says, with any campaign tags; from our app, your phone's system and its version, the app's package name or bundle identifier, version and build, and your screen's size); and, if the app asked you and you said yes, when you said it and to which version of its question) has no time limit: it is kept until you close your account, withdraw your cookie consent while you are signed in, turn off PostHog product analytics in the app, say no on the app's own screen once the app has sent PostHog anything for your account from that phone, or turn off Send analytics and crash reports there once it has sent PostHog anything for your account from that phone (when your account is not the one signed in there at the time, the deletion waits until it next signs in there), and any of those also deletes sooner the events and session replays held under that id (Section 10). Withdrawing while signed out removes PostHog's cookies and storage from that browser, but not the profile. If our website or the app goes on sending under your id after one of those deletions, because you accepted on our website or left PostHog on in the app on another phone, PostHog starts a new profile under that id, which the next of these steps deletes too.

The CareerVerse app.

  • Push tokens are kept while the phone can receive our notifications: until Apple or Google tell us it no longer accepts notifications, another account turns notifications on for that phone, a newer phone takes its place among your ten, or you close your account. Signing out of the app does not always end that (Section 2(r)). A record that we sent a given notification, kept so it is never sent twice, expires 30 days after the send. The delivery reference Expo gives us for a notification is deleted once we learn whether it was delivered, and otherwise expires 48 hours after the send. Each expired record is deleted automatically, usually within a few days of expiring.
  • App crash reports are kept by Sentry for up to 90 days, depending on our Sentry plan, and then deleted. Sentry keeps the notes of each time the app is used (Section 2(r)) for as long as Sentry's own rules allow; its published retention periods state none for them. The identifier Sentry's software creates for the installation can stay on your phone until you remove the app or clear its data, even after you turn off Send analytics and crash reports or sign out.
  • App analytics are kept by Google, tied to the app's installation, for at most 14 months, the longest data-retention setting our Google Analytics property can have. Totals in Google's standard reports, which are not tied to you, can be kept longer.
  • What our app sends Meta (Section 2(r)) is kept by Meta for as long as its own terms and privacy policy allow; we keep no copy of it and cannot delete it. On Android, Meta's kit keeps its installation identifier, its settings, any Meta ad-click and campaign identifiers and any copy of Google Play's note on your phone until you remove the app or clear its data, even after you turn it off; Android's backup of the app's data can restore them. On an iPhone, from version 1.0.3, it keeps its installation identifier and its settings until you remove the app, even after you turn it off, and the phone's own backup can restore them, with any events it had saved to send later (Section 5).
  • A mock-interview recording made in the app is kept on your phone until it is sent to us or deleted. While you record, it is written to your phone's temporary storage; when the interview ends, the app moves it to a folder that your phone's own backup (iCloud, or Android's device backup) does not copy, and your phone can clear that folder by itself when it runs short of space. The app deletes it from your phone once we hold it, or once it can no longer be sent, for example because no answer in the interview came through as words; when you discard it or delete the interview; and when you sign out or another account signs in on that phone. A recording that stops before the interview ends can be left in the temporary storage until your phone clears it. The few seconds the camera and microphone check records to test them never leave your phone and are deleted at once.
  • A purchase you made in the App Store or Google Play (Section 2(i)) is kept as a financial record, including after you close your account. Closing your account deletes the store-account token that tied the purchase to you and marks the purchase as belonging to no account, so we ignore any later notice the store sends about it. If you sign up again and restore that purchase on the new account, it is tied to the new account instead.
  • Where your app sign-up came from (Section 2(r)) is kept on your account until you close it. Labels the app is holding for a sign-in stay on your phone until you sign in or sign out, and the ones from Google Play for 90 days at most.

A plan bought on our website. Each time our payment processor (Section 2(i)) tells us about your plan or one of its payments, we keep a record of what it told us, as a financial record of what was charged and paid, and so that we can look into a payment that failed. The record holds the plan, its status and dates, each payment's amount, tax, fees and currency, the type of payment method and, for a card, its brand, last four digits and expiry date, any advertising click identifier your checkout carried (Section 2(k)), your account's identifier and the customer reference our payment processor gave you, and the message itself: only for messages about your plan, its payments or a refund, from which we first remove the name on the card and the email address of a PayPal account. A message of any kind that our payment processor sent us on or before 26 September 2026 may have been kept as it arrived, so it can also hold the name on the card, the email address of a PayPal account, and your name and email address as our payment processor holds them. These records have no clock. Closing your account does not delete or change them.

What our staff did on your account. When someone at CareerVerse takes one of these actions on your account through our staff tools, we keep a record of who did it, what they did, when and why, and, for most actions, what it changed: giving you access you did not buy or taking it back, resetting your usage, suspending your account or lifting a suspension, recording a Refer & Earn payout or refusing one, cancelling a Refer & Earn reward or approving one that was held back, recording that you were given a month's Refer & Earn goodies, correcting the country your Refer & Earn rewards are paid in, delivering or cancelling a recruiter review, confirming, refusing or completing an expert call you booked, and checking your App Store or Google Play subscriptions with the store again or detaching one from your account. Only those actions are recorded this way. We keep it so that we can always account for what we did on an account: our service can add to this record but cannot change or delete it. It is filed under your account's identifier, has no clock, and is not deleted when you close your account.

We retain personal data for as long as your account is active and as needed to provide the Service, and thereafter only as required to comply with legal obligations, resolve disputes, and enforce our agreements. When you delete specific content (such as an interview recording or forum post), we remove it from active systems, though a copy may remain in our routine backups for up to 35 days: they let us restore our database as it stood at any moment in that time. When you close your account, we delete or anonymise your personal data within a reasonable period, except where longer retention is required by law, and except the sound files described above, the store purchase records described above, the records of a plan bought on our website and of what our staff did on your account described above, our record of a referral described above, and the notes of bounced or rejected emails described in Section 2(p1). Rarely, something still being saved for your account as it was closed, or in the seconds after, such as a draft, a mark that your account was active that day, points or a badge, or the result we keep for a graded attempt, arrives after we have deleted that kind of data, and can then stay, even where this policy says that kind of data goes with your account: a clean-up we run afterwards normally removes it, but not if that clean-up fails, is skipped because we rolled our service back in the meantime, or ran before it arrived. What we delete when you close your account can also remain in those backups for up to 35 days. If you would like to know the retention period that applies to a specific category of data, contact us at support@careerverse.tech.

This part of Section 8 was rewritten on 24 September 2026. Until then it said that we could not delete your conversations with the AI mentor at all, and that a copy of your data did not include them. Both have changed, and what follows is the position now. It changed again on 5 October 2026, when you gained a control that deletes one conversation.

Your conversations with the AI mentor have no clock of their own, so here is exactly what removes them. Nothing removes them with time: they are kept for as long as your account is open, unless you delete one. Closing your account deletes them, and so does asking us to erase your account. Rarely, a message you had just sent the mentor, its reply and that conversation's summary can stay after that, as we say below. You can also delete any one of them yourself, as the next paragraph explains. Like other content we delete, they may remain in our routine backups for up to 35 days.

Deleting a conversation. You can delete any AI Mentor conversation yourself, with Delete this thread on the AI Mentor page. Its messages, the mentor's replies and its running summary are deleted for good, and the mentor no longer uses them. If the mentor was still writing a reply when you deleted the conversation, we take that reply back; the message you sent still counts toward your daily messages. Rarely, the conversation can show in your list again for a moment while we do that, or stay there if taking it back fails; you can then delete it again, and what is left is never used in a later reply. We keep a reference to the page the conversation belonged to (for example a lesson or a job in your tracker, never anything you or the mentor wrote) until the clean-up after your account is closed removes it (below), so that anything that arrives a moment after your delete can still be found and deleted with your account. Your wins, jobs and plan are not affected, and neither is your Done for you list, which is kept as described below. The name the list shows for a conversation (a company, a problem's title) is not stored with the conversation: it is looked up from that item each time you open the list, so a renamed item shows its new name and a deleted one shows none, and it is never taken from what was said in the conversation. Deleting a mock interview also deletes the conversation in which you asked for its questions in plainer words.

What is kept, and what goes, is the exchange itself — what you typed, what the mentor replied, and when — and a running summary of the conversation that the mentor writes as you go, so it can remember what you have already discussed. That summary is our own prose about what you told it. It is kept alongside the exchange, on exactly the same terms, and it goes when the exchange goes. When a conversation goes, all of it goes: your messages, the mentor's replies to them, and the summary. A copy of your data includes every conversation: your messages, the mentor's replies, when each was sent, the summary, and, for a conversation you opened from a page, a short label for that page.

So four of your rights now reach every one of your mentor conversations: access, a copy, taking them elsewhere, and erasure — you can delete any one of them yourself, or all of them by closing your account. Two rights still stop here for every conversation: correcting what one of them holds, and restricting the processing of one. Section 10 sets out why, where the rights themselves are stated. The plain advice therefore still holds: do not type anything into the mentor that you would later need us to correct. You can delete a whole conversation, but not one message in it. Apart from our ordinary server logs and the rate limits we keep to secure the Service (Section 2(h)), three things we keep that are connected with the mentor can stay after your account is closed. One is the audit record kept for each page description, which Section 4 describes: each is deleted about 90 days after it was made, and closing your account does not remove it sooner. Another is the running count of your mentor messages that we keep to apply your plan's limits: it holds how many you have sent in the current day and month and when it was last updated, never anything you wrote. It normally goes about 15 minutes after you close your account, and in any case it clears itself within about six weeks of that last update, which is normally your last message. The third is the list of references we keep to the pages your conversations belonged to (Deleting a conversation, above): it normally goes at the same time as that count, but if the clean-up that removes it fails, or is skipped because we rolled our service back in the meantime, it stays until we run that clean-up again, and so, rarely, does anything connected with the mentor that a request still running as your account was closed, or made in the seconds after, saved after we first deleted that kind of data, such as a message you had just sent the mentor, its reply and that conversation's summary, a Done for you row and the record of its tap, or your Mentor sees switches.

Your Mentor sees switches and your Done for you list are kept while your account is open, are included in a copy of your data, and are deleted when you close your account, except, rarely, as the paragraph above says. The Done for you list has no shorter clock of its own. Each Done for you row keeps the name of what was added (a job's role and company, a win's title, a saved item's title) and the button you tapped until you close your account, even if you later delete that item yourself; undoing an action clears both. When you tap a suggestion, we also keep a small record of the tap: a reference to the conversation's page, the time of the mentor's reply, the suggestion's place in it and when you tapped it, never any text. If the tap fails, that record is removed so you can try again. That record, and the suggestion each Done for you row came from, are kept until you close your account, including after you undo the action or delete that conversation, and are deleted with your account, with the same rare exception. Both are included in a copy of your data, including the record of a tap that stopped before it finished.

9. How we keep your data safe

In short: We use sensible technical and organisational measures, and a passwordless sign-in.

We take reasonable steps to protect your data, including: passwordless sign-in via email OTP (there is no password to steal); a secure, HttpOnly session cookie that client-side scripts cannot read; server-side handling of your authentication token so it is not exposed to the browser; same-origin protections and per-IP rate-limiting on sensitive endpoints; encrypted transport (HTTPS/TLS); and hosting on AWS with access controls. You can end every other signed-in session from your account settings. Stopping Google sign-in also ends the sessions it created, blocks ordinary Google sign-in from silently restoring it, and requires fresh email verification before it can be enabled again — it does not, however, remove a name or photo copied to your profile at sign-up, which by then are ordinary profile fields you control (Section 2(a2)). Stopping Sign in with Apple likewise signs you out on every other device, and on this one too if you signed in with Apple (Section 2(a1)). Keeping facial-landmark data on your device further reduces what we hold. No system is perfectly secure, so we cannot guarantee absolute security. Because we sign you in through your email, keeping your email account secure is an important part of protecting your CareerVerse account.

In the event of a personal-data breach, we will notify the relevant authorities and affected individuals where and as required by applicable law.

10. Your privacy rights

In short: You have strong rights over your data, and the exact rights depend on where you live. Two of them stop short of your AI mentor conversations: we cannot correct one, or restrict what we do with one. You can delete any one of them yourself, and closing your account deletes them all (Section 8). The audit records of page descriptions, which are connected with the mentor, are not part of the copy of your data we put together, though you can ask us for them separately while your account is open, and neither closing your account nor asking us to erase your data removes them sooner: each is deleted about 90 days after it was made (Section 4).

This section changed on 5 October 2026, when you gained a control that deletes one AI mentor conversation; and on 27 October 2026, to say what a copy of your data holds about the phones that can receive our notifications.

Some of these you can exercise yourself, without contacting us. Under "What builds your record" in your account settings you can stop us working anything out from any source; and on your Career Twin page you can remove a skill, detach a piece of evidence, decline a lower standing we propose or take off one you already confirmed, or mark a model-written note wrong and add your own comment to it. We stop reading the source straight away and begin deleting immediately; on a large account the deletion may take more than one step, and the page tells you if so and offers you a button to finish it (Section 4). That message lives on the page you started it from. If you close the tab before it finishes, write to support@careerverse.tech and we will complete it — the source stays switched off in the meantime, so nothing further is read from it either way.

You can also get a copy of your data, and delete your account, yourself. Under "Your data" in your account settings, you can request a copy of your data and download it once it is ready, and you can delete your account. Both ask you to confirm with a code we send to your email address. You can delete your account while a plan renews, a free trial included, and before you confirm we show you what deleting does to each plan you have. Deleting your account turns off the renewal of a plan bought on our website or in Google Play, so you are not charged again; if we cannot turn a renewal off, nothing is deleted: try again, or write to support@careerverse.tech and we will turn it off and delete your account. An App Store subscription keeps billing through Apple until you cancel it in the App Store: we cannot cancel it for you, and deleting your account does not. If you sign up again later, restoring that purchase on the new account works (Section 8). A copy of your data includes, for each phone that can receive our notifications, an identifier for the phone's registration, whether it runs iOS or Android, the app version, and when it was added and last updated. It does not include the push token itself, which is a delivery address for your phone rather than information about you. It also includes, for each purchase you made in the App Store or Google Play, the store, the product, its status, when it ends and whether it renews.

What PostHog holds goes too. Deleting your account, withdrawing your cookie consent while you are signed in, turning off PostHog product analytics in the app, saying no on the app's own screen once the app has sent PostHog anything for your account from that phone, or turning off Send analytics and crash reports there once it has sent PostHog anything for your account from that phone (when your account is not the one signed in there at the time, at its next sign-in there), asks PostHog to delete the profile it keeps under your pseudonymous id, with its events and session replays (Section 2(j)); PostHog finishes deleting them in the background. That includes what it recorded from both our website and the app. A copy of your data says what PostHog may hold, but does not include a copy of it. What PostHog recorded from a visit that was never linked to your account cannot be found by your account, and is deleted when its time runs out (Section 8).

What Meta holds does not. Deleting your account, turning off Ad measurement or Meta ad measurement, or turning off tracking for CareerVerse on an iPhone, does not delete what the app had already sent Meta (Section 2(r)): Meta decides what it does with it and answers requests about it under its own privacy policy, and you can write to support@careerverse.tech and we will pass a request on to Meta.

Whatever your location, contact support@careerverse.tech to exercise your rights (India residents may also contact the Grievance Officer in Section 12). We may verify your identity — usually by confirming control of your account email — before acting, and we will respond within the time the law allows. We will not discriminate against you for exercising your rights.

One limit, stated here rather than left for you to discover: your conversations with the AI mentor. A copy of your data includes every one of them, so your rights to access them and to take them elsewhere reach all of them. Closing your account deletes them, and so does asking us to erase your account, with the rare exception Section 8 names, and you can delete any one of them yourself (Section 8). The audit records of page descriptions have limits of their own, which we set out after the list below. Two more limits apply to every mentor conversation, and we would rather state them here than have you discover them by asking us:

  • We cannot correct one. A message is written once and is never edited afterwards, by you or by us, and the running summary the mentor keeps of a thread is rewritten only by the mentor itself, on a later turn of that same thread. So if the mentor has recorded something about you that is wrong, we have no way to put it right, and telling us it is wrong will not change what is stored.
  • We cannot restrict what we do with one. There is no mark we can put on a conversation that says "keep this but stop using it": every later turn of a thread reads what came before it, and the summary with it, and sends them to our AI provider again. The only things that stop that are your not sending another message in that thread — nothing reads a conversation unless you do — deleting that conversation, and closing your account, which deletes them all.

So wherever the rights below speak of correcting or restricting your personal data, read them as stopping at your mentor conversations. Where they speak of erasing it, read that, for your mentor conversations, as deleting a whole conversation, which you can do yourself at any time, or all of them with your account; a single message cannot be erased on its own. The audit records of page descriptions that Section 4 describes have limits of their own. They are not part of the copy of your data we put together, but while your account is open you can ask us for them separately at support@careerverse.tech, and we will send you what they hold about you. Neither closing your account nor asking us to erase your data removes them sooner: each is deleted about 90 days after it was made. The running count of your mentor messages that Section 8 describes is not in that copy either. Closing your account, or an erasure request, normally removes it about 15 minutes after your account is closed, and in any case it clears itself within about six weeks of its last update. The rights that none of this touches are these four: objecting to processing, withdrawing a consent you gave, being told the source of data we did not get from you, and complaining to a regulator. Access and taking your data elsewhere reach every mentor conversation, and for the audit records, access works as just described. Section 8 sets out what is kept and what goes.

India (DPDP Act, 2023)

The DPDP Act's rights provisions commence in May 2027 (Section 3). We are not waiting for that date — everything below is available to you today on request, whether or not the Act yet compels it.

You have the right to: access a summary of the personal data we process about you and related processing; correct, complete, update, and erase your personal data; grievance redressal (Section 12); and nominate another individual to exercise your rights in the event of your death or incapacity. Where we rely on consent, you may withdraw it at any time, as easily as it was given.

Separately, and in force now, section 43A of the Information Technology Act, 2000 and the 2011 Rules give you a route to compensation for a failure to protect sensitive personal data; a claim under it goes to an adjudicating officer under section 46 of that Act. Where CareerVerse acts as an intermediary in respect of content other users post, the Grievance Appellate Committee under the IT Rules 2021 can hear an appeal against our Grievance Officer's decision on such content.

European Union and United Kingdom (GDPR)

You have the right to: access your personal data and obtain a copy; rectify inaccurate or incomplete data; erase your data ("right to be forgotten"); restrict or object to certain processing, including processing based on our legitimate interests; data portability; withdraw consent at any time where we rely on it; be told the source of personal data we did not get from you directly — such as the display name and photo Google gives us when an account is created through "Continue with Google" (Section 2(a2)), the name Apple passes on the first time you use Sign in with Apple (Section 2(a1)), or what a LinkedIn import fetched (Section 2(g)); and lodge a complaint with your local supervisory authority. We do not use solely automated decision-making that produces legal or similarly significant effects on you. Your Career Twin is assembled automatically and does produce figures about you — a readiness figure, a match percentage and a completeness figure — and a standing for each skill on your record (Section 4) — but those figures and standings decide nothing: nothing is withheld from you because of them, no access, price or eligibility turns on them, and they are never shared with employers, recruiters or any other third party (our AI provider, which acts on our instructions, receives them only to write your own AI Mentor replies, while you let the mentor read your Career Twin — Section 4). You can see every piece of evidence behind them, dispute or remove any of it, decline a lower standing we propose, and add your own written comment, which is stored with the item and included if you ask for a copy of your data.

California (CCPA/CPRA)

You have the right to: know what personal information we collect and how we use and disclose it; access and obtain a copy of it; delete it; correct inaccurate information; opt out of sale or sharing for cross-context behavioural advertising; and not be discriminated against for exercising your rights. We do not sell personal information. Meta Pixel activity may constitute "sharing" under California law, but it remains off unless you opt in; declining the banner or choosing "Turn off" under "Cookie preferences" exercises that opt-out. Measuring our own ads in the app with your advertising ID may also be "sharing", and so may what the app sends Meta, from version 1.0.1 on Android and 1.0.3 on an iPhone (Section 2(r)), which Meta may use for its own advertising; on an iPhone both stay off unless you allow tracking, and you opt out in Settings > Privacy & Security > Tracking or, for Meta alone, with Meta ad measurement; on Android it is on unless you opt out, with Ad measurement or, from version 1.0.1, Meta ad measurement in the app's Privacy and data.

11. Third-party links

The Service may contain links to third-party websites and services that we do not control (including the LinkedIn, GitHub, and portfolio links you add). This Policy does not apply to those third parties, and we are not responsible for their content or privacy practices. Please review their policies before providing them your information.

12. Grievance Officer (India)

In short: In India, you can raise privacy concerns with our Grievance Officer.

In accordance with India's DPDP Act and the Information Technology Act, 2000 and rules thereunder, you may contact our Grievance Officer regarding the processing of your personal data:

  • Grievance Officer: Simran Budakoti, ASOasis Tech Private Limited
  • Address: WeWork HQ27, B-660, Sushant Lok Phase 1, Sector 27, Gurgaon, Haryana 122009, India
  • Email: support@careerverse.tech

We will acknowledge and address grievances within the timelines required by applicable law. If your grievance is not satisfactorily resolved, you may approach the Data Protection Board of India once it can hear complaints; Section 3 explains why it cannot yet.

13. Children

In short: CareerVerse is for adults only.

The Service is intended only for individuals aged 18 or older, and we do not knowingly collect personal data from anyone under 18. We do not direct the Service to children, track or profile children, or target advertising at them. If you believe a person under 18 has provided us personal data, contact support@careerverse.tech and we will take reasonable steps to delete it and close any associated account.

14. Content you post in public areas is public

In short: Discussions and comments you post in the public Community are visible to anyone on the internet and can appear in search engines. Posting anonymously hides your name from other people, but not from us. Don't post anything you need to keep private.

The public Community. CareerVerse includes a public Community. A discussion you post there — and comments on it — is visible to anyone on the internet, whether or not they have a CareerVerse account, and may be crawled, indexed, and displayed by search engines. Along with your title and text, this includes any tags and image, and associated information such as vote counts, the number of comments, and the times you posted or edited; some of this is also published as machine-readable structured data for search engines. It is not private and is not limited to signed-in members. (Replies nested under a comment are, for now, shown only to signed-in members — but you should treat anything you post as capable of becoming public.)

Once it's public, it's out of our hands. Anyone on the internet — including people and companies not bound by our Terms — can copy, screenshot, cache, republish, or use your public Community content to train AI or other systems. We cannot control or prevent that, and deleting a post cannot claw back copies others have already made.

Posting anonymously. If you post anonymously, we hide your name and profile photo from other users and the public. Anonymity protects your identity from other people — not from us: ASOasis and its moderators can still see which account posted (for safety, moderation, legal, and your own edit/delete purposes), and it does not make the content itself private — the text, tags, and images you posted remain public. If you post without choosing anonymity, your profile display name and photo are shown publicly with your post.

Blocking a member. If you block a member, we keep a list of who you blocked and hide their posts and comments from you; they are not told. A block made from a member's name, or from their public profile, hides their named posts and comments. A block made from an anonymous post or comment hides that author's anonymous posts and comments, and for it we keep a link to that author, which we never show you. If a member blocks you from one of your anonymous posts, they stop seeing all your anonymous posts, so they may be able to tell which anonymous posts were written by the same person, but never who. Your blocked list is in your data export (with the name of each member you blocked by name, and nothing that identifies an anonymous author), is deleted when you delete your account, and stays when you delete your community posts. You can unblock anyone at any time from your account settings, under Privacy.

Checking text before it is saved, and the community rules. Before a post, reply or edit is saved, and before the handle, headline or About on your public profile is saved, its text is checked on our own servers against a list of words we don't allow; no other company receives it for this. A refused text is not saved on our servers (it stays in your draft on your device). Before your first post or reply, we ask you to agree to our community rules, which are part of our Terms of Service. We keep a record that you agreed (which version, and when) until you delete your community posts or your account, and it is in your data export.

Post carefully. Do not include personal, confidential, sensitive, or identifying information — yours or anyone else's — in Community content you do not want to be public. You are responsible for what you post (see our Terms of Service).

What is not public here. Discussions attached to specific learning content (such as a course lesson) are not part of the public Community and stay visible only to signed-in users. This section covers the public Community feed and its discussion pages.

Deleting public content. When you delete a Community post or comment, we remove it from public view on CareerVerse promptly. Copies may remain in our routine backups for up to 35 days (see Section 8), and — as noted above — search engines and other third parties may keep copies that we cannot remove for you.

Public profile. Separately, you can give yourself a public profile by claiming a handle (your personal URL). Claiming that handle makes the profile public — we tell you so on the form before you confirm — and from then on the sections you have filled in are public and may be indexed by search engines. If your account was created through "Continue with Google", remember that your name and photo were filled in for you (Section 2(a2)) — so check them before you claim a handle, because publishing publishes those too. Accounts have no public profile until you claim a handle, sensitive contact details are always excluded, and you can switch back to private at any time from your account settings.

15. Changes to this Policy

We may update this Policy from time to time. When we do, we will revise the "Last updated" date above and, where the changes are material, provide additional notice through the Service or by email where appropriate. Where the law requires fresh consent, we will obtain it.

16. YouTube

CareerVerse, through its internal tool CareerVerse Social Publisher, uses YouTube API Services to publish CareerVerse's own videos to its official YouTube channel (@CareerVerse_Tech) and to find recent public YouTube videos about careers.

See the Google Privacy Policy: http://www.google.com/policies/privacy.

When our channel owner authorises the tool, we store a Google authorisation token limited to the youtube.upload permission. It lets the tool upload videos to the channel, set their thumbnails, upload a channel banner image and set the channel's watermark; it cannot delete anything. The tool uses it only to upload videos. We send YouTube each video with its title, description, visibility setting and made-for-kids setting. From each upload we keep the video ID YouTube returns, including any copy our tool posts in our team chat, for no longer than 30 days unless we refresh it from YouTube.

Once a day we search YouTube for recent public videos about careers, and we read our own channel's public upload list. From these we keep video IDs, channel IDs, titles and publish dates. We use them only to pick videos our team may watch or comment on by hand, and to confirm that our own uploads went live. The links are shown to our team in our internal workplace chat. Titles may be sent to an AI provider (Google Gemini) to suggest a draft comment that a person reviews. We do not sell this data, use it for advertising, or share it with anyone else. We delete it within 30 days of retrieving it, including the copies of YouTube links our tool posts in our team chat.

To ask us to delete the YouTube data we store, or to withdraw CareerVerse's access through us, email support@careerverse.tech. We revoke our access token with Google right away and delete the stored YouTube data within 7 days. In addition to that procedure, you can revoke CareerVerse's access at any time at https://security.google.com/settings/security/permissions. If you do, we delete the stored YouTube data within 30 days. Deleting the data CareerVerse stores does not affect any data stored by YouTube. To delete data on YouTube itself, use YouTube (for example YouTube Studio) or another authorised app that supports deleting it.

17. Contact us

For any privacy question or to exercise your rights:

  • Email: support@careerverse.tech
  • Company: ASOasis Tech Private Limited, India
  • India DPDP Grievance Officer: see Section 12.
Questions about this policy? Contact usBack to top