Skip to main content

​
What the control plane sees

To inspect a payload, the SDK sends its text to api.frostwolf.app over TLS. That is inherent to server-side detection. In return, the control plane sends back a verdict and offsets, never a rule and never a pattern.

Sent for detection

The text of the payload, and any tool declarations and calls you submit.

Returned

A verdict, the rules that fired, and offsets into your own text. For Cloak, entity types and ranges. Never a matched value unless you ask for evidence.

​
What is stored

​
Detection stays off the client

No signature, pattern, rule id list, or matching algorithm ships in an SDK. A rule set a client can read is a rule set an attacker can probe for a near miss. The same goes for Cloak: the SDK holds no recognisers, and is told where personal data is.

​
Redaction stays on your side

The control plane returns offsets and the SDK rewrites your text. A payload is not sent to FrostWolf to be rewritten. Your message structure, images, and provider parameters are never touched by anything but your own process.

​
Fail-safe defaults

​
Keys

An API key authenticates detection, telemetry, and capture. Keep it server-side. Keys can be revoked in the console, and a key can only change its own capture setting.

​
The Cloak vault

The default vault is process memory. It is bounded, it expires values after an hour, and a restart loses it. The SDK never encrypts what it stores. If you supply a persistent vault, encrypt it at rest and protect it as carefully as the data it holds. forget erases everything held for one identity.

​
Reporting

Telemetry and capture are fire-and-forget. A reporting failure never reaches your request path. To report a vulnerability, email support@frostwolf.app.