This public policy summarises the privacy-by-design controls used for the Valendra Recruitment service. Internal records should include the detailed retention schedule, processor/provider register, DPIA/risk assessments, incident records and access reviews.
Valendra collects information needed for accounts, recruitment, matching, security, legal obligations and clearly defined related purposes. Protected/sensitive characteristics are not used to increase or reduce candidate match scores. Candidate Market Review uses aggregate information rather than exposing identifiable candidates.
Candidate discovery is opt-in and separate from ordinary account registration. Employers with appropriate plan/permissions receive anonymised job-related information until the candidate applies, accepts an invitation or another lawful introduction route is completed. Turning discovery off prevents future discovery searches; it does not erase records that must lawfully be retained.
Candidate CVs and uploads are stored outside normal public-page access in a protected server directory. Uploads are extension/MIME/size checked, renamed with random server-side filenames and delivered through authenticated PHP routes. Employers may download a CV only for a candidate/application that has been lawfully shared with their organisation and only while their account/role has the required access. Download events are audit logged. Candidate database search does not expose direct CV download URLs.
Postcode/ZIP and coordinates may be used internally to calculate distance and radius. Candidate discovery and Market Review should show approximate distance/aggregate counts rather than a candidate's home address or precise coordinates. Small aggregate groups are suppressed/generalised to reduce re-identification risk.
Administrator access is server-side authenticated and separate from public navigation. Employer organisation roles control access to vacancies, candidate search, CVs, team management, analytics and billing. Candidate accounts are restricted to their own profile, invitations and applications. Access should be removed promptly when no longer required.
Valendra's matching engine uses documented, job-related criteria and provides explanations/confidence information. No match score alone automatically rejects a candidate. Human review/challenge routes are available, automated matching can be disabled where required, and jurisdiction-specific controls can block matching until compliance clearance is recorded. Matching changes and significant recruitment actions should be audit logged.
Because recruitment profiling can create significant risks, Valendra should maintain a living Data Protection Impact Assessment covering candidate discovery, matching/ranking, Market Review, invitations, notifications, CV sharing, international processing, providers and new AI/analytics features. Material changes should be assessed before activation.
Records receive a defined retention/review basis. For UK employment-agency/work-finding records, Valendra keeps the records required by the Conduct Regulations for at least 12 months from creation and, for relevant work-seeker/hirer application records, at least 12 months after the last work-finding service to that person or hirer. Commercial/accounting or dispute records may require longer retention. Inactive talent-pool information is reviewed and deleted/anonymised when no longer necessary. Archive status is not permission for indefinite retention.
Processors/providers receive only the access needed for their service and should be covered by appropriate contractual/security terms. UK personal data transferred internationally must use a valid UK transfer mechanism where required. Adding analytics, advertising pixels, AI services, storage providers or new integrations requires a privacy/security review first.
Controls include HTTPS on the live service, password hashing, secure/HttpOnly/SameSite sessions, CSRF protection, throttling/anti-spam controls, restricted uploads, role-based access, protected storage, audit logs, backups and server maintenance. Administrator and other high-risk access should use MFA as soon as the hosting/account stack supports it. Payment-card data should be handled by the payment provider rather than stored by Valendra.
Suspected personal-data incidents should be contained, assessed, documented and escalated promptly, with regulator/individual notification where legally required. Privacy requests are logged and tracked; identity may be verified before data is disclosed or changed. Candidates can correct source information and request human review of matching where available.
This policy, the DPIA, retention schedule, provider register, jurisdiction matrix and technical controls should be reviewed whenever the recruitment model materially changes and periodically during normal operation.