Violations & Consequences

Real examples of rule violations and their consequences. Understanding these helps maintain a fair, trustworthy marketplace.

Severity levels:Critical — Immediate actionHigh — Warning + enforcementMedium — Corrective action

Task Violations (Developer)

Soliciting App Store reviews

Critical

Example

"Please leave a 5-star review on Google Play after testing."

Rule

BetaPerks tasks are for gathering genuine product feedback only. App Store/Google Play review manipulation violates platform policies of Apple and Google.

Consequence

Immediate task removal. Repeat offenses result in account suspension.

Fake install requests

Critical

Example

"Download and keep the app installed for 7 days to boost our install count."

Rule

Tasks must have a genuine testing purpose. Using BetaPerks to inflate install metrics is strictly prohibited.

Consequence

Task removed and developer account flagged for review.

Malicious or unsafe links

Critical

Example

Linking to a phishing site, malware, or a URL that redirects to unrelated content.

Rule

All install links must point to the actual application being tested.

Consequence

Immediate account termination. Reported to relevant authorities if necessary.

Misleading reward promises

High

Example

Offering "$50 cash reward" but only providing a $2 coupon code after testing.

Rule

Rewards must match what was described when the task was published.

Consequence

Task frozen, all pending rewards honored at the described level, and developer trust score reduced.

Feedback Violations (Tester)

Copy-paste or AI-generated spam feedback

High

Example

Submitting generic text like "The app is good. UI is nice. No bugs found." across multiple tasks without actual testing.

Rule

Feedback must reflect genuine use of the application with specific, actionable observations.

Consequence

Feedback rejected, no reward issued, trust score reduced.

Multi-account abuse

Critical

Example

Creating 3 accounts to submit 3 feedbacks on the same task to collect multiple rewards.

Rule

Each user may only have one BetaPerks account.

Consequence

All accounts permanently banned. All pending rewards cancelled.

Fabricated bug reports

High

Example

Claiming "app crashes on launch" when the app works fine, just to appear productive.

Rule

Bug reports must be reproducible and accurately describe observed behavior.

Consequence

Feedback rejected, trust score significantly reduced, potential account suspension.

Reward Violations

Reward extortion

High

Example

"Give me a bigger reward or I'll leave a bad review on the App Store."

Rule

Rewards are determined by the developer when publishing the task. Testers accept the terms when applying.

Consequence

Tester account suspended. Dispute auto-dismissed.

Failure to deliver promised rewards

High

Example

Developer approves feedback but never sends the promo code, ignoring tester messages.

Rule

Developers must fulfill reward promises within 7 days of feedback approval.

Consequence

Developer trust score reduced. Tester can escalate via dispute. Repeated offenses lead to account restriction.

General Violations

Harassment or abusive communication

Critical

Example

Sending threatening messages through feedback descriptions or dispute forms.

Rule

All platform communication must be professional and constructive.

Consequence

Immediate account suspension pending review.

Impersonation

Critical

Example

Claiming to be a BetaPerks admin or moderator in communications with other users.

Rule

Users must not misrepresent their identity or platform role.

Consequence

Permanent account ban.

Appeal Process

If you believe an enforcement action was applied incorrectly, you may appeal by contacting our support team at appeals@betaperks.com. Include your account email, the action you're appealing, and your reasoning. We review all appeals within 5 business days.