Hi Apple team,
We’re evaluating how we generate appAccountToken for in-app purchases.
For privacy and security reasons, rather than using a stable UUID associated with an account across all purchases, we’re considering generating a different opaque value for each purchase/context. Internally, our backend would maintain the mapping needed to associate each value with the correct customer account and, potentially, additional purchase context.
In other words, the same customer account may result in different appAccountToken values across separate purchases, while our backend can still deterministically resolve each token to the correct account.
We’d like to confirm:
- Does Apple expect or recommend that appAccountToken remain stable for the same app account across purchases?
- Are there any concerns with this approach for non-subscription / one-time purchases, assuming we maintain the account association on our backend?
Our goal is to avoid exposing a stable account-correlatable identifier while still maintaining reliable server-side attribution.
Thanks!