Security
How we protect the information you share with us, and how to raise security questions or request due-diligence information.
Clarify what needs to change—and why it matters.
We confirm these points with your stakeholders, data and dependencies before recommending a route.
Customer problem
- Buyers, partners and candidates need verified company information before engaging.
- Generic company claims can obscure what is evidenced, governed or still subject to review.
- Contact, privacy and trust routes must match the controls that operate behind the website.
Business impact and decision
- Make approved company, trust and contact information easier to evaluate.
- Route each audience to the right governed information or inquiry path.
- Keep legal, security, location and employment claims behind their required approvals.
Move from context to an accountable delivery route.
How we move from your operating context to a clear, accountable delivery plan.
Scope
This page explains how Bright Brains protects information shared with us through this website and during engagements, and how to raise a security question.
Our Practices
This website is served over an encrypted HTTPS connection. Our contact form asks only for business contact details and the context of your inquiry, and we never ask for passwords or other credentials.
Data Handling
Information shared during an engagement is used only for that engagement. Access to customer environments is agreed with the customer and limited to what the work requires.
Supplier Boundary
When an engagement involves a vendor platform such as Nexthink, Creatio or iboss, the vendor is responsible for the security of its platform. Our own responsibilities are documented for each engagement.
Due-Diligence Requests
Procurement and security teams can send security questionnaires or due-diligence requests through our contact page.
Security Contact
If you have a security concern about Bright Brains or this website, contact us through the contact page and mention that it is a security matter.
Responsible Disclosure
If you believe you have found a vulnerability, please follow our responsible disclosure guidelines so we can investigate and fix it.
We describe only the practices we follow today. Questions about certifications or specific controls are answered for the engagement concerned.
Continue with the evidence and service route.
Have a security question?
Send us your question or due-diligence request, and we will route it to the right person.