Control exactly what leaves your application
Cloaking is the core of CloakGate. You define which sensitive data types matter and how each one is handled before a request reaches an AI model.
Four ways to handle sensitive data
Every sensitive data type maps to an action in your policy.
The value is removed before the request is sent. Best when the model does not need the value at all.
The value is replaced with a consistent placeholder such as Customer_1, so the model can still reason about structure and relationships.
The whole request is stopped when it contains data your policy forbids from leaving, such as live secrets.
Optionally map placeholders back to real values in the response, so your app receives readable output.
Detected patterns become placeholders
CloakGate is designed to detect common categories and apply consistent, structure-preserving placeholders. The exact set depends on the policies you enable and language support.
No detection system is perfect. Treat cloaking as a strong control and audit layer, not as a guarantee that every sensitive value is caught every time.
“Cloaking is not magic. It is a configurable risk-reduction layer that helps prevent unnecessary sensitive data exposure.”
Start using AI through a safer gateway
Prepaid credits, known models, sensitive data cloaked before it leaves your app. Join the developer preview.