Data sensitivity
Data sensitivity describes the classification your application declares for a governed request. The Platform does not automatically classify content.
| Class | Label |
|---|---|
| D0 | Public |
| D1 | Internal |
| D2 | Confidential |
| D3 | Restricted |
| D4 | Critical |
The ordering is D0 < D1 < D2 < D3 < D4. Set the key’s default and minimum sensitivity in API access. An application may declare request sensitivity using X-Steinkauz-Data-Sensitivity; the key minimum still applies. Stored Responses continuation also preserves the inherited sensitivity floor.
Before inference, the server checks effective sensitivity against the connection’s environment and the tenant’s routing matrix. A denied request has a policy decision ID and does not proceed to provider egress. Use Activity → Requests to inspect the declared, default, minimum and effective classifications.
Applications are responsible for classifying their inputs and derived artifacts. Multimodal inputs are processed transiently; safe file metadata may be retained as evidence. The Platform does not host files or provide a file classification library.
See API authentication and Provider environment.