Closer/docs/brand/visual-identity.md

# Closer visual identity

Closer should feel private, warm, and made for an equal partnership—not clinical, gamified, or like
a public dating profile.

## Brand mark

The mark is one heart formed by two equal halves. Pink and lavender represent two people meeting at
the center; neither side visually dominates. Keep the mark intact and do not separate, rotate, add
text inside, or place it directly over a busy image.

- Launcher source: `docs/store/sources/app-icon.svg`
- Android adaptive layers: `app/src/main/res/drawable/ic_launcher_*`
- Minimum clear space: one quarter of the mark's width on all sides.
- Minimum digital size: 24 px. At small sizes, use the solid monochrome mark.

## Core colors

| Role | Color | Hex |
| --- | --- | --- |
| Trust / deep background | Aubergine | `#24122F` |
| Primary brand | Deep purple | `#56306F` |
| Connection accent | Lavender | `#B98AF4` |
| Partner one | Soft pink | `#F7C8E4` |
| Partner two | Soft lavender | `#D9B8FF` |
| Warm light surface | Blush white | `#FFF8FC` |

Use the deep tones for trust and privacy, and the softer tones for connection and warmth. Product
text must continue using semantic Material theme colors so contrast remains correct in light and dark
mode.

## Store voice

- Primary promise: **A private space for two.**
- Supporting idea: **Private by design · Made for connection.**
- Prefer calm, specific language. Avoid promises to “fix” a relationship, competitive streak copy,
  urgency, or public/social framing.

## Rotating privacy messages

Approved production rotation:

- **Your relationship is yours, not ours.**
- **Answer honestly. Reveal intentionally.**
- **For conversations that belong to the two of you.**
- **No audience. No public feed. Just the two of you.**
- **Private by design.**
- **A private space for two.**

Do not publish universal “not even Closer can read it,” “no plaintext,” or “all responses are
end-to-end encrypted” claims until every legacy couple has migrated and every answer-bearing game
path fails closed when its couple key is unavailable. Security claims must describe deployed behavior,
not only the intended architecture.

Implementation status: answer-bearing writes now fail closed, all private game-answer paths use
ciphertext, and version-0/1 couples receive a per-partner migration to encryption version 2. Keep the
universal claim gated until that build is deployed and production data confirms no legacy couple
remains below version 2.

## Asset rules

- Store graphics and screenshots should use the same purple/pink palette as the product.
- Lead with privacy and mutual connection before feature volume.
- Do not show intimate answer content, real email addresses, invite codes, or notification tokens.
- Use clean demo data and crop out development indicators before publishing.