Making Google Ads More Secure with Updates to Developer Policies

We are updating our Google Ads Developer Policies formerly the “Google Ads API Policy”, to support developers in building robust, high-quality integrations as new AI capabilities continue to shape the advertising industry.

These updates establish clear frameworks for emerging technologies that are more secure and drive better outcomes for our shared customers.

To ensure a seamless transition to these updated standards, the Ads API Compliance team is actively reviewing existing integrations. Please check if your application requires updates by reviewing the policy. We will also reach out directly to developers who will need to transition with detailed guidance, technical resources and additional details.

Why we are introducing these updates now

As technology evolves, we periodically review our policies to make sure they reflect the current landscape. Historically, some integrations have relied on programmatic proxies, which bypass the verifiable and secure interface between end-users and Google. To help protect advertising partners against fraud and security risks, integrations now need to connect directly to Google Ads services using their own dedicated Google Cloud project.

This is critical to mitigate risks for customers, including:

  • Security Vulnerabilities: Using unaudited proxies can provide unauthorized actors access to your account. They also introduce the risk of cross-tenant data leaks, which could expose your data more broadly than intended.
  • Performance Bottlenecks: High-volume traffic routed through a single proxy can throttle throughput, cause latency across all users, and require enforcement across all users of a proxy when mitigating localized Denial of Service (DoS).

Next steps

  • Review your integrations to ensure they still follow Google Ads API policies. For full guidelines, visit the updated Google Ads Developer Policies.
  • Please ensure your contact email is up to date in the API Center so our Ads API Compliance team can easily share helpful communication or direct assistance from our compliance team as we do reviews. These communications will come from the google.com domain.

For technical support issues, please reach out to Google Ads Developer Support.

Emulator control for adaptive app development

Posted by Rob Orgiu, Developer Relations Engineer, Adaptive Apps, Android


Adaptive app development is fundamental on Android, but making sure everything looks good and every feature works the way it should require multiple tests on multiple devices. Or does it?

Well, yes… and no! While Android Studio is bundled with the Resizable Emulator to let you test layouts manually, there’s a faster, more streamlined way to control form factors directly from your terminal. By leveraging fire-and-forget console commands using the adb emu shortcut, you can execute commands that immediately return control to your invoking shell. 

If you have multiple emulators running at the same time, you can target a specific virtual device by passing in the shortcut's serial:

adb -s <serial> emu <command> <parameter>

First things first: Fold and unfold

To test foldable-specific user journeys and layout configurations, you can fold and unfold your emulated device programmatically.

adb emu fold

If your foldable emulator is unfolded, you can fold it to display its smaller screen configuration, powering on the (virtual) external display. To unfold the emulator and power on the internal display, simply run:

adb emu unfold

Now, you can instantly verify that your app preserves its state and that layouts appear exactly as they should on different display sizes.

Rotation, rotation, rotation

Correctly handling orientation changes is a cornerstone of adaptive app development. You can trigger device rotations programmatically to test how well your app handles configuration changes, including state restoration. The following command rotates the device 90° clockwise:

adb emu rotate

Simulating postures using sensors

What about placing the emulator into a specific physical posture, like tabletop mode? The easiest approach is querying for the number of available positions with .

First, list all available sensors and their current status:

adb emu posture

This returns  a list of positions similar to the following:

Usage: "posture <posture_id>" 1: closed	2: half-opened	3: opened	…

You can then invoke the tabletop posture by using the half-opened ID:

adb emu posture 2

Note: Not all postures are supported by every virtual device. Standard AVD templates like the Pixel Fold or the Resizable AVD only support postures 1 , 2 , and 3 . Attempting to set 4 or 5 on these templates will return a KO: Failed to set posture error.

What about the resizable emulator?

The resizable emulator has the super power to change its size with ease. With the adb emu command, you can move it freely with one command. Before you can do any changes, querying for the available resize presets requires only one call:

adb emu resize-display

This will return the list of available presents:

KO usage: "resize-display <index>" 0: phone	1: unfolded	2: tablet

Now, invoking the resize-display parameter with the wanted ID will resize the emulator to the wanted size:

