CorpusIQ is now live in the ChatGPT app store.

SOC 2 Aligned · GDPR Aligned · AES-256 Encrypted

Compliance, Security, and Privacy

CorpusIQ LLC, Scottsdale, Arizona. Last updated: March 24, 2026.

security@corpusiq.io·privacy@corpusiq.io

SOC 2 AlignedGDPR AlignedAES-256 EncryptedExternal Retrieval Read-OnlyLive Retrieval · Scoped Retention

This page documents the technical and organizational measures we apply to protect user data. It also provides exact answers for OpenAI and app store reviewers. Contact us with questions.

Why automatic orchestration is safer

A user asks a question. CorpusIQ picks one skill, runs it against the connectors that skill needs, and sends the authorized results to the selected AI client for the answer. The AI client receives the source context needed for that request.

CorpusIQ sits between your tools and the AI assistant. Read-only external-source retrieval tools on one side. Separately named and annotated write-capable connector and CorpusIQ control-plane tools on the other.

Table of Contents

1.Product scope 2.Data inventory and flow 3.Security controls 4.Privacy and lawful basis 5.Retention and deletion 6.Subprocessors 7.Incident response 8.Annual reviews and audits 9.User data rights 10.Notes for app store and OpenAI reviewers 11.Public API examples 12.Change log

Section 1

Product Scope

SourcesGmail, 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.

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

StorageDirect 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.

ControlsPer-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.

Section 2

Data Inventory and Flow

Your Data Sources

Gmail

Drive

Shopify

QuickBooks

Slack

40+ More

Scoped source OAuth

Encrypted

CorpusIQ

EncryptedRequest-scoped

AES-256TLS 1.3External Reads

Request-scoped

AI Clients

ChatGPT

Claude

PPerplexity

Request ContextPublished RetentionAI Plan Policies

Encrypted retrieval: data is encrypted in transit and at rest, scoped per user.
User-scoped isolation: each account operates in a separate namespace with no cross-access.
AI-client context: only the context needed for the current request is sent to your chosen AI client. That client's own retention policy applies after receipt.

Class	Examples	Encryption	Retention
Account	Email, OAuth subject	AES-256 at rest	Until account deletion
Optional indexed search	Embeddings, chunk IDs, minimal metadata	AES-256 at rest	Until connector revocation or account deletion
Operational MCP query logs	Raw query text and tool parameters in local AUDIT logs; bounded result summaries	AES-256 at rest	30 days in the Azure Log Analytics workspace

Section 3

Security Controls

CASA Tier 2 Certified by DEKRA

Assessed by DEKRA · OWASP Top 10 Verified

TransportTLS 1.3 only, HSTS, forward secrecy

Encryption at restAES-256, managed keys, key rotation every 90 days

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

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

SecretsStored in a dedicated secrets manager, never in source control

LoggingStructured logs, immutable audit stream

Pen-testingIndependent assessment at least annually, remediation tracked to closure

Business continuityDaily encrypted backups, restore tests every 30 days

Change controlVersioned IaC, peer review, and staged rollouts

Section 4

Privacy and Lawful Basis

Lawful basisUser consent at connection time, with clear scopes.

ChildrenNot directed to children under 16.

Data saleDo not sell personal information. No cross-context behavioral advertising.

International transfersStandard contractual clauses where relevant.

Section 5

Retention and Deletion

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.

Optional indexed-search features retain embeddings and minimal metadata only while the connector is active.

✓

Connector revocation removes its OAuth token and any optional indexed-search embeddings.

✓

Local AUDIT logs record raw query text and tool parameters plus bounded result summaries.

✓

The Azure Log Analytics workspace retains operational logs for 30 days.

✓

The selected AI client's plan and settings govern conversation handling after it receives authorized source context.

✓

Raw customer files and full connector response payloads are not retained in backup copies.

To request account-data deletion, contact privacy@corpusiq.io.

Section 6

Subprocessors

Vendor	Purpose	Data types	Region
OpenAI	Model inference	Prompts and derived embeddings	USA
Cloud hosting	Compute and storage	Encrypted data at rest	USA
Analytics (IP masked)	Product analytics	Anonymized events	USA

Section 7

Incident Response

Detect and triage. Open a ticket, assign severity.

Contain, eradicate, and recover.

Notify affected users within 72 hours after confirmation, when legally required.

Retrospective with corrective actions and ownership.

Section 8

Annual Reviews and Audits

✓

SOC 2 readiness program with quarterly control checks.

✓

Independent pen-test at least once per year.

✓

Vendor reviews and DPA renewals annually.

Section 9

User Data Rights

Users can request access, correction, export, and deletion of their data. Contact privacy@corpusiq.io. We respond within 30 days.

Access

Request a copy of all data we hold about you.

Correction

Ask us to correct inaccurate personal data.

Export

Receive your data in a machine-readable format.

Deletion

Permanently erase account data, tokens, and any optional indexed-search embeddings.

Section 10

Notes for App Store and OpenAI Reviewers

Google & App Store Reviewers

All data source connections are user-initiated via OAuth (Gmail, Google Drive, Google Ads, Google Analytics, Google Sheets, Google Calendar).
Read-only external-source retrieval tools request the documented retrieval scopes. Write-capable connector and CorpusIQ control-plane tools are separately named and annotated.
Domain ownership verified. OAuth callback: /oauth/google/callback

OpenAI

Actions use a documented OpenAPI spec with two endpoints:
/v1/query/v1/deep_search
We provide a reviewer account with synthetic data and a Postman collection.
No background data extraction. Only user-invoked actions.

Section 11

Public API and Examples

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

cURL, Query

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, Deep Search

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"}'

Section 12

Change Log

2025-12-31Initial publication with reviewer notes and API examples.

Key security terms

The trust-architecture concepts behind CorpusIQ, defined plainly for buyers, reviewers, and the AI assistants that cite this page.

Read-only external retrieval: Read-only external-source retrieval tools do not write back to vendor systems. Write-capable connector tools and CorpusIQ control-plane tools are separately named and carry explicit safety annotations; control-plane actions can update or remove user-declared facts, decisions, metric specifications, and source manifests.
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.

Common security questions

What is CorpusIQ and how does it access business data?

CorpusIQ is an AI intelligence layer that gives AI assistants and AI agents governed access to live business data through a single connection. Read-only external-source retrieval tools do not write back to vendor systems; write-capable connector and CorpusIQ control-plane tools are separately named and annotated. The intelligence layer reads data from 40+ connected systems on demand and returns a source-cited answer. Direct MCP does not retain raw customer files or full connector response payloads; operational logs follow the published retention schedule.

Why is read-only external retrieval safer than write-capable vendor access?

Read-only external-source retrieval tools limit vendor access to retrieval for those calls. Write-capable connector tools and CorpusIQ control-plane actions—such as updating or removing user-declared facts, decisions, metric specifications, and source manifests—are separately named and annotated. You can disconnect each external source independently without affecting the others.

Does CorpusIQ store my business data?

How does CorpusIQ protect data in transit?

All traffic uses TLS 1.3 with forward secrecy. HSTS is enforced on the canonical domain. Data at rest is encrypted with AES-256. Keys rotate every 90 days. All queries are audit-logged with an immutable trail.

What certifications does CorpusIQ hold?

CorpusIQ is CASA Tier 2 certified by DEKRA (certification ID 151c1b05, valid through March 5, 2027) and maintains a SOC 2 aligned security posture. Read the full technical and organizational measures on this page.