Website User Policy, Beta Tester Programme Terms And Conditions

Website: https://codesternetworksltd.com
Effective Date: September 11, 2026
Last Updated: September 11, 2026

1. Introduction

These Website User Policy, Beta Tester Programme Terms and Conditions govern access to and use of the Codester Networks Limited website, mobile applications, software platforms, information systems and Beta Testing Programme.

The website and Beta Testing Programme are operated by Codester Networks Limited, referred to in these Terms as “Codester Networks”, “the Company”, “we”, “us” or “our”.

A person who visits the website, creates an account, registers as a beta tester, downloads a test application or uses any of our services is referred to as the “User”, “Tester”, “you” or “your”.

By creating an account, selecting the acceptance checkbox, downloading a test application or participating in the Beta Testing Programme, you confirm that:

1. You have read and understood these Terms;
2. You agree to comply with these Terms;
3. The information you provide is true and accurate; and
4. You are legally capable of entering into this agreement.

Where you do not agree with these Terms, you must not register for or participate in the Beta Testing Programme.

PART A: GENERAL WEBSITE USER POLICY

2. Purpose of the Website

The Codester Networks website provides information about the Company and its services and may allow Users to:

• Register and manage user accounts;
• Apply to become beta testers;
• View available applications and systems requiring testing;
• Download or access approved beta software;
• Submit feedback, reports, screenshots and testing results;
• Track completed tests and payment status;
• Communicate with the Company;
• Access news, notices, documentation and support services; and
• Use other services introduced by the Company.

The availability of any feature does not guarantee that it will remain available permanently.

3. User Eligibility

To register as a Beta Tester, a person must:

1. Be at least eighteen years old;
2. Have the legal capacity to enter into an agreement;
3. Possess a compatible smartphone, tablet, computer or other approved device;
4. Have lawful access to the device used for testing;
5. Have an active telephone number and any other information required for payment;
6. Be able to install and keep the test application on the device for the required testing period;
7. Reside in a location where the Beta Testing Programme is available; and
8. Meet any additional requirements stated for a particular application or system.

The Company may request reasonable information to verify a User’s identity, age, device compatibility, location or payment details.

Registration does not automatically guarantee acceptance into the Beta Testing Programme or assignment of an application.

4. Account Registration

Users must provide accurate, complete and current information during registration.

Each User may maintain only one beta testing account unless the Company gives written permission for additional accounts.

Users must not:

• Register using a false name or identity;
• Use another person’s telephone number, payment account or identification information without permission;
• Create multiple accounts to claim more than one payment for the same test;
• Sell, rent, transfer or share an account;
• Permit another person to perform a test assigned to them; or
• Provide misleading information about the device on which an application was tested.

Users are responsible for maintaining the confidentiality of their passwords, verification codes and account credentials.

Any activity completed through a User’s account may be treated as activity authorised by that User, unless the User promptly reports unauthorised access.

5. Acceptable Use

Users must use the website and Beta Testing Programme lawfully and responsibly.

Users must not:

1. Attempt to gain unauthorised access to the website, applications, servers, databases or user accounts;
2. Introduce viruses, malicious software, automated scripts or harmful code;
3. Interfere with the operation or security of any application or system;
4. Copy, modify, reverse engineer, decompile or disassemble test software except where expressly authorised in writing;
5. Extract source code, security keys, database information or confidential technical information;
6. Use bots, emulators, device farms or automated tools to simulate testing unless specifically authorised;
7. Submit fabricated feedback, false screenshots or altered system records;
8. Exploit a discovered vulnerability for personal benefit;
9. Publicly disclose a security vulnerability before the Company has had a reasonable opportunity to investigate it;
10. Upload unlawful, offensive, defamatory, abusive or infringing content;
11. Impersonate the Company, its employees or another User;
12. Use the programme to advertise unrelated services;
13. Attempt to manipulate payment records or testing dates; or
14. Use the website or software for fraud or any illegal purpose.

Suspected unlawful activity may be reported to the relevant authorities.

---

PART B: BETA TESTER PROGRAMME

6. Nature of the Beta Testing Programme

The Beta Testing Programme allows approved Users to test mobile applications, websites, software platforms and information systems before their official publication or commercial release.

