# Keep sensitive information in the right place

Set rules for what connected AI tools may receive or send. Give people a reason and a useful next step when sensitive information needs protection.

[Talk to us](/contact)[Explore Athena](/athena)

Use AI. Keep control.

Supported checks. Clear information rules.

[ DATA CONTROL ]

## Protect the information the work needs

Client records, personal identifiers, credentials and code can enter AI requests. Apply the chosen checks where a supported connection can inspect them.

[Learn more](/athena)

Company and client data

Choose which project material may enter the connected request and which information must stay out.

Requests and destinations

Review the information and destination, including context added by files or tools.

Helpful next steps

Explain the rule and the approved route for continuing the task.

Checks at the supported connection

A supported rule may allow, warn, redact or block. Confirm which behaviour applies to the browser or coding route. A service listing alone does not establish inspection.

## See the rule, the decision and the reason

[Explore Athena](/athena)

01

### Choose the information

Define sensitive data and approved project material. Test the actual tool, version and request route.

02

### Apply the supported rule

Confirm what a warning, block or redaction does before relying on it. Give staff an approved next step.

03

### Review the result

Review findings and reasons in context. A detector result needs investigation before it is called a confirmed leak.

In practice

## Data Control across the workflow

Match the information rule to the browser, model request or tool response. Inspection and retention remain separate decisions.

### Managed-browser checks

Athena covers supported browser routes, approved tools, warnings and guidance. Request early access to discuss your browsers, tools and data rules.

### Coding and model requests

For Enterprise, map repository context, retrieved material and tool outputs entering the selected model connection. Test permitted and refused requests.

### Custom rules

Set rules for the project, data and destination. Review incorrect refusals and missed detections before expanding the workflow.

### Coverage and retention

Name the supported paths and gaps. Decide what to inspect, which records to retain and who can read them.

[Data flow and product limits](/trust#deployment-and-sovereignty)

[ EXPLORE ATHENA ]

## Choose your next step

See the connection options, set the rules or plan a first test.

[Product guide](/guides)

[##### Agent control

Actions that need approval

Learn more](/agent-control)

[##### Athena

Your company's AI, under your control

Learn more](/athena)

[##### Company policy

Apply your company's rules

Learn more](/policy)

## Which information does your team need to protect?

[Talk to us](/contact)[Explore Athena](/athena)
