bendolo

@owadud655

The cookie optn_visitor_type is currently set to expire in 100 years. While I understand the intent is to remember “returning” visitors, this duration conflicts with several core principles of the GDPR:

1. Storage Limitation (Art. 5 (1) (e) GDPR): Personal data (and even pseudonymized data like cookies) must be kept in a form which permits identification for no longer than is necessary for the purposes for which they are processed. A 100-year storage period for a simple visitor-type flag is legally unjustifiable and considered “excessive.”
2. Data Minimization (Art. 5 (1) (c) GDPR): Processing must be limited to what is necessary. A duration of 1 year is standard for “returning visitor” logic; anything beyond that (especially a century) will be flagged in any professional privacy audit.

The Issue for Users: As a site operator, I have to list every cookie and its expiration in my privacy policy. Listing a “100-year” cookie makes my site look like it’s using intrusive tracking, even though the cookie’s content ("returning") is actually harmless. It’s a “red flag” for automated compliance scanners and legal regulators.

Suggested Fix: Please update the cookie TTL to something reasonable, like 365 days or 730 days (to match your optn_analytics_id). time() + (365 * 24 * 60 * 60)

This small change would make the plugin much more compliant in the EU.

Best regards

@owadud655

The cookie optn_purchase_tracking seems to be missing from your overview. It should probably be added for those looking to identify all tracking cookies.

Could you also confirm if there are any other cookies that might have been missed, or is this now the complete list for a fully cookie-less setup?

I just wanted to say a big thank you for the latest update! Being able to disable the IP tracking/API call to ipinfo.io is exactly what I was looking for.

I really appreciate you listening to the community and giving us more control over privacy and performance. Keep up the great work!

I was able to temporarily solve the problem using the code below. It intercepts the request to ipinfo.io and returns a dummy response, which stops the issue from occurring:

add_action('wp_head', function() {
    ?>
    <script>
    (function() {
        const originalFetch = window.fetch;
        window.fetch = function() {
            // If the URL contains ipinfo.io, return a fake response
            if (arguments[0] && typeof arguments[0] === 'string' && arguments[0].includes('ipinfo.io')) {
                return Promise.resolve(new Response(JSON.stringify({
                    ip: "127.0.0.1",
                    country: "EU",
                    city: "Local",
                    org: "None"
                }), {
                    status: 200,
                    headers: { 'Content-Type': 'application/json' }
                }));
            }
            // Execute all other requests normally
            return originalFetch.apply(this, arguments);
        };
    })();
    </script>
    <?php
}, 1);

I am really looking forward to the feature you confirmed that will improve data privacy and allow for better control over this.

Hi,

Thank you for the update and for adding the previous request to your developer list (OPT-133). I will look into the firewall workaround for the time being.

Regarding the further development of the plugin, I have two specific questions concerning data privacy and infrastructure:

1. Local Geolocation: Are there plans to allow local geolocation? Specifically, we need an option to manually upload our own .mmdb files (e.g., MaxMind GeoLite2 or IP2Location LITE). This would allow the plugin to query the visitor’s IP locally via PHP ($_SERVER['REMOTE_ADDR']) against this database, ensuring that no visitor data leaves our infrastructure and no US-based servers are involved.To give you a better idea of how we imagine the settings interface for this, please see this mockup: https://i.imgur.com/j6BYzi6.png
2. IP Anonymization (Hashing): Do you plan to implement a feature to anonymize or hash IP addresses before they are processed or stored? We are looking for an option to either mask the last octet or use a salted hash to stay compliant with strict privacy requirements.

I look forward to hearing if these features might be on your roadmap.

Best regards