Thanks to visit codestin.com
Credit goes to docs.context.dev

Skip to main content
Context.dev can retrieve third-party webpages, assets, and company information. Access through the API does not grant a license to use that material or transfer responsibility for how your product uses it. This page is implementation guidance, not legal advice. The current Terms of Service, Privacy Policy, Data Processing Addendum, and your signed agreement govern your use.

​
Before shipping a use case

Confirm that you have a lawful and contractually permitted basis to:
  • Access the target content.
  • Store, transform, display, or redistribute the returned data.
  • Process any personal data involved.
  • Use third-party trademarks, logos, text, images, or other protected material.
  • Make automated decisions from inferred or classified data.
The correct answer depends on the content, jurisdiction, target site’s terms, your relationship with the rights holder, and your product. Do not assume that public availability alone answers those questions.

​
Brand assets and affiliation

  • Do not imply that a company sponsors, endorses, or partners with your product without authorization.
  • Preserve a clear distinction between your product’s identity and the third party’s identity.
  • Treat returned logos and imagery as third-party assets. Context.dev’s retrieval does not grant a trademark or copyright license.
  • Provide a correction or removal path when your product displays company identity data at scale.
  • Follow the rights holder’s current brand guidelines when your use is permitted.

​
Web content

  • Review the target site’s terms and applicable access rules before automating retrieval.
  • Bound crawl frequency, scope, and concurrency so your workload does not create unnecessary load.
  • Do not use browser actions or proxy routing to access private accounts, evade authorization, or bypass a paywall you are not permitted to access.
  • Preserve source URLs when users need to evaluate provenance.
  • Do not present extracted or summarized content as an exact quotation unless your application preserves and verifies the original wording.
Technical ability to fetch a page is not a statement about permission to use its content.

​
Personal and sensitive data

  • Minimize the personal data sent to Context.dev and retained in your own systems.
  • Do not send data that your agreement or applicable law prohibits the service from processing.
  • Use Zero Data Retention only after confirming the endpoint supports it and verifying the response header.
  • Define retention, deletion, access, and correction behavior in your own product.
  • Review the DPA and Trust Center before production processing that requires a vendor assessment.

​
Model output and classifications

Brand fields, extracted values, and industry candidates can be incomplete or incorrect. Confidence labels are not official registrations.
  • Keep human review for decisions with legal, financial, employment, safety, or compliance impact.
  • Use nullable fields when source evidence can be absent.
  • Preserve provenance for facts that users may need to challenge.
  • Do not silently turn a low-confidence classification into an authoritative claim.
Logo Link has product-specific embedding and usage restrictions. Follow the Logo Link guide and your plan terms rather than copying or rehosting assets by default.

​
When the answer is unclear

Pause the launch and get appropriate legal or rights-holder guidance. For questions about what your Context.dev agreement permits, contact [email protected].