• Resolved Bonaldi

    (@bonaldi)


    Hi Marc.
    As a long-time contributor and PTE of this plugin, I have several points I’d like to address:

    • It no longer works for my CF7 and WP Form Lite forms (it’s disappeared).
    • The files are commented in German, which makes understanding the code difficult (except for German speakers :-)) and penalizes contributions.
    • Disabling telemetry is impossible (the toggle reactivates after registration).

    I therefore have serious doubts about its GDPR compliance, mainly because of the previous point, and then the choice of opting out for telemetry (consent is defined as “any freely given, specific, informed, and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her”). Generally, opting in is the rule for compliance.

    I look forward to reading your point of view.

    Regards.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support forge12marc

    (@forge12marc)

    Hi @bonaldi

    thank you for raising your concerns – I value your contribution and the fact that you hold us to a high standard.

    We just released a hotfix that should address the issues you mentioned:

    1. CF7 / WP Form Lite forms disappearing – this was caused by a regression. The hotfix restores compatibility. If for any reason the forms are still missing, please go to Settings → Extended and simply re-enable the required services manually.
    2. Code comments in German – agreed, this penalizes contributions. We have started translating all comments into English so that the codebase is accessible to everyone.
    3. Telemetry toggle – fixed. The toggle now respects the user’s choice. Telemetry remains pseudonymized and limited to plugin usage data only (see updated README for the full list of collected fields).

    On telemetry:
    SilentShield does collect usage data by default, but it is fully pseudonymized and limited strictly to plugin-related technical information. We do not collect IP addresses, no form data, and no personal user data of any kind. Only plugin usage is measured – nothing that can identify a person or site visitor.

    To make this transparent, we have updated the README to list every single field that is tracked:

    • plugin_slug (technical identifier)
    • plugin_version (release used)
    • snapshot_date (collection date)
    • settings_json (active configuration options, pseudonymized)
    • features_json (which features are enabled)
    • created_at, first_seen, last_seen (timestamps, anonymized)
    • counters_json (usage counts of spam protection events)
    • wp_version (WordPress version)
    • php_version (PHP version)
    • locale (site language)

    That’s the complete list. Nothing else is collected.

    The purpose is solely to understand which features are actually used, so we can improve defaults, remove unnecessary complexity, and keep the plugin lightweight.

    SilentShield will always remain GDPR-compliant. But just as important: it will remain transparent – and you should know exactly what is being collected.

    Best regards,
    Marc

    Thread Starter Bonaldi

    (@bonaldi)

    Hi Marc,

    Thank you for this clarification. I appreciate the transparency effort.

    1. I tested version 2.2.42 and the arithmetic CAPTCHA fields still don’t appear in CF7 and WPForm Lite.
    2. The English translation of the strings is good news for the contribution. Danke.
    3. The telemetry toggle button seems to work (but unfortunately remains opted-out).

    On telemetry:
    One point remains to be clarified, however: is the data anonymized or pseudonymized? This is different with regard to the GDPR: pseudonymized data remains subject to the GDPR, while anonymized data is not.

    Best regards.

    Thread Starter Bonaldi

    (@bonaldi)

    The buttons to manually delete data entries don’t seem to work, either.

    Plugin Support forge12marc

    (@forge12marc)

    Hi @bonaldi ,

    thank you for testing again and for your feedback.

    On telemetry:
    SilentShield does not send any personal data. Only technical plugin usage information is collected.
    There are no emails, no names, no IP addresses, and no form content being transmitted.

    As mentioned above, the complete list of collected fields is:

    • plugin_slug (technical identifier)
    • plugin_version (release used)
    • snapshot_date (collection date)
    • settings_json (active configuration options, pseudonymized)
    • features_json (which features are enabled)
    • created_at, first_seen, last_seen (timestamps, anonymized)
    • counters_json (usage counts of spam protection events)
    • wp_version (WordPress version)
    • php_version (PHP version)
    • locale (site language)

    That’s the full scope. Nothing else is collected.
    SilentShield remains completely GDPR-compliant, as no personal data is ever processed.

    Best regards,
    Marc

    Plugin Support forge12marc

    (@forge12marc)

    Hello @bonaldi

    thank you for reporting this.
    The issue with the manual delete buttons has already been fixed in the latest release.

    Please update SilentShield to the newest version, and the buttons should now work as expected.

    Best regards,
    Marc

    Thread Starter Bonaldi

    (@bonaldi)

    Hi Marc,

    OK, I’ll test last version.

    I will also start the translations.

    It seems that there is an L missing in the source code of this string: Backlist IP Addresses

    Best regards.

    Thread Starter Bonaldi

    (@bonaldi)

    I get this message on WP Login page before login (PHP 8.3.25):

    Deprecated: Creation of dynamic property f12_cf7_captcha\core\timer\CaptchaTimer::$logger is deprecated in /var/www/html/wp/wp-content/plugins/captcha-for-contact-form-7/core/timer/CaptchaTimer.class.php on line 58

    Thread Starter Bonaldi

    (@bonaldi)

    Full translation into French done. 😉

    Thread Starter Bonaldi

    (@bonaldi)

    Extended and Dashboard should be translatable strings for a perfect interface.

    Plugin Support forge12marc

    (@forge12marc)

    Hello @bonaldi

    thank you for pointing this out.
    You’re right – labels like Extended and Dashboard should be translatable for a perfect interface. We already have this on our roadmap, but it’s not the highest priority at the moment.

    Still, we’ll make sure it’s included in a future update. Thanks again for the feedback!

    Best regards,
    Marc

    Thread Starter Bonaldi

    (@bonaldi)

    Hi Marc,

    The WP Job Manager Application Forms string does not want to show translated in the settings.

    Best regards.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Feedback about version 2.2.4’ is closed to new replies.