Skip to main content
Review the intended workflow before connecting an agent to people or sensitive data. Identify who operates it, who it contacts, what information it handles, and which services receive that information.
These guides help prepare a review with your legal, privacy, and security advisers. They do not amend the published policies, establish compliance, or approve a deployment. Check current execution availability separately.

Current policies

Use the canonical pages for the current policy text rather than a copied version in a prompt or deployment checklist. For a deletion request, contact legal@threetone.in. Identify the associated account or business and the scope of the request. The process includes identity or authority checks and confirmation of the records involved. Do not send credentials or entire conversations. Follow the published instructions for the review process; this guide does not set a completion deadline.

Choose a review

Call consent

Review the intended recipients, calling purpose, consent evidence, and recording decisions.

AI disclosure

Make the business identity, use of automation, and available assistance clear.

Healthcare

Assess the data, parties, agreements, and safeguards before a healthcare use case.

Prepare the review record

1

Describe one intended use

Record the business owner, task, channel, audience, locations, and agent version. Include the actions the agent may take and who handles exceptions.
2

Map information and access

List inputs, recordings, transcripts, knowledge sources, tool payloads, logs, and exports. Identify the recipient of each data flow and the people who can retrieve it.
3

Resolve notices and agreements

Have the appropriate reviewers determine the applicable requirements. Record the approved notices, consent approach, contractual scope, and unresolved restrictions for this use case.
4

Verify the controls before release

Use synthetic data to check access, disclosure, refusal handling, and data handling. When a runtime path is available, verify it separately. Keep unresolved items with an owner and a release decision.
Reopen the review when the audience, purpose, channel, data categories, connected services, or material agent behavior changes. Keep the review evidence in an access-controlled business system, not in this public documentation repository.

Frequently asked questions