Questions or requests? Contact CyberPopulus at [email protected]. Do not include passwords, payment card details or confidential records in an initial message.
1. About these terms
These terms cover use of the CyberPopulus website, consultation booking process and general conditions for professional services. CyberPopulus provides AI Safety support, consultation, assessments, awareness training, guided improvements, advisory support and authorised penetration testing, including customer-controlled AWS and Microsoft Azure environments.
A written proposal, statement of work, rules of engagement, data processing agreement or other signed service agreement defines the particular engagement. The written engagement agreement governs where it expressly differs from these general terms, subject to mandatory law. These website terms do not themselves authorise technical access or testing.
2. Booking and agreeing work
Submitting a consultation booking records your interest and gives us details for follow-up. We contact you privately to agree needs, deliverables, exclusions, responsibilities, fees and scheduling. A recorded booking is not a fixed appointment, permission to test or an obligation to pay an undisclosed fee.
Paid work begins only after the relevant scope, commercial arrangements and permissions have been agreed. Any questionnaires help scope and tailor the service; they are not proof of security or authorisation to access systems. A penetration-testing submission starts a scoping discussion.
Please provide accurate contact information and tell us promptly about changes. If you arrange work for a company, institution or another person, you must have authority to make those arrangements. For work involving children, appropriate parent or guardian arrangements must be in place.
3. Fees, payment and expenses
We communicate fees privately before you commit. The written quote or agreement should identify currency, applicable taxes, payment milestones, due dates, included work and any approved expenses. Extra work or changes to scope require agreement before additional charges apply.
Use only payment instructions issued through an agreed CyberPopulus channel. Verify unexpected payment changes through a separate trusted route. Never submit full card details, banking PINs or authentication codes through our forms or messages. Payment-provider terms apply where a hosted payment service is used.
Where payment is overdue, we may pause work after notifying you, subject to the engagement agreement and applicable law. Payment alone does not extend testing permissions or add services outside the agreed scope.
4. Scheduling, cancellation and refunds
Availability and dates are agreed personally. Ask about cancellation, rescheduling and any non-refundable commitments before accepting a quote. Engagement-specific charges or notice periods must be explained and agreed in advance; submitting a form does not create a cancellation charge.
If either party needs to change or cancel, contact the other promptly. We consider work already performed, unavoidable commitments and the agreed cancellation terms when determining any amount due or refund. If CyberPopulus cannot deliver agreed work, we discuss an appropriate reschedule, alternative or refund for undelivered work. Mandatory consumer rights continue to apply.
5. Authorised testing and cloud environments
Before testing, we require written permission from a person entitled to authorise it and a defined scope. This includes exact targets, ownership, permitted techniques, exclusions, time windows, test accounts, emergency contacts, stop conditions, data handling and reporting arrangements. Third-party systems require the relevant owner’s permission.
AWS and Azure testing must also follow the provider’s current policies. Your permission does not override provider restrictions. Any required approvals must be obtained before the relevant activity. We do not test provider infrastructure or other customers’ environments as part of a client engagement.
Denial-of-service, destructive testing, uncontrolled data extraction and activity outside written scope are excluded. Social engineering, physical testing or other simulations are not implied by a penetration-testing booking and require a separately agreed, permitted scope.
Testing can affect system behaviour despite precautions. Client and tester responsibilities for backups, production safeguards, monitoring, emergency escalation and restoration must be agreed. We may stop or defer activity if permissions are unclear, a provider restriction applies or unexpected impact occurs. Scope changes require renewed agreement.
6. Client responsibilities and access
Provide accurate scope information, appropriate ownership permissions, timely decisions and an authorised contact. Tell us about critical systems, restricted data, known dependencies and relevant third-party conditions. Maintain suitable backups and operational support as agreed.
Arrange dedicated, proportionate access through an agreed channel. Do not share passwords, cloud secrets, recovery codes or confidential records through the public website. You retain ownership and administrative control of your accounts. Temporary access and test resources should be removed or revoked at the agreed end of the engagement.
Implementation work requires agreed change controls, dependencies and rollback arrangements. Where your provider or internal team must make a change, we identify that responsibility instead of assuming control.
7. Deliverables, limitations and retesting
The written scope determines the deliverables. Depending on the service, these may include advice, an action plan, training materials, a findings report, a technical walkthrough or implementation guidance. Testing reports describe the assessed scope, methods, evidence, limitations and recommended remediation.
Assessments and penetration tests reflect the conditions and coverage at the time of testing. They cannot guarantee discovery of every weakness, future security, successful recovery or prevention of every incident. A scan, review, consultation and penetration test have different purposes; the agreed service should identify which is being delivered.
Retesting is included only where the agreement states its scope, timing and any fee. Fixes outside the original scope or later system changes may require additional assessment. Compliance certification, legal advice, continuous monitoring and emergency incident response are not included unless explicitly and appropriately contracted. We do not claim accreditation or certification that has not been established.
8. Confidentiality and personal information
Each party should protect non-public information received for an engagement, use it for the agreed purpose and restrict access to people who need it under appropriate obligations. Exceptions include information lawfully public, already lawfully known, independently developed or required to be disclosed by law.
We agree access, evidence minimisation, secure transfer, retention and return or deletion arrangements before handling sensitive engagement data. Where processing personal information on your behalf requires a data processing agreement, that agreement must be in place before the relevant access. The privacy notice explains website and enquiry processing.
Client findings are not published or used in a public case study without permission. Critical findings are communicated to agreed contacts. Disclosure involving a provider or third party is coordinated under applicable obligations and the rules of engagement; confidentiality does not prevent legally required disclosure.
9. Reports and intellectual property
You retain rights in information and materials you provide. CyberPopulus retains rights in its existing methods, templates, tools, training materials and general know-how. Ownership or licensing of commissioned deliverables is specified in the engagement agreement.
Unless otherwise agreed, completed deliverables supplied under a paid engagement may be used internally for the intended security and remediation purpose after the applicable fees are paid. Sharing with your responsible advisers or providers should preserve confidentiality and the report’s context. Public reproduction, resale, or use of our materials as your own commercial product requires permission.
Third-party tools, content and platforms remain subject to their own licences. A report must not be represented as a security guarantee or certification.
10. Website, accounts and acceptable use
Use the site lawfully. Do not submit fraudulent requests, attempt to access another person’s records, interfere with the service or treat the website as permission to test any system. Report suspected website vulnerabilities privately through our contact email, using minimal non-sensitive evidence; do not continue accessing data to demonstrate impact.
Accounts are optional and use verified email access. Protect the email inbox associated with your account and sign out on shared devices. The dashboard may display earlier records made with the same verified email. We may restrict access reasonably to protect the service or investigate misuse.
Website information is general guidance and may change. External links are provided for convenience and do not imply endorsement or responsibility for another service. Availability of a website feature does not expand a signed engagement.
11. Educational resources and student initiative
The self-check is educational. It processes your answers in your browser; it does not scan systems, provide a technical security rating or certify protection. You choose whether to save or share your results.
PROJECT POPULUSBUILD student learning and community participation are permanently free. Joining requests are reviewed separately from commercial bookings. Participation does not guarantee employment, an internship, qualification or a programme date. Eligibility and any guardian arrangements are explained before enrolment.
12. Responsibility, disruptions and complaints
We aim to deliver services with reasonable care and skill within the agreed scope. If you believe a service has fallen short, contact us with the engagement reference and a clear description so we can investigate and discuss an appropriate remedy.
Engagement-specific allocation of responsibility and any proposed liability limits must be stated in the written agreement. These website terms do not impose an undisclosed monetary liability cap. Nothing here excludes liability or consumer rights that cannot lawfully be excluded.
Events beyond reasonable control may delay delivery. The affected party should notify the other, take reasonable steps to reduce disruption and agree revised arrangements or an appropriate end to undelivered work.
13. Applicable law and updates
These general terms are governed by the laws of Nigeria, subject to mandatory protections and jurisdiction rights that apply to a client elsewhere. An engagement agreement may specify further applicable arrangements. We encourage an initial good-faith discussion of disputes without limiting your right to seek a legal remedy.
We may update these terms for future website use and engagements and will show a revised date. An update does not retrospectively change an existing signed agreement without the required agreement of the parties. Contact CyberPopulus through the published email for questions, complaints or proposed service arrangements.
