Scholarship application plugin privacy

The essay about the worst year of your life, uploaded to a contact form

A scholarship application can look like a name, a GPA, and a file upload. A hardship-essay field means the contact form is collecting a narrative, not a contact request. That essay can be the most personal document a high-school applicant has written. It can sit next to income, first-generation, parent, disability, or immigration answers you choose to collect. Those fields are configured, not documented defaults. The uploads folder does not know who won. A rejected essay can sit next to a winning one. An application is not a scholarship award. An essay is not proof of hardship. A page request is not proof anyone applied. The page URL can say scholarship 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 the application page, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a financial-aid-law claim, a FERPA claim, a scholarship-legitimacy claim, an essay-judging claim, a selection-fairness claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The 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 applications, essay files, and page tags go

Applications and essay files handled on your WordPress site

Check which hardship-essay, income, first-generation, parent, disability, immigration, or GPA fields you enable, who can open form entries and the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a decision that never became an award. Notification emails can also copy the same essay off-site. One table can list every applicant even when only the student typed. Ask your web vendor not to collect a hardship essay on the first public form, not to store that file next to income or immigration answers in one open submissions list, and to purge applications after a decision. A privacy-policy page does not by itself limit who can open an uploads folder. A stored application is not a scholarship award.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the scholarship application page. That page request can reach a vendor host before anyone submits. The page URL can say scholarship even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off application pages if you do not want that page request. A browser scan cannot inspect stored essays. A "secure application" badge is not a verified storage path.

Scholarship application, essay-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 scholarship or financial-aid software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Drag and Drop Multiple File Upload for Contact Form 7

Documented Contact Form 7 upload extension (plugin version 1.4.0). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. A hardship essay is a file you accept; it is not a documented default. The uploads folder can hold those files next to the application list. A rejected application can still leave the essay until the documented cleanup, and the email copy can remain. An uploaded essay is not a scholarship award. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified.

Visitor files stored under wp-content/uploads/wp_dndcf7_uploadsBrowser hosts not verifiedNot assessedNot tested
  • None
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. Hardship-essay, income, first-generation, parent, disability, immigration, or GPA questions are fields you add; they are not documented defaults. An essay file is a file you accept; it is not a documented default. Completing the form can record an application. A submitted application is not a scholarship award. An essay is not proof of hardship. A staff login can open the essay next to contact details and other configured fields. The uploads folder can hold a rejected essay next to a winning one. 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.

Application entries stored in WordPress; essay uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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, 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 hardship essay, income, or GPA field was sent. A page request from this script is not proof anyone applied. The page URL can say scholarship even when no form is submitted. Consent timing has not been tested. Review which tags you enable on application pages.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Hardship-essay, income, first-generation, parent, disability, immigration, or GPA fields often depend on the fields you configure. An application is not a scholarship award. An essay is not proof of hardship. A marketing-tag page request is not proof anyone applied. The page URL can say scholarship even when no form is submitted. The rejected essay can sit in the same uploads folder as the winning one. This page is about a solicited hardship narrative stored as a file, not a clinical-trial screen-fail row, a food-bank hardest-month form, a summer-camp signup, a tutoring intake, or an adult-literacy placement. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the application page, and how long records and backups are kept. A "secure" or "confidential application" 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 financial-aid law, FERPA, scholarship legitimacy, essay judging, or selection fairness. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on application pages, and backups.

Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-scholarship-application-plugin-privacy