Subprocessors (Public List)
Last updated on November 3, 2026
Contact: supportdocumentation.ai
This page discloses third‑party service providers that process personal data on behalf of Keevs Health Inc. (Documentation.AI) to deliver, secure, and support our Services. We require each subprocessor to use personal data only to provide contracted services, implement appropriate security measures, and comply with applicable law. This list forms Annex III of our Data Processing Addendum.
Change management: We will update this page and provide at least 30 days’ prior notice before adding or replacing a subprocessor, except for emergency replacements (we will notify promptly thereafter). To raise an objection where permitted by contract, email supportdocumentation.ai with “Subprocessor Objection” in the subject.
Current subprocessors
| Vendor | Purpose | Categories of data | Data location(s) | Key safeguards |
|---|---|---|---|---|
| Render Services, Inc. | Application hosting: API, background workers, AI assistant, MCP server, PDF rendering | All categories processed by the Services, in transit and in memory; application logs | United States (Oregon, Ohio) | TLS; network isolation; access controls |
| Vercel, Inc. | Hosting of the dashboard and published documentation sites; edge network; AI Gateway routing to model providers | Customer Content; reader request data (IP address, request headers); AI requests in transit | United States; global edge network | TLS; encryption at rest; isolation; access controls |
| Supabase, Inc. | Managed PostgreSQL database | Account and workspace data (names, emails, roles); documentation metadata; encrypted integration credentials | United States | Encryption at rest and in transit; role-based access |
| Cloudflare, Inc. | Object storage (R2) for documentation files, images, videos, and exports; CDN and DDoS protection | Customer Content files, uploaded images and videos, imported sources, and exports; request data (IP address, headers) | United States; global edge network | Encryption at rest and in transit; DDoS mitigation |
| imgix (Zebrafish Labs, Inc.) | Image optimization and delivery on published documentation sites | Images in Customer Content; reader request data | United States; global edge network | TLS; access controls |
| Upstash, Inc. | Redis caching for site configuration, reader sessions, and AI agent context | Site configuration; reader session data (for authenticated docs: identity claims such as first name, company, access roles); agent context | United States | Encryption at rest and in transit; access controls |
| GitHub, Inc. | Git hosting for documentation repositories managed by Documentation.AI | Customer Content; commit metadata (author names, commit messages) | United States | Encryption at rest and in transit; access controls |
| Trigger.dev | Background job orchestration (deployments, sync, AI jobs) | Job payloads, which may include Customer Content and account identifiers | United States | TLS; access controls |
| Inngest, Inc. | Background job orchestration (PDF export, cleanup) | Job payloads, which may include Customer Content and account identifiers | United States | TLS; access controls |
| Better Stack, Inc. | Application log management and monitoring | Application logs (request metadata, account and documentation identifiers, error details) | United States | TLS; access controls |
| turbopuffer, Inc. | Vector database for semantic search and Ask AI retrieval | Embeddings and text chunks of Customer Content; page metadata | United States (AWS us-east-1) | Encryption in transit; per-organization namespaces |
| Tinybird | Built-in documentation analytics, search analytics, page feedback, and Ask AI analytics | Session IDs; page paths; timestamps; referrer; user agent; viewport; search queries; feedback text; Ask AI question text and answer feedback | United States (AWS us-east-1) | TLS; access controls |
| Voyage AI (MongoDB, Inc.) | Text embeddings for semantic search and Ask AI | Customer Content and search or Ask AI query text | United States | TLS; no training on customer data |
| OpenAI | Large language models for the AI documentation agent and Ask AI | Prompts, Customer Content, Ask AI messages, and model outputs | United States | TLS; API data not used for training |
| Anthropic, PBC | Large language models for the AI documentation agent and its connected-tool assistants | Prompts, Customer Content, content retrieved from connected tools, and model outputs | United States | TLS; API data not used for training |
| Context.dev (formerly Brand.dev) | Crawling websites Customer adds as knowledge sources for the AI agent; extracting brand assets from a domain | URLs and website content Customer directs us to crawl, which may include personal data published on those sites | United States | TLS; access controls |
| Scalekit, Inc. | Connection broker for third-party tools Customer connects to the AI agent (Jira, Confluence, Linear, Notion, HubSpot, Plain) | OAuth tokens for connected accounts; content retrieved from connected tools, which may include names, emails, and other personal data | United States | Encryption at rest and in transit; token vaulting; access controls |
| Clerk, Inc. | Authentication and identity management | Names; emails; profile pictures; authentication factors; session and device metadata | United States | Encryption in transit; access controls |
| Stripe, Inc. | Payment processing, invoicing, and usage metering | Billing name; email; payment method token; transaction and AI-credit usage metadata | United States | PCI DSS Level 1; tokenization (we do not store full card numbers) |
| Intercom | Customer support and in-app messaging | Name; email; user ID; support messages | United States | Encryption at rest and in transit; access controls |
| PostHog, Inc. | Product analytics in the Documentation.AI dashboard | User and organization identifiers; name; email; feature usage events | United States | TLS; access controls |
| Loops | Transactional email (for example, export-ready notifications) | Name; email; message content | United States | TLS; access controls |
| hCaptcha (Intuition Machines, Inc.) | Bot and abuse protection on Ask AI | IP address; browser and device signals | United States | TLS; used only for abuse prevention |
Notes
- Integrations you enable: third-party analytics, chat, and custom scripts that you add to your documentation site send data directly to those providers under your own agreements with them; they are not our subprocessors.
- Regionality: Where supported, we select regions to align with our hosting footprint; exact regions may change as we scale, subject to the notice above.
- AI models: We use model providers as configured to fulfill user requests. We do not permit model providers to train on customer content.