## 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/idlen/09112380-17fc-499b-a8d2-71eed663a053-1789538554-7.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/idlen/09112380-17fc-499b-a8d2-71eed663a053-1789538482510-full.webp
- Component on Kage: https://kage.design/component/idlen-feature-grid-4

## Before you start
Ask what the user's product, audience, and brand are, then apply the principles below to that product rather than copying this reference.

Create a privacy/security section with a subtle blue-black radial glow. Start with a small trust badge, a large centered headline, and a supporting sentence. Add three horizontal security cards with simple icons and short explanations, followed by a compact syntax-highlighted code example showing the privacy-preserving mechanism, and a centered policy link.

Design rules:
- Center the heading and constrain it to roughly 620px; place the cards in a three-column max-width grid.
- Use 36–44px headline text, 14–16px supporting copy, 14px card titles, and 12–13px descriptions.
- Approximate colours: background #151515 with glow #102849, text #f5f5f5, muted #9a9a9a, borders #252525, code surface #12151a, syntax accents #a78bfa and #6ee7b7.
- Use restrained 8px card radii and a 6–10px radius code panel with monospace typography.
- Make the claims specific, auditable, and understandable to a non-security specialist.
- On mobile, stack the cards and keep the code panel horizontally scrollable.

Never:
- Never use logos, product names, copy, illustrations, or imagery from the reference.
- Never make unsupported security promises.
- Never expose real secrets, tokens, or private source code in the example.