Gravatar
How to configure Gravatar at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Unlock additional website features
Overview
This guide explains how to implement different privacy configurations for Gravatar avatars and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Gravatar avatars (Automattic Inc., US), typically in WordPress comments.
What the service does in this scope. WordPress checks for a Gravatar by sending an MD5 hash of each displayed author's email address to gravatar.com; even the default avatars are served from gravatar.com. When a visitor opens the page, gravatar.com receives the visitor's IP address and the hashed email addresses. WordPress' suggested privacy text notes that the hash may be provided to Gravatar. Avatars can be disabled with add_filter( 'get_avatar', '__return_empty_string', 1000 );.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Gravatar disabled; local avatars or none. |
| Configuration B — Medium risk | Gravatar enabled; avatars loaded from gravatar.com. |
⚠ Recommendation — Configuration B. Avatar images are plain image requests, but they disclose the visitor's IP address and commenters' email hashes to a US provider. Whether this needs consent or can rely on Art. 6(1)(f) GDPR is debated in the WordPress community; have your DPO decide, or load comments with avatars after Consenter consent.
Step 1 — Configure Gravatar
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — | Unlock additional website features |
| 2 | Avatars | Settings > Discussion > Avatars or get_avatar filter | Off / local | Gravatar |
| 3 | Loading | Consenter (see ⚠) | — | Per DPO decision |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|
| Entry needed | No | Yes |
| Processing purposes | — | Unlock additional website features |
| Tracking method | No tracking | Third party tracking (single session, cross-website) |
| Identifier | No identifier | IP address, Probabilistic identifiers (email hash) |
| Data categories | — | IP address, Device characteristics, Probabilistic identifiers |
| Legal role of data recipient | — | Individual Controller |
| Personalisation model | — | No personalisation |
| Maximum storage duration | — | Per Automattic privacy policy |
| Processing location | — | United States (Automattic; the US CLOUD Act) |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on