As between you and us, you own your Customer Data. We only use it to provide, secure, support, and improve the Service for you, and as this section and our Privacy Policy describe.
The FleetWarrant Gateway is the path your Agents’ traffic takes to reach an LLM provider, so it receives every prompt and response in the clear in transit. Nothing is stripped before it reaches us. By default we don’t keep the raw request and response. We store a redacted preview of each call, encrypted under your Tenant’s own key, plus the call’s metadata. To make the preview, the Gateway redacts a fixed set of known secret- and personal-data-shaped patterns and a fixed set of sensitive field names; this is not general PII or business-data redaction, and there’s currently no way to configure your own rules. See the Privacy Policy for the specific patterns covered. Content that doesn’t match that fixed ruleset is transmitted to the Service and kept in the preview: in our operational store for the dashboard, and in the audit archive.
A Tenant admin can turn on raw capture for your Tenant. While it is on, we also archive the full request and response, encrypted under a per-Event key, and anything the preview removed is still in that raw copy. You decide whether to turn it on. The archive is Object-Locked for 1 year by default, a period you can change within the limits of your plan, and our application never deletes an archive object. Because that archive exists to be trustworthy evidence, individual records in it can’t be edited or deleted on request the way an ordinary database row can. A raw body can instead be shredded on request or by your raw-body retention, with a legal hold pausing shredding: that makes it unreadable without deleting the archived object. See the Privacy Policy for how erasure works and where its limits are.
Because redaction is limited to that fixed, non-configurable ruleset, and raw capture keeps the complete request and response, you’re responsible for not routing data you need redacted or withheld from us (personal information, credentials outside our supported patterns, or other sensitive business data) through the Service until per-Customer redaction configuration is available, and for deciding whether to turn raw capture on. See the Privacy Policy for the current scope of redaction.