Beta software is under development and may contain errors, incomplete features, performance problems or other defects.

Participation in the programme does not create an employment relationship, partnership, agency, joint venture or permanent service contract between the Tester and Codester Networks.

A Tester participates as an independent programme participant for the limited purpose of evaluating assigned software and submitting feedback.

7. Assignment of Tests

Available tests may be displayed on the User’s dashboard or communicated through email, SMS, telephone, WhatsApp or another approved communication channel.

Each test assignment may include:

• The name or identification number of the application;
• Compatible devices or operating systems;
• Installation instructions;
• Testing tasks;
• The official testing start date;
• The required testing period;
• Feedback requirements;
• Payment amount;
• Submission deadline; and
• Any special conditions.

A User is entitled to payment only for a test that has been officially assigned to or accepted by that User through the Company’s system.

Downloading an application without an official assignment does not create a right to payment.

The Company may limit the number of Testers assigned to an application.

8. Testing Period

Unless otherwise stated in the specific test instructions, the standard testing period is thirty consecutive calendar days.

The testing period begins on the date recorded by the Company as the official activation, installation or test-start date.

For a test to qualify for payment, the Tester must:

1. Successfully install or access the assigned application;
2. Keep the application installed and reasonably available on the registered device throughout the thirty-day period;
3. Use or test the application according to the assigned instructions;
4. Avoid disabling required testing permissions without a valid reason;
5. Submit the required feedback and test evidence;
6. Complete the test using the approved account and registered device; and
7. Avoid uninstalling the application before the test completion date.

Keeping an application installed without performing the required testing activities or submitting feedback may not qualify as a completed test.

Where the Company requires a period longer or shorter than thirty days, the different period must be clearly communicated before the Tester accepts the assignment.

9. Tester Responsibilities

During the testing period, the Tester must:

• Follow the testing instructions supplied by the Company;
• Test the application honestly and in good faith;
• Report errors, crashes, broken links and performance problems;
• Provide clear and constructive feedback;
• Submit reports within the stated deadlines;
• Use only devices lawfully owned or controlled by the Tester;
• Maintain sufficient storage space and internet connectivity;
• Install available test updates where reasonably requested;
• Notify the Company promptly where the application cannot be installed or used;
• Protect confidential information relating to unreleased software; and
• Avoid actions that may damage the software, device, Company systems or other Users.

The Tester must not knowingly submit the same issue repeatedly for the purpose of appearing more active.

10. Evidence of Testing

The Company may require reasonable evidence that a test was properly completed. Evidence may include:

• Installation and activation records;
• Login or activity records;
• Device type and operating-system information;
• Application version information;
• Crash and diagnostic reports;
• Screenshots or screen recordings;
• Completed questionnaires;
• Written feedback;
• Bug reports;
• In-application testing logs; or
• Confirmation that the application remained installed for the required period.

The Company will only request evidence that is reasonably necessary to verify testing, investigate errors, prevent fraud, improve software or process payment.

Testers must not submit screenshots, documents or recordings containing unnecessary personal information belonging to another person.

11. Beta Testing Payment

Unless a different amount is stated before a test is accepted, Codester Networks will pay an approved Tester UGX 5,000 for each application test successfully completed and approved.

The UGX 5,000 payment is a completion reward for one qualifying test. It is not a daily, weekly or monthly salary.

Payment becomes eligible only after:

1. The required thirty-day testing period has ended;
2. The application remained installed for the required period;
3. All required testing tasks were reasonably completed;
4. The Tester submitted the required feedback or report;
5. The Company verified the test results; and
6. No fraud, duplication or serious violation of these Terms is identified.

A User is not entitled to payment merely because an application was downloaded.

12. Payment Processing

Approved payments will normally be processed within seven to fourteen business days after the test has been verified and marked as completed.

Payments may be made through:

• Mobile money;
• Bank transfer;
• An approved digital payment service; or
• Another payment method communicated by the Company.

The Tester is responsible for providing accurate payment details.

The Company will not be responsible for payment delays or losses resulting from:

