Contents
On this page
Privacy and GDPR - Plugixa FAQ
Where this appears: Tools, then Export Personal Data and Erase Personal Data in WordPress; Settings, then Privacy, then Policy Guide; and the Feedback and Submission tabs of the plugin’s settings. Since 1.1.0.
Only two parts of the plugin collect anything from visitors: feedback voting and the question form. Both are Pro, so everything on this page is too. A free site stores no visitor data at all.
IP addresses are hashed
A feedback vote stores a one-way hash of the visitor’s IP address, never the address itself. The hash is keyed with your site’s own secret, so it cannot be turned back into an address or matched against another site. It is only used to stop the same visitor voting twice.
The real address is passed only to Cloudflare Turnstile, and only when you have turned spam protection on.
A vote also keeps the browser’s user agent, the account if the visitor was
signed in, the optional comment, and a cookie named plugixa_feedback_session
holding a random ID for one year.
Export and erase personal data
The plugin plugs into WordPress’s own tools under Tools. A request for an email address now covers:
| Tool | Finds | Erasing removes | Erasing keeps |
|---|---|---|---|
| FAQ Feedback | Votes from the WordPress account with that email | The account link, IP hash, browser, session and comment | The vote itself |
| FAQ Submissions | Questions sent with that email | The name, email, consent record and personal custom field answers | The question and its answer |
Guest votes are not tied to an email address, so they cannot be found by one. That is a consequence of not storing the IP address.
Text for your privacy policy
Under Settings, then Privacy, then Policy Guide, WordPress shows a Plugixa FAQ section you can copy into your policy. It describes what feedback stores, the cookie and how long votes are kept, what the question form stores and that a copy is emailed to you if notifications are on, and the Turnstile check.
Consent on the question form
Settings, then the Submission tab, then the Privacy Consent (GDPR) card. Turned on, the form shows a required checkbox so visitors agree to how their name and email are stored. It is off by default.
Checkbox Text sets the label. The default is “I agree to the storage of my
data as described in the %privacy_policy%.”, where %privacy_policy% becomes a
link to your privacy policy page.
The check is made on the server too, so a form posted without the box ticked is refused. The time of consent is stored with the submission and included in its export.
Anonymising old feedback
Settings, then the Feedback tab, then the Privacy (GDPR) card.
Anonymize after (days) clears the IP hash, browser and account from votes
older than that, once a day. The votes and comments are kept, so the totals do
not change. 0, the default, means never.
The daily job uses WP-Cron and is only scheduled while the setting is above zero.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| An export finds no votes | They were cast while signed out | Guest votes cannot be matched to an email |
| No Plugixa FAQ text in the Policy Guide | This is the free build | It stores no visitor data, so it has nothing to declare |
| Old votes are not anonymised | WP-Cron does not run on a quiet site | Use a real cron job to call wp-cron.php |
| No consent checkbox | It is off by default | Turn on Privacy Consent (GDPR) |
What to do next
Settings lists every tab, including the two that hold these options.
Quick Links
Share