[MUSIC PLAYING]
THERESA: Hi.
I'm Theresa, product marketing manager for Android and Google
Play.
Welcome to Google Play PolicyBytes.
And thanks for joining us.
Today, we'll start with an update on our safety
initiatives.
Then we'll talk about our user choice billing, policy updates,
and timeline.
Our safety initiatives and policies
are core ways that we maintain trusted experiences
that users expect.
Today, we'll share new features and programs
to better partner with you in making Google Play a safer
platform for everyone.
First, we launched Play Integrity API
to help you defend against unknown, risky traffic.
In addition to features for customizing API responses
and setting up tests in Play Console,
we're launching new reporting so you
can analyze and break down API responses
across your install base.
And, soon, you'll be able to debug Integrity API responses
from the Play Store's apps developer settings
on any device.
These new features will help you spot issues and refine
your anti-abuse strategy.
Second, we know it's critical that app reviews remain
accurate and relevant so developers
can grow successful businesses and users can have
trustworthy information to help them decide
if an app is right for them.
So earlier this year, we rolled out an enhanced program
to proactively stop inaccurate, coordinated attacks on app
ratings and reviews.
Our strengthened system now proactively
detects anomalies and unexplained spikes
in low star ratings so that our team can quickly
investigate suspicious activity and block so-called review
bombs.
Next, we've heard from you that you want more direct policy
support from us.
So early last year, we launched our Google Play Developer
Helpline pilot.
We've expanded the program to 44,000 developers
in 17 countries who now have direct access to phone support.
Today, we're also proud to share that the program has completed
nearly 4,000 policy support sessions with our developers.
This program has helped developers
navigate complex policy compliance issues.
And we look forward to further scaling the support
to more developers in countries.
We've also launched Play Strike Removal pilot
to give developers deeper education
on important but commonly misunderstood policy areas.
This lets developers remove an enforcement strike
by successfully taking a training
course, an assessment for the policy area
that their app violated.
And, last, we've launched more developer previews
for the Privacy Sandbox for Android initiative
to create innovative technology, to protect user privacy,
and give you tools to build thriving digital businesses.
These solutions will make current tracking mechanisms
like Ad-ID obsolete and limit covert tracking techniques
like fingerprinting.
We're working in close partnership
with developers like you.
So please make sure to test the developer previews
and send us feedback.
If you'd like to read more about these new features
and programs, check out the blog at this link or QR code.
Let's also talk about our pilot program and guidelines
on user choice billing.
We've launched the user choice billing pilot
offering more choice to developers and users.
Developers in the pilot can test offering an alternative billing
option alongside Google Play's billing system.
Our goals are to learn from developers and consumers
in different countries to ensure that we
can maintain a positive user experience
with alternative billing systems,
understand requirements and challenges for developers,
and understand complexities involved in supporting
user choice billing.
In order to be eligible for this pilot,
your app must be a non-gaming mobile or tablet app.
And the developer must be a registered business.
We expect the pilot to continue to evolve as we learn more
and hear your feedback.
In order to ensure a consistent user experience
and to help them make informed decisions,
one of our key requirements is that you
must follow the user experience guidelines for the pilot.
If you offer an alternative billing system,
you'll need to show users an information
screen and a separate billing choice screen.
The information screen helps users understand
the context of the change to help them make an informed
choice.
You only need to show this to each user
the first time they initiate a purchase.
The billing choice screen presents users
with two checkout options to complete their purchase.
Each billing service option must also
display the available forms of payment.
Once users make their choice, the purchase
will be completed through the selected billing system option.
So to get started, first, determine
if the app meets eligibility and requirements listed
on the pilot page.
Go to the link or QR code on this slide
to access this information on our Help Center article.
Next, complete the billing declaration form,
and accept the terms of service by clicking the Open
Declaration Form link.
We will review your submitted form
and send additional instructions which includes a required
enrollment form in order to identify the apps
and countries in which you will offer user choice
billing and instructions for how to report your paid
transactions on a monthly basis and what payments you
are required to remit for service
fees and any applicable taxes.
If you have any additional questions,
you can contact our support team through our alternative billing
system questions form also located in the link and QR
code shown here.
Now let's talk about recent policy updates
on self-certified ads SDK for our family's program,
deceptive ads, and user data.
We're updating our families self-certified ads
SDK policy to require developers with apps in the Families
Program to only use self-certified versions
of an ads SDK when serving ads to children
or users of unknown age.
So if you've declared that your app only targets kids,
it must only use self-certified versions
of an ads SDK regardless of the user's age.
And if you've declared that your app targets mixed audiences,
like both kids and older audiences,
then it must only use self-certified ads SDK versions
when serving ads to kids or users of unknown age.
But you can use other SDKs for older audiences.
We're also updating our deceptive ads policy
to clarify that ads must not simulate or impersonate
the user interface of any app feature,
like notifications or warning elements of an operating
system.
Here's an example of a common violation where a feature
section mimics other features but only leads
the user to an ad or ads.
We're also updating our user data policy.
We already prohibit selling personal and sensitive user
data.
Now we're making it extra clear with this update
that developers are responsible for the end-to-end user
data handling practices for data acquired within their apps.
So this means that providers for SDKs
and other third-party code in your app
must also not sell personal and sensitive user data.
Finally, here are some upcoming policy deadlines.
For policies that may take more work to update your app,
like the families self-certified ads SDK,
we've made sure to give you longer grace periods.
And, remember, all apps must comply with the target API
level policy by November 1.
If you need more time, you can request an optional extension
until May 2023.
For a full list of recent policy updates,
please visit goo.gle/playupdates.
We encourage you to review these updates carefully
in case any of them impact your apps.
I hope this helped you better understand our policies.
For free courses on Google Play policy,
visit Google Play Academy at g.co.playacademy/policy.
Thank you for continuing to partner
with us to make Google Play a safe and trustworthy platform
for everyone.
Until next time, stay safe and healthy out there.
[MUSIC PLAYING]