Client Agreement
Effective Date: 7 October 2026
Last Updated: 7 October 2026
This Client Agreement (“Agreement”) applies to businesses, organisations and individuals who submit products or services for testing through TestmeQa, operated by TestmeQa Limited (“TestmeQa”, “we”, “us”, or “our”).
By creating a Client account, submitting a product for testing, purchasing a testing service, or otherwise using TestmeQa’s services as a Client, you agree to this Agreement, our Terms of Service, and our Privacy Policy.
1. Our Services
TestmeQa may provide or facilitate services including:
- Website testing;
- Mobile application testing;
- Software testing;
- Beta testing;
- Usability testing;
- Bug identification;
- User feedback;
- Quality assurance services; and
- Other product-testing services.
The specific services provided will depend on the project agreed between TestmeQa and the Client.
2. Client Eligibility
You must provide accurate information when creating a Client account or submitting a project.
If you are acting on behalf of a company or organisation, you confirm that you have authority to act on its behalf.
3. Product Ownership and Authorisation
By submitting a product for testing, you confirm that:
- You own the product or have permission to have it tested;
- You have the authority to provide the required access;
- The testing request does not knowingly violate another person’s rights;
- You have the necessary permissions to provide any materials or information supplied to TestmeQa; and
- The testing activities requested are lawful.
TestmeQa is not responsible for determining whether you have sufficient rights to submit a product for testing.
4. Project Scope
Before a testing project begins, the Client may be required to provide information including:
- Product name;
- Product URL or application;
- Testing environment;
- Testing objectives;
- Features to be tested;
- Features excluded from testing;
- Test accounts;
- Test credentials;
- Supported devices or browsers;
- Testing period;
- Number of testers;
- Required deliverables; and
- Other project requirements.
The agreed project scope determines the activities that TestmeQa and participating testers are authorised to perform.
5. Authorised Access
Clients are responsible for providing appropriate access to the product.
Where possible, Clients should provide:
- Dedicated test accounts;
- Test environments;
- Test data;
- Non-production credentials; and
- Appropriate access restrictions.
Clients should not provide unnecessary access to production systems or sensitive information.
6. Production Systems
Clients should clearly identify whether a project involves a production environment.
Where possible, testing should be conducted in a dedicated testing or staging environment.
If a Client specifically authorises testing in a production environment, the Client acknowledges the associated risks and remains responsible for ensuring that such testing is appropriately authorised and controlled.
7. Personal Data and Sensitive Information
Clients should avoid providing real customer personal information to testers wherever reasonably possible.
Where personal data is necessary for testing, the Client is responsible for ensuring that:
- The data may lawfully be used for testing;
- Appropriate safeguards are in place;
- Testers receive only information necessary for the project; and
- Appropriate instructions are provided regarding the handling of the information.
Clients should preferably use synthetic or test data.
8. Client Responsibilities
The Client is responsible for:
- Providing accurate project information;
- Providing appropriate testing access;
- Clearly defining testing requirements;
- Providing accurate test credentials;
- Ensuring that the product can legally be tested;
- Responding to reasonable project queries;
- Reviewing testing results; and
- Paying agreed fees.
Delays caused by missing or inaccurate information may affect project timelines.
9. Tester Access
By submitting a project, the Client authorises TestmeQa to provide selected testers with access reasonably necessary to perform the agreed testing activities.
Testers are required to follow the applicable TestmeQa Terms and Tester Agreement.
Testers are not authorised to access systems or information outside the agreed testing scope.
10. Bug Reports and Feedback
TestmeQa may provide Clients with:
- Bug reports;
- Testing results;
- Screenshots;
- Screen recordings;
- Usability observations;
- Tester feedback;
- Test summaries; and
- Other agreed deliverables.
Testing results represent the findings of the testing activities performed within the agreed scope.
TestmeQa does not guarantee that every defect or issue will be discovered.
11. Client Review
Clients may review submitted findings and provide reasonable feedback through the applicable project process.
TestmeQa may assist in clarifying, categorising or validating reported issues.
12. Fees and Payment
The applicable project or service agreement will specify the fees payable by the Client.
Fees may depend on factors including:
- Number of testers;
- Testing duration;
- Product type;
- Testing scope;
- Testing requirements;
- Testing complexity; and
- Additional services requested.
Clients agree to pay the applicable fees according to the agreed payment terms.
13. Cancellation
Clients may request cancellation of a project before testing begins.
Once testing has commenced, cancellation and refund eligibility will be determined under the Refund & Cancellation Policy and the applicable project terms.
14. Confidentiality
TestmeQa and participating testers may receive confidential information belonging to the Client.
The Client acknowledges that:
- Testers may need access to non-public product information;
- TestmeQa may need to share necessary project information with selected testers; and
- Testers are required to maintain confidentiality under the applicable TestmeQa agreements.
The Client must also maintain the confidentiality of non-public information belonging to TestmeQa and participating testers.
15. Client Data and Credentials
Clients are responsible for the credentials and access information they provide.
Clients should:
- Use dedicated testing credentials where possible;
- Avoid using administrator credentials unless necessary;
- Avoid providing unnecessary production access;
- Disable credentials when testing is complete; and
- Notify TestmeQa promptly if credentials are compromised.
16. Security Testing
Standard product testing does not automatically include penetration testing, vulnerability assessment or other security testing.
Security testing must be expressly authorised and included in the project scope.
Clients must clearly identify any authorised security-testing activities and applicable restrictions.
17. Intellectual Property
The Client retains ownership of its products, applications, content, trademarks, designs, source code and other materials.
The Client grants TestmeQa and participating testers the limited rights necessary to access and test the product for the agreed project.
Testmeqa does not acquire ownership of the Client’s product merely because it is submitted for testing.
18. Client Feedback and Use of Results
Clients may use testing reports and findings provided to them for product-development, quality-assurance and business purposes.
Unless otherwise agreed, TestmeQa may retain project records for legitimate business, quality-assurance, legal and operational purposes.
19. No Guarantee of Product Readiness
TestmeQa’s testing services are intended to identify issues and provide feedback.
Completion of a testing project does not constitute a certification that a product is:
- Bug-free;
- Secure;
- Compliant with applicable laws;
- Ready for production;
- Ready for commercial release; or
- Suitable for a particular purpose.
The Client remains responsible for its final release and deployment decisions.
20. Prohibited Client Activities
Clients must not:
- Submit products they do not have permission to test;
- Provide testers with unauthorised access;
- Request testers to perform unlawful activities;
- Request testing outside the agreed scope;
- Attempt to obtain testers’ personal information unnecessarily;
- Use TestmeQa to conduct unauthorised surveillance;
- Circumvent TestmeQa fees;
- Misrepresent project requirements; or
- Use the Platform for fraudulent or unlawful purposes.
21. Account Suspension
TestmeQa may suspend or terminate a Client account where the Client:
- Violates this Agreement;
- Fails to pay applicable fees;
- Provides unauthorised access;
- Misuses tester information;
- Engages in fraudulent activity;
- Violates applicable law; or
- Creates a significant security or privacy risk.
22. Limitation of Liability
To the extent permitted by applicable law, TestmeQa Limited will not be liable for indirect, incidental, special or consequential losses arising from a Client’s use of testing services.
Nothing in this Agreement excludes or limits liability that cannot lawfully be excluded or limited.
23. Governing Law
This Agreement is governed by the laws of the Federal Republic of Nigeria, subject to applicable law.
24. Disputes
If you have a complaint or dispute relating to a TestmeQa service, please contact:
We will make reasonable efforts to resolve disputes through good-faith communication before formal proceedings are commenced, subject to applicable law.
25. Changes to This Agreement
TestmeQa may update this Agreement from time to time.
Where material changes are made, we may provide appropriate notice.
Continued use of TestmeQa services after an updated Agreement becomes effective constitutes acceptance of the revised Agreement.
26. Contact
For general support:
For formal complaints and disputes:
TestmeQa Limited
Website: testmeqa.com.ng