• Incorrect telephone numbers;
• Incorrect account information;
• Inactive mobile-money accounts;
• Accounts registered in another person’s name;
• Network failures;
• Payment-service interruptions;
• Identity-verification problems; or
• A Tester’s failure to respond to a verification request.

Where a payment fails because of incorrect details, the Company may request corrected information and reprocess the payment during the next available payment cycle.

Any transfer charges, withdrawal fees or taxes imposed directly on the Tester may be deducted or borne by the Tester where permitted by law and clearly communicated.

13. Costs of Participation

Unless the Company expressly agrees otherwise in writing, the Tester is responsible for:

• Internet data costs;
• Electricity and charging costs;
• Device maintenance;
• Storage space;
• Mobile-money withdrawal charges;
• Replacement of a lost or damaged device; and
• Any other ordinary cost of participating in the test.

The UGX 5,000 testing payment should not be interpreted as reimbursement for all costs incurred by the Tester.

The Company will not require a Tester to pay a registration fee before joining the Beta Testing Programme unless a separate paid service is clearly identified and voluntarily purchased.

Users should report any person claiming that payment must be made to secure a beta testing assignment.

14. Circumstances Where Payment May Be Withheld

Payment may be withheld or rejected where the Company has reasonable evidence that:

1. The application was removed before completion of the testing period;
2. The Tester did not complete the required tasks;
3. Required feedback was not submitted;
4. Feedback was copied, fabricated, automatically generated or materially false;
5. The same User created multiple accounts;
6. The same application was claimed multiple times using different accounts or devices;
7. The test was performed by another person;
8. Testing records, dates, screenshots or device information were altered;
9. The User attempted to manipulate the application or payment system;
10. The User violated confidentiality requirements;
11. The User engaged in fraudulent or unlawful conduct;
12. The payment details cannot reasonably be verified; or
13. The assignment was cancelled before testing began.

Before rejecting a payment for an incomplete or disputed test, the Company may provide the Tester with an opportunity to submit additional evidence or correct missing information.

The Company should provide a brief reason where a payment is rejected, except where disclosure would compromise a security or fraud investigation.

15. Interrupted or Cancelled Tests

Where a test cannot be completed because of a confirmed technical failure caused by the test application, the Company may:

• Extend the testing period;
• Provide a replacement application version;
• Pause the test until the defect is corrected;
• Assign another application; or
• Approve a full or partial payment where sufficient testing work was completed.

Where the Company cancels a test after a User has substantially completed the required work, the Company will determine a fair payment based on the verified work completed.

A Tester who changes, loses, damages, resets or replaces the registered device must notify the Company promptly. The test may be restarted, transferred or cancelled depending on the circumstances.

16. Payment Disputes

A Tester who believes that a payment has been incorrectly rejected or delayed should submit a complaint within thirty days after the expected payment date.

The complaint should include:

• The Tester’s registered name;
• Account username or registration number;
• Application tested;
• Testing start and completion dates;
• Payment telephone number or account;
• Relevant screenshots or reports; and
• A description of the issue.

The Company will review the complaint and communicate its decision within a reasonable period.

---

PART C: SOFTWARE, CONFIDENTIALITY AND INTELLECTUAL PROPERTY

17. Beta Software Disclaimer

Test applications are provided on an “as available” and developmental basis.

Because beta software is incomplete, it may:

• Crash or stop responding;
• Contain programming errors;
• Consume additional battery power or data;
• Be incompatible with some devices;
• Lose locally stored test information;
• Display incomplete or inaccurate information;
• Change without notice; or
• Be withdrawn before public release.

Testers should back up important information before installing beta software.

Beta applications must not be relied upon for emergency services, medical decisions, financial transactions, personal safety or other critical activities unless the Company expressly states that the application is approved for that purpose.

18. Device Permissions and Safety

Before installation, the Company should inform Testers of the main device permissions required by an application.

Testers should review permission requests and must not install an application where they do not understand or accept the requested access.

The Company will not intentionally require access to information that is unrelated to the legitimate testing purpose.

A Tester must immediately report unexpected permission requests, suspicious behaviour, excessive data use or a possible security incident.

19. Confidentiality

Some applications, systems, designs, documents and features provided through the Beta Testing Programme may be confidential and not yet publicly available.

