diff --git a/.lane/reports/fix-remove-submission-prep-copy-privacy-pages.md b/.lane/reports/fix-remove-submission-prep-copy-privacy-pages.md
new file mode 100644
index 00000000..6742381d
--- /dev/null
+++ b/.lane/reports/fix-remove-submission-prep-copy-privacy-pages.md
@@ -0,0 +1,60 @@
+# Lane 1 report — remove internal editorial/submission-prep copy from public app pages
+
+Branch: `fix/remove-submission-prep-copy-privacy-pages`
+Date: 2026-08-14
+
+## What the item meant
+
+The fleet item says "internal editorial and submission-prep notes are live as
+visible copy on four public app pages." On current main, the four product and
+support pages were already cleaned up by PR #28 (e71a689). The live leak on
+main is on the two **app privacy pages**:
+
+- `public/promptly/privacy/index.html`
+- `public/drishti/privacy/index.html`
+
+Both carried submission-prep voice as visitor-facing copy:
+- H1s: "Promptly's privacy page is already public ahead of release." /
+  "Drishti's privacy page is already in place before launch."
+- Hero lead: "reflects the current planned launch scope and should stay
+  aligned with the final App Store privacy disclosures before release."
+- Aside: "Current release scope" / "not publicly released yet" /
+  "currently planned launch configuration."
+- First card eyebrow: "At launch" / "...is planned."
+- "Important note" section: "both this page and the App Store privacy answers
+  should be updated before that version is submitted."
+
+These are internal submission-prep notes (App Store Connect language,
+launch-calendar self-commentary) published as visible copy. Several sibling
+lanes had previously attempted this same fix on unmerged branches
+(fix/app-privacy-page-h1s*, fix/public-app-copy-internal-notes-privacy-pages,
+fix/public-app-pages-editorial-copy-voice-lane1); none ever merged to main.
+
+## What I changed
+
+Rewrote the leaked passages on both privacy pages as visitor-facing policy
+copy that describes what data each app handles, how it is used, and the
+choices available — without referencing the internal submission process.
+Heading levels, links, meta tags, chips, and JSON-LD are unchanged.
+
+## Verification
+
+Full-scan of every public page for prep-note phrases
+(already|in the meantime|current build|submission|before release|not
+publicly released|planned launch|launch scope|ahead of release|before
+launch|before that version is submitted|for submission|ready for
+submission|launch day|future launch|current release scope|At launch|submitted):
+0 hits on all 13 public pages.
+
+Public-site test suites (all green):
+- heading hierarchy: 89 checks, 0 failures
+- structured data: 127 checks, 0 failures
+- link targets: 77 checks, 0 failures
+- brand disambiguation: 11 checks, 0 failures
+- conversion signal: 126 checks, 0 failures
+- soft-404: 19 checks, 0 failures
+
+## Files touched
+
+- `public/promptly/privacy/index.html` — rewrote leaked submission-prep copy
+- `public/drishti/privacy/index.html` — rewrote leaked submission-prep copy
diff --git a/public/drishti/privacy/index.html b/public/drishti/privacy/index.html
index 3917f378..e151f74a 100644
--- a/public/drishti/privacy/index.html
+++ b/public/drishti/privacy/index.html
@@ -83,11 +83,12 @@
         <section class="page-hero-card reveal">
           <div>
             <p class="eyebrow">Drishti privacy</p>
-            <h1>Drishti’s privacy page is already in place before launch.</h1>
+            <h1>Drishti privacy for mindful screen time.</h1>
             <p class="page-lead">
-              This is the app-specific privacy destination for Drishti. It
-              reflects the current planned launch scope and should stay aligned
-              with the final App Store privacy disclosures before release.
+              This page explains what information Tiny Studio may receive
+              through Drishti, how it is used, and the choices you have. Drishti
+              is Tiny Studio’s mindful screen time app for interrupting the
+              scroll reflex.
             </p>
             <div class="meta-row">
               <span class="chip accent">Effective date: March 14, 2026</span>
@@ -96,10 +97,10 @@ <h1>Drishti’s privacy page is already in place before launch.</h1>
           </div>
 
           <aside class="page-card dark">
-            <p class="eyebrow">Current release scope</p>
+            <p class="eyebrow">What this page covers</p>
             <ul class="plain-list">
