Reference
Data & security
Understand retained data and where the preview’s controls begin and end.
What is stored
| Data | Current handling |
|---|---|
| Submitted data | Evaluated in memory, not written to the application database or included in audit responses. |
| Destination and task context | Stored and visible to the owner. Avoid secrets and sensitive URL parameters. |
| Category, verdict, reason | Stored with timestamps and identifiers. |
| API keys | Raw value returned at creation/rotation; a SHA-256 hash and display metadata are stored. |
| Owner identity | Project records can include owner ID, email, and name from authentication. |
| Reviews | Status, timestamps, and resolver identity are stored separately from original verdicts. |
What the gate enforces
The API authenticates keys, evaluates rules, scopes database access to a project, and records decisions. Owner endpoints manage policies and reviews.
It does not isolate processes, mediate actual network traffic, automatically scan files, issue task-bound credentials, or ensure the later action matches the checked proposal. Those controls need the planned runtime or your integration.
Regex detection is incomplete and returns one category. An approval means configured checks passed, not that every aspect of the action is safe.
Your integration’s responsibilities
- Check immediately before an action and execute only on explicit approval.
- Keep pending proposals unchanged; recheck changed content or destinations.
- Keep keys in trusted server-side code and out of agent conversation text.
- Block on failures and use bounded retries.
- Prevent duplicate execution at the real tool boundary.
- Provide adequate review context without relying on stored raw payloads.
- Record actual execution outcomes separately.
Local and hosted boundaries
Localhost and 127.0.0.1 receive an automatic identity. Use a trusted machine; this configuration does not separate users.
Hosted owner authentication trusts identity supplied by Sites. A deployment outside that environment needs a trusted authentication boundary that incoming client headers cannot spoof. Do not expose the development configuration as a production multi-user service.
Application data handling does not establish guarantees for proxy logs, hosting logs, infrastructure, or your agent framework. Review those before sending sensitive data.
Retention, exports, and deletion
No scheduled retention purge or customer deletion API is implemented. No retention period, residency option, backup policy, or compliance certification is promised by this preview.
The logs endpoint has pagination limitations and is not a guaranteed complete export. Logs alone do not establish a formal compliance guarantee.
Report a concern
Contact hello@kernall.ai with a description and reproduction steps. Omit real keys and raw personal data. Include identifiers only when they help locate the issue.