Privacy
Background Verification Privacy Policy
Learn how ZenNextVerify handles website enquiries, user accounts, candidate information, verification evidence, access, reporting and retention.
Last updated: 31 October 2026
Purpose of this notice
This notice explains the categories of information that may be handled through ZenNextVerify's public website and verification services, why that information is used, and the operational safeguards around it.
Information handled
The information depends on whether you are a website visitor, business contact, authorised MIS user, candidate, client, vendor, or reviewer.
- Business contact and enquiry information
- Account, role, authentication, and audit information
- Candidate identity, address, education, employment, and reference details relevant to selected checks
- Permitted documents and verification evidence
- Case, assignment, QC, notification, and report records
- Technical security and access logs
Why information is used
Information is used to respond to enquiries, administer authorised accounts, perform the agreed verification workflow, request missing information, review quality, release reports, protect the service, and maintain required operational records.
Public website analytics
We use Google Analytics on public information pages to understand page visits, referral sources and basic browser/device information. Google Analytics may use cookies and process this information through Google's services. This integration excludes login, MIS workspaces, candidate intake and report-reference lookup pages. We do not add candidate records, case details or enquiry form values to analytics events.
Access and sharing
Access is restricted by role and engagement scope. Information may be made available to the relevant employer/client, assigned verification provider, authorised operations or quality personnel, infrastructure provider, or another party required for the permitted verification process.
- Client users are scoped to their organisation
- Vendor users are scoped to assigned work
- Candidates receive case-specific intake access
- Public report checks expose only limited release metadata
Retention and deletion
Retention should follow the applicable client agreement, verification purpose, operational requirement, and legal obligation. Production retention schedules and deletion procedures must be configured and reviewed before live candidate processing.
Questions and requests
Questions about access, correction, retention, or privacy should be sent through the contact page with enough context to identify the relevant engagement. Identity or authority may need to be confirmed before acting on a request.
Questions or requests?
Contact our team for guidance on privacy, corrections or use of the service. For a case-specific request, ask for the authorised secure channel; your identity or authority may need to be confirmed. Use the business emails for general enquiries, not for sending sensitive records.
Business emails
Call us
For general enquiries only. Share candidate documents through your authorised secure intake, not these public contact channels. Never share passwords or OTPs.