fix(public): replace internal submission-prep notes visible on four pages

.lane/reports/fix-lane1-submission-prep-notes-visible-copy.md

@@ -0,0 +1,91 @@
+# Lane 1 report — internal editorial and submission-prep notes live as visible copy on four public app pages
+
+- Item: `[unreviewed-by-opus] Internal editorial and submission-prep notes are live as visible copy on four public app pages`
+- Item ID: `de469a3800`
+- Branch: `fix/lane1-submission-prep-notes-visible-copy`
+- Commit: `2dc939f fix(public): replace internal submission-prep notes on four pages`
+- Date: 2026-08-17
+
+## What was live
+
+Four tinystudio.in pages in `public/` carried internal editorial and
+submission-prep notes as visible copy:
+
+1. `public/promptly/privacy/index.html`
+   - H1: "Promptly's privacy page is already public ahead of release."
+   - Lead: "reflects the current planned launch scope and should stay
+     aligned with the final App Store privacy disclosures before release"
+   - Aside "Current release scope": "Promptly is not publicly released
+     yet." / "This page reflects the currently planned launch
+     configuration."
+   - Card eyebrow "At launch".
+   - "Important note" telling visitors both this page and the App Store
+     privacy answers "should be updated before that version is submitted".
+
+2. `public/drishti/privacy/index.html` — same pattern ("already in place
+   before launch", "current planned launch scope", "current release
+   scope", "not publicly released yet", "at launch", "should be updated
+   before that version is submitted").
+
+3. `public/terms/index.html`
+   - "Product-specific terms can be expanded later if a released app
+     needs them."
+   - "Content may change as products are updated or launched."
+   - "...as new releases are prepared or existing products change."
+
+4. `public/privacy/index.html` (studio privacy hub)
+   - "so App Store metadata can point to a more specific policy"
+   - "so their App Store privacy disclosures can stay connected to
+     app-specific public documentation"
+
+## What changed
+
+Rewrote the internal-notes passages as visitor-facing copy describing
+what each page covers and how information is used, deleting every
+reference to the internal launch calendar, release scope, planned launch
+configuration, and App Store submission process. Heading levels, links,
+meta tags, chips, and JSON-LD are unchanged (heading hierarchy, link
+targets, structured data, and social-preview geometry are intact).
+
+- Promptly privacy: H1 "Promptly privacy for bookings, reminders, and
+  client data."; lead explains what data Promptly handles; aside "What
+  this page covers"; card eyebrow "Advertising and tracking"; important
+  note now says the page will be updated if new services are added.
+- Drishti privacy: H1 "Drishti privacy for mindful screen time."; same
+  visitor-facing rewrite pattern.
+- Terms: lead now says each app may publish its own terms if needed;
+  scope bullet and use-of-site paragraph no longer reference "releases
+  are prepared" / "a released app needs them".
+- Privacy hub: app-policy passages now describe that each app has a
+  dedicated page describing that app's data handling.
+
+## Validation
+
+- `git diff --check`: clean
+- `node scripts/test-public-conversion-signal.mjs`: PASS
+- `node scripts/test-public-structured-data.mjs`: PASS
+- `node scripts/test-public-brand-disambiguation.mjs`: PASS
+- `node scripts/test-public-heading-hierarchy.mjs`: PASS
+- `node scripts/test-public-link-targets.mjs`: PASS
+- `node scripts/test-public-social-preview.mjs`: PASS
+- `node scripts/test-public-soft-404.mjs`: PASS
+- `node scripts/test-public-deploy-bundle.mjs`: PASS
+
+Fresh sweep of `public/` for `launch scope|launch configuration|release
+scope|not publicly released|ahead of release|before launch|should be
+updated before|is submitted|releases are prepared|a released app
+needs|App Store metadata` returns zero matches.
+
+## Notes
+
+- A prior lane authored the same two-page privacy rewrite on branch
+  `fix/remove-submission-prep-copy-privacy-pages` (commits `04e635d` /
+  `fc95af9`) but it was never merged; main's two app privacy pages were
+  byte-identical to that branch's pre-image, so this branch applies the
+  same already-validated rewrite and goes further to cover the terms
+  page and the studio privacy hub (the other two pages of the four).
+- The live tinystudio.in deployment still serves stale content (old
+  footer "clean public foundation before launch", old privacy hero
+  copy) because deploys are blocked on the missing Cloudflare token
+  documented by prior lane reports; the source fix on main is the
+  durable fix and will surface once deploys resume.

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,23 +97,23 @@ <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>
         </section>
 
         <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>

public/privacy/index.html

@@ -88,7 +88,7 @@ <h1>The studio privacy center for Tiny Studio.</h1>
             <p class="page-lead">
               This page covers the Tinystudio.in website and acts as the main
               studio-level privacy hub. Each app also has its own privacy page
-              so App Store metadata can point to a more specific policy.
+              that describes what that app handles in more detail.
             </p>
             <div class="action-row">
               <a class="button" href="/privacy-choices/">Privacy choices</a>
@@ -135,9 +135,8 @@ <h2>To respond, troubleshoot, and improve.</h2>
             <p class="eyebrow">App policies</p>
             <h2>Each app still gets its own policy page.</h2>
             <p>
-              Promptly and Drishti each have a dedicated privacy URL so their
-              App Store privacy disclosures can stay connected to app-specific
-              public documentation.
+              Promptly and Drishti each have a dedicated privacy page that
+              describes the data that app handles and the choices available.
             </p>
           </article>
         </section>

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,23 +96,23 @@ <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>
         </section>
 
         <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>

public/terms/index.html

@@ -87,16 +87,16 @@
             <h1>Website terms for Tiny Studio’s public pages.</h1>
             <p class="page-lead">
               These terms apply to the Tiny Studio website and the public pages
-              used for app, support, privacy, and contact information. Product-
-              specific terms can be expanded later if a released app needs them.
+              for app information, support, privacy, and contact. Each app may
+              publish its own terms alongside these website terms if needed.
             </p>
           </div>
 
           <aside class="page-card dark">
             <p class="eyebrow">Scope</p>
             <ul class="plain-list">
               <li>The website exists to share app information and public links.</li>
-              <li>Content may change as products are updated or launched.</li>
+              <li>Content may change as the apps and their pages evolve.</li>
               <li>The site is not a substitute for in-app records or purchases.</li>
             </ul>
           </aside>
@@ -107,8 +107,8 @@ <h1>Website terms for Tiny Studio’s public pages.</h1>
             <p class="eyebrow">Use of the site</p>
             <h2>Information may evolve over time.</h2>
             <p>
-              Tiny Studio may update copy, links, and public app details as new
-              releases are prepared or existing products change.
+              Tiny Studio may update copy, links, and public app details as the
+              apps and pages change or grow.
             </p>
           </article>