Security and Privacy

The Cloud Proxy is a managed forward proxy. It authenticates each device with an org key plus that device's user email, forwards the connection, and attributes the traffic to the right subject in Flowstate. Attributed sessions and spend appear under Insights → Agent insights.

It is not the same as Agent Enterprise capture. In the shipped Cloud Proxy network mode, Flowstate does not store prompt bodies, response bodies, attachments, vendor cookies, or vendor API keys from the encrypted provider connection.

Authentication Data

Devices authenticate to proxy.flowstate.inc with a short-lived signed token minted from two inputs:

Field	Purpose
User email	Identifies the subject the traffic is attributed to. On the MDM path your MDM expands the $EMAIL placeholder per device; on the self-install path it comes from the user's sign-in.
Org key	Authenticates the organisation. It is embedded in the generated MDM profile and stored in your MDM. Self-install devices hold their own per-device credential instead.

The full org token is revealed once, when you generate the MDM profile at Settings → AI → Cloud Proxy. It is not retrievable afterwards, and the UI does not display it (or a prefix of it) after that reveal. Flowstate stores only the material needed to validate the credential, never the cleartext token.

Traffic Data Stored

The Cloud Proxy attributes and meters traffic in the backend. There is no status card or per-subject meter on the settings page; the attributed data surfaces in the insights views:

Data	Where it appears
Sessions, attributed per subject	Insights → Agent insights → Agent sessions.
Spend and usage rollups	Insights → Agent insights → Dashboard and Spend insights.
Each person's own sessions	My AI → My sessions.
Key lifecycle events	Settings → Organisation → Activity Log.

Provider invoice data is not created by the Cloud Proxy. Connect provider billing APIs at Usage providers for invoice reconciliation.

Data Not Stored by Cloud Proxy Network Mode

In the shipped network-proxy flow, Flowstate does not store:

• prompt text;
• response text;
• files or attachments sent to AI tools;
• vendor Authorization headers or API keys;
• vendor cookies;
• raw TLS payloads inside the proxied provider connection.

If your governance program needs prompt inspection, content DLP, prompt-quality scoring, or a prompt audit trail, deploy the Flowstate Agent and choose the appropriate Telemetry vs Enterprise capture mode.

DLP and Enforcement

Content DLP and request-time policy blocking depend on traffic that Flowstate can inspect. The shipped Cloud Proxy network mode is for routing and metering, so it does not by itself feed prompt-body DLP or Agent enforcement.

Policy authoring still lives at Governance -> Policy and enforcement. Enforcement for managed endpoint traffic is handled by the Flowstate Agent enforcement flow.

Retention and Deletion

Cloud Proxy configuration, key metadata, and the attributed session and metering records follow the same organisation-scoped retention, audit, and deletion controls as the rest of Flowstate's settings and telemetry data.

Subject-level deletion removes or anonymises Flowstate records associated with that subject according to your organisation's standard data-retention process. Because shipped Cloud Proxy network mode does not store prompt or response bodies, there is no Cloud Proxy prompt corpus to delete.

Operational Privacy Commitments

• Store the org key in an MDM secret variable, not in plaintext scripts or shared documents.
• Keep the MDM user-email placeholder intact so attribution stays per subject.
• Follow the key-rotation runbook if the secret is exposed.
• Use the Flowstate Agent for full capture only after your organisation has the appropriate employee notice, consent, and data-processing basis.