CorpusIQ is now live in the ChatGPT app store.

Accelerate your business. All your tools in one place.

SOC 2 Ready · 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 ReadyGDPR AlignedAES-256 EncryptedRead-OnlyZero Data Stored

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, returns the answer. The user never types raw data into the AI assistant. The AI assistant never sees your data directly.

CorpusIQ sits between your tools and the AI assistant. Read-only on one side. Source-backed answers on the other. Every step is logged.

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 and webhooks 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.

StorageEmbeddings and minimal metadata. No raw file bodies stored. Read-only access to connected data.

ControlsPer user namespace, immediate deletion endpoint, immutable audit trail.

Section 2

Data Inventory and Flow

Your Data Sources

Gmail

Drive

Shopify

QuickBooks

Slack

37+ More

Read-only OAuth

Encrypted

CorpusIQ

EncryptedEphemeral

AES-256TLS 1.3Read-Only

Ephemeral

AI Clients

ChatGPT

Claude

PPerplexity

Ephemeral ContextNo Persistent AccessNo Model Training

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.
Ephemeral context: only short-lived query context is passed to your AI client (ChatGPT, Claude, Perplexity), never persisted.

Class	Examples	Encryption	Retention
Account	Email, OAuth subject	AES-256 at rest	Until account deletion
Derived	Embeddings, chunk IDs	AES-256 at rest	Until connector revocation or account deletion
Operational	Audit logs, deletion receipts	AES-256 at rest	24 months, security only

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

We store zero customer data by default. Embeddings and metadata are retained only while the connector is active.

✓

Connector revocation removes all associated embeddings and tokens immediately.

✓

Audit receipts retained for 24 months for compliance purposes only.

✓

Account deletion removes all data, tokens, and metadata with final audit receipt.

✓

No backups of customer content retained after deletion.

Deletion API

DELETE https://api.corpusiq.io/v1/delete_my_data
Authorization: Bearer <token>

Response 200:
{
  "status": "deleted",
  "deleted_resources": ["embeddings","metadata","tokens"],
  "audit_id": "del_01J9Z3R4A2",
  "timestamp": "2025-10-14T15:32:10Z"
}

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 all data, tokens, and 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).
We request only the minimum read-only scopes required. No write, delete, or admin scopes are requested.
Domain ownership verified. OAuth callback: /oauth/google/callback

OpenAI

Actions use a documented OpenAPI spec with three endpoints:
/v1/query/v1/deep_search/v1/delete_my_data
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 · DELETE /v1/delete_my_data

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

cURL, Deletion

curl -s -X DELETE https://api.corpusiq.io/v1/delete_my_data \
  -H "Authorization: Bearer $TOKEN"

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 OAuth: Read-only OAuth means CorpusIQ connects to your tools with permission to read, never to write, change, or delete. You authorize each connector through the provider's own login, and you can revoke access at any time.
Zero customer file storage: Zero customer file storage means CorpusIQ does not store the raw bodies of your files or messages. It works from embeddings and minimal metadata in a per-user namespace, and customer data is not used for model training.
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 secure, read-only access to live business data through a single connection. It sits between your business tools and the AI assistant. The intelligence layer reads data from 37+ connected systems on demand to answer a plain-English question, then returns a source-cited answer. It does not store the raw data it reads and does not write, modify, or delete anything in connected tools.

Why is read-only OAuth safer than other integration approaches?

Read-only OAuth limits the permission scope to read access at the source. CorpusIQ cannot send emails, modify records, delete files, or move money. Even if a credential were compromised, the blast radius is limited to read access on the scopes you authorized. You can also revoke each connector independently at any time without affecting the others.

Does CorpusIQ store my business data?

No. CorpusIQ reads data from your connected tools on demand to answer a question. It does not retain the raw content of your files, emails, or records on its servers. Customer data is not used to train any model. 37+ connectors, zero customer file storage.

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.