On a phone, the import review's bottom bar stacks: the count on one line, a full-width Add button under it, instead of a half-empty wrapped row.
On a phone, the fit report's section links no longer scroll sideways; they wrap, so Responsibilities and Expand all are on screen.
The notes AppliAid leaves on an import review ("Read with low confidence") are now written for you: which record, what was read, what was done with it, in a plain sentence. They used to cite the parser's own rules and field names.
The home page, the walkthrough and the Start page now describe the same sequence, in the order AppliAid runs it: the posting first, then your CV, the questions, the verdict, the documents.
Projects are counted one way everywhere on the import review and the landed screen: projects under positions and standalone projects, named as such.
On the Conversation, the three opening questions no longer carry a priority word, and on later questions the word is set in plain ink rather than the colour a gap uses.
Pasting a link instead of a posting, on New fit or on the first screen, now says that AppliAid cannot open links and asks for the text. A posting too short to be one now says so on the first screen too, instead of reloading the form in silence.
In the Conversation, Cmd or Ctrl + Enter saves the answer.
An answer you have typed or dictated in the Conversation now survives a reload of the page. It is kept in your browser tab until you save or dismiss the question, and nothing reaches your graph until you save.
Dismissing a question, or skipping the opening ones, now offers Undo on the line that confirms it. The questions come back exactly as they were.
A fit you started and walked away from now shows on the Postings page and on New fit while it runs, with its steps, and the row it is for says Fit running. When it finishes, you are taken to the report.
On the import review, the margin now lists the records AppliAid was least sure of, least sure first, each a link to its row, so the ones to read before keeping are one click away.
The Add to your graph button on the import review waits until the page is ready before it can be pressed, so a press on a slow connection no longer goes through with nothing changing on screen.
On a fit report that came back poor, the filled button is now Generate questions, and once those are asked it is New fit. The documents are still one click away as links. The report also ends on its tally and that same next step, so you are not sent back to the top.
On the report, only must-have partials and gaps open by default; nice-to-have and responsibility cards fold to one line each, with Expand all and Collapse all beside the section links.
After an import lands, one filled button: Run the fit when a posting is waiting, otherwise Run a fit. Answering the questions and seeing your graph are still there, less loudly.
While a CV is being read, Discard this import is available on that page, for a wrong file. The read still counts as a run.
An account you open every day without signing in again no longer looks inactive: the date you last opened AppliAid is kept (one small cookie, today's date only), it resets the 12-month deletion clock, and the privacy policy says so. If you subscribed with a promotion code, the code is kept with your subscription record.
If the connection drops while AppliAid reads a CV you uploaded on Import, the page now reloads and shows the CV as waiting for your review, or as still being read, instead of saying something went wrong.
Reloading the page while AppliAid reads the CV you attached before signing up no longer reads it a second time. You land on Import, where it shows as still being read.
If you attached a CV before signing up and the connection dropped while AppliAid was reading it, you saw "Something went wrong. Nothing was changed" even though the CV had been read. You now land on Import, which shows the CV as waiting for your review, or as still being read.
A new page, One record, two postings (/example): the founder's own CV against two of the invented sample postings, every must-have shown with its status and the judge's reasoning, one verdict apply and one skip. Linked from Should I apply?.
If you cancel and pick a reason from the list Stripe shows, that one word is kept with your subscription record; the privacy policy says so under Payment records. Nothing you type in the comment box is copied.
Each next-step email now carries a one-click link that stops them for your account without signing in, and your mail client's own Unsubscribe button works on them too. Settings can turn them back on.
A new page, Should I apply? (/should-i-apply): the rule AppliAid uses for a posting you do not fully meet, written as advice you can apply by hand, with the fit check at the end. Linked from the footer and from Fit check. The Fit check page also now says correctly that a poor fit gets the recommendation skip, not develop.
If you stop partway through the free pass, AppliAid now sends a short email a day later saying what the next step is: the CV, the first fit, the resume, and after the free pass what the subscription adds. At most four, each once, none once you subscribe, and a switch in Settings turns them off.
A new page, Fit check (/fit-check): the same box as the home page on its own address, with a plain account of what a verdict is and four questions answered, for anyone who arrives looking for a fit score rather than for AppliAid. Linked from the footer.
The privacy policy says the usage counts now note which site or campaign link a visit came from, whether it was from a phone, and whether a crawler made it, and that the pricing, start and scoring pages are counted as well as the home page. The Usage counts switch in Settings covers all of it, as before.
Subscribing asks you to tick a box agreeing to the renewal terms before you pay: $34.99 a month, renewing until you cancel in Settings. Right after, an email sets out the price, the next charge date, how to cancel, and the refund and price-change rules. The Subscribe button at the edge of the free pass now carries the same renewal terms as the one on the pricing page.
The terms name Trophe Labs LLC as the company that runs AppliAid, set out the renewal terms in full, and add an arbitration section you can opt out of within 30 days by writing to support@appliaid.com. The privacy policy names Trophe Labs LLC as responsible for your data. The 120-run monthly limit resets when your plan renews instead of on the 1st, and answers to intake questions stop at it as well as counting toward it.
Subscribe and Manage billing no longer fail with a server error for an account whose Stripe record is gone. Subscribe opens a fresh checkout; Manage billing says on Settings that the plan is not billed through Stripe. Deleting such an account works too.
When AppliAid reads a CV, nothing appears twice. A committee seat or a volunteer role that it recorded under a job no longer also shows up in the import's "Not placed" list, and "References available on request" is no longer listed as something it could not place. It was intermittent, about one import in three.
A new setting, off unless you turn it on, for accounts opened from today: Keep my corrections as examples. With it on, correcting something AppliAid read from your CV keeps that one line, what AppliAid made of it, and what you wrote, as an example we use to check that AppliAid reads CVs correctly. Settings lists every example kept and deletes any of them; turning the setting off deletes all of them. Nothing is used to train a model, nothing changes in the product either way, and lines touching health, religion, politics, union membership, ethnicity or sexuality are never kept. The privacy policy and the terms both say so, and outside counsel reviewed the flow before it was built.
A skill claim on the graph page shows its provenance only when you stated it. Every claim is read from your CV unless marked stated, and the section says so once, instead of every row repeating the word imported.
The import review screen lists what AppliAid read but could not place, under its own "Not placed" heading with the kind of thing named (a grant, teaching, a committee seat), instead of as lines among the low-confidence notes. The fit judge reads a compound requirement part by part before weighing evidence: a requirement joined by "or" is met by any one part, a span of stages needs its first and last stage evidenced, and a list of activities is met by the most demanding one. Repeated reads of the same posting now land on the same status more often, and the rationale says which part carried it.
The privacy policy's note on corrections now covers edits as well as deletions, naming the field that changed and never its content, and a second note records when a CV held something AppliAid has no kind of record for, as the word for its shape. Same Settings switch turns both off. When AppliAid reads a CV, anything it could not place now appears in the import's notes as "Not placed", with its shape named, instead of being folded into the nearest record or lost.
On a 320px screen the Start for free button no longer covers the Attach your CV label on the home page; it drops to its own line. The tab on the page for a wrong address reads "Nothing at this address".
How scoring works, the terms, the privacy policy and this page are on the same layout as the pricing page: the page ground, a rail of facts on the left (the weights and the strong threshold, the effective date, the number of changes), the text in the reading column, and the table of contents in the margin. The "Back to AppliAid" link above each title is gone; the header is one click away. Nothing in the text changed.
Settings leads with Billing, then the resume length, then three switches that say what is on ("Ask me how it went", "Use my corrections to improve AppliAid", "Count how I use AppliAid") instead of three "Do not" boxes. The postings list drops its second rule, moves "How did it go?" under the verdict it is about, and the tab reads Postings. The app footer links to How scoring works and the changelog. A button that is waiting is drawn empty with faint text instead of filled grey, and the sign-in button no longer waits for the bot check to load before it can be pressed. The error page is on the same shell as every other page. A resume preview shows, after each bullet, how many records it cites; that was a tooltip. The sample mark on a posting is a square word like every other mark.
The graph page is on the same shell as the rest of the app: the records in the reading column, and beside them the counts, the section list and the key to imported, stated and defining. Edit and Delete on every record are visible at rest instead of appearing when the pointer crosses the row, every record's provenance sits in a column of its own so the statements start on one line, and skill claims show their provenance too. What a defining project means is said once, in the key, instead of under every list. An expired certification's date is drawn in the same red as every other warning; its colour was undefined and fell back to black.
The conversation asks one question at a time. The question and the answer box are in the reading column; why the question was asked, the count, and the titles of what is left wait in the margin. When an answer saves, one line above the next question says what it became, with a link to it on your graph, and the next question is already there. Before, every open question from your postings sat fully expanded down the page, and a saved answer showed a Next question button that only reloaded the page.
An import left open across a change to how CVs are read can now be discarded, from the Import page and from its own screen. It used to sit as "waiting for your review" for good, with a button into a page that could only send you back. The review screen and the Import page are on the same shell as the rest of the app: the checklist and the upload box in the reading column, what was found, how the confidence marks read, and past imports in the margin.
New fit and the first screen a new account sees are on the same page shell as the rest of the app, with the paste box in the reading column and the sample postings in the margin. Every page loads into a placeholder the same width as the page, instead of a narrower one that widened.
The posting page leads with the report. The score, the verdict and the summary come first, then every requirement, then the documents and the two-week questions. One filled button offers the next step for that posting (the resume, then the cover letter, then the interview prep) and the other actions are links beside it; before, five equal buttons sat above everything with Re-run the fit as the biggest. An open requirement shows the reasoning and the evidence side by side, the evidence score shows on a phone, and the tab is named after the role and the company.
The edge of the free pass is a panel with a Subscribe button in it, on the page where you pressed. It was a red error box that said to see the pricing page and did not link it. After checkout, Stripe sends you back to that page with a note that the plan is active, not to Settings.
One vocabulary across the product. An answer is saved to your graph, not landed; a fit is a fit, not a fit run or a fit analysis; AppliAid reads your CV, not an engine or a parser; and the record is called your graph on both sides of sign-in. Button labels say what they do: Save answer, Next question, Generate questions, Re-run the fit, Send again.
The fit summary and every requirement's reasoning are written to you, as "you", in at most ninety words. They were written about "the candidate".
The notice after a sign-in email is sent now says the link expires an hour after it is sent. It used to say only that it expires soon.
The privacy policy's retention line says Vercel keeps request logs for one day. It said one hour, which was true of the plan the app was on until today.
The sign-in form has a bot check by Cloudflare and a limit on how many sign-in emails one network address can ask for, after a machine spent four days feeding other people's addresses into it. A person sees nothing unless Cloudflare is unsure, in which case one click.
Signing in with the emailed code lands you on your postings with the header and footer in place. Before, they were missing until you reloaded the page.
Fourteen days after a fit run, the posting's page asks whether you applied and whether you heard back, with fixed answers. Once per run, skippable, and Settings can turn it off for every run.
This page, linked from the footer.
A table of contents beside the privacy policy, the terms and the scoring page on a desktop screen, and anchors on those pages land below the header instead of under it.
Sign-in links now work in whichever browser opens them, for their whole lifetime. Before, a link opened more than five minutes after it was requested failed, and so did one opened on a different device from the one that asked.
Both sign-in emails carry a numeric code as well as the link, and the code can be entered on every screen that sends one, including the screen shown when a link has failed.
Settings has a switch that stops AppliAid counting how you use it and deletes the counts already stored.
The privacy policy says how long usage counts and server logs are kept, with the figures.
A cover letter and an interview brief now say what your part in a publication was, when you have told the graph.
The fit judge reads how proficient you said you are in a skill, for how many years, and when you last used it.
Delete your account from Settings. It is a real deletion, at once.
Skill claims are listed on the graph page and can be edited or deleted there.
Each verdict on a fit report links to the record it rests on.
The privacy policy names all five processors, including Stripe, and says the usage count carries the domain of your sign-in address.
The position editor on the graph page opens again.
A page on how scoring works: what the engine reads out of a posting, how each requirement is judged, how the judgements become a score, what the bands mean, and what it will not do. Linked from the footer and from the pricing FAQ.
The privacy policy names Deepgram as the processor for spoken answers and says how long a recording lives.
The landing page holds together on a 360px phone, the app navigation no longer hides half of itself, and loading states stop dragging the page sideways.
A new look across the site and the app: one type scale, one set of controls, and the same chrome on both sides of sign-in.
The pricing page is rebuilt in the order a visitor decides, and stops ending on the refund clause.
The emailed sign-in code accepts codes of six to ten digits. It only accepted six, and the project sends eight.
Signing in with the code keeps the posting you pasted before signing in.
A resume no longer calls a publication peer-reviewed unless the record says so.
Paste a posting on the landing page without a CV. It is held, unread, for 24 hours or until you sign in.
Attach a CV on the landing page before you have an account. It is held, unread, for 24 hours or until you sign in, and the notice under the box says so.
The posting comes first: paste it, then import your CV, and the first fit runs only when you ask.
The sign-in flow has real states: sent, expired, already used, wrong browser, each with one sentence and one action.
The privacy policy says how long everything lives and names the second cookie.
The FAQ, the hero paragraph, and a follow-up conversation that is bounded and can be dismissed.