Is a personal drive.file reporting utility an approved Google Drive API use case?

Google Workspace Developers Q&A
, ,
1

Hello,

I am developing a private Windows Desktop utility for my own use with my personal Google account.

The utility uses only the non-sensitive drive.file OAuth scope. It generates small text-only project status reports locally, uploads them as individual documents into an app-created folder in my own Google Drive, and downloads each file to verify its integrity.

I use the resulting documents as a reporting handoff between my own development tools. The utility does not back up repositories, databases, entire directories or existing Drive files. It does not delete, share or modify Drive files.

I have completed one synthetic test upload. Recurring publication is currently disabled.

Could you clarify:

  1. Does this qualify as a permitted productivity or reporting use case under the Google Workspace API User Data and Developer Policy?

  2. Would this be considered the prohibited backup of developer application or project content to Drive?

  3. Do these restrictions apply to applications using only the non-sensitive drive.file scope?

  4. Can a private, single-user Desktop OAuth application remain in Testing for ongoing personal use?

  5. If express written consent is required, where can I request it?

I am seeking policy guidance before enabling scheduled publication.

Thank you.