BoardEvaluator™ is used in a context where confidentiality, discretion, and controlled handling matter. This page explains how BoardEvaluator™ by Celagenix® approaches personal information, evaluation data, site usage data, data minimisation, retention, rights requests, and privacy-aligned governance. It is designed to help buyers, governance teams, and participants understand the privacy logic around the platform and the website.
This page is part of the trust architecture around BoardEvaluator™. It should reassure governance buyers and participants that privacy is handled with the seriousness expected in a board-evaluation environment.
Board evaluation data is sensitive because it can reflect boardroom dynamics, governance weaknesses, independence concerns, and strategic oversight quality.
Information should be collected and used for defined purposes such as responding to enquiries, operating evaluations, supporting reporting, and maintaining the service.
Only the information reasonably required for the product, support, commercial process, or compliance need should be processed.
Privacy should not be hidden. Users and stakeholders need a clear route to understand handling practices and make requests where applicable.
The privacy model spans both the public website and the BoardEvaluator™ platform environment.
The point of this section is to show that privacy is not a disconnected policy page. It follows the real BoardEvaluator™ journey from enquiry to evaluation delivery and ongoing governance support.
Gather only the information needed to support an enquiry, a demo request, or an evaluation workflow.
Match data use to a legitimate product, advisory, contractual, or governance purpose before broader processing happens.
Apply role-based access, administrative boundaries, and workflow controls appropriate to a board context.
Use security measures, including the posture described on Security, to safeguard information in use and at rest.
Keep information for a justified period based on service delivery, evidence needs, legal obligations, and contract terms.
Provide a route for privacy requests, questions, corrections, or other lawful data-subject interactions through Contact.
A strong privacy page anticipates the practical questions that legal, company secretariat, procurement, and risk stakeholders will ask.
Information may be shared with trusted service providers, hosting infrastructure, implementation or support personnel, and other parties where that is necessary to operate the service, meet contractual commitments, or comply with law. Information is not treated as an open commercial asset simply because it is available to the business.
Privacy and security work together. Hosting, encryption, role-based access, and audit-aware administration support more controlled handling of evaluation-related data in sensitive governance workflows.
Retention depends on the nature of the engagement, governance evidence needs, legal requirements, and operational necessity. When information is no longer reasonably required, deletion or de-identification should follow the applicable process and obligations.
Privacy matters more when it is linked to the platform, the module architecture, and the real board processes behind the data.
Privacy becomes more understandable when the evaluation process itself is clear.
Module scope affects the nature and sensitivity of the information being processed.
Privacy is stronger when read together with company, methodology, and security context.
The goal is clarity for governance teams, participants, and stakeholders reviewing trust, compliance, or procurement fit.
Privacy is one part of the buyer-confidence journey. The commercial decision still depends on platform fit, module scope, reporting needs, security expectations, and the right delivery model.