## 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/relic/11197dbe-e39c-44cc-b0a1-5cdca0c05213-1789279382-6.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/relic/11197dbe-e39c-44cc-b0a1-5cdca0c05213-1789279305759-full.webp
- Component on Kage: https://kage.design/component/relic-card

## Before you start
Ask what the user's product does with customer data, what it never does, and which security claims can be substantiated. Build a trust section from those facts.

Create a large dark rounded security panel inside a light page. Use a bold white headline with a warm italic accent, a concise explanation, and a two-column list of numbered proof points. Add a row of three or four compact dark cards at the bottom for concrete guarantees. Use panel `#111210`, slightly lighter cards `#1b1c19`, cream text `#f6f0e4`, muted text `#aaa497`, and amber `#d89a18`; use a 24–30px radius, 32px padding, subtle 1px translucent borders, and generous line height. Keep claims specific and avoid fear-based language. Make the panel readable on mobile by stacking the proof list and cards.

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