> ## Documentation Index
> Fetch the complete documentation index at: https://docs.context.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Setting up Context.dev for a user? Follow https://docs.context.dev/agent-quickstart.md. MCP clients sign in with OAuth and need no API key; application code reads CONTEXT_DEV_API_KEY.

# Responsible use

> Understand the responsibilities that accompany third-party content and company data.

API access does not grant a license to reuse third-party material. The [Terms](https://www.context.dev/term), [Privacy Policy](https://www.context.dev/privacy), [DPA](https://www.context.dev/dpa), and your agreement govern use.

## Content and brand assets

Confirm permission to access, store, display, or redistribute the material your product uses. Public availability alone does not establish reuse rights. Keep source URLs where users need provenance and provide a correction or removal path.

Returned logos do not establish affiliation or endorsement. Follow the rights holder’s requirements and [Logo Link’s embedding restrictions](/brand/logo-link#usage-restrictions).

## Web access and personal data

Bound crawl scope and frequency. Use browser actions and target-site credentials only for access you are authorized to make. Minimize personal data sent to the API and retained in your own systems, and define deletion and correction behavior.

Use [ZDR](/optimization/zero-data-retention) only on supported endpoints and verify its confirmation. Review the [Trust Center](https://trust.context.dev) when your workflow requires vendor assessment.

## Inferred information

Extracted facts, identity matches, and classifications can be incomplete or wrong. Keep nullable fields and unresolved states. Preserve evidence and review consequential or ambiguous outputs before acting on them.

For questions about your Context.dev agreement, contact [support@context.dev](mailto:support@context.dev).