AppReviewX Log in

Published developer reviews: consent and anonymity

How owners may publish accepted feedback only with the tester's consent, anonymously.

In this guide

Feedback on AppReviewX is private by default. An owner may want to show a good piece of it on their app page. That is allowed only under two conditions.

The two conditions

  1. The tester agrees. Nothing is published without the tester's consent.
  2. It is anonymous. The tester is not named.

The feedback must also have been accepted by the owner. Unaccepted or unclear feedback stays private.

What this is not

  • It is not a store rating. It does not appear on Google Play or the App Store and does not change your store average.
  • It is not a reward. Consent is asked for the text, not traded for credits or favours.
  • It is not a substitute for store reviews. Do not present it as one.

Testers wrote privately and may have mentioned things they would not say in public. Asking first respects that. Anonymity also keeps comments honest, because nobody has to worry about how a public quote reflects on them.

Consent can be a question you ask after accepting feedback: "May we show this sentence on the app page, without your name?" A "no" or no answer means it stays private.

How to choose what to publish

  • Pick specific, useful statements ("The onboarding was clear in under a minute") over general praise.
  • Quote exactly; do not edit meaning. Trim only for length and say so if you do.
  • Do not cherry-pick to hide known problems in a way that misleads visitors.
  • Leave out anything that identifies the tester or reveals other apps' details.

Data protection rules vary by country. This is general information, not legal advice; get proper advice if you are unsure.

Where to reply to what: respond to feedback vs reviews. Using hard feedback well: learn from your one-star reviews.

Get started.

Related: hub, respond to feedback vs reviews, learn from one-star reviews.