Request for Official Contact – Google Drive API Express Prior Written Consent for Backup Use Case

Google Workspace Developers Q&A
1

Hello Google Workspace / Drive API Team,

My name is Elad, and I am developing SmartDocs Mobile apps, a privacy-focused Android document management application intended for worldwide release on Google Play.

Our application allows users to scan, import, organize, and manage their personal documents locally on their devices.

We have implemented optional Google Drive backup and synchronization using the drive.appdata OAuth scope and the application’s private appDataFolder.

While reviewing the Google Drive API Terms of Service, we identified the restriction concerning:

“Backup of user or app content from a developer’s app or project to Drive.”

We understand that this use case may require Google’s express prior written consent.

Before publicly releasing this functionality, we would like to clarify the official approval process.

Could a Google representative please provide:

  1. The official email address, private contact channel, or application form for requesting express prior written consent.

  2. The name of the Google team authorized to review and approve this use case.

  3. Confirmation of whether backup and synchronization through drive.appdata and the private appDataFolder fall under this restriction.

  4. Any documentation or technical details required to submit a formal approval request.

We are committed to complying with Google’s policies and would prefer to resolve these requirements before launching the application.

We are not requesting OAuth verification assistance, but specifically guidance regarding Google’s express prior written consent requirement under the Google Drive API Terms of Service.

Thank you for your assistance.

Kind regards,
Elad.

2

This won’t help you, but my understanding is that there is no public-facing portal or direct Google team you can pitch to request consent. While Google’s Trust & Safety teams handle standard OAuth verification, those reviewers only enforce existing rules—they can’t negotiate or grant prior written consent for ToS exceptions.