Provision record
OpenSea · OpenSea Terms of Service · View original document ↗

API Security Vulnerability Notification Obligation

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

This analysis describes what OpenSea'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
3
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.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
If you become aware of actual or potential security vulnerabilities in your integration of the API, you must immediately notify OpenSea and promptly work to resolve the issue.

Excerpt from OpenSea's Terms of Service

Applicable regulations

CFAA
United States Federal

Provision details

Document information
Document
OpenSea Terms of Service
Entity
OpenSea
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-032609
Document ID
CA-D-00209
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
76b04082fc896790748950b58f45fa27b32b077fa7f68023f3882c090ed2ad1f
Analysis generated
July 9, 2026 06:20 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: OpenSea
Document: OpenSea Terms of Service
Record ID: CA-P-032609
Captured: 2026-07-09 06:20:04 UTC
SHA-256: 76b04082fc896790…
URL: https://conductatlas.com/platform/opensea/opensea-terms-of-service/provision/CA-P-032609/api-security-vulnerability-notification-obligation/
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 OpenSea's API Security Vulnerability Notification Obligation clause do?

The clause states: “If you become aware of actual or potential security vulnerabilities in your integration of the API, you must immediately notify OpenSea and promptly work to resolve the issue.”

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 OpenSea?

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