Sub-Processors

Last updated: March 28, 2026

Diana Intelligence Corp. ("Diana") uses the following sub-processors to deliver the Diana service. Each sub-processor is contractually bound to process customer data only as necessary to perform services on our behalf and in accordance with our data protection obligations.

Infrastructure & Hosting

Sub-Processor	Purpose	Data Processed	Location
Cloudflare, Inc.	Compute, edge routing, request handling, sandboxed agent execution (Workers, Durable Objects, Containers)	Request metadata, task payloads during processing	United States
Supabase, Inc.	Managed PostgreSQL database, authentication	Task metadata, agent memory, user account data, integration credentials (encrypted)	United States
Vercel, Inc.	Web application hosting (dashboard, authentication, API endpoints)	User session data, account information	United States

AI / Language Model Providers

Sub-Processor	Purpose	Data Processed	Location
Anthropic, PBC	Large language model inference (Claude) for AI task processing	Task prompts and responses (real-time processing only, not retained by provider)	United States
OpenAI, Inc.	Large language model inference (GPT) for AI task processing	Task prompts and responses (real-time processing only, not retained by provider)	United States

Both Anthropic and OpenAI operate under commercial API agreements that prohibit the use of customer data for model training. Prompts and outputs are processed in real time and are not stored by the provider after the API response is returned.

Monitoring & Analytics

Sub-Processor	Purpose	Data Processed	Location
PostHog, Inc.	Product analytics and usage metrics	Anonymized usage events, feature interaction data	United States
Sentry (Functional Software, Inc.)	Error monitoring and performance tracking	Error logs, stack traces, request metadata (no message content)	United States

Third-Party Integrations

When customers connect third-party services through Diana, data is shared with those services as necessary to perform the requested tasks. These integrations are user-initiated and optional:

Service	Purpose	Data Processed
Slack Technologies, LLC	Primary platform — messaging, events, user identity	Messages sent to Diana, workspace metadata, user profiles
Notion Labs, Inc.	Workspace and knowledge management integration	Page content, database entries as requested by user
GitHub, Inc.	Code repository and issue management integration	Repository data, issues, pull requests as requested by user

How We Manage Sub-Processors

All sub-processors undergo a security and privacy review before engagement.
Sub-processors are contractually required to maintain appropriate security measures and process data only as instructed.
We maintain data processing agreements (DPAs) with each sub-processor.
Customer data is encrypted in transit (TLS 1.2+) and at rest (AES-256) across all sub-processors.

Changes to This List

We will update this page when sub-processors are added or removed. If you have questions about our sub-processors, contact us at [email protected].