-              <li>Drishti is not publicly released yet.</li>
-              <li>This page reflects the currently planned launch configuration.</li>
+              <li>What information Tiny Studio may receive and how it is used.</li>
+              <li>Retention and the choices you have.</li>
               <li>Support questions can be sent to Tiny Studio’s support inbox.</li>
             </ul>
           </aside>
@@ -107,12 +108,12 @@ <h1>Drishti’s privacy page is already in place before launch.</h1>
 
         <section class="card-grid">
           <article class="info-card reveal delay-1">
-            <p class="eyebrow">At launch</p>
-            <h2>No third-party advertising or cross-app tracking is disclosed here.</h2>
+            <p class="eyebrow">Advertising and tracking</p>
+            <h2>No third-party advertising or cross-app tracking.</h2>
             <p>
-              This page does not currently describe targeted advertising,
-              cross-app tracking, a public sign-in system, or website payments
-              for Drishti.
+              The Drishti website has no public sign-in system and does not
+              process payments. In-app accounts or payments are not described
+              on this page.
             </p>
           </article>
 
@@ -149,10 +150,9 @@ <h2>To respond, improve, and keep records when necessary.</h2>
             <article>
               <p class="eyebrow">Important note</p>
               <p class="section-copy">
-                If Drishti launches with analytics, crash reporting, accounts,
-                sync, or another external service not described here, both this
-                page and the App Store privacy answers should be updated before
-                that version is submitted.
+                If Drishti adds analytics, crash reporting, accounts, sync, or
+                another external service not described here, this page will be
+                updated to describe it.
               </p>
             </article>
           </div>
diff --git a/public/promptly/privacy/index.html b/public/promptly/privacy/index.html
index 281cc9f5..010e8b60 100644
--- a/public/promptly/privacy/index.html
+++ b/public/promptly/privacy/index.html
@@ -83,11 +83,11 @@
         <section class="page-hero-card reveal">
           <div>
             <p class="eyebrow">Promptly privacy</p>
-            <h1>Promptly’s privacy page is already public ahead of release.</h1>
+            <h1>Promptly privacy for bookings, reminders, and client data.</h1>
             <p class="page-lead">
-              This is the app-specific privacy destination for Promptly. It
-              reflects the current planned launch scope and should stay aligned
-              with the final App Store privacy disclosures before release.
+              This page explains what data Promptly handles, how it is used, and
+              the choices you have. Promptly is Tiny Studio’s booking and
+              no-show prevention app for solo professionals.
             </p>
             <div class="meta-row">
               <span class="chip accent">Effective date: March 14, 2026</span>
@@ -96,10 +96,10 @@ <h1>Promptly’s privacy page is already public ahead of release.</h1>
           </div>
 
           <aside class="page-card dark">
-            <p class="eyebrow">Current release scope</p>
+            <p class="eyebrow">What this page covers</p>
             <ul class="plain-list">
-              <li>Promptly is not publicly released yet.</li>
-              <li>This page reflects the currently planned launch configuration.</li>
+              <li>What data Promptly handles and how it is used.</li>
+              <li>Retention, service providers, and your choices.</li>
               <li>Privacy and support questions can be sent to Tiny Studio’s support inbox.</li>
             </ul>
           </aside>
@@ -107,12 +107,12 @@ <h1>Promptly’s privacy page is already public ahead of release.</h1>
 
         <section class="card-grid">
           <article class="info-card reveal delay-1">
-            <p class="eyebrow">At launch</p>
-            <h2>No third-party advertising or cross-app tracking is planned.</h2>
+            <p class="eyebrow">Advertising and tracking</p>
+            <h2>No third-party advertising or cross-app tracking.</h2>
             <p>
-              Promptly is described as a booking workflow for solo professionals.
-              This policy does not describe targeted advertising, cross-app
-              tracking, or selling personal information.
+              Promptly is a booking workflow for solo professionals. This policy
+              does not describe targeted advertising, cross-app tracking, or
+              selling personal information.
             </p>
           </article>
 
@@ -170,10 +170,9 @@ <h2>Booking links, notes, payment proof, and support records.</h2>
             <article>
               <p class="eyebrow">Important note</p>
               <p class="section-copy">
-                If Promptly launches with analytics, crash reporting, new payment
-                processors, expanded account sync, or another external service not
-                described here, both this page and the App Store privacy answers
-                should be updated before that version is submitted.
+                If Promptly adds analytics, crash reporting, new payment
+                processors, expanded account sync, or another external service
+                not described here, this page will be updated to describe it.
               </p>
             </article>
             <article>