Companies / Context.dev / Subprocessors
Context.dev provides an API for AI agents and LLM apps to scrape, search, monitor, and collect data from the web. It serves developers and companies building AI agents and products.
Summarized from its homepage on 6 Nov 2026.
1007 N Orange St. 4th Floor Suite #1839, Wilmington, DE, 19801, US
Subprocessors of Context.dev
Context.dev declares 15 subprocessors, including AI providers OpenAI.
| Subprocessor | Purpose |
|---|---|
| Storing logs and traces from the Context.dev API and browser service for debugging, monitoring, and security. | |
| Providing customer support chat functionality within the product dashboard. | |
| Routing and protecting traffic to our website and API, including DDoS protection, web application firewall, and DNS. | |
| Tracking referral and partner links and attributing sign-ups to partners. | |
| Hosting and running the Context.dev API, user authentication (Firebase), account and organization data storage, API usage history, queues, and file storage. | |
| Business email, documents, and internal collaboration used to support customers. | |
| Scoring sign-ups and free tool requests to detect bots and abuse. | |
| Processing API requests that use AI features, such as extraction and answers. | |
| Deploying and running the Context.dev API and browser service on our cloud infrastructure. | |
| Product analytics, feature usage analysis, and error tracking for the API and dashboard. |
5 more subprocessors
See the full list with purpose, location and first seen date.
Create a free accountWork email, no card. Already have one? Log inQuestions about Context.dev
Certifications
| Standard | What the source says | Checked |
|---|---|---|
| SOC 2 Type IICompany's statement | “Visit trust center SOC 2 Type 2”The company's own statement. SOC 2 has no public registry; the report itself is shared by the company, usually under NDA. | 13 Nov 2026Source |
We last read its homepage on 13 Nov 2026 and the FedRAMP Marketplace on 8 Nov 2026. A standard not shown here was not found in these sources. That does not mean Context.dev lacks it.
Vendor's own statement, retrieved from the source URL on the date shown. StrataDB does not verify the underlying claim. Data sources.
See Context.dev's full stack
Every vendor with its source and date, and an alert when Context.dev adds or drops one. The same lookup works for any company.
- Every company and vendor, with its public source
- 100 API calls a month, plus MCP and the Chrome extension
- Work email only. No card, no sales call