Data boundary

Business content stays with the business.

Trace Intake is designed so the owner can operate access and provider safeguards without receiving the content businesses use to serve their customers.

Business-controlled workflow

Operational content

Form submissions and attachments
Caller identity and telephone recordings
Transcripts, summaries, and dossiers
Client and project folders
Inventory products, quantities, values, and imports
Historical source files and analysis output
Business storage paths and local encryption material

This content is written to the local and cloud locations chosen by the business.

Owner control plane

Narrow administration

Sponsored grant status and expiry
Module entitlements
OpenAI and Twilio spending limits
Provider project, subaccount, and number references
Billing status and aggregate service health
Release version and technical incident metadata

The owner service does not need the lead, call, file, inventory, or folder contents to perform these functions.

Design rules

Protection is enforced in the workflow.

Least access

Tester installations receive isolated project or subaccount credentials—not the owner's master credentials.

Verified callbacks

Stripe and Twilio callbacks are validated before they can change billing, calls, or usage controls.

Review uncertainty

Ambiguous client or project matches are retained for review instead of being guessed.

Explicit activation

Number search is read-only. A paid number is activated only after a person selects it and confirms.

Provider processing still exists.

When a selected feature uses OpenAI, Twilio, Stripe, Cloudflare, Google Drive, or another connected provider, the minimum information required for that operation is processed under that provider's terms. Final public disclosures and consent language will be published before commercial sales.

View release gates