Reentry program plugin privacy
The job-readiness intake that stores what the sealed record no longer shows
A reentry-program site can look like a short enrollment form and a resume-upload box. The same form often asks for a conviction type, a release date, a parole officer, and a housing status — and asks for a resume — and stores those answers next to the participant contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a job-readiness enrollment next to a conviction-type answer, a release date, a parole-officer name, a housing-status note, a resume upload, and a marketing pixel — the job-readiness intake that stores what the sealed record no longer shows, typed once into a vendor table next to a newsletter signup. An enrollment row is a program-authored intake, not a court filing. An uploaded resume is a stored client document, not a verified employment history. A conviction-type answer is the enrollee's words, not an adjudicated docket. A page request is not proof anyone enrolled. The page URL can say reentry-program even when no form is submitted. Ask what happens to the conviction-type and parole-officer rows after the participant leaves — the quietest field is the conviction type next to a resume, a voluntary confession of sealed-record material stored where ban-the-box rules were meant to keep it out of hiring databases. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on the enrollment page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a ban-the-box or record-sealing claim, a parole claim, a hiring-discrimination claim, a program-effectiveness claim, a claim about any nonprofit or employer partner, a claim about the program's data-security practices, a provider-quality 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 job-readiness enrollments, reentry-program intake, and page tags go
Enrollments and uploads on your WordPress site
Check which conviction-type, release-date, parole-officer, or housing-status fields you enable, who can open form entries and resume uploads, which inboxes receive copies, and how long records, emails, and backups are kept after a participant leaves — when the job-readiness intake that stores what the sealed record no longer shows. Notification emails can also copy those fields off-site. One table can list every enrollment next to a resume upload and a conviction-type answer. Ask your web vendor not to keep resume uploads next to plaintext conviction-type, release-date, parole-officer, and housing-status rows in one open submissions list longer than operations need, and to purge enrollment rows when the program relationship ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored enrollment is not a court filing. A conviction-type sentence in a form table is not an adjudicated docket the plugin claims to verify.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the reentry-program enrollment or intake page. That page request can reach a vendor host before anyone submits. The page URL can say reentry-program even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off job-readiness enrollment and reentry-program intake pages if you do not want that page request. A browser scan cannot inspect stored entries or uploads. A "trusted workforce partner" badge is not a verified storage path.
Job-readiness enrollment, reentry-program intake, 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 reentry SaaS platforms 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 — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which resumes, certificates, or other reentry-program documents you accept depends on the fields you add; they are not fixed reentry-program defaults. Filenames chosen by visitors can include full names or ID numbers. An uploaded resume is a stored client document, not a verified employment history — and a mail copy of those files next to a job-readiness enrollment is still a mailbox that holds the job-readiness intake that stores what the sealed record no longer shows. 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. Conviction-type, release-date, parole-officer, or housing-status fields are fields you add; they are not documented defaults. Completing the form can store a conviction type next to a release date, a parole-officer name, a housing-status note, and optional resume uploads — typed once as the job-readiness intake that stores what the sealed record no longer shows, into the same tables as a newsletter signup. An enrollment row is a program-authored intake, not a court filing. An uploaded resume is a stored client document, not a verified employment history. A conviction-type answer is the enrollee's words, not an adjudicated docket — and a staff login can open "felony theft, released 2024-03-12, PO Rivera, couch-surfing, resume.pdf" next to everyone else's newsletter signup. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Job-readiness enrollment stored in WordPress; optional resume 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 conviction-type, release-date, parole-officer, or housing-status field was sent. A page request from this script is not proof anyone enrolled. The page URL can say reentry-program even when no form is submitted. Consent timing has not been tested. Review which tags you enable on job-readiness enrollment and reentry-program intake pages. | 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. Conviction-type, release-date, parole-officer, or housing-status fields often depend on the fields you configure. An enrollment row is a program-authored intake, not a court filing. An uploaded resume is a stored client document, not a verified employment history. A conviction-type answer is the enrollee's words, not an adjudicated docket. A marketing-tag page request is not proof anyone enrolled. The page URL can say reentry-program even when no form is submitted. The job-readiness intake that stores what the sealed record no longer shows — that is a storage path next to a resume upload, not a feature these plugins claim. This page is about that reentry-program enrollment, not an expungement-service petition, a prison-family care-package form, or a criminal-defense intake. Ask your web vendor who can open entries, whether a marketing tag loads on the enrollment page, and how long conviction-type and parole-officer rows and backups are kept after the participant leaves. A "trusted workforce partner" 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 ban-the-box law, record sealing, parole rules, hiring discrimination, program effectiveness, any nonprofit, or any employer partner. Review stored records, uploads, connected services, exports, notification emails, marketing tags on enrollment pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-reentry-program-plugin-privacy