QnA Init Docs — UC_1.9.1-1.9.4 (Marketing Website — Utility Suite: Privacy Policy, Terms of Service, Risk Disclosure, 404 Error Page)
Related WBS: UC_1.9.1 (Privacy Policy Page), UC_1.9.2 (Terms of Service Page), UC_1.9.3 (Risk Disclosure Page), UC_1.9.4 (404 Error Page)
Category: MARKETING WEBSITE → Module: Utility Suite
Source pre-flight completed:
- CR:
References/CR/_CR_INDEX.md — no CR entries affect Marketing Website / Utility Suite. (checked all 4 CR summaries: TradeSea/NinjaTrader, Nuvei/EBANX, Everflow/Impact, Freshdesk/Zendesk — none touch marketing pages)
- QnA confirmed:
References/QnA from clients/01_MARKETING_WEBSITE/QnA_MARKETING_WEBSITE.md — currently empty (no answered/open items yet for this category)
- Customer supplies:
References/Customer supplies/_SOURCE_MANIFEST.yaml, dashboard_v7_full.txt §"Template System" row 12 — "Utility Suite — General & System. A clean text layout used for FAQ, Privacy, Terms, Risk Disclosure and the 404 Error Page." (Source: RFQ_ Website and Dashboard Implementation V7.pdf; line 142)
- WBS: rows 45–49 (UC_1.9.1–UC_1.9.4), Status design = "Checking" for all 4 rows (design not yet fully locked by client)
- Wireframe:
References/Wireframe/Marketing website/Utility Suite/ — 3 PNG files exist: Utility Page Template_Terms of Services.png, Utility Page Template_Privacy Policy.png, Utility Page Template_Risk Disclosures.png, 404 Not Found.png
The 4 wireframe PNGs were opened via the file-reading tool but their visual content (headings, body text, layout structure, illustration) could not be reliably extracted in this session — only file dimensions were confirmed readable. Per project rule "NEVER fabricate data, field names, or business rules not in the source," I am not inventing exact heading text, Table-of-Contents behavior, section counts, or 404 illustration content. All items below that depend on visual wireframe detail are logged as open questions rather than assumed.
| ID | Question / Assumption | Type | Status | BA Answer |
|---|
| A-01 | What is the exact hardcoded legal body copy for the Privacy Policy? Customer supplies only confirms the page uses the "Utility Suite clean text layout template" with "mandatory legal text (no CMS)" — no actual legal copy is present in References/Customer supplies/. | Question | ⚠️ Superseded 2026-08-13 | Customer provides all the content in the wireframe; content cannot be changed via CMS. → Superseded (user confirmation, BA session 2026-08-13): the Privacy Policy body is now fully configured via Sanity CMS, not hardcoded. The wireframe remains the initial content seed + layout reference; the published Sanity document is the runtime source of truth. Ref: UC_1.9.md BR-1.9.1-01. (Original answer kept for historical record.) |
| A-02 | Does the Privacy Policy page include a Table of Contents / sticky anchor-jump sidebar (similar to The Rules Page UC_20/UC_1.8.1 pattern), or is it a single continuous scroll with numbered sections only? Could not confirm from wireframe. | Question | Confirmed | Single continuous scroll with numbered sections only (no TOC / anchor-jump sidebar). |
| A-03 | Is there a "Last Updated" / "Effective Date" line displayed on the page? If yes, exact label text and date format? | Question | Confirmed | "Last Updated" date/time is generated dynamically by the system, reflecting the real system time when the content was last changed (not a manually-typed static date). |
| A-04 | [ASSUMPTION: A-04] The page reuses the shared Global Layout header/footer defined in UC_01 (nav dropdowns + footer legal links/social icons/newsletter) rather than a custom header/footer. | Assumption | Confirmed | Yes. |
| A-05 | WBS row 45 note says: "Hiện đang áp dụng màn Utility Page Template(?) - Đã Q&A". Is that Q&A the final confirmed answer for this page's design, and if so, can the confirmed decision be summarized here so it can be cited as source? | Question | Confirmed | Yes — the Utility Page Template shown in the wireframe is the confirmed final design. |
| ID | Question / Assumption | Type | Status | BA Answer |
|---|
| A-06 | What is the exact hardcoded legal body copy for the Terms of Service page? No legal copy found in Customer supplies. | Question | ⚠️ Superseded 2026-08-13 | Customer provides all the content in the wireframe; content cannot be changed via CMS. → Superseded (user confirmation, BA session 2026-08-13): the Terms of Service body is now fully configured via Sanity CMS, not hardcoded. Ref: UC_1.9.md BR-1.9.2-01. (Original answer kept for historical record.) |
| A-07 | Same TOC/anchor-nav question as A-02 — applies to Terms of Service. | Question | Confirmed | Single continuous scroll with numbered sections only (no TOC / anchor-jump sidebar). |
| A-08 | Same Last Updated/Effective Date question as A-03 — applies to Terms of Service. | Question | Confirmed | "Last Updated" date/time is generated dynamically by the system, reflecting the real system time when the content was last changed. |
| A-09 | [ASSUMPTION: A-09] Same shared Global Layout header/footer reuse assumption as A-04 — applies to Terms of Service. | Assumption | Confirmed | Yes. |
| A-10 | Checkout flow (UC_49, dashboard_v7_full.txt Step 5) references a separate "Terms of Service for the Data Processing and Performance Evaluation Service (Associate Track)" checkbox/consent text tied to purchase — is that the SAME document as the public /terms page (UC_1.9.2), or a distinct contract shown only inside checkout? Needed to avoid conflating two different legal documents. | Question | Confirmed | It is different. The checkout-only "Terms of Service for the Data Processing and Performance Evaluation Service (Associate Track)" is a distinct document from the public /terms page (UC_1.9.2). SRS must not conflate the two. |
| ID | Question / Assumption | Type | Status | BA Answer |
|---|
| A-11 | What is the exact hardcoded body copy for the Risk Disclosure page? Customer supplies contains one confirmed legally-required snippet used elsewhere in checkout (dashboard_v7_full.txt, Step 5): "HYPOTHETICAL OR SIMULATED PERFORMANCE RESULTS HAVE CERTAIN LIMITATIONS..." — is this snippet part of the /risk-disclosure page body, or is it a separate checkout-only disclosure unrelated to UC_1.9.3? | Question | ⚠️ Superseded 2026-08-13 | Customer provides all the content in the wireframe; content cannot be changed via CMS. → Superseded (user confirmation, BA session 2026-08-13): the Risk Disclosure body is now fully configured via Sanity CMS, not hardcoded. The checkout-only snippet is still treated as a separate item, not conflated with this page body. Ref: UC_1.9.md BR-1.9.3-01. (Original answer kept for historical record.) |
| A-12 | Same TOC/anchor-nav question as A-02 — applies to Risk Disclosure. | Question | Confirmed | Single continuous scroll with numbered sections only (no TOC / anchor-jump sidebar). |
| A-13 | Same Last Updated/Effective Date question as A-03 — applies to Risk Disclosure. | Question | Confirmed | "Last Updated" date/time is generated dynamically by the system, reflecting the real system time when the content was last changed. |
| A-14 | [ASSUMPTION: A-14] Same shared Global Layout header/footer reuse assumption as A-04 — applies to Risk Disclosure. | Assumption | Confirmed | Yes. |
| ID | Question / Assumption | Type | Status | BA Answer |
|---|
| A-15 | What is the exact custom illustration/icon shown on the 404 page (per user's explicit callout: "including custom illustrations/icons")? Could not extract visual content from 404 Not Found.png in this session. | Question | Confirmed | The illustration is exactly as shown in the wireframe image; it is a fixed static asset and cannot be customized/changed via CMS. |
| A-16 | What is the exact heading and body text (e.g., "404", "Page Not Found", subtext)? | Question | Confirmed | "404 - Page not found or has been removed." |
| A-17 | What CTA button(s) are shown (e.g., "Back to Home")? Exact label text and destination route for each? | Question | Confirmed | "Back to homepage" (single CTA button, destination = site homepage /). |
| A-18 | Does the 404 page include a search bar or "suggested links" block, or is it CTA-button-only? | Question | Confirmed | No — CTA-button-only, no search bar / suggested links block. |
| A-19 | [ASSUMPTION: A-19] The 404 page reuses the shared Global Layout header/footer (same as the 3 legal pages), consistent with it being part of the same "Utility Suite" template family per dashboard_v7_full.txt row 12. | Assumption | Confirmed | Yes. |
| A-20 | [Impact — HTTP behavior, MANDATORY per Impact Analysis] When a visitor navigates to a non-existent route, does the server respond with an actual HTTP 404 status code (SEO/technical requirement) while rendering this page, or does it soft-redirect to /404 with a 200 status? This affects search-engine indexing and is not a pure UI concern. | Question | Confirmed | Server returns an actual HTTP 404 status code (not a 200 soft-redirect). |
| ID | Question / Assumption | Type | Status | BA Answer |
|---|
| A-21 | dashboard_v7_full.txt row 12 groups FAQ into the same "Utility Suite" template family as Privacy/Terms/Risk/404. However, WBS categorizes Help Center/FAQ as UC_27 / UC_1.8.8 under the "Resources" module (Sanity CMS-driven, dynamic), separate from the "Utility Suite" module (UC_1.9.1-1.9.4, static/hardcoded). [CROSS_UC_CONFLICT] flagged: is FAQ (UC_27/UC_1.8.8) intentionally excluded from this static Utility Suite doc because it is dynamic/CMS-driven (unlike UC_1.9.1-1.9.4), or should FAQ share the same static layout component? Per user's explicit request, only UC_1.9.1-1.9.4 are in scope for this SRS — flagging for BA awareness only, not blocking. | Question | Confirmed | It is excluded. FAQ (UC_27/UC_1.8.8) is intentionally out of scope for this doc — it is CMS/Sanity-driven and dynamic, unlike the hardcoded UC_1.9.1-1.9.4 pages. |
| A-22 | UC_01 (Global Layout footer) description mentions footer legal links include "ToS, Privacy, CFTC" — CFTC appears to be a distinct legal page not covered by UC_1.9.1-1.9.4. Is a CFTC disclosure page in scope elsewhere in the WBS, or out of scope entirely for now? Flagging for awareness — not blocking this doc. | Question | Confirmed | In scope (elsewhere in the WBS, not part of UC_1.9.1-1.9.4). Noted for BA awareness only — no action in this SRS. |
| A-23 | [PATTERN] All 4 pages (UC_1.9.1-1.9.4) share one structural template ("Utility Suite clean text layout") with only body content/copy varying. Suggest documenting this shared layout as a single reusable "Utility Page Template" component description in the SRS (header + optional TOC + body + footer), then only vary the body content per page — rather than repeating identical layout description 4 times. Confirm this documentation approach is acceptable. | Question | Confirmed | Yes — approach accepted. |
| A-24 | [Impact] Since content is described as "hardcoded" (no CMS), what is the process for updating legal text when it changes (e.g., regulatory update to Risk Disclosure)? Does that require a code deploy, or is there some other mechanism? This affects whether "Impact: content change requires redeploy" should be documented as a system behavior note. | Question | ⚠️ Superseded 2026-08-13 | It requires a code deploy. → Superseded (user confirmation, BA session 2026-08-13): legal copy for all 3 pages is edited and published in Sanity CMS — no code deploy required. Only structural/layout changes to the Utility Page Template still need a deploy. Consequently the "Last Updated" timestamp in A-03/A-08/A-13 now tracks the Sanity publish, not a deploy. Ref: UC_1.9.md §Shared Component. (Original answer kept for historical record.) |
Gate passed. All items A-01 through A-24 confirmed by BA. Proceeding to Step 3 (Architect) to author the final SRS at docs/BA/UC_1.1-1.9/UC_1.9/UC_1.9.md using these confirmed answers.