Privacy Policy
Last updated: 10 October 2026
1. Who we are
TrueFit operates a job-search and employer-introduction service. For privacy questions, contact the person who provided your beta invitation. The operator's legal identity, applicable regional requirements and provider agreements must be published and reviewed before a public international launch.
2. What we collect
Account data (email, authentication identifiers, the invite code that authorised your seat); CV contents you upload and the structured facts derived from them; your stated job preferences, urgency tier and right-to-work declarations (which you alone provide — we never infer them); application records (what was submitted where, when, with which documents); voice transcripts if you use the optional voice features — the spoken-answer bot transcribes in your browser, so the recording itself is not uploaded and what reaches us is the text you review before saving; service telemetry (logs, model usage counts); and, separately, employer account data for the companies we work with. You are never charged anything, so we hold no payment data about you as a job-seeker; Stripe is used for employer purchases, and card numbers are never stored by us.
Optional browser analytics is off by default and can be enabled or withdrawn on the Cookies page. Its event names and properties are restricted; CV and message text are not analytics fields. The server also records operational events needed to run the service. Where linked to an account, analytics identifiers are hashed rather than stored as email addresses. Hashed identifiers are still personal data. Retention depends on the configured scheduler, as described below.
3. Lawful bases
We process account and application information to provide the service you request, operational records for service security and abuse prevention, and employer accounting records for the employer relationship. Optional browser analytics, voice processing and employer sharing have separate controls. The applicable legal bases and regional notices must be reviewed for the operator and the countries actually served; this beta notice does not certify international compliance.
4. Sensitive and special-category data
We do not infer special-category data (ethnicity, health, religion, sexual orientation, trade-union membership) from your CV, voice or behaviour. Where an employer's form asks demographic/compliance questions, the question is passed to you to answer or decline; your answer is stored as a user-declared fact and used only to complete that field. Those categories are also filtered out of anything we disclose to an employer: the employer's candidate view can only return facts your share record lists, and it drops anything marked sensitive or recorded as not confirmed by you.
5. AI processing
Profile parsing, matching and application preparation can use deterministic rules without sending data to a model provider. Optional model enhancements are disabled by default. When enabled, a configured provider may receive the profile evidence and job text needed for that task; a failed request may fall back to another configured provider. Providers can include Microsoft Azure, OpenRouter, Google or Amazon. Their applicable processing and retention terms must be confirmed for the configured service. Generated documents are checked against your evidence, and you should review them before submitting.
6. Automated decision-making
Job fit scoring and application ordering produce recommendations. Missing evidence or eligibility answers can pause preparation. Review recommendations and documents before applying; the beta workflow sends you to the employer's website for submission. Optional worker workflows require separate configuration and your authorization. You can edit your evidence and preferences and pause your campaign.
7. Sharing
Employer sharing is off by default. An introduction requires your approval for a named company and role, with a preview of the exact confirmed values to be shown. Contact and eligibility facts are excluded from that profile preview. After approving, you may exchange messages with members of that company in a conversation about the role; anything you type there is shared, including contact details you voluntarily include. Withdrawing access stops employer reads and new messages in the app, while you retain your own conversation history until account deletion. It cannot recall information someone already copied. Disclosure records are visible in Profile. We do not sell profiles or share them with advertisers.
The service uses Firebase for authentication and stored records and a configured hosting provider. Optional integrations may include the model providers described above, Stripe for employer purchases, and the configured transactional email provider. A deployment-specific provider and processing-region register must be confirmed before wider launch; a fallback model may use a different provider. Dictation uses your browser's speech-recognition service, which may process audio remotely. The app receives text and does not store audio recordings.
8. International transfers
Data can be processed outside your country by configured hosting, database, inference and browser speech services. The operator must verify the actual processing regions, applicable transfer safeguards and provider agreements before enrolling a country cohort. This notice does not assert that a specific transfer agreement has already been executed.
9. Retention
Profile, evidence and application records are kept while your account is open. Request deletion in Profile. Processing is paused while cleanup runs; if it is interrupted, the app reports that cleanup remains and a retry or configured scheduler can resume it. Success is reported after application records, generated documents, declarations, disclosure records and the sign-in account are removed. Employer access through the app ends, although we cannot recall files already downloaded. An employer's own accounting records may be retained with candidate references removed.
Raw analytics events have a 180-day retention policy, enforced by the configured scheduler. Historical daily metrics retain numerical counts rather than device hash sets; temporary current-day memberships remain personal data. Deletion removes linked account events and memberships. Dictation uses the browser's speech-recognition service, which may process audio remotely. The app receives text and does not store an audio recording.
10. Your rights
Access, rectification, erasure, restriction, portability (machine-readable export), objection, and withdrawal of consent — exercise these in-app (dashboard: Employer sharing for the consent and its disclosure log, Export my data, Delete my account) or by email. We respond within one month. You may complain to the ICO at any time (ico.org.uk) — we would rather you told us first so we can fix it.
11. Cookies and local storage
Firebase Auth stores the session needed to sign in. Local storage also remembers optional analytics consent. Browser analytics identifiers are created only after you enable that option; withdrawing it removes those identifiers from the browser. The app does not include advertising pixels. See the Cookies page for the control and details.
12. Security
The service uses encrypted connections and Firebase storage. App data routes verify sign-in and scope access to the account or current company membership; employer reads also check the approved disclosure and current consent. Job records are accessed through server routes, including private imports. Application changes have audit records. Operational configuration and secret storage must be reviewed for the deployment. These controls reduce risk; they are not a certification that every integration or deployment is secure.