Provision record
DocuSign · DocuSign Privacy Statement · View original document ↗

Google API Limited Use Requirements Compliance

High severity Explicit document language Common · 108 of 352 platforms
Stay ahead of the changes
Track DocuSign and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF

This analysis describes what DocuSign's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

Clause Stability Stable

0
Changes
4
Months Monitored
Jul 10, 2026
First Seen
Jul 10, 2026
Last Seen
This clause type exists across 333 other provisions on other platforms.

How other platforms handle this

Runway Medium

Your Applications made available to end users must prominently display "Powered by Runway" and link to runwayml.com on applicable user interfaces and in accordance with our Branding Guidelines.

DeepL Medium

DeepL API Growth and DeepL API Developer are designed to process at least 600 characters per minute and per Customer; exceeding use may be limited, and Customers may encounter a 429 "Too Many Requests" error message.

Calendly Medium

Certain features of the Services, including notifications, AI Features, and use of Calendly's API, and credit-based or credit-enabled functionality may be provided through shared or collectively operated systems...

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
Docusign's use and transfer of Customer Data via Google APIs meets the requirements set by Google under the Google API Services User Policy, including the Limited Use Requirements.

Excerpt from DocuSign's Privacy Statement

Applicable regulations

CFAA
United States Federal

Provision details

Document information
Document
DocuSign Privacy Statement
Entity
DocuSign
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-031396
Document ID
CA-D-00198
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
db171ce667d98db1d8936fb125acc66e0d283cc7f0c00e08307fb68fd757092c
Analysis generated
July 9, 2026 06:43 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: DocuSign
Document: DocuSign Privacy Statement
Record ID: CA-P-031396
Captured: 2026-07-09 06:43:10 UTC
SHA-256: db171ce667d98db1…
URL: https://conductatlas.com/platform/docusign/docusign-privacy-statement/provision/CA-P-031396/google-api-limited-use-requirements-compliance/
Accessed: Aug. 2, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Frequently Asked Questions

What does DocuSign's Google API Limited Use Requirements Compliance clause do?

The clause states: “Docusign's use and transfer of Customer Data via Google APIs meets the requirements set by Google under the Google API Services User Policy, including the Limited Use Requirements.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 108 platforms. See the full comparison.

Is ConductAtlas affiliated with DocuSign?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by DocuSign.