Security and control designed for serious board processes.
BoardEvaluator™ is built for confidential board evaluation activity, which means trust cannot be treated as a footnote. This page gives buyers, governance teams, and risk stakeholders a practical view of the platform posture: AWS hosting, encryption in transit and at rest, role-based access, audit trail capability, and POPIA/GDPR-aligned data handling.
Built for the confidentiality requirements of board governance.
BoardEvaluator™ operates in a controlled, access-managed environment designed for the sensitivity of board-level evaluation work. This page sets out how data is handled, how access is managed, and how the platform is positioned relative to common regulatory and compliance expectations.
Protected data handling
BoardEvaluator™ is positioned for confidential governance processes, so data handling is designed to support privacy, controlled access, and board-level trust.
Structured permissions
Role-based access matters because board participants, administrators, and advisors should not all experience the same level of system visibility.
Traceable workflows
Auditability supports confidence. It helps governance teams understand how an evaluation cycle was administered and monitored.
Compliance-aware posture
POPIA/GDPR-aligned handling and SSO-ready posture help the platform fit more comfortably inside enterprise governance environments.
What most buyers actually want to know.
In practice, the security conversation usually comes down to a few clear topics: where the platform is hosted, how data is protected, who can see what, and whether the environment fits regulatory expectations.
Core control themes
- AWS hosting for the BoardEvaluator™ platform
- Encryption in transit and at rest
- Role-based access control across the workflow
- Full audit trail support for platform activity
- SSO-ready posture for more controlled enterprise environments
AWSEncryptionRBACAudit trailSSO ready
Regulatory and privacy fit
Security on this site is deliberately connected to the legal and privacy layer. Buyers should be able to move from this page into the policy pages without friction.
- Privacy for data handling principles
- POPIA for South African privacy relevance
- Terms for legal framing
- Cookies for site-level disclosure
- Contact for direct security enquiries
Security has to support board participation, not make the process unusable.
A board evaluation platform lives in a sensitive operating space. The challenge is to balance confidentiality, controlled administration, and usability for directors and governance teams.
Confidential participation
Directors need a workflow that feels confidential and appropriately protected, not improvised or overly exposed.
Administrative control
Governance teams need visibility into invitations, reminders, completion, and system handling without compromising the integrity of the process.
Enterprise fit
Risk teams need assurance that the platform posture is mature enough to sit inside real governance and compliance environments.
Security is one part of a wider governance trust picture.
Buyers assessing BoardEvaluator™ typically consider security alongside methodology, legal terms, company context, and platform fit. The sections below connect each area of the trust picture so nothing requires hunting.
Understand the broader trust layer
If the buyer is testing credibility, they usually need more than one page.
- About for product origin and company relationship
- Methodology for evaluation logic
- Privacy for data-handling context
See what the controls are protecting
Security becomes more meaningful when the buyer also understands the product, workflow, and board-use context.
- Platform for the end-to-end process
- Modules for the evaluation architecture
- Packages for delivery depth
Move to a live conversation
If the platform fit is clear but the stakeholder has risk or compliance questions, the next step should be obvious.
Security assurance supports a commercial decision - it does not replace it.
Most governance buyers reach the security question after they have already assessed platform fit and module scope. The information here is designed to provide the confidence needed to move forward - not to delay the commercial conversation.
Book a Demo
Best when the buyer wants to combine security questions with a practical view of the platform and scope.
Security contact route
Best for direct security, privacy, risk, or compliance follow-up that does not need a product walkthrough first.
Privacy and POPIA
Best for stakeholders who need policy-level data handling comfort before progressing.
About Celagenix® and BoardEvaluator™
Best when the real concern is trust in the company and product relationship, not just technical control language.
Security questions answered directly.
The questions most commonly raised by company secretaries, risk stakeholders, and governance teams during due diligence on a board evaluation platform.
Where is BoardEvaluator™ hosted
BoardEvaluator™ is hosted on AWS. The security page uses that fact as a core trust signal because buyers often want immediate clarity on the infrastructure environment.
How is data protected
The platform posture includes encryption in transit and at rest, role-based access control, and audit trail capability to support a more controlled board-evaluation workflow.
Is the platform aligned to POPIA and GDPR expectations
The platform is described as POPIA/GDPR-aligned in its data-handling posture. Buyers who need more formal policy context should also review Privacy and POPIA.
Can the platform fit enterprise access expectations
The security messaging includes an SSO-ready posture, which helps position BoardEvaluator™ more credibly for controlled enterprise environments.
What should I do if security is part of a broader buying review
Use this page together with Platform, Packages, About, and Book a Demo so that the risk review stays connected to the actual product and buying context.
If the controls look right, the next move is to test fit in context.
Security builds confidence, but a buying decision still depends on workflow fit, module scope, reporting needs, and the right engagement model.