Indeed
How to configure Indeed 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 reflect Indeed integrations on your website (such as the "Apply with Indeed" button on a careers page) in the Consenter Manager. The sources document no visitor-facing privacy settings, so this guide uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. "Apply with Indeed" / Indeed Apply integrations on an employer's careers site. Plain links to job listings on indeed.com need no entry.
What the service does in this scope. If the Indeed integration is enabled on a careers site, Indeed may place cookies. Domains that are not country-specific, such as indeed.com or apply.indeed.com, place cookies on the browser when the user interacts with them. For application materials submitted through Indeed Apply, Indeed can act as a processor for the employer.
Step 1 — Implement Indeed
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features (apply with an Indeed profile) |
| Integration | Apply with Indeed button / Indeed Apply |
| Loading | Load the button only after Consenter consent, or use a plain link to the Indeed listing |
| Contract | Indeed employer terms and data protection terms |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Entry needed | Only for an embedded button/widget | Plain link: no entry |
| Processing purposes | Unlock additional website features | — |
| Tracking method | Third party tracking (crosssession, cross-website) | Cookies on indeed.com domains |
| Identifier | Device identifiers, Authentication-derived identifiers | Cookies; Indeed account login |
| Data categories | Browsing and interaction data, Device identifiers, User-provided data (application materials), Direct identifier | — |
| Legal role of data recipient | Processor | For Indeed Apply application materials; Indeed is controller for its own site cookies |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Per Indeed cookie list | — |
| Processing location | United States | US enterprise; 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