Voiceover plugin privacy
The demo reel that hands over the one credential you can never rotate: your voice
A voiceover site can look like a demo reel and a booking calendar. It also stores demo reels, client audition uploads, and raw session files — hours of clean, high-quality recordings of a named person's voice. In the voice-cloning era those uploads are biometric credentials: a leaked form-entries table or an open uploads directory is enough training data to impersonate the artist (or the client who uploaded a scratch track) to their bank, their family, or their customers. Passwords rotate; a voiceprint does not. Demo-reel-upload, audition-upload, session-raw, client-name, usage-rights, and character-voice fields are configured, not documented defaults. Optional WAV and MP3 demos go in the site uploads folder. A session booking is not proof a take was recorded. A demo upload is a file, not consent to clone the voice. A page request is not proof anyone booked a session. The page URL can say voiceover even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and albums, whether demo URLs stay reachable, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a deepfake claim, a fraud claim, an impersonation 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, bookings, uploaded audio, portfolio albums, email inboxes, staff permissions, vendor accounts, or backups.
Where auditions, session bookings, and demo portfolios go
Forms, bookings, and portfolios handled on your WordPress site
Check which demo-reel-upload, audition-upload, session-raw, client-name, usage-rights, or character-voice fields you enable, who can open form entries and bookings, where uploaded demos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a session. Notification emails can also copy the same client name and audio link off-site. One table can name the artist, the demo WAV, and the audition scratch track next to a buyout note, even when the session never happens. Ask your web vendor not to collect raw session files next to contact details on the first public form, not to store audition uploads in one open submissions list longer than casting needs, and to purge unused demos after the date passes. A privacy-policy page does not by itself limit who can export a client list. A stored booking is not proof a session was recorded.
Albums or tags handled by a vendor
Some gallery or marketing tools load a vendor script or sync portfolios to a vendor host. That path can re-expose the same named voice demos. Review which portfolio connectors and tags you enable, account access, and retention there. Keep demo and audition pages off vendor sync if you do not want that copy. A browser scan cannot inspect stored demos, audition files, or session bookings. A "pro VO" badge is not a verified storage path.
Voiceover audition, session-booking, and portfolio 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 VO marketplace or casting SaaS without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Easy Appointments Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A VO session is a booking you create; a service name such as commercial demo, audiobook chapter, or ADR pickup is a label you configure. Neither is a documented default. Demo-reel-upload, audition-upload, session-raw, client-name, usage-rights, or character-voice questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked slot is not proof a session was recorded, and a character-voice answer is not proof a clone exists. Cancelling or missing the slot later does not erase custom fields or unsend a confirmation email already delivered. How long that row sits after a booking that never became a session is not a documented default of the plugin. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified. | Session bookings, custom intake fields, and automatic confirmation emails on your WordPress site | 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. Demo-reel-upload, audition-upload, session-raw, client-name, usage-rights, or character-voice questions are fields you add; they are not documented defaults. A WAV or MP3 demo is a file you accept; that file type is not a documented default. An audition is not proof a session was booked. A demo upload is a stored file, not consent to clone the voice. A dead lead still leaves clean voice audio in the uploads folder. 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 an audition row sits after a request that never became a session is not a documented default of the plugin. | Audition and inquiry form entries stored in WordPress; audio uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| NextGEN Gallery Documented gallery plugin when it serves media from your WordPress install. On resize it copies camera metadata from the original onto the generated file. The listing does not document stripping GPS from the original upload. A VO demo portfolio or client reel gallery is an album you create; captions that name the artist, client, or character voice are labels you configure. Neither is a documented default. Audio demos linked from a portfolio page may still live as separate uploads; this row covers the gallery/plugin path that serves site-hosted media. A gallery page request is not proof anyone booked a session. The page URL can say voiceover even when no form is submitted. Social-feed galleries are not this row. Consent timing is not tested here. Review who can open albums, whether demo files stay publicly reachable, and how long originals remain after a reel is replaced. | Portfolio media served from your WordPress install, including metadata on generated files | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Demo-reel-upload, audition-upload, session-raw, client-name, usage-rights, or character-voice fields often depend on the fields you configure. A VO booking is not proof a session was recorded. A demo upload is a file, not consent to clone the voice. A gallery page request is not proof anyone booked a session. The page URL can say voiceover even when no form is submitted. Clean demo and audition audio can sit after the lead dies. This page is about unrevolvable voice biometrics in uploads, not podcast listener analytics, not video player tracking, not ghostwriting uncredited authorship, and not an image-only gallery portfolio. Ask your web vendor who can open entries and albums, whether demo URLs stay reachable, and how long records and backups are kept. A "pro VO" 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 deepfakes, fraud, or impersonation. Review stored records, uploaded audio, portfolios, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress booking plugin privacy
- WordPress gallery plugin privacy
- All privacy guides
/wp-voiceover-plugin-privacy