[RESOLVIDO] O que é isso agora da gp?

Alguém da Fabapp para ajudar com isso? Recebi este e-mail da GP e não sei o que devo fazer!

DEVELOPER UPDATE
Hello Google Play Developer,
We strive to make Google Play the safest and most trusted experience possible. To that end, we make regular updates to our policies. You can find the details of the latest changes to our policies, including when these changes take effect, in our Policy Center.
You’ll have at least 30 days from the date of this notification to update your app to comply with the following policy changes:
Upcoming new policies

  • We’re introducing a new restricted permission requirement for Exact Alarm API, stating that apps must only declare this permission if their core functionality requires an exact alarm. Apps declaring the new restricted permission that do not meet these criteria will not be permitted on Google Play.
  • We’re adding new guidelines to our Ads policy to improve the in-app user experience and to prohibit unexpected interstitial ads, inspired by the Better Ads Standards - Mobile Apps Experiences guidelines.
  • We’re introducing new requirements for the FLAG_SECURE declaration under our Device and Network Abuse policy stating that all apps must respect the FLAG_SECURE declaration and must not facilitate or create workarounds to bypass the FLAG_SECURE settings in other apps.
  • We’re introducing new requirements under our Permissions policy to state that all apps must have acceptable core functionalities to use VPNService class. We’ve also added guidance on key requirements for using VPNService class.
    Policy updates
  • We’re updating our Subscriptions policy to state that users must be able to easily cancel their subscriptions from within the app.
  • We’re updating our existing stalkerware guidance with a monitoring apps flag “IsMonitoringTool” for all legitimate monitoring applications. All apps that use this tool must also disclose monitoring or tracking functionality in their Google Play store description.
  • We’re updating health misinformation guidelines to state that we don’t allow apps containing misleading health claims that contradict existing medical consensus, or that can cause harm to users.
  • We’re updating our Families Self-Certified Ads SDK Program to require that self-certified ads SDK providers must submit new policy-compliant, self-certified versions and a test app to remain in the Families Self-Certified Ads SDK Program. Learn more about Families Self-Certified Ads SDKs.
  • We’re updating our Impersonation policy to clarify that the policy prohibits impersonation of other entities or organizations. We’ve also added some new examples regarding app titles and icons.
    Additionally, we’ve added new examples and clarifications to some of our existing policies. Because these policies aren’t new or updated, our enforcement standards and practices for these policies remain the same.
  • We’re clarifying our Ads policy to state that the Ad ID may no longer be connected to a persistent identifier or personally-identifiable information for any purpose including analytics purposes.
  • We’re consolidating health and medical-related policies into an easy-to-navigate page.
  • We’re clarifying the Made For Ads guidelines under our Spam policy to prevent apps from displaying interstitial ads repeatedly to distract users from engaging with an app and performing in-app tasks.
  • We’re clarifying our Ads policy to emphasize that ads and their associated offers served in your app must be consistent with your app’s content rating.
  • We’re clarifying our Families Data Practices policy to state that apps that solely target children must not transmit Android advertising identifier (AAID), SIM Serial, Build Serial, BSSID, MAC, SSID, IMEI, and/or IMSI. Apps that target both children and older audiences must not transmit AAID, SIM Serial, Build Serial, BSSID, MAC, SSID, IMEI, and/or IMSI from children or users of unknown age.
  • We’re clarifying our sensitive events definition and examples under the Inappropriate Content policy to state that we don’t allow apps that capitalize on or are insensitive toward a sensitive event with significant social, cultural, or political impact (e.g. civil emergencies, natural disasters, public health emergencies, conflicts, deaths, or other tragic events).
  • We’re moving country-specific guidelines from our Real-Money Gambling, Games, and Contests policy page to a link on our Gambling Application Form for easier reference.
  • We’re clarifying Privacy Policy guidelines under our User Data policy to state that all apps must post a privacy policy link in the designated field within Play Console and a privacy policy link or text within the app itself. We’re also specifying that privacy policies must be publicly accessible and non-geofenced. Learn more about adding a privacy policy.
  • We’re clarifying our Child Endangerment policy to reinforce that we prohibit the use of apps to endanger children, including the facilitation of child trafficking, grooming, and sextortion.
    Additional reminders
  • The Data safety section launched on Google Play in late April. All developers must have had their Data safety form approved and included a privacy policy by July 20, 2022. Apps that still need a Data safety form and privacy policy will receive warnings and updates will be rejected. In the future, these apps may be subject to removal from Google Play. Review new FAQs, including on the Data safety form’s deletion request mechanism badge, in the Help Center.
  • All apps using Advertising ID and targeting API level 33 must have declared the Advertising Identifier permission in the manifest file and completed the declaration in Play Console by July 26. Apps without this permission will receive a string of zeros instead of the identifier if they attempt to access the identifier. Also, you will not be able to create releases targeting Android 13 until you complete the advertising ID declaration form.
  • Starting November 1, 2022, apps that don’t target an API level within two years of the latest major Android version release will not be available on Google Play to new users whose devices run the latest versions of Android. Later this year, developers can request a six-month extension if more time for migration is needed. Learn more about target API level requirements for Google Play apps.
    We encourage you to review these policy updates carefully in case any of your apps are impacted. To learn more, watch this PolicyBytes video or register for a policy webinar, available for multiple regions (Global, India, Japan, Korea, or Brazil).
    REVIEW UPDATES

Bom dia Claudio, tudo bem?

Este e-mail fala sobre as novas políticas do Google e sobre como seu app precisa estar em conformidade com elas, como por exemplo a possibilidade de exclusão da conta do seu usuário… O tratamento correto de dados!

Por enquanto estamos tomando os devidos cuidados para ficar de acordo com as politicas do Google no app, neste caso não é necessário fazer nada :wink:

Se tiver qualquer dúvida, pode nos chamar!

Entendi que o atendimento das exigências da GP neste caso serão tomadas por vocês e não preciso fazer nada. Ufa!
Obrigado!

Bom dia Claudio, exato! Caso tenha algum ponto que você precise fazer, o Google avisará como pendência da publicação, por exemplo, aquele formulário de coleta da dados, mas nestes casos, nós temos os artigos, canais de suporte…

Valeu! Muito Obrigado!

Bom dia Claudio, imagina! Se tiver qualquer dúvida, é só chamar!