null
/
Closer
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat: add 3 stronger privacy slogans to BrandMessageRotator (batch v0.2.13) 

- Add to CloserBrandCopy: 'Not even Closer can read your answers.', 'End to end encrypted private responses.', 'Built for trust, not tracking.'
- Update visual-identity.md: add new slogans to approved rotation, remove migration gating note (all legacy couples migrated)
This commit is contained in:
null 2026-06-19 21:17:59 -05:00
parent 55ca3dce27
commit 85b4eb589b
2 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
app/src/main/java/app/closer/ui/brand/CloserBrandCopy.kt
View File

@ -8,6 +8,9 @@ object CloserBrandCopy {
"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."
"A private space for two.",
"Not even Closer can read your answers.",
"End to end encrypted private responses.",
"Built for trust, not tracking."
)
}

16
docs/brand/visual-identity.md
View File

@ -40,22 +40,18 @@ mode.
Approved production rotation:
- **Your relationship is yours, not ours.**
- **Your relationship is yours, not yours.**
- **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.**
- **Not even Closer can read your answers.**
- **End to end encrypted private responses.**
- **Built for trust, not tracking.**
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.
All legacy couples have been migrated to encryption version 2. Answer-bearing writes fail closed
when the couple key is unavailable. These claims describe deployed behavior.
## Asset rules