Three prevalent themes in the discussion
- Data‑privacy guarantees and contractual safeguards
- Users want assurance that proprietary or CUI data never leaks to model training or third parties.
- runamuck: “Will this guarantee that proprietary/ sensitive/ CUI data won't leak to model training or other parties?”
-
ericmags: “Correct. We have contractual agreements to ensure no data that passes through our platform will be used for model training purposes. In addition, we have in our contracts that we (Consus) will also not use any data for training purposes. We couldn't if we wanted to since we do not store any prompt data.”
-
Guidance and tool‑level controls for AI‑assisted workflows (MCP, plugins, web‑search, etc.)
- Commenters ask how the gateway manages the tools that AI agents invoke and what controls are offered to organizations.
- projectescape: “Do you give customers guidance or controls for that side, or is it out of scope for the gateway?”
- ericmags: “We do give our customers guidance to make sure they are thinking about this properly. This typically happens during on‑boarding. We also built out pre‑defined controls for common tools so they can click a button and not think about it.”
-
projectescape (suggestion): “You could strip non‑approved tools from the request and block calls to them in the response, based on an org allowlist.”
-
Compliance, security monitoring, and regulator‑aligned controls (HIPAA, FedRAMP, abuse detection)
- Concerns about meeting specific compliance regimes and how the gateway handles provider‑side abuse monitoring or data retention.
- jayonsoftware: “Does this work with HIPAA data ?”
- ericmags: “We've been focused on defense, so we haven't set up HIPAA (BAAs) yet. The underlying controls are essentially FedRAMP High, so it wouldn't be a big lift on our side.”
- ericmags (abuse monitoring): “The infra providers call this 'abuse monitoring' or 'abuse detection' and we've worked with them to turn it off. … We have one case remaining for OpenAI's GPT‑5.x models in AWS. AWS's automated classifier can retain a flagged request for up to 30 days. … We are actively working to turn that off as well.”
These three themes—privacy guarantees, tool‑level governance, and compliance/security controls—dominated the conversation.