Workspace/Privacy
Open workspace

PRIVACY / UPDATED 10 NOVEMBER 2026

Your incident, your context.

This page explains the behaviour of the application as supplied. The deployment owner is responsible for its configuration, provider settings and any future changes.

What the app processes

The browser holds the current incident, report and any workspace access key in memory. Importing a text file fills the form locally. Its text is sent for live processing only when you submit an analysis.

Sample reports use prepared example data. They do not invoke a model or process the form as a new incident.

Live AI processing

A live request sends the incident context to Cloudflare Workers AI. The application applies best-effort redaction for some common secret formats first. Remove passwords, tokens, personal information and confidential information you are not authorised to share before using the tool. Do not rely on automatic redaction to remove everything sensitive.

Database records

The usage database stores a daily attempt counter. In optional Gateway mode it also stores a hash of a used payment context and its expiry time to prevent reuse. The application does not store incident text or generated reports in that database.

Hosting and payment services

Cloudflare may process connection information and operational records under its own service terms and settings. If Gateway payments are enabled, payment processing involves the configured Gateway and facilitator; no wallet keys are collected by this browser interface.

Browser behaviour

The supplied app does not install analytics or advertising scripts, set application cookies, or store reports in local storage. Copy actions use the clipboard only when chosen. Downloads are created in your browser when requested.

Deployment owner

Before offering this tool to customers, publish your own business contact details, data-handling terms and support process. This starter does not claim to meet an organisation's regulatory or contractual obligations.