GeminiFor applications routed through RedactWall.
Compatible applications you explicitly configure to route through RedactWall send Gemini requests through the gateway. Requests and responses on that route use the approved policy; direct provider traffic remains outside the gateway.
What that looks like
A routed internal tool sends a customer file to Gemini for summarising
Stopped before it leaves, and the attempt is on the record.
A Gemini response returns through RedactWall with a member ID
Caught on the way in, before staff see it.
A workflow moves from one provider to Gemini
The approved policy applies after the compatible application is configured to use the RedactWall route.
What it takes to switch on
Configure each compatible application to use the RedactWall gateway endpoint for Gemini traffic. Only requests and responses that use that route are governed.
How far this is proven
Built to the vendor’s own connection and testedRedactWall is built to Google’s own connection to Gemini and tested against it. This broader product integration is outside the proposed first pilot. The first run against a live Google account remains to be verified separately, and every provider’s standing is published in the disclosures.
Every limit, in one place: Disclosures.
Review the proposed first pilot
The proposed first pilot covers ChatGPT text in managed Chrome and a separately verified Anthropic gateway path. Other integrations are part of the broader product.
- Coverage is published for this integration
- Proof status is shown explicitly
- Pilot scope is agreed before onboarding