Why "no raw prompt storage by default" is a feature, not a limitation
Storing every prompt and response can create a larger data surface than most teams need. Evidence-first records focus on decisions and policy context, which makes reviews possible without retaining raw content by default.
Less data, less risk
Raw prompts often contain sensitive business context. Storing them by default expands the retention surface and increases review scope. Data minimization reduces exposure while keeping accountability intact.
Evidence-first still answers the important questions
Request id, decision, policy reference, timestamps, and approval metadata give reviewers the evidence they need. If a pilot requires more context, that can be defined explicitly in scope rather than stored automatically.
Scope control keeps pilots credible
A pilot works best when the data handling posture is clear. The gateway can be configured to store more context if the use case requires it, but the default posture should stay minimal unless there is a reason to expand it.
Next step
If you need clarity on data handling for a pilot, we can map it in a short discovery or pilot outline. That keeps the evidence story aligned with what is actually stored.