A pool only works with clear consent
A seasonal role can end even when someone has been a good fit for the team. An employer may want to ask later whether that person is interested in returning. That requires voluntary, understandable consent, a clear purpose and an easy way to withdraw.
Vencur is not planning one shared candidate pool across companies. Applicant data will not be passed to other employers. Each employer remains responsible for its own applicant data.
What must be clear before launch
- Which role or purpose permits a follow-up message.
- How long data is kept and who can access it.
- How applicants can withdraw consent or request access or deletion.
These points need technical and operational review before a release. That is why the feature is labelled “Coming soon” and is not a current service promise.
Status and limits
The pool is not generally available. Until then, an employer should only contact a former applicant again with its own transparent legal basis. The pilot will explore workflows for returning and seasonal workers.
Frequently asked questions
Can employers use the candidate pool now?
No. It is planned for a later stage and is not available.
Will applications be shared with other companies?
No. Vencur is not planning a cross-company candidate pool or transfers of applicant data between employers.
How long will pool data be stored?
A specific period must be set and explained before launch. The feature is still being planned.
Can a person withdraw consent?
A future pool must provide a simple way to withdraw consent and request deletion. That needs to be checked before release.