Unless the Company gives written permission, a Tester must not:

• Publish screenshots or videos of unreleased software;
• Share installation files or download links;
• Disclose confidential features or technical details;
• Share usernames, passwords, activation keys or test credentials;
• Provide test software to another person;
• Publish vulnerability information;
• Discuss private client projects publicly; or
• Use confidential information for personal or commercial benefit.

Confidentiality obligations continue after the test period ends.

Information that was already lawfully public, independently developed by the Tester or lawfully obtained from another source without a confidentiality obligation will not be treated as confidential.

20. Intellectual Property Rights

All intellectual-property rights in the website, applications, systems, designs, source code, databases, logos, trademarks, documentation and other materials remain the property of Codester Networks or the relevant owner or client.

Participation in the Beta Testing Programme does not transfer ownership of any software or intellectual property to the Tester.

The Company grants the Tester a limited, temporary, personal, non-exclusive, non-transferable and revocable right to use the assigned beta software only for authorised testing.

The Tester must not sell, license, reproduce, distribute or commercially exploit the beta software.

21. Ownership and Use of Feedback

The Tester permits the Company to use feedback, suggestions, bug reports and recommendations submitted through the programme for purposes including:

• Correcting software errors;
• Improving performance;
• Designing new features;
• Developing future applications;
• Preparing technical documentation;
• Conducting quality assurance; and
• Supporting publication or commercial release.

Where legally permitted, feedback may be used without an additional royalty or payment beyond the agreed testing reward.

The Company will not publicly identify the Tester as the author of feedback without permission, except where required by law.

---

PART D: PRIVACY AND PERSONAL INFORMATION

22. Information We May Collect

The Company may collect information including:

• Full name;
• Email address;
• Telephone number;
• Date of birth or age confirmation;
• District, country or general location;
• Account username;
• Password in protected form;
• Payment details;
• Device model;
• Operating system and application version;
• Device identifiers where reasonably required;
• Internet Protocol address;
• Login and activity records;
• Installation and testing dates;
• Crash logs and diagnostic information;
• Feedback, screenshots and support communications;
• Records relating to completed tests and payments; and
• Fraud-prevention and account-security information.

The Company will not request a User’s mobile-money PIN, bank PIN, email password or one-time transaction password.

23. Purposes of Processing Information

Personal information may be processed to:

• Register and manage User accounts;
• Determine eligibility for testing;
• Assign compatible applications;
• Verify installations and testing completion;
• Communicate instructions and updates;
• Process and confirm payments;
• Prevent duplicate accounts and fraud;
• Provide technical support;
• Investigate security incidents;
• Improve applications and services;
• Maintain financial and operational records;
• Enforce these Terms; and
• Comply with legal obligations.

24. Consent and Lawful Processing

By registering and participating, the User authorises the Company to process personal information for the purposes described in these Terms and the Company’s Privacy Policy.

Where consent is the legal basis for processing, the User may withdraw consent by contacting the Company. Withdrawal will not affect processing already lawfully completed.

Withdrawal of information that is necessary to operate an account, verify a test or process payment may make it impossible for the User to continue participating.

25. Sharing of Information

The Company may share limited information with:

• Developers and quality-assurance personnel;
• Clients who own the tested application;
• Payment-service providers;
• Website hosting and cloud-service providers;
• Technical support providers;
• Professional advisers;
• Fraud-prevention providers;
• Government agencies, courts or regulators where legally required; and
• A successor organisation following a lawful merger, restructuring or transfer of business.

Service providers must only receive information reasonably necessary to perform their functions.

The Company will not sell a Tester’s personal information to advertisers.

26. Information Security

The Company will take reasonable administrative, organisational and technical measures to protect personal information against:

• Unauthorised access;
• Accidental loss;
• Unlawful disclosure;
• Destruction;
• Alteration;
• Misuse; and
• Fraudulent access.

However, no website, internet transmission or electronic-storage system can be guaranteed to be completely secure.

Users must protect their login details and immediately report suspected unauthorised access.

27. Retention of Information

Personal information will be retained only for as long as reasonably necessary to:

