Algolia
How to configure Algolia 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, Personalise the website
Overview
This guide explains how to implement different privacy configurations for Algolia search and Insights 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. Algolia site search (InstantSearch / API) and the Search Insights library for click analytics and personalisation. Algolia, Inc. is a US company.
What the service does in this scope. Since Search Insights v2, anonymous user tokens are generated on every page load and not stored in a cookie by default. With useCookie: true, the token is stored in the first-party _ALGOLIA cookie (default 6 months, adjustable with cookieDuration) to identify users across sessions; Algolia advises obtaining consent before enabling it and switching useCookie dynamically when consent is granted. setAuthenticatedUserToken sets a token for logged-in users.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Search only, or Insights with in-memory tokens (useCookie: false, default). |
| Configuration B — Medium risk | Insights with useCookie: true after Consenter consent; 6-month _ALGOLIA cookie. |
| Configuration C — Higher risk | As B, plus authenticated user tokens and Algolia Personalization. |
Configuration A. No cookie is set; the search request transmits the query and IP address to Algolia as part of the search the visitor requests. Treat this under Art. 6(1)(b) or (f) GDPR after DPO review.
Step 1 — Configure Algolia
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features | Unlock additional website features; Personalise the website |
| 2 | useCookie | aa('init', { useCookie }) | false | true after consent | true after consent |
| 3 | cookieDuration | init | — | 6 months (default) | 6 months |
| 4 | Authenticated token | setAuthenticatedUserToken | Off | Off | On |
| 5 | Personalization | Algolia dashboard | Off | Off | On |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Algolia is a US enterprise subject to the US CLOUD Act; list the United States in addition to the application's data-centre region.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|
| Entry needed | Optional | Yes | Yes |
| Processing purposes | Unlock additional website features | Unlock additional website features | Unlock additional website features, Personalise the website |
| Tracking method | First party tracking (single session) | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers | Device identifiers, Authentication-derived identifiers |
| Data categories | Browsing and interaction data, IP address | As A, plus Device identifiers | As B, plus Authentication-derived identifiers, Users' profiles |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | Group based (behaviour) | Profile based |
| Maximum storage duration | Page view (in-memory) | 6 months | 6 months |
| Processing location | Data-centre region; United States | Data-centre region; United States | Data-centre region; 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