Community Guidelines

For testers

• Really use the app. Open it, try the features the developer asked about, and spend real time in it.
• Write useful feedback. Say what you did and what happened. "Nice app" every day is not feedback.
• Stay for 14 days. A developer's production access depends on you staying opted in. If you must leave, use the Leave button (−15 credits) instead of silently uninstalling.
• Use your own real device and account. No emulators, scripts, or shared accounts.

For developers

• List real, working apps with a valid closed-test opt-in link.
• Add testers promptly to your Play Console email list or Google Group.
• Write clear testing instructions and, ideally, set an in-app verification code.
• Moderate fairly. Remove testers only for genuine reasons (never opted in, fake feedback, abuse). Removal gives the tester a strike.
• Reply to feedback. It keeps testers motivated.

Not allowed

• Apps with malware, deceptive behaviour, adult content, gambling for real money, or anything violating Google Play policies.
• Asking testers to pay, leave Play Store reviews, or share sensitive personal data.
• Harassment, hate speech, or spam in feedback or replies.
• Multiple accounts, credit farming, or trading credits outside the platform.

Strikes

Strikes come from being removed from a test. 3 strikes block an account from joining new tests. Serious abuse can lead to immediate suspension. If you think a removal was unfair, contact us with the app name.