Privacy Notice
PM Career Desk is a service of PME Consulting, Inc., 6545 Market Ave N, Ste 100, Canton, OH 44721 ("we", "us").
Summary
- We collect only what we need to run the tools and services you choose.
- Our public pages use Google Analytics 4 to count visits and the steps people take (cookies named _ga, up to 14 months), with Google signals and advertising features off. It does not run inside your account or at checkout, and it never receives your resume, your review or what you type into a form. If your browser sends Global Privacy Control or Do Not Track, we do not load it. We also keep our own first-party event log, with two cookies of our own on pmcareerdesk.com and its app (pmcd_lid, a random visit code, and pmcd_src, the source of the link that first brought you; up to 180 days). If you choose a language on our public pages, we keep only that choice in a cookie named pmcd_lang (up to 1 year), and if you close the note that offers a page in your browser's language, your browser's local storage keeps a key named pmcd_lang_offer_closed so the note does not return; neither identifies you.
- We do not sell or share your personal information, and we do not use it to train AI models.
- Reed, our resume analyst, is an AI. We do not have staff review your resume as part of the service. Our team reads only the notes you choose to send about a check from our Chrome extension, with a line of your resume only if you tick the box for it (section 16).
- You can download your data or delete your account at any time.
1. Information we collect
You give us:
- Contact details: email address, name (if you create an account) and US state. We ask for your state because some services work differently by state.
- Your resume and career content: the file you upload for a review, the answers you give in the career interview, the facts you confirm, and the documents we prepare for you.
- Your free review: with or without an email, the page of a free review and its link work for 30 days after it is ready; then the report is deleted, and the uploaded file sooner (section 9). If you give an email, we save the review under it and send you the link.
- Optional details you choose to give, such as whether you are job searching after a layoff. We use that only to show you relevant guidance and to plan our service, never for pricing, advertising or sharing.
- Recruiter emails and job postings you forward to us (Desk). These contain information about recruiters and employers (section 8).
- Your free Career file, if you open one: your email and the sign-in codes we send to it (no password, no resume), the list of your free results (which result it was and its counts, for example an archetype or how many lines a review flagged, never the text you gave), and the steps you mark. Without a paid plan it is kept for 180 days after your last visit, sign-in or new result, then deleted with its account; you can delete it any time from the file page (section 9).
- If you confirm your PM Archetype result by email, our website passes the result code and a coded form of your email (not the address) to our app, so the result can appear in a free Career file you open with the same email. If you do not open one within 30 days, it is deleted.
- Your choices and consents, for example whether you want our newsletter, and the plan you are interested in.
- Answers you give to optional research questions on the waitlist, and the test price you were shown.
Created when you use the Service:
- The free resume to job posting check (/tools/resume-job-match/ and the same check on our job entry pages) runs on our server: the resume and the job posting you paste are matched in memory by fixed rules and are not stored; we record one statistics row with the counts of the match and the type of role, without any text. Our Chrome extension uses the same check (section 16).
- The PM Archetype test, the resume line check and the title fit check run in your browser: your answers and the line you paste are not sent to us. The LinkedIn headline and About check runs on our server: the text you paste is checked in memory and not stored. For these tools, we record only that a tool was used and the type of result (for example, which archetype or how many findings), with a random result code. If you press Share my score, we keep a card with your section scores and the role we read (never your text) for 12 months so anyone with its link can see it; you can remove it from the card in the same browser at any time. Sharing is not offered when your browser sends Global Privacy Control or Do Not Track.
- Usage events: which pages and steps were used, the page version shown, and any campaign or referral code in the link you followed. Our public pages keep a random visit code (for example lead_3f9a0c1d2e4b5a6c) in a first-party cookie named pmcd_lid, and the source of the link that first brought you (for example seo, linkedin or claude) in a cookie named pmcd_src, both on pmcareerdesk.com and its app for up to 180 days, and add them to links to our app, so the steps of one visitor on our site, the free review and the LinkedIn check can be counted together. These events and the visit code do not include your name, email or resume text. To know which version of a page to show (for example the order of the plans or whether a plan is open yet), our public pages ask our app, sending only the visit code; the app stores nothing from that request.
- Account security data: sign-in codes and a session record.
- Technical data: your IP address and browser type, kept in security logs and, when you give or withdraw a consent, in the record of that consent.
From payment providers: Stripe and Link tell us the product, the amount and the payment status. We never receive your full card number.
2. Sensitive information
We do not need sensitive information such as Social Security or other ID numbers, date of birth, photos, immigration or work-authorization status, health information, ethnicity, religion or salary history. Please remove it before you upload. We try to remove it automatically before processing and we show you what we removed. If some remains, we process it only to produce your review, and only with your consent, which you give with a separate checkbox at upload and can withdraw by deleting your review. If we detect an ID, Social Security or bank number, we delete the uploaded file within 24 hours. We never use sensitive information for statistics, analytics or marketing.
3. How we use information
- To provide the tools and services you ask for.
- To sign you in and keep your account secure.
- To send emails you request or need: sign-in codes, your results, service notices. Newsletters and follow-up tips only with your consent.
- To apply state rules, for example which plans are offered in your state.
- To give referral rewards you earned (section 5).
- To understand and improve the Service using usage events that do not identify you by name.
- To comply with law, enforce our Terms and protect the Service against abuse.
We do not use your information for advertising, we do not sell it, and we do not share it for cross-context behavioral advertising.
4. AI processing and anonymous statistics
AI provider. Reed, our resume analyst, is an AI. To review your resume or draft documents, we send the relevant text to our AI provider, Anthropic, PBC, through Anthropic's commercial API, after we remove contact details such as email addresses and phone numbers. Under Anthropic's Commercial Terms of Service (version effective June 17, 2025), Anthropic may not train its models on our customers' content. Under Anthropic's published API data retention policy, Anthropic deletes inputs and outputs within 30 days, except that it may keep them longer (up to 2 years) if content is flagged for a violation of its Usage Policy, or if the law requires. Anthropic acts as our service provider under a data processing addendum. We do not use your content to train AI models, and we do not collect, use or sell personal data to train large language models.
No hiring decisions. Reed gives suggestions about your own resume. We do not make hiring decisions about you or anyone else, and we do not rate candidates for employers.
Anonymous statistics. We may combine the results of free reviews and quiz answers into statistics that cannot reasonably be linked to you or your device, for example the share of resumes in a group where our rules found a given pattern. We use the results of a review, never your resume text. We publish a figure only when it is based on at least 50 records, and we never publish resume text, names, employers, pay or any individual's results. We take reasonable measures to prevent these statistics from being linked to a person. We publicly commit to keep and use this data only in anonymous form and not to try to identify anyone from it, and we require anyone who receives it to make the same commitment. You can ask us not to include your future reviews by ticking the box at upload or writing to [email protected]. Statistics already published cannot be changed. Counts are rule matches made by an AI, not findings that any line is false.
5. Referral links
If you save your email with a quiz result, we link that result and any referral credit to your email so we can give you the rewards you earned. When a friend completes the test from your link, we record only that it happened, not who your friend is. When a friend completes a free review from your link, they give us their own email for their review, and we record the referral so we can credit you. We do not send emails to your contacts.
6. Cookies and tracking
Our public pages use Google Analytics 4, a service of Google LLC, to count visits and the steps people take on them (for example, opening the free review or choosing a plan). Google Analytics sets first-party cookies named _ga (including one that adds an ID after _ga_), kept for up to 14 months, and receives the page address without personal details, your browser and device type and an approximate location that Google derives from your IP address. We have turned off Google signals and advertising features, so this information is not used for advertising or to link your visits across devices. Google Analytics does not run inside your account or at checkout, and it never receives the resume you upload, your review, your email address or what you type into a form. If your browser sends a Global Privacy Control or Do Not Track signal, we do not load Google Analytics at all. Apart from Google Analytics and the language cookie described below, our public pages and our app set two cookies of our own on pmcareerdesk.com: pmcd_lid, a random visit code for our own event log, and pmcd_src, the source of the link that first brought you (for example seo or claude). Neither holds a name, email or text; both are kept for up to 180 days and are not set at all when your browser sends Global Privacy Control or Do Not Track. Those two cookies do not use local storage. Our public pages also have a language switcher. When you click a language link (in the header menu, the mobile menu, the footer or the note described next), the page sets a third cookie of our own named pmcd_lang on pmcareerdesk.com, which holds only the language code you chose (for example ru) and is kept for up to 1 year; our app reads it to show its pages in the same language. We do not pick a language for you by IP address or browser language and we do not redirect you. The cookie is set only when you choose a language, or when you open an address of our app that names a language (for example ?lang=ru). Unlike pmcd_lid and pmcd_src it is also set when your browser sends Global Privacy Control or Do Not Track, because it holds only the choice you just made and is not used to count or track you. If the first language of your browser differs from the language of the page and the page exists in that language, the page may show a note offering it. If you close that note, your browser's local storage keeps a key named pmcd_lang_offer_closed with the value 1, so the note does not come back. That key is not an identifier, stays on your device and is not sent to us or to anyone else; apart from it, our own scripts keep nothing in local storage. A few marks for the current tab (for example that the visit was already counted, the tool named in the link you followed, or the result or referral code of a test you just took) stay in session storage, which your browser clears when the tab closes; our scripts read them on your device and they hold no name, email or resume text. We also count page visits and steps with our own first-party event log that records the page, the step, the page version and any campaign or referral code in the link. Inside your account we use only necessary cookies: a session cookie that keeps you signed in (up to 14 days), a language cookie if you change the language (pmcd_lang, described above, up to 1 year), and a short sign-up cookie (1 hour). We do not track you across other sites. We also treat Do Not Track and Global Privacy Control signals as a request not to sell or share your information, which we already honor.
7. Who receives information
We disclose information only to service providers that help us run PM Career Desk, under contracts that limit their use of it:
| Provider | Purpose | Information |
|---|---|---|
| Anthropic, PBC | AI analysis and drafting | Text passages after contact details are removed |
| Cloudflare, Inc. | Domain name service, network security and secure connection to our server | All traffic to our service in transit, including uploads, and your IP address |
| Google LLC (Google Analytics 4) | Counting visits and steps on our public pages (not inside your account) | Pages viewed, steps taken, device and browser type, approximate location derived from your IP address, an analytics cookie identifier |
| Netlify, Inc. | Hosting of our public website, and storage of waitlist entries and site events | Waitlist entries (email address, state, plan choice, research answers such as when your interview is); site events; visitor IP address in request logs |
| Plus Five Five, Inc. (Resend) | Sending sign-in codes, results and emails you asked for | Email address, subject and message |
| Namecheap, Inc. (Private Email) | Our company email for support and privacy requests | Messages you send us |
| Stripe, Inc. and Link (Stripe's merchant of record service) | Seller of record for our paid plans and the Interview Coach Pass: checkout, payment, sales tax, receipts, payment support and refunds | Your payment and billing details, which they receive as the seller under their own terms and privacy policies |
We may also disclose information if the law requires it, to protect rights and safety, or as part of a sale or reorganization of the business, in which case this notice continues to apply.
Claude connector. If you use our tools inside Claude, the text you send is processed in memory to produce the result and we do not store it; we count which tool was used, with an anonymous code: a salted hash of the Claude session or of your connector sign-in, or, when there is neither, of the network, changed every 30 days; never your IP address itself. Your conversation with Claude is governed by Anthropic's terms and privacy policy.
8. Information about recruiters and employers (Desk)
If you forward recruiter emails to us, we process the names, business contact details and message content in those emails, which we receive from you, only to prepare drafts and records for you. We keep message bodies for 90 days, or while your account is open if you turn on "keep my recruiter history". We do not use this information to contact people for ourselves, to build profiles, or to sell. A recruiter can ask us to delete information about them by writing to [email protected].
9. How long we keep information
| Information | How long |
|---|---|
| Uploaded resume file (free review) | 7 days after your review is ready (24 hours if we detect an ID, Social Security or bank number) |
| Free review report (no account) | 30 days after it is ready |
| Free Career file (the list of your free results, step marks and your sign-in email, without a paid plan) | 180 days after your last visit or new result, then deleted with its account; with a paid plan, as your career record; delete it any time from the file page |
| PM Archetype result you confirmed by email, kept for a Career file you have not opened yet (the result code and a coded form of your email, not the address) | 30 days, then deleted, unless you open a free Career file with the same email; it then stays in the file |
| Email you left in "Open to a 15-minute call?" (with the date and the name of the free tool you used) | 90 days after you left it, then deleted; earlier if you ask at [email protected]. It is used only to write to you about one call and does not sign you up for any emails |
| Quiz result without an email | 12 months from your last visit |
| LinkedIn score card you chose to share | 12 months, or until you remove it |
| Waitlist email, state, plan interest and research answers | up to 24 months from signup, or 12 months after our launch email if you do not buy, unless you unsubscribe first |
| Referral credits | until the reward is delivered or expires, plus 12 months |
| Sign-in codes; expired sessions | deleted 24 hours after expiry; deleted 14 days after expiry |
| Career record, interview and documents | while your account is open, plus 90 days so you can export them; for a one-time Career Build, 12 months after delivery unless you keep a plan |
| Recruiter email bodies (Desk) | 90 days, or while your account is open if you choose |
| Records of sends and approvals (Desk) | 24 months |
| Security logs | 90 days |
| Usage events | 13 months, then only as totals |
| Billing records | 7 years |
| Records of your consents and requests | 4 years after our relationship ends, without the content |
| Emails you send to support or privacy | 3 years |
| Backups | up to 8 weeks |
| Notes you send from the Chrome extension with "Not right?" or "Was this check right?" (the line of the job posting, what the check said, your answer and, only if you ticked the box, one line of your resume) | 180 days, then deleted; earlier when you use Delete all data or Withdraw consent in the extension, or ask us |
After you unsubscribe, we keep only a one-way fingerprint of your address so we do not email you again. When you delete your account, the encryption keys for your content are destroyed, so copies in older backups can no longer be read. Our AI provider's retention is described in section 4.
10. Security
We encrypt your resume and career content with a key specific to your account, and we destroy that key when you delete your account. The files of your account (your resume, the facts you confirmed, your interview and the documents of your library) are stored encrypted with that key and are decrypted only in temporary memory while a step you start runs. Resumes tailored to a single job posting in Jobs and Desk are kept as separate files on our server, protected by its access controls, and are deleted with your account. We do not have staff review your content as part of the service; a person may access it only to fix a problem you report, or to investigate abuse or a security issue. Access logs do not record your email address or the content of your requests. No method of storage or transmission is completely secure. If a breach affects your information, we will notify you as the law requires.
11. Your choices and rights
- Access and export: download your data from your account settings at any time.
- Deletion: request deletion in your settings or by email. You can cancel within 24 hours; after that we delete your account and content and confirm by email within 30 days.
- Correction: edit your information in your account, or contact us.
- Email: unsubscribe from any marketing email with the one-click link in each email.
- Consent: withdraw any consent you gave, for example for sensitive details, by deleting the related review or writing to us.
- Your state's rights: depending on where you live (for example California, Colorado, Connecticut, Texas, Virginia and other states), you may have rights to know, access, correct, delete or obtain a copy of your personal data, to opt out of sale, targeted advertising and profiling (we do none of these), and to appeal our decision on your request.
How to make a request: use your account settings or write to [email protected] with the subject "Privacy request". We may need to confirm that the request comes from you, using your sign-in email. We answer within 45 days. An authorized agent may make a request for you with your signed permission.
Appeal: if we decline your request, you can appeal by replying with the subject "Privacy appeal". We will answer within 60 days and explain our decision. If you are not satisfied, you can contact your state attorney general.
We will not discriminate against you for using these rights.
12. Children
PM Career Desk is for working adults. You must be at least 18 to use it. We do not knowingly collect information from anyone under 18, and we delete it if we learn we have.
13. Where we operate
We operate in the United States. Our public website and free tools run on infrastructure operated by PME in the United States. Our service providers may process information in other countries under contracts that protect it. The Service is built for the US job market and is available worldwide: you can use our public website, free tools and Chrome extension from any country, and accounts and paid plans are offered in the countries our sign up and checkout pages show. If you use the Service from outside the United States, your information is transferred to and processed in the United States as this notice describes.
14. Changes
If we change this notice, we will update the date above. For material changes, we will tell you by email or in the product before the change applies, and we will not use information collected earlier in a materially different way without your consent.
15. Contact
PME Consulting, Inc., 6545 Market Ave N, Ste 100, Canton, OH 44721. Email: [email protected].
16. The PM Career Desk Chrome extension
The PM Career Desk extension for Chrome shows which requirements of a job posting are covered by the lines of your resume, lists the jobs you checked with the stage you set for each (with a reminder to follow up on an application, a count of the days to an interview date you entered and a file of the list you can download), and helps you start interview preparation for that job, or rework your resume for it, in Claude. This section explains what the extension keeps, when it reads a page, what it sends, how it reads a resume file you choose, what our server saves for you under a handoff code, what it keeps of the notes you choose to send about a check, how it compares your resume versions, and how to delete it. It describes version 0.9.0 of the extension. The same extension can run in Google Chrome and in Microsoft Edge; this section applies the same way in both (Microsoft Edge gives extensions the same storage areas named below).
What the extension keeps in your browser
- Your resume versions: up to three versions of your resume text (each up to 30,000 characters), which you paste or load from a file (PDF, Word .docx, .txt or .md; see Reading a resume file), each with a name you give it (up to 40 characters, for example TPM), kept in your browser's extension storage (chrome.storage.local) so you do not paste your resume for every job, with whether each was pasted or loaded from a file, the kind of file and when it was saved, and which version is your default. Only the text you save is kept, never the file itself. The names of your versions never leave your browser: when a version is sent to PM Career Desk, it goes under a label (v1, v2 or v3), never under its name. If you used an earlier version of the extension, the resume you saved there becomes the version named My resume. Your resume versions are not synced to your browser account.
- Your consent: that you agreed to the disclosure shown before the first check, with the date and the version of that disclosure.
- A random visitor id (for example lead_3f9a0c1d2e4b5a67), made in your browser. It is not linked to your name or email.
- Your recent checks: for each of your last 50 checks of a job posting, its job title, company, the name of the site (for example jobs.example.com), the page address, the overall result of the check as a short key (strong_fit, worth_applying, long_shot or none) and the date, kept in your browser's extension storage (chrome.storage.local) so the side panel can list them under Recent checks and Open again can open that page in a new tab. The text of the posting and the text of your resume are never kept there. A new check of the same page replaces its entry; the sample job and checks that did not work are not kept. Remove deletes one entry and Clear all deletes them all; Withdraw consent and Delete all data delete them too. Recent checks are not sent to PM Career Desk or anyone else and are not synced to your browser account. Since version 0.8.0, each entry also holds the stage you set for that job (Saved, Applied, Interview, Offer or Not moving forward; Saved for a new entry and for an entry made by an earlier version of the extension) and the date it was last set (for a new entry, the date of the check), so the side panel can count and filter your checks by stage; a new check of the same page keeps the stage of its entry. When there are more than 50 entries, the oldest entry at the stage Saved goes first; an entry at another stage goes only when no entry but the newest is at Saved. The order you choose for the list (Newest first, or Fewest gaps first, which sorts by the counts of the snapshot described below) and the stage you filter by are held only while the side panel is open: they are not kept in storage and not sent. Only the name of a stage you set is sent, as a product statistic without the job (see Product statistics). Since version 0.7.0, an entry made by a check of one of your resume versions also holds a snapshot of that check, so that a later check of the same posting can show what changed (Since your last check of this job): a short one-way code (made with SHA-256) of the text of the posting and of the text of the resume version used, the label of that version (v1, v2 or v3, not its name), the counts of the requirements, and of the must-haves, that were covered, partly covered or had no resume line, and a short one-way code of the text of each requirement that had no resume line or was only partly covered (at most 45 of each). Since version 0.8.0 the snapshot also notes whether the must-haves counted are the requirements the posting marks as required or, when it marks none, all its requirements (mb: must or all), so that the side panel names the counts right. The snapshot holds no text of the posting, of your resume or of a requirement. Deleting a version removes the snapshots made with it. Since version 0.9.0, an entry also holds the date you last pressed Followed up for that job, if you did (followup_at). The side panel shows the reminder "No reply for <n> days. Follow up?" with that button on an entry at the stage Applied when 7 or more days of your browser's calendar have passed since the date of the stage or, when it is later, the date of Followed up; pressing it keeps the entry at Applied, and the reminder comes back 7 days later if the entry is still at Applied. An entry also holds the interview date you entered in the interview details of that job, if you entered one (iv_date, a calendar day only; it is kept only when this browser already has an entry for that page, never for the sample job), so that the side panel puts the date back in the date field when the result of that job is shown again and, at the stage Interview, shows how many days are left to it. The stage and the interviewer's job title you enter are not kept there. A new check of the same page keeps both dates of its entry. The interview date stays in the entry until you clear the date field for that job or the entry is deleted (Remove, Clear all, Withdraw consent, Delete all data, or the entry being pushed out as described above). The line This week (how many of your recent checks are dated within the last 7 days of your browser's calendar, and how many entries now at the stage Applied or Interview were set to it within those days) is worked out in the side panel each time the list is shown; it is not kept and not sent. Download as CSV makes a file of all your recent checks in your browser (the job title, company, site name and page address, the dates of the check, of the stage and of Followed up, the stage, and the counts of the snapshot with whether they count must-haves or all requirements; never a text of the posting, of your resume or of a requirement and never the name of a version) and your browser saves it like any other download (named pm-career-desk-checks-YYYY-MM-DD.csv); the extension has no permission to manage your downloads. Nothing of the file is sent to PM Career Desk or anyone else; only that the button was used is sent, as a product statistic without the job (see Product statistics). The file stays on your computer like any other download: removing the extension or Delete all data does not delete it.
- The job posting read from the current page, with its title, company, page address and the result of the check (with the label of the resume version used, since version 0.8.0 a short one-way code of the text of that version, so that a version changed, or deleted and added again, is not taken for it, and, when shown, the difference with an earlier check of the same posting), held in memory only (chrome.storage.session) until you close the browser, so the side panel can show the result again.
- The results of comparisons of your resume versions (see Comparing your resume versions): for each comparison, the counts of each version under its label, filed under short one-way codes of the posting text and of the text of each version, at most the last 10, held in the same memory (chrome.storage.session) until you close the browser, so that the same comparison is not sent again. They hold no text and no name of a version.
- The interview details you enter, if any (the interview date, the stage and the interviewer's job title), held in the same memory (chrome.storage.session) with the posting they belong to until you close the browser; they are dropped from that memory when you check another posting. Since version 0.9.0 the interview date you enter is also kept with the recent check of that job in extension storage (chrome.storage.local) until you clear it or that entry is deleted, as described under Your recent checks; the stage and the interviewer's job title stay in that memory only.
- The handoff codes made in this browser and when each ends, held in the same memory (chrome.storage.session) until they end or you close the browser, so that Withdraw consent and Delete all data can erase them on our server (see Deleting your data). Web pages cannot read this memory.
- A count of successful checks and a yes or no mark that the request to rate the extension in the store of your browser (the Chrome Web Store, or Microsoft Edge Add-ons in Microsoft Edge, where the request is not shown until the extension is listed there) was shown (numbers only, no text), so that the request comes once, after the third check.
- The marks you made with "Not right?" and your answer to "Was this check right?" for the posting shown, held in the same memory (chrome.storage.session) with that posting until you close the browser, so the side panel shows them again; with the code of each note on our server, so that Undo can delete it there.
- A yes or no mark that a note was sent from this browser (fb_sent), with no text, so that Withdraw consent and Delete all data can tell you that your notes were deleted on our server.
- A yes or no mark that the setup was completed once (installed_sent), with no text and no id, so that a new setup is not counted as a new install.
When the extension reads a page
Only when you press the PM Career Desk icon or its keyboard shortcut, or choose "Check this job with PM Career Desk" on text you selected (see The menu item on selected text). After a press on the icon or the shortcut it reads the job posting on that tab, in this order: the job posting data the page publishes for search engines (schema.org JobPosting, part of the page but not shown on screen), unless the visible text of the posting is much longer; the visible posting block on the job sites and careers site platforms it knows (Greenhouse, Lever, Workday, Indeed, Ashby, iCIMS, SmartRecruiters, Taleo, SuccessFactors, Oracle Recruiting Cloud, Keka, BambooHR, Workable, JazzHR, Recruitee, Teamtailor, Paylocity, Phenom and Radancy TalentBrew), or, where the platform shows the posting in a frame of the same site inside the page (as iCIMS does), that block in the frame, with the company name taken from the job posting data of that frame; on a company page with an embedded Greenhouse job form, the visible text of the page or, when it has none, the posting's public board name and job number; the text you selected, when it is at least 100 characters long; otherwise the main block of visible text of the page, or of a frame of the same site inside it, but only when that block reads like a single job posting and not like a list of jobs, an article or another kind of page. If the first reading finds no posting (on any site but LinkedIn), or finds one while the page shows that it is still drawing its posting block (as pages of Oracle Recruiting Cloud do), the extension reads the same tab once more about one and a half seconds later, in case the page was still loading; if the page then still shows that it is drawing its posting (almost no readable text yet, or the posting block not there yet), it reads the tab a third time about five seconds after the press. These readings are part of the same press. From the page itself it takes only visible text. "Try it on a sample job" reads no page at all: it checks your resume against a made up posting built into the extension. It does not run in the background, does not read other tabs, never changes a page, never clicks or fills in forms. On LinkedIn it reads only the text you select.
The menu item on selected text
Version 0.6.0 adds one item, "Check this job with PM Career Desk", to the menu Chrome shows when you right click text you selected on a web page. Chrome shows the item only when text is selected, and nothing happens unless you choose it. Choosing it opens the side panel and gives the extension access to that tab for this one use, as a press on the icon does; the extension then reads only the text you selected, in the part of the page where you selected it, and only if it is at least 100 characters long. It does not read the rest of the page, and it does not use the copy of the selected text that Chrome hands over with the click. Before you have saved a resume and agreed, choosing the item only opens the setup and reads nothing. The check then goes as described under What is sent to PM Career Desk when you check a job.
Reading a resume file
When you set up the extension, change your resume or add a resume version, you can choose a file instead of pasting the text. A .txt or .md file is read in your browser and nothing is sent. A PDF or Word (.docx) file is sent over HTTPS to app.pmcareerdesk.com only after you have ticked the consent box (when you change your resume or add a version, under the consent you already gave), and only so that our server can read its text: the extension sends the file, with its file name as part of the upload, and nothing else, not your visitor id. Our server reads the text in a separate process with limits on size, time and memory (the same reader as for resumes uploaded on our site) and sends the text back. The file and its text are not stored: they are held in a private temporary folder only while the file is read and deleted right after, whether the reading worked or not; they are not written to a database or a log, and the file name is not written anywhere. When a file cannot be read safely (for example our checks refuse it because it has macros or its content is not the type its name says, it is a scan without text, it has too many pages, it is a compressed file that would unpack to far more than its size, or reading it takes too long), our security log records the code of the reason, the step at which reading stopped, the type and size of the file, a short one-way code of its content and, for some reasons, a short technical note such as an error type, never its name or its text. The text then appears in the resume box for you to check and correct; nothing is kept until you save it, and then only the text, in your browser, as described above. A file can be up to 2 MB and 30 pages; a scanned PDF without a text layer, an old .doc file or a file with a password cannot be read, so paste the text instead. Reading a file writes no statistics row on our server; our hourly request limits count these requests like the others, under a salted one-way code of your IP address.
What is sent to PM Career Desk when you check a job
When you press the icon on a job posting, or choose the menu item on selected text, the extension sends over HTTPS to app.pmcareerdesk.com:
- the text of the resume version used for the check (your default version, unless you pick another one in the side panel; never its name) and the text of the job posting (for a Greenhouse posting embedded on a company site, it may send the posting's public board name and job number instead, and our server reads that public posting from Greenhouse's job board);
- the group of the job site (Greenhouse, Lever, Workday, Indeed or other), not the page address;
- the careers site platform the page runs on (platform: one key from a fixed list of the platforms named under When the extension reads a page, linkedin or other), never the page address or the domain;
- how the posting was read (extract_method: page data, site rule, Greenhouse board, your selection, the main text of the page, or sample for the made up posting built into the extension, whose job site group is sample too);
- how you started the check (trigger: action for the icon or the shortcut, context_menu for the menu item);
- the browser (browser: chrome, edge or other, worked out in your browser from the brand it reports; the full description of your browser is never sent);
- how many resume versions you keep (resume_versions: 1, 2 or 3) and how the version for this check was picked (version_pick: default, suggested after a comparison, or chosen in the side panel);
- whether the side panel shows the difference with an earlier check of the same posting (recheck: yes or no);
- your random visitor id and the extension version.
For the made up sample posting the extension sends neither the platform nor how the check was started.
Our server matches the resume to the posting with fixed rules and sends the result back. The result may quote lines of your resume word for word: as the line that shows a requirement, as the line closest to a requirement it does not show or shows only partly, and with the questions the same fixed rules expect an interviewer to ask. Since version 0.6.0 the result also has an overall verdict worked out from the statuses of the requirements (the side panel may show only the counts and the requirements to fix first), the terms of the posting (tools, methods, certifications and domains) with whether each appears in your resume word for word or in a common spelling, a model line to adapt for a requirement your resume does not show or shows only partly, and up to 8 questions you may be asked. All of it is made by fixed rules at the moment of the check, without an AI model. The resume, the posting and the result are not stored on our server: they are not written to a database, a file or a log. The server writes one statistics row (ext_match_run) to our event log with these fields and no text: the type of role the rules recognised in the posting (role, for example a program manager key, or none); the counts of the match (requirements_n, covered_n, partial_n, gap_n, not_checked_n); how the posting was read (extract_method); the job site group (job_site); the overall verdict of the result as a short key (verdict: strong_fit, worth_applying, long_shot or none, never its words or reasons); when the extension sends them, the careers site platform (platform), how the check was started (trigger), the browser (browser), the number of resume versions (resume_versions), how the version was picked (version_pick) and whether a difference with an earlier check is shown (recheck), a value outside their fixed lists written as unknown; the extension version (ext_version); the channel (source, always extension); the country from our hosting provider's header (country); your random visitor id; the time of the row and its own id in our event log; and a test group mark (variant): while we run a test of our pages, the group of that test worked out from your visitor id, otherwise none. No cookies are used. A check saves nothing for later; only "Prepare for this interview in Claude" and "Rework my resume for this job in Claude" may save the texts under a handoff code, as described under Moving into Claude.
Comparing your resume versions
When you keep two or three resume versions, after the result of a check of a job posting is shown the extension sends one more request over HTTPS to app.pmcareerdesk.com to compare your versions on that posting: the text of the job posting, the text of each of your versions under its label (v1, v2 or v3, never its name), the label of the version whose result is shown, your random visitor id, the extension version, the browser (chrome, edge or other) and, when known, the careers site platform key described above. It is not sent for the made up sample posting or when the text of the posting was not read from the page, and once a comparison of the same posting with the same versions has worked, it is not sent again until you close the browser. Our server matches each version to the posting with the same fixed rules as a check and sends back counts only: for each version, how many of the requirements it compares (the must-haves, or the must-haves and key duties together when there are fewer than three must-haves) are covered, partly covered or have no resume line, the status of the main requirement, and which version covers more, if one does. The answer quotes no line of your resume or the posting. The posting, the versions and the result are not stored on our server: they are not written to a database, a file or a log. The side panel shows the counts next to the names it keeps in your browser; if the comparison does not work, the side panel shows nothing more and the result of your check stays as it is. The server writes one statistics row (ext_compare_run) to our event log with no text: the number of versions compared (versions_n); whether one version covers more, they cover the same, or they could not be compared (outcome); by how many of the compared requirements (the must-haves, or the must-haves and key duties, as above) the version that covers more is ahead, as a range (margin: 0, 1, 2, or 3 or more); when the extension sends them, the browser, the careers site platform and the extension version; the channel (source, always extension); the country from our hosting provider's header; your random visitor id; and, like the other rows, its time, its own id in our event log and the test group mark (variant). Our hourly request limits count these requests apart from checks, under a salted one-way code of your IP address.
Product statistics
After you agree, the extension sends six events to app.pmcareerdesk.com: that the setup was completed, that a resume was saved (pasted or from a file), that "Prepare for this interview in Claude" was pressed, that the line "Practice your answers before <date>" (shown when the interview date you entered is 14 days away or less; it links to the Interview Coach Pass card on our pricing page) was pressed, that a page gave no posting text, and that a button of the side panel was pressed. Each event has the extension version, the channel extension and the visitor id, never any text (the fields: ext_installed with ext_version; ext_resume_saved with source_kind, paste or file, and, for a file, file_type, the kind of file (txt, md, pdf or docx), never its name, and versions_n, how many resume versions you keep after saving (1, 2 or 3), never their names; ext_handoff_clicked with has_date, has_stage and has_interviewer, each "yes" or "no" for whether you entered that interview detail, never the detail itself, and handoff_method, "code" when a handoff code was made or "clipboard" when the texts went through your clipboard; ext_practice_clicked with ext_version only, never the date; ext_extract_failed with reason, why no posting was read (not_found, not_posting, blocked, linkedin or error), platform, the careers site platform key described above, collapsed, "yes" or "no" for whether the page had folded sections, and ext_version, never the page address, the domain or any text; ext_panel_action with action, which button was pressed (copy_keywords, copy_template, open_line_check, open_recent, remove_recent, clear_recent, use_version for checking the posting again with another resume version (picked in the side panel or, when shown, suggested by a comparison), delete_version, open_changes for opening What changed, set_stage for setting the stage of a recent check, rework_claude for "Rework my resume for this job in Claude", followed_up for Followed up on a recent check, or export_csv for Download as CSV), for set_stage only, stage, the key of the stage you set (saved, applied, interview, offer, or rejected for Not moving forward), and ext_version, never what was copied, a term, a line of your resume, the name of a version, an address, or the job, its title or company). No event contains a handoff code. Like the statistics row, each event also has its time, its own id in our event log and the test group mark (variant), and, when your browser sends Global Privacy Control or Do Not Track, the mark no_cookie, so that it is counted apart from our page tests. The country of an event comes from the header our hosting provider adds. The events and the statistics rows do not contain your IP address. As for any request to our service, your IP address may appear in our security logs (section 1, kept as section 9 says), and our hourly request limits count requests under a salted one-way code of the address, never the address itself. Before you agree, the extension sends nothing.
Moving into Claude
When you press "Prepare for this interview in Claude" (or "Practice in Claude" under Questions you may be asked, which does the same), the extension sends over HTTPS to app.pmcareerdesk.com the resume version of the result shown (never its name), the text of the job posting (for a Greenhouse posting embedded on a company site whose text the extension could not read, the posting's public board name and job number instead, and our server reads that public posting from Greenhouse's job board), its job title and company, the type of role the rules recognised, the interview details you entered (the interview date, the stage and the interviewer's job title, all optional), your random visitor id and a mark that you agreed. Our server saves them for you under a handoff code, so that the PM Career Desk connector in your own Claude can read them:
- What is saved. The resume, the job posting, the job title, the company, the role type, the interview date and stage and the interviewer's job title, with your visitor id and where the code was made (the extension or our site). Before anything is saved, the lines of your resume that carry a personal detail (contact details, identifiers, citizenship and visa, salary and the other items listed in section 2) are removed and your name is masked; contact details in the posting, the job title, the company and the interviewer's job title are masked too.
- Encrypted, and found only by the code. The record is sealed with AES-256-GCM under a key made from the code, and its name in our storage is a one-way code of the handoff code, so without the handoff code the record cannot be found or read, by us either. The code (PCD- and 16 random characters) is shown only to you in the extension and in the request it puts into Claude; we do not write it to our logs or events.
- For up to 2 hours. The record is deleted 2 hours after it was made; once the connector has read it, it is deleted 30 minutes after that first read, never later than the 2 hours. It is kept in the memory-backed temporary storage (tmpfs) of our app server, never in our database and never in a backup (section 9).
- Who reads it. The code is read only by a PM Career Desk tool in the Claude where the request with the code is sent: the tool opens the record and uses the texts to prepare your interview, or to rework your resume for the job, in that chat. Anyone who has the code can do the same while it lasts, so do not share it. A wrong code or a code past its time opens nothing.
- Statistics, without text. When the code is made, the server writes one statistics row (handoff_created: where it was made, extension or site; the role type; the channel; the country from our hosting provider's header; your visitor id). When the connector first reads the record, it writes one row (handoff_opened: where the code was made; how long after it was made it was first read, as a range such as under 5 minutes; the visitor id of the record; and the anonymous code of the connector's caller described in section 7). Like the other rows, each has its time, its own id in our event log and the test group mark (variant), and neither contains the code or any text. For a code made by "Rework my resume for this job in Claude", both rows, and the row the connector tool writes when it works from that code (prep_started), also carry the mark purpose rework; a code of the prep carries no such mark.
Since version 0.8.0, "Rework my resume for this job in Claude" (shown under the result when a requirement has no resume line or is only partly covered, never for the sample job) takes the same path: the extension sends the same fields, except that the interview details are left empty, with the purpose of the code (purpose: rework), and our server saves them under a handoff code in the same way, for the same time and with the same protections as described above. The purpose is sealed in the record; when the connector reads such a code, its result adds a note that the code was made to rework the resume for this job posting, so that Claude goes through the requirements without a resume line or only partly covered with you, one at a time.
The extension then opens claude.ai/new with a short request in its address that carries only a fixed request (one for the prep, one for the rework) and the handoff code, never your resume, the posting or any personal details. You send it yourself; Claude, run by Anthropic, then receives the texts in your own Claude chat through the connector, under Anthropic's terms and privacy policy. If the connector is not added to your Claude, Claude cannot read the code: add it once and send the request again. The code is put into your clipboard only when you press "Copy code". If you press the same button again for the same posting and the same details within 20 minutes of making the code, the extension uses that code again and nothing more is saved; later it makes a new code, saved the same way.
If no code can be made (for example the code service is switched off, our server cannot be reached or answers with an error, or too many codes were made from your connection), or our server could not read a Greenhouse posting embedded on a company site, nothing is saved: the extension copies the resume version of the result shown, the posting and, for the prep, the interview details you entered to your clipboard instead and opens claude.ai/new with a short fixed request in its address (one for the prep, one for the rework), the same for everyone and without your resume, the posting or any personal details. If the connection breaks after our server has made a code but before the code reaches the extension, that code may have been saved; you never receive it, and it is deleted within 2 hours like any other code. When the text of the posting could not be read from the page (a Greenhouse job form embedded on a company site), the clipboard text has the page address instead, without its query and fragment (tracking and referral marks are removed) except the Greenhouse job number gh_jid, which the page needs to show that job. Your resume and the job posting then reach Claude only when you paste them from the clipboard into your own Claude chat yourself; Claude, run by Anthropic, then receives them under Anthropic's terms and privacy policy. If you have added the PM Career Desk connector to Claude, Claude may send the text to PM Career Desk to run its tools, as described in the paragraph about the Claude connector in section 7.
Either way, this step sends us one event without any text (ext_handoff_clicked for the prep, or ext_panel_action with rework_claude for the rework, described under Product statistics).
Notes you send with "Not right?"
Under each requirement of a check, and under its main requirement, the side panel shows "Not right?"; under the whole result it asks "Was this check right?". Nothing is sent until you choose an answer. When you choose one, the extension sends over HTTPS to app.pmcareerdesk.com:
- the line of the job posting you marked (none for "Was this check right?"), what the check said about it (Covered, Partly covered, No resume line or Not checked, or that it is the main requirement, and the same marks of its parts, without their text) and your answer: "I have this", "This line doesn't prove it", "Not a requirement", "It's optional, not required" or "Not the main ask", or for the whole result Mostly right, Some mistakes or Mostly wrong;
- what you typed into the optional box "What's missing?" (up to 200 characters), if anything;
- one line of your resume (of the version of the result shown), only if after "I have this" you chose that line and ticked "Include this resume line to help fix it". The box is off by default; without the tick no line of your resume is sent;
- the job site group (not the page address), how the posting was read, the extension version, the version of the disclosure you agreed to and your random visitor id.
Our server masks contact details in the posting line and in your note, and does not keep a resume line that carries a contact detail, an identifier or another item listed in section 2. It adds the version of our matching rules and the country from our hosting provider's header; it does not store your IP address. We keep each note for 180 days and then delete it. People on our team read the notes, grouped by the kind of mistake, to correct the matching rules for everyone; the working summaries we make from them are kept outside our code and deleted when that work is done. We do not use the notes for anything else, do not use them to train AI models, and do not sell or share them. Each note also writes one statistics row without any text (ext_feedback_given: the kind of answer, what the check said, the job site group, the extension version, your visitor id, the country, its time, its own id in our event log and the test group mark).
Undo next to your mark deletes that note on our server at once. If you agreed to the extension's disclosure before version 0.4.0, the side panel shows you the sentence about these notes and asks once before your first note is sent; until you agree, your mark stays in the side panel only.
Deleting your data and withdrawing consent
- A handoff code already made. Delete all data and Withdraw consent first ask our server to erase every code made in this browser that has not ended yet (the extension sends the code and your visitor id to app.pmcareerdesk.com); the record is erased at once and the code opens nothing afterwards. Our server answers the same whether a record was still held or not. If our server cannot be reached or does not erase it at that moment, after you close the browser (the extension then no longer holds the code), and when you remove the extension, the code stays on our server until its time ends (2 hours at most, 30 minutes after the connector first reads it) and is then deleted. For each erasure request the server writes one statistics row (handoff_revoked: where the code was made, extension or site; whether a record was held, yes or no; your visitor id; never the code or any text).
- Notes you sent with "Not right?" Delete all data and Withdraw consent first ask our server to delete every note of your visitor id (the extension sends the visitor id to app.pmcareerdesk.com); our server answers the same whether notes were kept or not. If our server cannot be reached at that moment, the extension tells you so: write to us with the visitor id shown, or the notes are deleted after 180 days. Removing the extension does not reach our server; the notes are then deleted after 180 days, or sooner if you write to us with your visitor id.
- Settings, Delete version removes one resume version and the snapshots of recent checks made with it. The last version left cannot be deleted this way; Delete all data and Withdraw consent remove it.
- Settings, Delete all data removes everything the extension keeps in your browser: all resume versions with their names, the consent, the visitor id, the count of checks and the rating mark, the mark that a note was sent, your recent checks with their stages, dates of Followed up, interview dates and snapshots, and the posting, interview details, marks, results of comparisons and handoff codes held in memory. Only the yes or no mark that the setup was completed once stays (no text, no id), so that setting up again is not counted as a new install; removing the extension deletes it too.
- Settings, Withdraw consent removes all resume versions with their names, the consent, the mark that a note was sent, your recent checks with their stages, dates of Followed up, interview dates and snapshots, and the posting, interview details, marks, results of comparisons and handoff codes held in memory (after asking our server to erase those codes and your notes), and stops all checks, comparisons, handoff codes, notes and events until you agree again. The visitor id stays until you use Delete all data or remove the extension.
- Removing the extension from Chrome or Microsoft Edge deletes its storage. The browser then opens a page on our site that asks, optionally, why you removed it. That page records one event (ext_uninstalled) with the reason you chose, if you chose one, and no text, under the visit code of our public pages (section 6).
- The statistics rows and events on our server, including handoff_created, handoff_opened and handoff_revoked, contain no text and no contact details and are kept as the row for usage events in section 9 says (13 months, then only as totals); to have the rows of your visitor id deleted, write to us with the id shown in the extension's Settings.
Limited Use
The use of information received from the PM Career Desk Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. These requirements cover all information we receive from the extension: the text of your resume versions and of the job posting, a resume file you choose to have read, the job title, company and interview details, the record saved under a handoff code, the notes you send with "Not right?" or "Was this check right?" (with a line of your resume only if you ticked the box), the statistics rows and events, the country and the visitor id. We use the text of your resume versions, the job posting text, the job title, company and interview details, and the record saved under a handoff code only to provide the job match, the comparison of your resume versions, and the interview preparation and the rework of your resume you ask for; a resume file only to read its text for you; the notes only to improve the accuracy of that job match, read by our team as described under Notes you send with "Not right?", which you agree to before the first note; and the statistics rows, events, country and visitor id only to run and improve the extension. We do not sell any of this information, do not transfer it to others except to provide that service, do not use it for advertising, do not use it to determine creditworthiness or for lending, and do not let people read it, except with your consent, for security purposes, to comply with the law, or, for our internal operations, as totals that do not identify you.
Last updated: November 15, 2026