diff --git a/app/src/main/java/app/closer/ui/brand/CloserBrandCopy.kt b/app/src/main/java/app/closer/ui/brand/CloserBrandCopy.kt
index 97ba5ce6..d5ce2ddd 100644
--- a/app/src/main/java/app/closer/ui/brand/CloserBrandCopy.kt
+++ b/app/src/main/java/app/closer/ui/brand/CloserBrandCopy.kt
@@ -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."
     )
 }
diff --git a/docs/brand/visual-identity.md b/docs/brand/visual-identity.md
index 98969087..474a998d 100644
--- a/docs/brand/visual-identity.md
+++ b/docs/brand/visual-identity.md
@@ -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