> For the complete documentation index, see [llms.txt](https://ce-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ce-docs.keywordrush.com/faq/is-content-egg-gdpr-compliant.md).

# Is Content Egg GDPR Compliant?

{% hint style="warning" %}
**Legal Disclaimer**

We are developers, not lawyers. The information provided on this website is for technical reference only and should not be considered legal advice. Below, we outline how the plugin operates to help you make informed decisions regarding GDPR compliance.
{% endhint %}

### Admin-Side Data Collection

When you activate and use the plugin on your website, our license server collects certain data, including your license key and domain name. This data is used to provide plugin updates and enhance support services.

### **Frontend Data Handling**

By default, **Content Egg does not collect any personal data** from your website visitors. However, some optional features within the plugin may collect user data:

* **Price Alerts** – Stores the subscriber's email address and the date consent was given, to send price drop notifications. Subscribers are included in the WordPress **Export Personal Data** and **Erase Personal Data** tools, and a suggested text is added to the WordPress privacy policy guide.
* **GA4 Link Tracking** – Sends affiliate link clicks to Google Analytics 4 as custom events. Disabled by default.
* **Track Clicks Without Redirect** – Counts clicks with a small request to your own site. Only daily click totals are stored, no personal data. Disabled by default.

Additionally, **Content Egg does not set cookies directly**. However, some **affiliate networks and third-party services** (such as Amazon, eBay, and others) may place cookies when users click on affiliate links to track their behavior.

### Product Images and Embedded Content

Product titles, prices, descriptions and buttons are stored in your WordPress database, so displaying them does not load anything from third-party servers.

Some elements, however, can be loaded directly from external servers. In that case the visitor's browser connects to that server, which can see the visitor's **IP address** and **browser information**:

| Element                           | Loaded from                 | How to serve it from your site                                                                    |
| --------------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------- |
| Amazon product images             | Amazon servers              | Enable **Image Proxy**                                                                            |
| Product images from other modules | Merchant or network servers | Enable **Save images** in the module settings                                                     |
| Merchant logos                    | Your site by default        | Keep **Logo Hotlinking** disabled (default)                                                       |
| External featured images          | Merchant servers            | Keep **External Featured Images** disabled (default), or enable **Image Proxy** for Amazon images |
| YouTube videos                    | YouTube                     | Use a consent or content-blocker plugin for embedded videos                                       |
| Pexels videos                     | Pexels servers              | Use a consent or content-blocker plugin                                                           |

**Amazon prohibits local caching** of product images, so **Save images** is not suitable for the Amazon module. For Amazon, use the **Image Proxy** option instead. You can find it under `Content Egg > General settings > Image Proxy`.

With Image Proxy enabled, Amazon images are streamed through your own site **without being stored on your server**. Visitors' browsers connect only to your site, never to Amazon. Proxied image links do not expire, so they keep working on pages served from a page cache.

**Important Considerations:**

* While the Image Proxy feature may aid in GDPR compliance, **we cannot guarantee full adherence to Amazon’s policies**.
* Each image request passes through your server, which may **increase server load**, so use it only if necessary.

### Final Considerations

Content Egg **can** be GDPR compliant, but compliance also depends on how you configure third-party services, cookies, and tracking mechanisms on your website.

For full compliance, we recommend consulting a legal professional who can assess your specific setup and ensure adherence to GDPR regulations.
