HirePotential Privacy Policy

Last updated: 22 October 2026

HirePotential ("the app", "we", "us") is developed by an independent developer. This policy explains what information the app collects, how it's used, and your choices. It describes version 1.6.0 of the app.

What we collect

• Job advert text you paste, upload (PDF or Word), or add as a link, so the app can generate tailored interview themes and competency questions.
• Your CV text, pasted or uploaded (PDF or Word), used for CV Review and to compare against your LinkedIn profile in LinkedIn Review.
• Your LinkedIn profile, provided one of three ways: pasted text, LinkedIn's own PDF export, or up to five screenshots you choose via the system photo picker. Screenshots are analysed directly by an AI vision model to judge photo presence, recommendations, and layout — the app itself never gets open access to your photo library, only the specific images you pick.
• Spoken answers you record in Practise and in mock interviews. These are transcribed to text using Apple's Speech framework — the app itself does not store or send the audio. Where your device supports it, transcription happens on your iPhone; otherwise it may use Apple's own servers, governed by Apple's privacy practices, not ours.
• AI features: when you use job advert analysis, CV Review, LinkedIn Review, rehearsal scoring or mock interviews, the content that feature needs (job advert, CV text, LinkedIn text or screenshots, and transcribed answers) is sent to our backend (hosted on Microsoft Azure) to generate themes, questions, follow-up questions, feedback, scores, and review suggestions using an AI model. The reviews, scores, questions, and feedback you see are generated by AI. The app asks for your permission before anything is sent for AI processing, and you can turn AI data sharing off in Settings at any time. This happens per request — we do not maintain a database of your submissions.
• Documents and links, without AI processing: PDFs are read on your iPhone, but Word (.docx) files you upload (a CV or a job advert) are sent to our backend just to extract their text, and job advert links you add are fetched by our backend to get the advert's text. The extracted text is returned to the app and not kept. This works whether or not AI data sharing is turned on; nothing goes to the AI model until you use an AI feature.
• Contact form: if you use Contact the developer in the app (or the form on our Support page), your message and, if you choose to give one, your email address for a reply are sent via our backend and delivered to the developer by email through Resend. Messages from the app also include the topic you picked, the app version, the iOS version, and the device type (for example "iPhone"), so a problem can be looked into.
• Device state for free limits and security: every request to our backend is signed using Apple's App Attest, so only genuine copies of the app can use it. Our backend stores, in Microsoft Azure Table Storage, an anonymous key id created for each install of the app, together with how much of the free allowance that install has used (free scored rehearsals and the free mock interview), a request count used to prevent abuse, and whether that install has a verified full version purchase. This isn't linked to your name, email, Apple Account, or anything you submit.
• If you make the in-app purchase, payment itself is handled entirely by Apple — we never see or store your payment details. To recognise that an install has unlocked the paid features (and to correctly re-lock them if a purchase is later refunded), the app sends Apple's own signed proof of purchase to our backend, which verifies it with Apple and stores a paid/not-paid flag and Apple's original transaction id against that install's key id — no billing information, just entitlement status.
• Your app data on your device: checklist and guide progress, which stories you've ticked in the story bank, how many free rehearsal sessions you've used, your rehearsal and mock interview history (past scores, feedback, and transcripts, so you can revisit them), your saved roles (up to 2, or 5 with the full version — each with the job title, job advert, a summary, and generated questions), your CV text, the LinkedIn text you last reviewed, and your latest CV Review and LinkedIn Review results. The app doesn't have user accounts or sign-in, so none of this is linked to an account.
• iCloud sync: with iCloud sync on (the default, when you're signed in to iCloud), the app keeps your data in step across your devices using Apple's CloudKit, in your own private iCloud database. We can't see or access it. What syncs: your rehearsal and mock interview history (including transcripts and feedback), your saved roles and their job adverts, analyses and questions, your CV text and file name (not the file itself), and your preferences and progress (checklist ticks, guides read, Stories steps, story bank ticks, warm-up results, and your latest CV and LinkedIn Review scores and number of fixes). The LinkedIn text, full review results, whether you have the full version, free-session counts, and your AI data sharing choice aren't synced. You can turn sync off in Settings, and iCloud storage is governed by Apple's privacy practices.

What we don't collect

• No advertising or analytics tracking, and no tracking across other apps or websites.
• No camera, location, or contacts access.
• No open photo library access — LinkedIn screenshots are picked through the system picker, which never grants the app broader access to your photos.
• No audio recordings — only the text transcript of your answer is used.
• No account or sign-in system — there is no persistent identity tied to your submissions.

Third parties

Job adverts, CV text, LinkedIn profile text/screenshots, and transcribed answers are processed by Microsoft Azure (Azure AI Foundry) to generate results, only after you've agreed to AI data sharing. This processing happens entirely within Azure's UK South region, so this content never leaves UK data centres. Microsoft acts as a data processor for this purpose and does not use this content to train its models. Microsoft is contractually bound, under the Microsoft Product Terms and its Data Processing Addendum, to data protection safeguards equivalent to our own obligations under UK GDPR — see Microsoft's own privacy and compliance terms for the full detail. Our backend runs on Microsoft Azure Functions, and the per-install device state described above is kept in Microsoft Azure Table Storage. Contact form messages are delivered by email through Resend. Apple provides App Attest, speech recognition (where it isn't on your device), iCloud sync through CloudKit, and in-app purchases, under Apple's own privacy practices; our backend also verifies purchases directly with Apple and receives refund/cancellation notifications from Apple's servers, solely to keep each install's entitlement status accurate.

Data retention

We don't operate a database of user submissions. Content sent for AI processing, Word files sent for text extraction, and job advert links we fetch are used only to produce your immediate response and aren't retained by our backend afterwards. The exceptions are the per-install device record (anonymous key id, free-allowance use, request count, and entitlement status), kept so free limits and purchases work without an account, and contact form messages, which stay in the developer's email inbox so we can reply. Data in the app stays on your device, and in your private iCloud if sync is on, until you delete it: Settings › Your data lets you reset your progress or delete all your data, including from iCloud. Deleting the app removes the data on your device; data in your iCloud can also be managed in your device's iCloud settings.

Children

HirePotential is not directed at children under 16, and we don't knowingly collect information from them.

Your rights

Since we don't retain a database of your submissions or operate accounts, there is very little personal data for us to hold beyond what's described above. If you'd like a contact form message you sent to be deleted, ask via the Support page. If you have questions about this policy or how your data is handled, contact us via our Support page.

Changes

We'll update this policy as the app's features change.