Build Log
Jul 2026 client
Found the compliant path after the vendor said no
For a financial-advisory firm's client-facing AI build, the model vendor declined a custom zero-data-retention agreement. The answer was AWS Bedrock with retention set to none: zero retention by default, zero operator access, self-serve, no platform fee.
AWS BedrockClaude
The vendor never receives the data at all. A planned MCP dependency was also killed, since no official server existed and every artifact was third-party, in favor of a direct REST integration that adds no new vendor to the Reg S-P chain. A vendor’s no is usually the wrong door, not a dead end.
Related project: Client-Facing AI Advisor System