Dear Publishers,
We want to bring to your attention some recent issues that have been reported with regards to data safety on Google Play. One of the main concerns has been around Invalid Encryption Declaration, which was fixed in the app rather than in Data Safety. As a result, all server requests are now being served via https, ensuring a higher level of data safety for your app users.
It's important to note that publishers need to update their aab file, not the Data Safety section, to ensure their app is compliant with these new data safety requirements. In some cases, Google Play may reject an update and provide old bundles as a reject reason. To resolve this issue, you will need to publish an update again.
We are aware that Google is currently asking for an advertising id declaration. Please note that this can be ignored for now, as it doesn't affect your publishing process. Additionally, Google may also be asking for an account creation declaration in the Data Safety section. While we are preparing a guide on how to complete this requirement, it can also be ignored for the time being.
To solve the current issues with Data Safety on Google Play, publishers must submit an updated aab file to the platform. We apologize for any inconvenience this may have caused and thank you for your patience and cooperation in ensuring the highest level of data safety for your app users.
