## 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/loqui/a3dfb9eb-3572-4db1-a73a-a6d0266fe180-1793081142-8.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/loqui/a3dfb9eb-3572-4db1-a73a-a6d0266fe180-1793080985787-full.webp
- Component on Kage: https://kage.design/component/loqui-feature-grid-7

## Before you start
Ask what the user's product actually does with data, where processing occurs, and which privacy claims can be supported. Only then write the section and its guarantees.

Build a privacy section with an editorial heading on the left, a simple local-vs-server processing diagram beneath it, and a structured list of four privacy principles on the right. Follow it with a full-width purple callout bar containing a platform shortcut or setup message.

Design rules:
- Use a two-column layout with a 44/56 split and generous top/bottom whitespace.
- Use #111111, warm white #fbfaf8, and neutral #eeece8; reserve purple #8b3dff for the callout bar.
- The diagram should show two labelled nodes connected by a dotted path and a small text-only payload indicator.
- Privacy principles should use horizontal separators, 15–17px bold titles, and 13–14px muted descriptions.
- Make the callout bar a 20–28px rounded rectangle with white text and a small keyboard-key treatment.
- Do not make unsupported absolute claims; phrase guarantees around the user's real architecture.
- On small screens, stack the diagram, principles, and callout.

Never:
- Never use logos, product names, copy, illustrations, or imagery from the reference.
- Never invent or copy privacy guarantees, platform labels, or exact wording.