Race registration plugin privacy
The entry form one join away from the results page that already names you
A race registration can look like a shirt size and a bib number. The same form often stores date of birth, an emergency contact, and a medical-conditions note you typed so the medic tent would know. Those fields are configured, not documented defaults. Running culture already publishes the other half: finish-line results list name, age, and city for anyone to search, forever. The private entry row and the public results row describe the same person — one join away. A published result is the organizer's choice, not the plugin's. A registration is not proof anyone ran. A medical-conditions field is a safety note, not a health record. A page request is not proof anyone registered. The page URL can say race registration even when no form is submitted. Ask what happens to the private half after race day — results stay up for years, so does the form table, and only one of them was meant to. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on the registration page, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a HIPAA claim, an event-insurance claim, a liability-waiver-enforceability claim, a timing-company 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 registrations, waiver files, and page tags go
Registrations and waiver files handled on your WordPress site
Check which date-of-birth, emergency-contact, medical-conditions, shirt-size, or waiver 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 race day — when a public results page may still name the same runner. Notification emails can also copy the same waiver off-site. One table can list every entrant. Ask your web vendor not to keep medical-conditions notes next to contact details in one open submissions list longer than race operations need, and to purge registrations when the event is over. A privacy-policy page does not by itself limit who can open an uploads folder. A stored registration is not proof anyone ran. A medical-conditions field is a safety note, not a health record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the race registration page. That page request can reach a vendor host before anyone submits. The page URL can say race registration even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off registration pages if you do not want that page request. A browser scan cannot inspect stored entries or waivers. A "secure registration" badge is not a verified storage path.
Race registration, waiver-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 race-timing or registration 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). 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 signed waiver or medical-clearance letter is a file you accept; it is not a documented default. The uploads folder can hold those files next to the registration list. An uploaded waiver is not proof anyone ran. 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_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. Date-of-birth, emergency-contact, medical-conditions, or shirt-size questions are fields you add; they are not documented defaults. A waiver file is a file you accept; it is not a documented default. Completing the form can record a registration. A submitted registration is not proof anyone ran. A medical-conditions answer is a safety note, not a health record. A staff login can open the DOB and emergency contact next to other configured fields. The same person may later appear on a public results page by name, age, and city — that publication is the organizer's choice, not this plugin. 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. | Registration entries stored in WordPress; waiver 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, 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 DOB, emergency contact, or medical-conditions field was sent. A page request from this script is not proof anyone registered. The page URL can say race registration even when no form is submitted. Consent timing has not been tested. Review which tags you enable on registration 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. Date-of-birth, emergency-contact, medical-conditions, shirt-size, or waiver fields often depend on the fields you configure. A registration is not proof anyone ran. A medical-conditions field is a safety note, not a health record. A published result is the organizer's choice, not the plugin's. A marketing-tag page request is not proof anyone registered. The page URL can say race registration even when no form is submitted. The private entry row and a public results page can describe the same person — that adjacency is the sport's publication habit next to a form table, not a feature these plugins claim. This page is about that join, not a volunteer background-check form or a volunteer meal-delivery route sheet. Ask your web vendor who can open entries, where uploaded waivers live, whether a marketing tag loads on the registration page, and how long records and backups are kept after race day. A "secure" or "athlete data protected" 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 HIPAA, event insurance, liability-waiver enforceability, or timing-company systems. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on registration 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-race-registration-plugin-privacy