Store policy

What Google says

Your app shouldn't ask the user any questions before or while presenting the rating button or card, including questions about their opinion (such as "Do you like the app?") or predictive questions (such as "Would you rate this app 5 stars").

You should not have a call-to-action option (such as a button) to trigger the API.

From Google's In-App Review guidelines, page dated 2026-01-30, verified 2026-09-18.

What Apple says

On iOS, reviews are requested through the system prompt only, and the system shows it at most three times in 365 days, whatever the app asks for. See Apple's page on ratings and reviews.

What the SDK does

• The store prompt fires only from a trigger. TrackAsync is the only path to it, and it takes a trigger name — nothing about the screen, the tap or the button that led there. Call it where the behaviour happens (a level finished, a trip saved), never from a button that asks for a review.
• The default components never trigger it. The Blazor FeedbackAsk component and the Unity FeedbackAskPanel never call TrackAsync, so nothing a user does inside the ask can cause a store prompt.
• No question in front of it. The SDK shows nothing before the store prompt. One IFeedbackLoop takes at most one action per session, so an ask and a store prompt never follow each other in the same session.
• Fixed limits the rules cannot change: at most 3 store prompts in any rolling 365 days; none within 60 days of a note the user sent; none within 7 days of an ask the user was shown, however they answered it.
• A store link is a link. Where there is no native prompt (the web), StoreLinks gives you the listing URL for a plain link, not a button that claims to open a review.

Ordering the two: defensible, not blessed

Your rules can order the actions: the private ask first, the store prompt days later, and not for someone who wrote to you recently. We think that ordering is defensible: the ask is a request for things to fix, shown in a different session from the store prompt; no question stands in front of the store prompt; and the optional 1-to-5 rating in the ask is private — the engine never reads it, so a high rating does not bring the store prompt any closer.

It is not blessed. Neither Google nor Apple endorses it, and sending a note does hold the store prompt back for longer than seeing an ask does (the two quiet periods above). If you use it, describe it plainly, to your users and to store reviewers, as what it is: a private way to reach you, and, separately, the store's own prompt. Policies change; re-read the two pages above before you ship.