adb emu resize-display 1

Streamline your testing today

And that's it! By integrating fire-and-forget commands into your command-line workflow, you save a lot of time and resources compared to running multiple emulators simultaneously.

Now is the time to start experimenting. If you haven't used these console shortcuts before, open up your terminal, fire up your emulator, head over to the documentation, and get started today!

Google Workspace Weekly Recap – August 28, 2026

Now available: A refreshed user interface for Google Meet hardware touch controllers on Neat and Poly devices

On August 26, 2026, we are officially launching our updated user interface for Neat touch controllers and  the Poly TC8. Overall, the design allows users to concentrate on their meetings rather than searching for controls, resulting in a more efficient and aesthetically pleasing experience. | Learn more.

Generate interactive simulations and models in the Gemini app

Gemini can transform your questions and complex topics into custom, interactive visualizations — directly within your Gemini app chat.  | Learn more.

Restrict who can view the member lists in Google Chat spaces

Space owners and managers can now control who can view the full list of members in a Google Chat space, providing enhanced privacy and administrative control for sensitive, large-scale, or external collaboration spaces. | Learn more.

Introducing data import for Microsoft Teams: An easier, faster, and higher-fidelity migration to Google Workspace

For enterprise organizations, migrating communication history and collaboration channels to a new platform can feel daunting and risk interrupting daily business operations. To make this transition smoother, we are excited to announce that migrating chat data from Microsoft Teams to Google Workspace for large scale workloads is now generally available in data import. | Learn more.

Introducing data import for Microsoft OneDrive: An easier, faster, and higher-fidelity migration to Google Workspace

For enterprise organizations, migrating files along with their permissions to a new platform can feel daunting and risk interrupting daily business operations. To help simplify this transition, we are excited to announce general availability of Google Workspace data import (advanced mode) to support large-scale file migrations from Microsoft OneDrive. | Learn more.

Preserve and reuse grouped pivot table fields in Google Sheets

Google Sheets now supports grouped field persistence for pivot tables. When you create custom groupings or work with grouped date, time, or numeric fields, these fields are now retained directly in the pivot table editor sidebar as reusable source fields. | Learn more.

Control “Take notes for me” directly from Google Meet hardware touch controllers

On August 31, 2026, we’ll start rolling out the ability to start, stop, and manage the “Take notes for me” feature directly from the Google Meet Hardware touch controller for eligible meetings. This ensures in-room participants have direct control over Gemini note-taking without being in Companion mode. | Learn more.

Google Classroom now supports Context-Aware Access controls

We’re excited to introduce the ability to specify Context-Aware Access policies to control access to Google Classroom. This update allows Google Workspace administrators to set granular security parameters for Classroom access directly from the Admin console. | Learn more.

Improving Google Calendar’s interoperability with third-party video conferencing solutions

We are introducing improvements to Google Calendar that make it easier to join third-party video meetings, including Microsoft Teams, Zoom, and Cisco Webex, when collaborating across different calendar and email clients. | Learn more.

Suppress email responses to calendar invitations and updates

We’re introducing a new per-event setting in Google Calendar that allows meeting organizers or their delegates to decide whether or not to receive RSVP emails and automatic responses, such as out-of-office messages and vacation responders. | Learn more.

Preview client-side encrypted PDF and image files directly in Google Drive, now available in beta

Previously, users needed to download encrypted non-native files to their local devices to view the contents. With this capability, authorized users can immediately preview encrypted content in their web browser without leaving Drive. | Learn more.

Gemini-based data classification in Google Drive is now available in open beta

This feature leverages Gemini models to apply data classification labels to files in Google Drive. Previously, AI classification required admins to identify and manually label training files for the AI model to learn the types of data associated with each data classification level. | Learn more.

The announcements above were published on the Workspace Updates blog over the last week. Please refer to the original blog posts for complete details.

Gemini-based data classification in Google Drive is now available in open beta

Gemini-powered AI classification in Google Drive is now available in open beta.

