Font Awesome
How to configure Font Awesome 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 Font Awesome icons 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. Font Awesome icons, either self-hosted or loaded via a Font Awesome Kit (Fonticons, Inc., US).
What the service does in this scope. A Font Awesome Kit is a personal CDN that manages icons for a project; alternatively the files can be downloaded and self-hosted. Kits use Cloudflare's CDN technology. Font Awesome's privacy notice lists service providers including Amazon Web Services for running the content delivery networks.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Self-hosted Font Awesome files; no request to Font Awesome. |
| Configuration B — Medium risk | Font Awesome Kit from the CDN; loaded after Consenter consent (with fallback icons). |
Configuration A without consent. Self-hosted files make no third-party request; no Consenter entry is required.
⚠ Configuration B. Kit requests transmit the visitor's IP address to Font Awesome's CDN providers in the US. By analogy with LG München I (judgment of 20 January 2022, 3 O 17493/20) on Google Fonts, where self-hosting is possible a transfer without consent is legally uncertain; prefer A or have your DPO confirm B.
Step 1 — Configure Font Awesome
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — | Unlock additional website features |
| 2 | Delivery | Download vs Kit | Self-hosted | Kit (kit.fontawesome.com) |
| 3 | Loading | Consenter script blocking | — | After consent / per DPO |
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 | No tracking |
| Identifier | No identifier | IP address |
| Data categories | — | IP address, Device characteristics |
| Legal role of data recipient | Self-hosted | Processor |
| Personalisation model | — | No personalisation |
| Maximum storage duration | — | Per Font Awesome privacy notice |
| Processing location | Your server | United States (Cloudflare, AWS; 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