• Operate the Beta Testing Programme;
• Verify completed tests;
• Process payments;
• Resolve complaints;
• Prevent fraud;
• Maintain accounting and tax records;
• Enforce agreements; and
• Meet legal or regulatory requirements.

Information that is no longer required will be securely deleted, anonymised or archived as required by law.

28. User Privacy Rights

Subject to applicable law, a User may request to:

• Access personal information held about them;
• Correct inaccurate or incomplete information;
• Withdraw consent where processing is based on consent;
• Object to certain processing;
• Request deletion of information that is no longer legally required;
• Obtain information about how their data is being used; or
• Submit a privacy complaint.

Requests may be subject to identity verification and lawful record-retention requirements.

The Company should provide a separate detailed Privacy Policy explaining its data-controller identity, contact details, cookies, international data transfers, retention periods and complaint procedures.

---

PART E: ACCOUNTS, SUSPENSION AND TERMINATION

29. Account Suspension

The Company may temporarily suspend an account where it reasonably suspects:

• Fraud;
• Duplicate registration;
• Unauthorised access;
• False information;
• Payment manipulation;
• Abuse of an application;
• A security threat;
• Violation of confidentiality; or
• A serious breach of these Terms.

Suspension may remain in place while an investigation is conducted.

30. Account Termination

The Company may terminate an account where:

1. The User repeatedly or seriously violates these Terms;
2. The User submits false testing evidence;
3. The User creates multiple accounts to obtain improper payments;
4. The User misuses confidential software;
5. The User threatens the security of Company systems;
6. The User engages in abusive or unlawful conduct;
7. Continued participation creates a legal or security risk; or
8. The Beta Testing Programme is discontinued.

Where reasonably possible, the Company will notify the User of termination.

Termination does not remove a User’s right to receive an approved and undisputed payment for testing properly completed before termination.

Rights concerning confidentiality, intellectual property, fraud, privacy, liability and dispute resolution continue after termination where applicable.

31. Closing an Account

A User may request account closure by contacting the Company through the official contact details.

Before closing an account, the User should complete any active test or notify the Company that the test cannot be completed.

Closing an account before completing an assigned test may result in loss of eligibility for that test’s payment.

The Company may retain limited records after account closure where required for payment, accounting, fraud prevention, legal compliance or dispute resolution.

---

PART F: LIABILITY AND DISPUTE RESOLUTION

32. Limitation of Liability

The Company will take reasonable measures to provide safe and functional testing software. However, to the extent permitted by law, the Company will not be responsible for indirect, incidental or consequential losses arising from:

• The ordinary use of incomplete beta software;
• Temporary website or application unavailability;
• Loss of unsaved test data;
• Device incompatibility;
• Network or internet interruptions;
• Failure of third-party payment services;
• A User’s failure to follow instructions;
• Unauthorised use of an account caused by the User’s failure to protect credentials; or
• Use of beta software for an unauthorised or critical purpose.

Nothing in these Terms excludes liability that cannot lawfully be excluded, including liability arising from fraud, wilful misconduct or other liability protected by applicable law.

33. User Responsibility and Indemnity

A User is responsible for losses reasonably caused by their:

• Fraudulent activity;
• Unlawful use of the service;
• Deliberate damage to Company systems;
• Unauthorised disclosure of confidential information;
• Infringement of another person’s intellectual-property rights; or
• Material violation of these Terms.

The Company will not hold a User responsible for losses caused solely by an undisclosed defect in the beta software where the User followed the provided instructions.

34. Complaints

Complaints concerning accounts, testing, payments, privacy or conduct should first be submitted to:

Codester Networks Limited
Email: info@codesternetworksltd.com
Telephone: +256 701 840337
Physical Address: Ntinda
Website: https://codesternetworksltd.com

The complaint should clearly describe the problem and provide relevant supporting information.

The Company will attempt to investigate and respond within a reasonable period.

35. Dispute Resolution

The parties should first attempt to resolve any dispute through good-faith communication and internal review.

Where a dispute is not resolved, the parties may attempt mediation or another mutually agreed alternative dispute-resolution procedure.

Nothing in this section prevents either party from referring a matter to a competent court, regulator or lawful authority.

