> ## Documentation Index
> Fetch the complete documentation index at: https://silmaril.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Data handling

> Understand the event data sent to Firewall and plan evidence access for your deployment.

## Classification data

A classification request sends event text and the context supplied by your integration. This can include a hook, tool name, conversation ID, request identity, and governance resource context. Tool responses and generated output can contain sensitive application data.

Send the context needed to evaluate the protected boundary. Review event construction before production use and remove credentials that the check does not need. Inspect the [API schema](https://silmaril.dev/docs/api-reference/classify.md) for supported fields.

## Credentials

Keep service keys in the protected service's environment or secret manager. Direct macOS installs save a typed key in the user's login Keychain. Managed profiles supply the connection values and are readable by MDM administrators.

Restrict access to completed profiles. Rotate managed URL and key values together. Local app removal leaves server-side credential revocation to your deployment administrator.

## Evidence and access

Dashboard findings and captured conversation evidence can contain event content. Restrict evidence access to authorized reviewers and check capture availability when investigating a decision. [Firewall MCP](https://silmaril.dev/docs/integrations/firewall-mcp.md) provides tenant-scoped evidence tools with separate permissions for restricted detail.

## Deployment planning

Confirm the following with Silmaril during setup. Record the agreed values in your deployment plan.

| Area | Confirm |
| - | - |
| Processing | Runtime location and any external model dependencies |
| Capture | Which event content and metadata are retained |
| Retention | Retention period and deletion process for your agreement |
| Access | Operator roles and access to full payloads and traces |
| Support | Approved channels for sharing diagnostic evidence |

Use the [privacy policy](https://silmaril.dev/privacy) and your service agreement for applicable terms. See [self-hosted deployments](https://silmaril.dev/docs/deployment/self-hosting.md) for responsibility planning.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.