By automating file identification and labeling across Drive, AI classification helps organizations enforce granular data loss prevention (DLP) policies at scale, establish retention rules, and utilize label metadata during audit investigations. This also becomes a critical aspect in elevating an organization’s security posture in the agentic era, preventing agentic workflows from accessing and acting autonomously on sensitive data. 

This feature leverages Gemini models to apply data classification labels to files in Google Drive. Previously, AI classification required admins to identify and manually label training files for the AI model to learn the types of data associated with each data classification level. With this new capability, Gemini models offer admins an alternative method for data classification that is faster and more efficient, eliminating the need for manual model training and replacing it with administrator-defined instructions.



In the Admin console, Gemini models interpret instructions, evaluate files, and apply appropriate data classification labels.


Administrators maintain full control of the Gemini-based data classification process. They select the label, provide Gemini with instructions, and scope the audience for the files being evaluated. For Gemini-labeled files, editors and owners of those files with the appropriate label permissions will have the opportunity to either review and accept, or modify the automatically-applied label. Audit logs capture when files are labeled, including any user acceptance or modification of a Gemini-applied label.



In the Admin console, once enabled, Workspace Admins can see metrics on the labels applied to files by Gemini.


Data classification is a critical activity for organizations that are conscious about data protection, compliance, and reporting. However, data classification can also be challenging to put into practice, particularly when it comes to accurately classifying files at scale. By using the new Gemini-based capabilities in AI classification for Drive, admins are able to achieve a higher degree of data classification accuracy at scale.

Rollout pace

Getting started

  • Admins: For customers on a supported product license, the option for configuring Gemini-based AI classification instructions will appear in the Workspace Admin Console under the Data Classification option in the Security section (Security > Access and data control > Data classification). Use our Help Center to learn more.
  • End users: There is no end user setting for this feature.

Availability

  • Enterprise: Enterprise Plus
  • Education: Google AI Pro for Education
  • Other Editions: Frontline Plus

Resources

Preview client-side encrypted PDF and image files directly in Google Drive, now available in beta

Client-side encryption (CSE) provides organizations control over access to their confidential data, with customer controlled encryption keys and data that is indecipherable to third-parties, including Google. Google Drive now supports direct file previewing for CSE files. Previously, users needed to download encrypted non-native files to their local devices to view the contents. With this capability, authorized users can immediately preview encrypted content in their web browser without leaving Drive.

This feature streamlines productivity and bolsters security by eliminating unnecessary downloads. At launch, preview is supported only on Drive, and for:

  • Encrypted PDF documents
  • Encrypted Image file formats

Admins with eligible Workspace licenses can sign up for the beta program, which provides access to the feature.



Preview of an encrypted PDF, accessible in Drive

Getting started

  • Admins: Admins with eligible Workspace licenses can sign up for the beta program. We’ll provide more information on how to get started if you’re accepted.
  • End users: This feature is ON for users in domains that have registered for the beta program.

Availability

  • Enterprise: Enterprise Plus
  • Education: Education Standard and Plus
  • Other Editions: Frontline Plus, Assured Controls, Assured Controls Plus

Resources

Suppress email responses to calendar invitations and updates

We’re introducing a new per-event setting in Google Calendar that allows meeting organizers or their delegates to decide whether or not to receive RSVP emails and automatic responses, such as out-of-office messages and vacation responders.

By default, this new setting, called “Get an email when guests respond,” is checked - ensuring organizers receive email responses for RSVPs. If the box is unchecked:

  • Organizers will not receive RSVP emails from attendees using Google Calendar, but their RSVP status will still show up on the Calendar event.
  • Organizers will not receive RSVP emails from attendees using third-party calendar tools (e.g. Outlook) and their RSVP status will not show up on the Calendar event.
  • Organizers will not receive any email auto-replies (like out-of-office messages and vacation responders).

This feature is beneficial for organizers of large meetings, who don’t need to be informed about individual RSVP responses. Please note that for recurring events, this setting can only be applied to the full series.


Getting started

  • Admins: There is no admin control for this feature.
  • End users: By default, meeting organizers will get email responses for RSVPs. To stop receiving email responses, a meeting organizer must uncheck the box. Visit the Help Center to learn more.

Rollout pace

Availability

  • Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts

Resources