36. Governing Law

These Terms are governed by the laws of the Republic of Uganda.

Subject to any mandatory legal rights, disputes arising from these Terms will be handled by courts or other competent authorities in Uganda.

---

PART G: GENERAL CONDITIONS

37. Changes to the Programme

The Company may modify, suspend or discontinue:

• A particular beta test;
• The UGX 5,000 standard payment for future tests;
• Testing requirements;
• Available applications;
• Payment methods; or
• The entire Beta Testing Programme.

A change to payment or testing requirements will not normally apply retrospectively to a test already accepted unless the change benefits the Tester, is required by law or is necessary to address fraud or security risks.

The payment amount applicable to a test should be the amount displayed when the Tester accepts that assignment.

38. Changes to These Terms

The Company may update these Terms to reflect:

• Changes in law;
• Changes to the website or programme;
• New payment methods;
• Security requirements;
• New application-testing procedures; or
• Operational improvements.

Updated Terms will be published on the website with a revised effective date.

Where a change materially affects an active test or a User’s rights, the Company should provide reasonable notice through the website, email, SMS or account dashboard.

Continued use of the service after the effective date of updated Terms constitutes acceptance of the revised Terms.

39. Notices and Electronic Communication

Users agree that notices, testing instructions, payment information and other communications may be provided electronically through:

• The website;
• The User’s dashboard;
• Email;
• SMS;
• WhatsApp; or
• Another contact method provided by the User.

Users are responsible for keeping their contact information current.

Electronic acceptance of these Terms, including selecting an acceptance checkbox, may serve as confirmation of agreement.

40. Third-Party Services

The website and applications may use third-party services including hosting providers, analytics services, app-distribution platforms, payment providers and communication services.

The Company is not responsible for third-party services outside its reasonable control. Use of those services may also be governed by the third party’s own terms and privacy rules.

41. Assignment

A User may not transfer their account, testing assignment, payment entitlement or obligations to another person without written permission.

The Company may transfer its rights and responsibilities to an affiliated company, successor or lawful purchaser of the relevant business, provided Users’ legal and privacy rights remain protected.

42. Severability

Where any provision of these Terms is found to be invalid or unenforceable, the remaining provisions will continue to apply.

The invalid provision will be interpreted or replaced, as far as legally permitted, in a manner that most closely reflects its original purpose.

43. No Waiver

Failure by the Company to immediately enforce a provision of these Terms does not mean that the Company has waived its right to enforce that provision later.

44. Entire Agreement

These Terms, together with the Privacy Policy, specific testing instructions and any other terms expressly accepted by the User, constitute the agreement governing participation in the Beta Testing Programme.

Where specific test instructions conflict with these general Terms, the specific instructions will apply only to that particular test, provided they are lawful and were disclosed before the Tester accepted the assignment.

45. Contact Information

Questions about these Terms or the Beta Testing Programme should be directed to:

Codester Networks Limited
Website: https://codesternetworksltd.com
Email: info@ codesternetworksltd.com
Telephone: 0774881979
Physical Address: Ntinda

---

BETA TESTER ACCEPTANCE DECLARATION

By selecting “I Agree”, registering as a Beta Tester or accepting a testing assignment, I confirm that:

1. I am at least eighteen years old;
2. I have provided accurate registration and payment information;
3. I understand that registration does not guarantee a testing assignment;
4. I understand that downloading an application alone does not qualify me for payment;
5. I agree to keep an assigned application installed for the full required testing period;
6. I agree to perform the required testing activities and submit genuine feedback;
7. I understand that the standard payment is UGX 5,000 for each successfully completed and approved application test;
8. I understand that payment is processed after the testing period and verification have been completed;
9. I will not create multiple accounts, falsify evidence or manipulate testing records;
10. I will protect confidential and unreleased information;
11. I agree to the processing of my personal information as explained in these Terms and the Privacy Policy; and
12. I agree to comply with these Terms and Conditions.

Acceptance checkbox wording:

☐ I have read, understood and agree to the Codester Networks Limited Website User Policy, Beta Tester Programme Terms and Conditions, and Privacy Policy. I confirm that I am at least eighteen years old.