## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/public-com/cb41c975-325f-4844-b439-84e9d28bd7b7-1789146537-8.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/public-com/cb41c975-325f-4844-b439-84e9d28bd7b7-1789146490836-full.webp
- Component on Kage: https://kage.design/component/public-feature-grid-5

## Before you start
Ask what the user's product and brand are, then apply these principles to that context rather than reproducing the reference.

Build a dark trust-and-security section. Begin with a split hero row: a large serif two-line trust statement on the left and an abstract, nonliteral technology visual on the right. Under it, use a three-column grid over two rows, where every item has a concise heading, two or three lines of proof-oriented copy, and optional small compliance chips. Use black (#050505), warm white (#F2F2ED), subdued gray text (#929292), #202020 dividers, and one cool blue accent. Keep the visual subdued and avoid decorative clutter; the content should communicate regulation, coverage, transparency, infrastructure, and uptime with clear hierarchy.

Never use logos, product names, copy, illustrations, or imagery from the reference.