Resume writing plugin privacy
The draft that proves you are leaving before your employer knows
A resume-writing intake can pair a resume file with a current-employer field. A form can collect employment dates, salary expectations, a why-leaving textarea, a client name, and a phone number. Resume PDFs, cover letters, and revision drafts can sit in the site uploads folder. Those uploads can name the current employer: a third party who never consented to being listed. The file's presence timestamps a job hunt while the client still works there. Current-employer, employer-name, employment-dates, salary-expectation, current-salary, why-leaving, resume-file, revision-draft, client-name, phone, and email fields are configured, not documented defaults. A resume file is an upload, not proof anyone is job-hunting. A why-leaving answer is a stored textarea, not proof of a grievance. A named current employer is a stored third-party name, not consent. A salary field is a stored number, not proof of pay. A revision draft is an upload, not proof the story was polished. A resume form is not proof anyone left a job. A page request is not proof anyone is job-hunting. The page URL can say resume even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on resume-intake pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a job-search-success claim, a staffing claim, a tutoring claim, a college-consultant claim, a workers-comp claim, or a GDPR or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where resume files, why-leaving answers, and page tags go
Resume forms and uploads handled on your WordPress site
Check which current-employer, employer-name, employment-dates, salary-expectation, current-salary, why-leaving, resume-file, revision-draft, client-name, phone, or email fields you enable, who can open form entries, where uploaded resume files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after the rewrite is delivered. Notification emails can also copy the same resume PDFs, revision drafts, employer names, salary numbers, and why-leaving answers off-site. One table can name a current employer, a salary number, and a why-leaving answer next to a resume file, even when no rewrite is delivered. Ask your web vendor not to collect a current-employer name next to a why-leaving textarea and a salary number on the first public form, not to store those resume files next to employer names in one open submissions list, and to purge unused intake rows after the rewrite is delivered. A privacy-policy page does not by itself limit who can export an intake list or republish an upload. A stored resume file is not proof anyone is leaving a job.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the resume-writing intake page. That page request can reach a vendor host before anyone submits. The page URL can say resume even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off resume-intake and upload pages if you do not want that page request. A browser scan cannot inspect stored resume PDFs or why-leaving answers. A "confidential rewrite" badge is not a verified storage path.
Resume-intake, upload, and marketing-tag setups
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
Three plugins reviewed from public documentation. Specialty resume-writing or career-coaching SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission. That is the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which resume PDFs, cover letters, revision drafts, or other career-support files you accept depends on the fields you add; they are not fixed resume-writing defaults. Filenames chosen by visitors can include a last name, a current employer, or a target-job title. A resume file is an upload, not proof anyone is job-hunting. A named current employer in a filename is a stored third-party name, not consent. A revision draft is an upload, not proof the story was polished. Pro documents Media Library storage, custom upload folders, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified. | Uploaded files attached to email; temporary copies under wp-content/uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| Forminator Forms – Contact Form, Payment Form & Custom Form Builder Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. Current-employer, employer-name, employment-dates, salary-expectation, current-salary, why-leaving, client-name, phone, or email questions are fields you add; they are not documented defaults. Resume PDFs, cover letters, and revision drafts are files you accept; those file types are not documented defaults. A resume file is an upload, not proof anyone is job-hunting. A why-leaving answer is a stored textarea, not proof of a grievance. A named current employer is a stored third-party name, not consent. A salary field is a stored number, not proof of pay. A revision draft is an upload, not proof the story was polished. A resume form is not proof anyone left a job. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a pairing sits after the rewrite is delivered is not a documented default of the plugin. | Resume-intake entries stored in WordPress; file uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| PixelYourSite – Your smart PIXEL (TAG) & API Manager Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, OpenAI Pixel, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that a current-employer, salary, or why-leaving field was sent. A page request from this script on a resume-upload page is not proof anyone is job-hunting, and a pre-consent tag on that page can still treat job-hunting interest as an audience segment from the URL alone. The page URL can say resume even when no form is submitted. Consent timing has not been tested. Review which tags you enable on resume-intake and document-upload pages. Keep marketing tags off those pages if you do not want that page request. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Current-employer, employer-name, employment-dates, salary-expectation, current-salary, why-leaving, resume-file, revision-draft, client-name, phone, or email fields often depend on the fields you configure. A resume file is an upload, not proof anyone is job-hunting. A why-leaving answer is a stored textarea, not proof of a grievance. A named current employer is a stored third-party name, not consent. A salary field is a stored number, not proof of pay. A revision draft is an upload, not proof the story was polished. A resume form is not proof anyone left a job. A marketing-tag page request is not proof anyone is job-hunting. The page URL can say resume even when no form is submitted. The resume file, the why-leaving answer, and the current-employer name can sit after the rewrite is delivered. This page is about the uploaded resume that timestamps a job hunt while the client still works there, not a staffing onboarding packet, not a tutoring coaching file, not a college-consultant application, and not a workers-comp employer-naming form. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the resume-intake page, and how long records and backups are kept. A "confidential rewrite" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess job-search success, staffing, tutoring, college consulting, or workers-comp claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on resume-intake pages, and backups.
Documentation snapshot: Oct 16, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress file upload plugin privacy
- WordPress email plugin privacy
- All privacy guides
/wp-resume-writing-plugin-privacy