Last updated 24 August 2026 · build 5cdcb2c
You are about to give a piece of software your work history, so this says exactly what happens to it - including the parts that are not finished. If you only read one section, read the one about your data leaving the UK.
Tragic Talent operates this site at www.tragictalent.uk and is the data controller for the personal data described here. That means we decide what is collected and why, and we are the people you hold responsible for it.
We have not yet published a monitored contact address for privacy requests. This is a gap and it is stated rather than hidden. Until it is filled, the controls described under your rights are the reliable route: your account page can change your name, change your passphrase and delete everything, and those act immediately without anyone needing to read a message.
You can complain to the Information Commissioner's Office at any time, and you do not have to contact us first: ico.org.uk/make-a-complaint.
Five things, and the second and the third are the substantial ones. We do not buy data about you, we do not enrich your profile from other sources, and there is no tracking on this site at all.
Your email address and the name you give us. Your passphrase is stored only as a one-way hash, so we cannot read it and cannot tell you what it is - which is why resetting it is the only recovery route.
The file you upload, kept byte for byte, and the individual facts extracted from it. Those facts fall into ten categories: employment, education, skills, certifications, projects, languages, achievements, contact details, preferences, and work authorisation. Each one is stored with a pointer back to the exact characters of your CV it came from, so that anything we later say about you can be traced to the sentence it came from rather than asserted.
The questions employers put on their forms that a CV does not answer, given once here and reused: whether you are allowed to work in a given country and whether you need visa sponsorship there, which country you live in, which country you intend to work from, the town or city and your postcode, your legal first name and the first and last name you go by where those differ, whether the name on your account is your full legal name, who you work for now and your job title, your notice period, whether you are under a non-compete, how you heard about the role, whether employers may email you about other openings, whether you would move to a country for a job, whether you are willing to work from an office and whether you would be in an office five days a week, links to your LinkedIn, GitHub and your own website, and every company you have worked for.
One more, and it is worth its own paragraph because of what it is: some employers ask, as a required question, whether you are a citizen or resident of a country under sanctions. Twilio names Cuba, Iran, North Korea, Syria and the Crimea region of Ukraine. We ask you that question in exactly those words and store your yes or no, and it is used only on a form naming exactly those five places. An employer that names anywhere else is asking a different question, so your answer is not reused there and the application waits for you.
Two of those are worth calling out, because they are about your present job rather than your history: who you work for now and what your title there is. Employers ask for both on their own forms and we store what you type so you do not type it again. Neither is used for anything else, and neither goes anywhere except onto the form of an employer that asks for it.
Each answer is stored with the date you gave it, and most of them stop being used after a while - six months for the two right-to-work answers, three months for a notice period, and a year for the ones describing where you live and work and what you do now, meaning your country, the country you intend to work from, your town and postcode, your current employer and job title, the non-compete answer, the three about moving and working from an office, and the sanctions declaration. That is a safety limit rather than housekeeping: an out-of-date “I am allowed to work here” is a false statement made to an employer in your name. An answer that has lapsed is not deleted, it stops being used until you confirm it, and the screen tells you which ones those are.
The list of companies carries one extra thing: a tick saying the list is complete. It is the only thing in this product that turns an absence into an answer - it is what lets a form asking whether you have worked at a particular company be answered no when that company is not on your list. Untick it and those questions are left for you instead. That tick is on the same kind of clock as the answers, and lapses after six months.
One question on those forms is never put to you. Employers ask whether you are currently located in a particular country - Mozilla asks it about Spain, Sweden and Canada - and rather than put a second version of a question you have already answered on the screen, we answer it from the country you have already given. Nothing is stored for it: no row, no date and nothing to expire, because it is worked out again for each form. What you should know is that it is still an answer sent to an employer in your name and never shown to you before it is sent, that it is a yes only where the country on the form is the country you gave us, and that changing that country changes every one of these answers at once.
The occupations you choose to apply in, your limits - how many applications in total, how many a day, how many per company, the lowest fit score you will accept - and whether sending is switched on.
A record of every application prepared and every application sent, including the text that was written for it, plus a security log of significant actions on your account.
A CV very often contains information the law treats as special category data - health and disability, ethnicity, religion, trade union membership, sexual orientation, political opinion - along with things like nationality, immigration status and your home address. We do not ask for any of it in your CV and we do not want it there.
One exception, and it is deliberate. The answers screen asks you directly whether you are allowed to work in a country, whether you need visa sponsorship, which country you live in and your postcode. Employers ask those as required questions on nearly every form, and the only alternative to asking you is inferring it - which would mean a language model making a statement about your right to work, in your name, to an employer. So they are asked in plain words, they are stored as you gave them, and they are used for one thing: answering the same question on a form. None of them is special category data under the law. They sit close enough to it that asking rather than guessing is the entire point, and it is also why an answer you have not given leaves the field blank and stops the application rather than being filled in for you.
A second exception, narrower. When an employer's form asks a self-identification question - race, gender, disability - and offers a way to decline, we decline. When the form requires an answer and offers no way to decline, as South African employment-equity questions often do, the answers screen shows you that employer's exact question. Your answer is special category data: it is stored as you gave it, against that employer and that question, and used only to answer that question. No language model drafts, suggests or infers it, and if you do not answer, that application stops.
Where the parser recognises information of that kind it flags it, and the flag has a specific consequence: a flagged fact is withheld entirely from the language model and from anything written on your behalf. It is dropped, not masked, because a placeholder would still tell the model something was there. Everything that survives that filter is then put through a second redaction pass on the assumption that the flag is incomplete - because it is: the flag is set once when your CV is read, and you can edit a fact afterwards.
The same rule is applied separately in each of the four places your facts are used - writing the plan for a document, writing the text of it, assembling the contact lines printed on it, and scoring how well a job fits you. Four filters rather than one is deliberate: any one of them being removed by mistake leaves the other three standing.
Three honest limits. First, this detection is pattern-based and cannot be complete - it recognises the shapes this information usually takes, not every possible phrasing. Second, a flagged fact is still stored, because it was in the document you gave us; what the flag governs is use, not existence. Third, and most precisely: at the points where data goes to the language model or onto a document, flagged facts are filtered out rather than the operation being refused. A refusal - the system declining to act at all because it detected personal data - is a control this product has, but it guards the security log and the account-wide stop reason, not the model. We would rather say which is which than let one word cover both.
So the practical advice is the honest one: remove information you would not want an employer to see from your CV before you upload it. Nothing in this system needs it, and the strongest control over data is the data never arriving.
This product scores how well each job posting fits you and ranks postings against each other. That scoring is automated, and it decides which jobs get applied for. Three things constrain it, and they are defaults rather than options you have to find:
No decision made here has a legal effect on you: we apply for jobs, and employers decide whether to interview or hire. If you want to know why a particular posting was chosen or scored the way it was, every fact used is traceable to the part of your CV it came from, and you can ask us to explain it.
We do not sell your data and we do not share it for advertising. There is no advertising on this site. Your data goes to four kinds of recipient, all of them because the service cannot work otherwise:
When an application is sent, the employer receives it - that is the point of the product. Today only one hiring system can be submitted to directly. For every other employer we prepare the application and give you a link to their form, and nothing is transmitted by us; you send it yourself or you do not. Every application, sent or prepared, is listed in your account.
Facts derived from your CV are sent to a model hosted by Microsoft on Azure AI Foundry, in the United States, to write each application against a specific job posting. What is sent is the filtered, redacted projection described under special category data - not your CV file, and not the facts we flagged.
us-east-1 (United States). Your CV file and every fact derived from it live there.iad1 region (United States).We use a third-party service to collect public job postings from employers' career sites. It receives search criteria and returns postings; it is not sent anything about you.
Stated plainly because it is the thing people are least likely to guess: this service is not hosted in the UK. The database, the website and the language model are all in the United States. Your CV is stored in the United States.
Transfers of UK personal data to the United States are permitted where an approved safeguard is in place with each provider - the UK Addendum to the EU standard contractual clauses, or the UK extension to the EU-US Data Privacy Framework. These are the mechanisms we rely on with the providers named above.
The database region cannot be changed after a project is created, so moving this to a UK or EU region would mean migrating to a new database rather than changing a setting. If that matters to you, it is better to know before you upload than after.
HttpOnly so no script can read it, Secure so it never travels unencrypted, and carries a __Host- prefix that the browser itself enforces.One cookie, and it exists so you can stay signed in. It is called __Host-jr_session, it holds a session identifier and nothing else, and it expires seven days after you sign in or after 48 hours of not using the site, whichever comes first. Signing out deletes it.
There are no analytics, advertising or third-party cookies here. Because the only cookie is strictly necessary for a service you asked for, we do not need to ask your permission for it - which is why this site has no cookie banner. That is the rule working as intended rather than an omission.
Your uploaded CV, and every document written for you, stop being readable 180 days after they are written. That clock starts at upload for your CV and at the moment of writing for each application document, so a document prepared in March goes before a CV uploaded in June. When it passes, the file is refused to everyone including you: the download link stops being offered on your applications and the file itself is no longer served. The facts read out of your CV are not on this clock - see below.
Two things are worth separating here, because they are not the same promise. Refused happens on the deadline, in the database query, with no job needing to run. Deleted from disk is done by a sweep that runs hourly in the part of the system that does the work, and if that part is not running the row is unreadable but still on disk. So the honest statement is: after 180 days nothing and nobody can read the file through this service, and it is removed entirely on the next sweep.
Your account, the facts read out of your CV, the answers you gave once, your occupations, your campaigns and the record of every application are kept until you delete them. We do not expire inactive accounts, which means an account you abandon stays until you come back and delete it. That is a real limitation rather than a feature, and the control that answers it is in your hands: deletion is immediate and complete.
Internal job records - the bookkeeping for work queued on your behalf - are deleted seven days after they finish, by the same hourly sweep, with the same caveat. Our security log keeps identifiers and what happened, not content: there is a check that refuses to write an audit line containing an email address or a long run of digits.
Deleted data can also persist briefly in database backups. Our provider keeps a point-in-time restore window, and until that window rolls past, deleted rows remain recoverable by us from a backup - they are gone from the live system immediately and from the backups when the window passes.
Under UK data protection law you have the right to see your data, correct it, delete it, restrict or object to how it is used, take it elsewhere, and withdraw consent. Here is specifically how each one works here, including where it does not work well yet.
Your CV page has a delete that removes your candidate record, your CV file, every fact read out of it, your campaigns and your applications, in a single database transaction, and tells you how many records went. It is not a request that gets queued for someone to action.
Two things it cannot undo. Work already queued for you is allowed to run and finds nothing, which is intended. And an application already in transit to an employer cannot be recalled by anyone.
You can change your name and your passphrase on your account page. Both take effect on the next application written for you.
You cannot edit an individual fact read out of your CV. This notice said you could, on the CV page, and there is no such control there or anywhere else - it was a description of something that had never been built. What does work is replacing the whole set: uploading a corrected CV deletes every fact that is no longer in it and keeps the ones that are, so nothing lingers from the old file. Download your data first if you want to see what is about to be replaced.
Your account page has a download that gives you everything this product holds about you as a single file: the facts read out of your CV - each with the page and the character range it came from, so you can check it against the original - the answers you gave once, each with the date you gave it, your occupations, your campaigns, and every application including the ones that failed. The file also names what it leaves out, which is the CV file itself, the documents written for each application, and the audit log of what the system did. Those gaps are in the file rather than only in this notice.
In the product itself, your occupations are on the lanes page and every application is on the board.
No screen shows you the facts read out of your CV. The CV page shows the file's size, how long ago it arrived, when it deletes itself and a fingerprint of its contents - and this notice used to claim your facts were on it as well. They are in the download above and nowhere else. That satisfies the right of access and it is still worse than a screen, because a person checking whether we have understood their CV should not have to read JSON to find out.
Turn sending off, delete your CV, or delete your account. Each takes effect at once, and the account-wide stop button halts everything in progress.
This service is for people aged 16 or over. A CV is a detailed record of a person, and the reason for the floor is that below it we would be relying on a parent's consent that we have no way to obtain or verify.
The sign-up page asks. Creating an account requires ticking I am 16 or over, the box starts unticked, and the check is made on our server rather than in your browser, so it is not something that can be clicked past. Until 2026-08-24 nothing asked at all, which made the paragraph above a rule rather than a control.
What you tick is a declaration, and we do not verify it. We do not ask for a date of birth and we hold nothing that could check one against, so somebody under 16 who states otherwise will get an account. What changed is that they have to state it. We would rather say so than let a tick box imply an age check we have not built.
We also do not keep a record that the declaration was made. The check happens and nothing about it is stored, so we could not show afterwards which accounts confirmed it.
This matters most to the group most likely to be affected: a sixth-form or school student looking for a first job. If you are under 16, please do not create an account; if one has been created, deleting it on the account page removes everything at once.
We are stating all of this rather than writing "we do not knowingly collect data about anyone younger" and leaving it there, because the honest reading of that sentence is that we have arranged not to know.
Listing this is unusual and it is deliberate. A notice that reads as finished when it is not is the kind of document that makes people trust a system more than the evidence supports.
We have not published a legal entity name, a registered address, or a data protection contact. We have not appointed a data protection officer, and have not assessed whether we are required to. This notice has not been reviewed by a solicitor.
You should weigh that when deciding whether to upload your CV. The technical controls described above are real and are in the code; the paperwork around them is not finished.
You can complain to the Information Commissioner's Office about any of this, at ico.org.uk/make-a-complaint.