Prescreen
How to configure Prescreen 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 Prescreen (now part of XING / onlyfy) in the Consenter Manager. On the employer's website Prescreen appears as a job widget or a link to the hosted career page; the sources document no configurable 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. Prescreen e-recruiting (Prescreen International GmbH, Vienna, Austria; acquired by XING in 2017).
What the service does in this scope. Prescreen operates the e-recruiting system where companies advertise vacancies and manage applications; the employer is responsible under data protection law. Prescreen uses session cookies and permanent cookies (e.g. to return to an application later).
Step 1 — Implement Prescreen
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Unlock additional website features (job listings, applications) |
| Integration | Link to the hosted career page, or embedded job widget |
| Loading | Plain link: no entry needed; embedded widget: after Consenter consent |
| Contract | DPA with Prescreen / XING E-Recruiting |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Entry needed | Only for an embedded widget | Link sets nothing on your site |
| Processing purposes | Unlock additional website features | Job listings |
| Tracking method | Third party tracking (crosssession, cross-website) | Permanent cookies on Prescreen's domain |
| Identifier | Device identifiers | Cookies |
| Data categories | Browsing and interaction data, Device identifiers, User-provided data (applications) | — |
| Legal role of data recipient | Processor | Employer is responsible |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Per Prescreen cookie information | Not documented |
| Processing location | Austria / Germany | Austrian company in the German New Work group; no CLOUD Act flag unless US sub-processors |
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