Acceptable use policy

Use of Google Photos APIs is governed by the Google API Services User Data Policy. Read this policy closely before requesting user data.

In addition to the Google Photos User Content and Conduct Policy, your application and its users must also comply with the following policies when using our services.

Solve problems for people

Google Photos is for storing, enjoying and sharing personal memories. You must not use Google Photos APIs to store or serve media such as photos or videos that aren't of a personal nature. For storing internal enterprise data or hosting website media, consider using Google Cloud Storage instead.

Innovate, don't duplicate

Don't make a substitute for Google Photos or use this API to create, train, or improve (directly or indirectly) a similar or competing product or service. For example, if your app's primary aim is to provide a general purpose photo gallery app, it's a substitute for Google Photos.

Respect usage limits

Usage limits help keep our service fair for everyone. Design your application to respect the per-user and per-app API request limits. If you think you are likely to exceed the published usage limits, your application might qualify for the Google Photos partner program.

Always ask permission

You must let our users know what data you're requesting and why. Don't access, cache, copy, analyze, or perform any action involving user data unless expressly permitted by the content owner (for example, when a user picks a specific photo to copy into a blog post). In general, unless absolutely critical to your product's functionality, media should only be presented in your UI and downloaded by the end user's device.

Data migration tools that help users copy their media between services are only permitted if the transfer is done with the user's explicit permission and no data is stored or analyzed by any intermediary service.

In all other cases, bulk processing of media is not permitted.

Minimize data access and storage

You must not cache or copy user data without the content owner's permission. If you need to copy or cache media for performance reasons, including thumbnails, you must only do so temporarily and for no longer than 60 minutes.

We recognize that some use cases (for example, copying photos to a blog post) might require longer term access to data. In such cases, you must adhere to the following requirements:

  • The user must explicitly choose the specific media items to which you are granted access.
  • You must delete a user's data within 60 days of a request to do so.

As an alternative to longer term data access, consider storing media item IDs or album IDs instead, and using the Google Photos Library API to dynamically load the relevant data.

Respect Google's copyrights and attribute

Use the Google Photos logo only as prescribed in the UX guidelines and Terms of Service. Don't imply endorsements or a stronger connection than really exists between your app and Google.

Printing services require a commercial agreement

If your product transfers a user's photos onto physical goods (such as photo prints or t-shirts) and you charge money for this service, you must have a commercial agreement. For more information, see the Google Photos partner program.