The Drive API is not allowed for certain use cases without Google’s
express prior written consent, including the following:
Backup of user or app content from a developer’s app or project to Drive.
Cryptocurrency mining.
Broad video distribution or dissemination of copyrighted content
without authorization.
Using Drive as a replacement for a large-scale content delivery
network (CDN) is not allowed.
File cloning tools that enable sharding of user storage and/or circumvention of Drive storage limits.
Use of restricted scopes
The use of restricted scopes is allowed for certain situations, such as:
Platform-specific and web apps that provide local sync or automatic backup
of users’ Drive files.
Productivity and educational applications whose user interface might involve
interaction with Drive files (or their metadata or permissions). Productivity
applications include task management, note taking, workgroup communications,
and classroom collaboration applications.
Reporting and security applications that provide user or customer insight
into how files are shared or accessed.
If you’re using restricted scopes, the restricted scope verification
process and a security assessment are required. For more information on
Drive scopes and their sensitivity levels, see
Google Drive scopes. Additionally, review the
OAuth API verification FAQs
to determine when your app should go through verification and what type
of verification is required.
When possible, we recommend using non-sensitive scopes as it grants per-file
access scope and narrows access to specific functionality needed by an app.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-18 UTC."],[],[],null,["Last modified:\nJuly 8, 2022\nBy using this API, you consent to be bound by these terms in addition to the [Google APIs Terms of Service (\"API ToS\")](/terms).\n\nGoogle Drive API Policies\n\nCustomer implementation\n\n\nThe Drive API is ***not*** allowed for certain use cases without Google's\nexpress prior written consent, including the following:\n\n- Backup of user or app content from a developer's app or project to Drive.\n- Cryptocurrency mining.\n- Broad video distribution or dissemination of copyrighted content without authorization.\n- Using Drive as a replacement for a large-scale content delivery network (CDN) is not allowed.\n- File cloning tools that enable sharding of user storage and/or circumvention of Drive storage limits.\n\nUse of restricted scopes\n\n\nThe use of restricted scopes is allowed for certain situations, such as:\n\n1. Platform-specific and web apps that provide local sync or automatic backup of users' Drive files.\n2. Productivity and educational applications whose user interface might involve interaction with Drive files (or their metadata or permissions). Productivity applications include task management, note taking, workgroup communications, and classroom collaboration applications.\n3. Reporting and security applications that provide user or customer insight into how files are shared or accessed.\n\n\nFor more information, see\n[When to use a restricted scope](/workspace/drive/api/guides/api-specific-auth#restricted).\n\n\nIf you're using restricted scopes, the restricted scope verification\nprocess and a security assessment are required. For more information on\nDrive scopes and their sensitivity levels, see\n[Google Drive scopes](/workspace/drive/api/guides/api-specific-auth#scopes). Additionally, review the\n[OAuth API verification FAQs](https://support.google.com/cloud/answer/9110914)\nto determine when your app should go through verification and what type\nof verification is required.\n\n\nWhen possible, we recommend using non-sensitive scopes as it grants per-file\naccess scope and narrows access to specific functionality needed by an app."]]
