MaxMind GeoIP
How to configure MaxMind GeoIP at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Personalise the website
Overview
This guide explains how to implement different privacy configurations for MaxMind GeoIP lookups 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. GeoIP databases (server-side) and the GeoIP JavaScript client (browser-side).
What the service does in this scope. MaxMind provides binary databases and client APIs for local IP lookups. The JavaScript client lets sites use GeoIP web services from the browser; the script must be served from MaxMind's servers (geoip-js.com). MaxMind recommends server-side integration over the JavaScript client. Data collected via the JavaScript client is covered by MaxMind's privacy policy.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | GeoIP database queried on your own server; no request from the browser to MaxMind. |
| Configuration B — Medium risk | GeoIP JavaScript client loaded from geoip-js.com after Consenter consent. |
⚠ Recommendation. A uses the IP address only on your own server and sets nothing on the device; whether it needs a banner entry depends on what you do with the location. Have your DPO confirm the legal basis.
Step 1 — Configure MaxMind
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Personalise the website | Personalise the website |
| 2 | Integration | MaxMind account | Downloaded database, server-side lookup | JavaScript client, registered domains |
| 3 | Loading | Front-end | — | After Consenter consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. MaxMind is a US enterprise; list the United States for B.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|
| Entry needed | Per DPO assessment (⚠) | Yes |
| Processing purposes | Personalise the website | Personalise the website |
| Tracking method | No tracking | No tracking |
| Identifier | IP address | IP address |
| Data categories | IP address, Non-precise location data | IP address, Non-precise location data |
| Legal role of data recipient | Self-hosted | Individual Controller |
| Personalisation model | Group based (properties) | Group based (properties) |
| Maximum storage duration | Your log retention | Per MaxMind privacy policy |
| Processing location | Your hosting location | United States |
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