Tester Programme Terms

Last updated: 14 November 2026

These terms describe the proposed Android app and game testing programme. By accepting them, you confirm that you understand the requirements. Acceptance and Google sign-in do not by themselves guarantee selection, assignment or payment.

1. Programme scope

Selected participants may be assigned up to 20 Android applications or games. The coordinator will provide the list, access instructions, testing start date and exact programme duration before testing begins.

2. Daily testing commitment

For each assigned app, the participant is expected to spend at least 6 minutes per day using it genuinely for the agreed 25–30 consecutive day period. Participants must follow the app-specific instructions and report genuine observations, defects and usability feedback. The coordinator must confirm in writing whether any schedule adjustments are approved.

3. Rewards and payment

The stated reward is USD $25 for each assigned app that is fully completed and verified, up to USD $500 for 20 completed apps. Payment is conditional on completion of the agreed testing tasks and verification by the programme team. Before beginning, the coordinator must confirm the exact start/end dates, verification criteria, payment method, applicable fees and payout date. Do not begin work if these details have not been explained and agreed.

4. Genuine testing and conduct

Participants must use the apps as real users, provide truthful feedback and promptly report issues. No fabricated activity, automated usage, fake reviews, manipulated ratings, misleading feedback, or attempts to bypass app-store testing rules are permitted. Testing does not require a positive review or public rating.

5. Eligibility and app access

Participants must have a compatible Android device, reliable internet access and the ability to complete the daily schedule. App availability, geographic eligibility, age requirements and any device requirements will be communicated by the coordinator. Do not share passwords, one-time codes or payment-card details with anyone claiming to represent the programme.

6. Application identity

Google sign-in is used to identify an application by its email address. Signing in is not a contract of employment and does not mean that an applicant has been selected. The programme team should confirm selection and all material terms before testing starts.

7. Questions and support

For clarification, contact the testing coordinator using the WhatsApp link provided after sign-in. Keep a copy of the agreed testing instructions and payment terms.

8. Changes

Any material change to the duration, assigned apps, completion criteria or reward must be communicated and accepted before it takes effect.