Do App Developers See Your Name and Email When You Review?

No — when you leave an app review, the developer never sees your email address. On the Apple App Store they see only the nickname you picked. On Google Play they see your public Google profile name and photo, plus your device model and the app version you reviewed. Neither store hands over your email, and neither gives the developer a private way to message you.

That last detail is the whole reason a developer's reply is public. They can't DM you, they can't email you, they can't look you up. The comment stacked under your review is the only channel they have to reach the person who wrote it. That's exactly why it matters how they use it.

Less than most people assume, and it differs by store. A developer reads your review inside App Store Connect (Apple) or the Play Console (Google), and each dashboard exposes a fixed, public set of fields, not your account and not your contact details. Here's the full picture on each side.

No. Apple requires you to set a nickname before you can post a review, and that nickname is the only identity attached to it: not your real name, not your Apple ID email. You choose it in your device settings under your Apple Account, and you can change it. If you named yourself "appfan_2019," that string is what the developer sees, forever, on every review you leave.

This is deliberate on Apple's part. The App Store treats reviews as pseudonymous by design, so the person reading your one-star rant knows you as a handle, not a human they could email. It also means a developer genuinely cannot tell whether two reviews came from the same real person unless the nicknames match.

This is the one that surprises people. Google Play displays the name on your Google account, and if you never changed it, that's usually your real first and last name plus your profile photo. It still isn't your email, and a developer can't message you through it. But your review is more identifiable on Play than on Apple, because Play piggybacks on your everyday Google identity instead of a review-only nickname.

If that bothers you, you can change the display name and photo on your Google account, and existing reviews update to match. Plenty of people leave app reviews under a nickname on Google for exactly this reason. The two stores' different approaches to reviewer identity are part of a bigger set of gaps we map out in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

No, and this is the part worth internalizing. There is no button in App Store Connect or the Play Console that lets a developer email or message a reviewer. If they want to respond, apologize, or tell you a bug is fixed, their only option is to post a public reply beneath your review. That reply then shows up for every future visitor to the listing, and triggers a [notification back to you](/blog/what-happens-when-a-developer-replies-to-your-review).

So when you see a developer write "email us at support@…" inside their reply, that's not them having your address. It's them trying to move the conversation somewhere they can actually help you, because the store won't give them a private line. The public reply is a doorway, not the destination.

Notice what that reply is doing. The developer can't see this reviewer's email, can't contact them off-listing, and gets exactly one public shot to turn a two-star into a refund request and, ideally, a re-review. Every future shopper reading the listing sees it too. That's why a calm, specific public answer is worth so much more than a private support ticket. It works on the reviewer and the audience at once. If you're a developer wondering how to write ones like this, [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) is the playbook.

If you're the developer, the takeaway flips. You can't reach unhappy reviewers by email, so the public reply isn't a nicety. It's your single lever, and it moves ratings measurably. Google shared at I/O 2019 that apps average about a +0.7-star lift when developers respond to reviews. In a study of 4.5 million reviews, Hassan et al. found reviewers who got a reply were roughly six times more likely to raise their rating than those who didn't (4.4% versus 0.7%). You're not just being polite in that reply box; you're using the one door the store leaves open.

The catch is that the door slams shut fast. Reviews go stale, they pile up across two stores, and they arrive in whatever language the reviewer speaks. Answering all of them, on time, in the reviewer's own tongue, by hand, is the actual hard part. The mechanics above are simple.

So the short answer holds: your email stays yours, your App Store identity is just a nickname, and the only thing a developer can do is reply in public. If you're on the other side of that reply box — trying to reach reviewers you'll never be able to email, across two stores and a dozen languages — that's the exact job ReplyArgus does for you. [Start free, no card](/signup), and Argus drafts your first reply in minutes.