In this guide
A real sentence from a real tester can say more than your own copy. It only works if it is real, and if the person agreed to it. This is general guidance, not legal advice.
Rules to hold yourself to
- Ask first. Private feedback was given to help you improve the app. Using it in marketing is a different purpose, so get a clear yes for that use.
- Never invent a quote, a name, a job title or a company.
- Never change the meaning. You may fix a typo. You may shorten with a clear mark ("..."). You may not cut "not bad, but too slow" down to "bad" or "not bad".
- Don't pay or reward for a quote, and don't make test access depend on agreeing to one. A reward-driven quote is not an honest opinion.
- Let people withdraw. If someone asks you to remove their quote, do it.
- Anonymous by default on your own site. Use a name only if the person wants to be named and says so. For a store listing, see below.
What to ask for
Ask for one thing, in plain words, and offer an easy "no".
Template, adapt it: "Hi [name], thank you for your feedback on [app]. One sentence you wrote was: '[exact quote]'. May I show it on my website [and in the store listing]? I would [not name you / name you as '(first name, role)']. You can say no, or ask me to remove it later, and that will not affect anything. If you want a different wording, just send it."
Save the reply (a message is enough) with the date and the exact text you agreed on.
Where it can go
- Your own website or landing page.
- Marketing material.
Be careful with store listings. Google Play's metadata policy does not allow unattributed or anonymous user testimonials in the app description, so an anonymous quote does not belong there. Apple's guideline 2.3.14 says creative assets should not include unverifiable product claims. Check the current official pages before you put quotes into screenshots or listing text.
Don't turn feedback into a trade
Do not offer a quote request as a condition of getting feedback, and do not ask for a store review at the same time. Store ratings are the user's own, voluntary choice, never traded; see app review exchange for why swaps are not a path.
How AppReviewX handles it
Feedback is private and structured. One feedback you write earns one credit; new accounts start with 0 credits. A developer review is published on an app page only with the tester's consent and anonymously: public developer reviews on app pages.
Related
Get started and collect feedback you can ask permission for later.