Compliance, Security, and Privacy

Sources

Gmail, Google Drive, OneDrive, Dropbox, Outlook, Shopify, QuickBooks, HubSpot, Google Analytics, Google Ads, Meta Ads, YouTube, TikTok, eBay, PostgreSQL, SQL Server, and more. User-authorized only. No device agents. No browser extensions.

Outputs

In-chat answers, ranked references, and optional deep search results.

Storage

Direct MCP connector requests use live retrieval and do not build embeddings or file indexes. Optional indexed-search features use embeddings and minimal metadata in a per-user namespace. No raw file bodies are retained.

Controls

Per-user namespace, connector revocation controls, and structured audit logging. Local AUDIT logs contain raw query text and tool parameters plus bounded result summaries; the Azure Log Analytics workspace retains those logs for 30 days.

Transport

TLS 1.3 only, HSTS, forward secrecy

Encryption at rest

AES-256, managed keys, key rotation every 90 days

Network

Private subnets, deny by default, WAF and rate limits on all public endpoints

Access

SSO, least privilege, hardware key for production access. Production data is not copied to developer laptops

Secrets

Stored in a dedicated secrets manager, never in source control

Logging

Structured logs, immutable audit stream

Pen-testing

Independent assessment at least annually, remediation tracked to closure

Business continuity

Daily encrypted backups, restore tests every 30 days

Change control

Versioned IaC, peer review, and staged rollouts

OpenAPI spec v3.0.3 · Base: https://api.corpusiq.io · Endpoints: POST /v1/query · POST /v1/deep_search

curl -s -X POST https://api.corpusiq.io/v1/query \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"q":"what is the renewal date for the ACME contract"}'

curl -s -X POST https://api.corpusiq.io/v1/deep_search \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"q":"Q4 keyword performance report"}'

Read-only external retrieval

Connector tools are retrieval-only and do not write back to vendor systems. The only tools that accept writes are CorpusIQ control-plane tools, which manage your own CorpusIQ configuration such as declared facts, decisions, metric specifications, and source manifests. They do not act on the connected business systems.

Scoped customer data handling

For direct MCP connector requests, CorpusIQ fetches source records live and returns them to the requesting AI client. The direct path does not retain raw customer files or full connector response payloads, and it does not build embeddings, file indexes, or cached or indexed summaries. Local AUDIT logs record raw query text and tool parameters plus bounded result summaries. In Azure, the Log Analytics workspace retains those logs for 30 days. The selected AI client's plan and settings govern conversation handling after it receives the data. Optional indexed search is separate and retains embeddings and minimal metadata until connector revocation or account deletion.

Source-backed answer

A source-backed answer cites the exact records it came from. Every response links back to the underlying message, file, or record, so the output supports verification instead of asking you to trust it blind.