Developer Preview

The Chameleon Eye API is in developer preview. Production access is not yet generally available.

API

API Data Handling

How Chameleon Eye API handles customer data, approved payloads, local mode, and logging.

A. Data Processing Principles

How Chameleon Eye AI processes data across all modes.

Approved payload only

Chameleon Eye AI never performs automatic full archive upload. Only explicitly approved payloads are processed.

Local / Offline Mode

Does not contact third-party AI APIs. Processing remains entirely on the user device or local deployment.

Hybrid Approval Mode

Sends only selected text or approved summaries to cloud AI, and only after explicit user approval.

Private Cloud / ZDR Route

Uses an approved privacy route where the contract supports zero data retention. Request is blocked rather than silently downgraded if this route is required but unavailable.

Standard Cloud / API Mode

Processes only the current approved request through Chameleon Eye API and approved AI infrastructure.

B. What Is Sent to Cloud AI

Only the approved payload is ever sent — never a customer's full private archive.

When cloud AI processing is used, only the current approved payload is sent. Chameleon Eye AI does not automatically send a customer's full document library, local memory, source code repository, HR database, or financial records.

C. Logging

What Chameleon Eye AI does and does not log.

+Raw private prompts are not stored in normal application logs by default.
+Raw AI responses are not stored by default.
+Provider API keys are never logged.
+Usage metadata (counts, timestamps, plan checks) may be stored for billing, abuse prevention, and audit integrity.

D. Private Cloud / Zero Data Retention Route

For sensitive analysis requiring stricter data handling.

A Private Cloud / Zero Data Retention route is available for sensitive analysis where the contracted AI provider route supports zero data retention. If this route is required but unavailable, the request is blocked rather than silently downgraded.

E. Regulated / Sensitive Data Warning

Customer responsibility for regulated data categories.

Important Notice

Customers should not process regulated medical, financial, legal, or highly sensitive personal data through cloud analysis unless they have verified the applicable contractual, legal, and compliance requirements for their use case.