5 items
On job pages, see how the role fits your résumé and if the posting looks current, then fill the application from your résumé. Velai checks the job you're looking at before you apply. On the main job boards and applicant-tracking sites, a small Velai card shows up on job pages by itself (on a page that doesn't publish its job details, when the page reads as a job or Velai has the role). It gives your fit for the role and what's known about the posting: whether it looks actively posted, when it was posted, what it pays and the apply-by date. Every line says where it comes from, the page or Velai, and anything nobody knows is left out rather than guessed. On company careers sites, turn the card on once from the welcome page or the panel, for every site or just one, and it shows there too. Chrome asks you first. Or click the Velai button on any page. Your fit. Add your résumé on velai.app, free and with no account (it stays in your browser), and you get the same fit label velai.app gives, with its reasons: how closely the role matches your experience, its level against yours, and whether it's in your country. The card and panel show the words in the role's title that the fit counts, ticked when your résumé has them, and similar roles on Velai carry their own fit label. Your résumé for this role. The panel proposes changes to your résumé for this job: lines reworded in the job's words, your summary, and the lines and skills the job asks for moved first. Each shows your own text beside the proposal and why, and you accept or reject it. Nothing changes until you accept it, and any rewording uses only words already in your résumé, so nothing is made up. Download your résumé with the changes you accepted as a one-page PDF, or copy the text. For bigger changes, edit your résumé on Velai in a small window; the job is checked again when you close it. Fill the form. On a job's application form, "Fill from your résumé" fills in your name, email, phone, location and links from your résumé and attaches your résumé as a PDF with the changes you accepted for that job (as you wrote it if you accepted none). Fields that are already filled, drop-downs and check boxes stay yours. You check the form and send it yourself; the extension never sends one. Answer the questions. Under a form's free-text questions ("Why are you interested in this role?", "Describe your experience with…"), "Draft an answer" writes a draft from the lines of your résumé that bear on that question. It never drafts the questions that are yours alone: work authorization, pay, demographics, start date, relocation, background checks, consents. A draft is marked as a draft from your résumé, says which résumé lines it comes from, and goes into the form only when you pick "Insert in the form". With a paid month on Velai, a sealed AI writes the draft from those lines. Check every claim before you send the form. Track it (signed in to Velai). "Save" next to "I applied" puts the job in your Velai tracker's Saved column, without saying you applied. Once the site confirms an application the card filled, the job goes into your tracker as Applied. Applied some other way? Pick "I applied". Signing in happens in a small window over the job page. It closes itself when you're done and the job is checked again, no second click. You can also select a job title on any page, right-click and choose "Search Velai" to see matching roles from company careers pages. How it treats your data The card reads job pages only on the job sites it lists and on sites you turn it on for, and on those it checks each page inside your browser and tells Velai nothing about pages that aren't jobs. Anywhere else, the extension reads a page only when you click its button or choose "Search Velai". Without a paid month, your résumé is the one velai.app keeps in your browser: the extension reads it on velai.app's own pages and keeps the same copy in Chrome's storage on your computer, replaced or removed when you change or remove it on velai.app, and never sends it anywhere. With a paid month, your résumé comes from your Velai account, where it is saved encrypted, and the extension holds it in memory only, never in Chrome's storage. Your fit and the changes proposed to your résumé are worked out inside the extension, and your résumé with the changes you accepted stays in your browser until you download or copy it. For each job you reviewed, the extension remembers which proposed changes you accepted or rejected, as short codes with none of your résumé's text. Checking a job sends only its title and employer to Velai. When you fill a form, your contact details go from your résumé into that form inside your browser, and the site gets them only when you send it. When you pick "Draft an answer", the question, the job's title and employer and the few résumé lines that bear on the question, without your name, email, phone number or links, go to an AI model on a sealed server (Tinfoil's), which is part of a paid month: the extension first checks that server's hardware proof and encrypts the request to it, so Velai's servers pass it on without being able to read it. Without a paid month, or if sealed AI isn't available or can't be verified, nothing is sent and the draft is those résumé lines as they are. The extension keeps no copy of a draft. Signed in, it uses the velai.app sign-in in your browser and never sees your password. Your fit, the résumé changes, form filling and the drafts need only your résumé on velai.app, free and with no account. The job checks need nothing. The tracker needs a Velai account, and a sealed AI writing the drafts needs a paid month.
Nov 1, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.