Add static Privacy Policy navigation + dedicated policy page(s) for landing experience

[Copilot]

This PR adds first-class Privacy Policy support to the static site by wiring it into existing landing navigation and providing a policy page that matches current Prexus visual structure. Routing is kept fully static-host compatible via relative HTML links.

• Landing navigation updates

  • Added Privacy Policy to the hamburger dropdown in frontend/landing.html
  • Added Privacy Policy to the footer links in frontend/landing.html

• Privacy Policy page implementation

  • Replaced frontend/privacy-policy.html content with a generic, product-aligned privacy policy (collection, use, sharing, cookies, security, retention, transfers, rights, children, changes, contact)
  • Kept typography/layout consistent with existing Prexus styling and structure (header/nav + footer continuity)

• Static hosting path compatibility

  • Added root-level privacy-policy.html to support root-served static deployments
  • Used relative links appropriate to each page context (e.g., privacy-policy.html in frontend, frontend/landing.html from repo root page)

<!-- frontend/landing.html -->
<nav class="menu-dropdown" id="menu-dropdown" aria-hidden="true">
  ...
  <a href="privacy-policy.html" class="menu-item">Privacy Policy <span class="arr">→</span></a>
</nav>

<div class="footer-links">
  ...
  <a href="privacy-policy.html">Privacy Policy</a>
</div>

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1181/chrome-linux/headless_shell /home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1181/chrome-linux/headless_shell --disable-field-trial-config --disable-REDACTED-networking --disable-REDACTED-timer-throttling --disable-REDACTEDing-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-REDACTED-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AcceptCHFrame,AutoExpandDetailsElement,AvoidUnnecessaryBeforeUnloadCheckSync,CertificateTransparencyComponentUpdater,DestroyProfileOnBrowserClose,DialMediaRouteProvider,ExtensionManifestV2Disabled,GlobalMediaControls,HttpsUpgrades,Impro alloc-76b5fe9328c1063f.rlib 6e1dc71b.rlib ccc.rlib (dns block)
  • Triggering command: /home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1181/chrome-linux/headless_shell /home/REDACTED/.cache/ms-playwright/chromium_headless_shell-1181/chrome-linux/headless_shell --disable-field-trial-config --disable-REDACTED-networking --disable-REDACTED-timer-throttling --disable-REDACTEDing-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-REDACTED-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AcceptCHFrame,AutoExpandDetailsElement,AvoidUnnecessaryBeforeUnloadCheckSync,CertificateTransparencyComponentUpdater,DestroyProfileOnBrowserClose,DialMediaRouteProvider,ExtensionManifestV2Disabled,GlobalMediaControls,HttpsUpgrades,Impro 766fa6.rlib alloc-76b5fe9328ldd 6e1dc71b.rlib bb49/build_script_build-76885401-y git (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Repository: devXyi/prexus-intelligence

Goal: Add Privacy Policy support to the static site.

Tasks:

1. Update the existing landing page file landing.html to add a "Privacy Policy" link in the footer-links section.
2. Update landing.html to add a "Privacy Policy" item in the hamburger dropdown menu.
3. Create a new static HTML file at the repo root named privacy-policy.html.
4. Ensure all links work correctly with static HTML routing (i.e., relative links that work on GitHub Pages or any static host).
5. Keep existing Prexus styling and typography consistent (reuse existing CSS classes/layout; do not introduce a new design system).

Implementation notes:

• Use relative hrefs like privacy-policy.html (not framework routes).
• Preserve existing footer/menu structure and existing classes; add minimal markup.
• The new privacy policy page should include the same header/nav and footer (or as close as existing site structure allows), and be styled consistently by reusing the existing CSS.
• Content: include a reasonable Privacy Policy template (sections like Information We Collect, How We Use It, Sharing, Cookies, Security, Retention, International Transfers if applicable, Your Rights, Children, Changes, Contact). Keep it generic and aligned to a "probability predictive intelligence engine" product; avoid legal guarantees.

Deliverable:

• Open a PR with the changes to landing.html and the new privacy-policy.html file, with a clear description and confirmation that links are correct.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Add Privacy Policy support to landing.html.

Tasks:

1. Add "Privacy Policy" link in footer-links section.
2. Add "Privacy Policy" item in hamburger dropdown menu.
3. Create a new file named privacy-policy.html.
4. Ensure all links work correctly with static HTML routing.
5. Keep existing Prexus styling and typography consistent.

Assistant: I’m waiting for you to approve the pending repository change request in the dialog; once you do, I’ll proceed to update landing.html, add the hamburger/footer links, and create privacy-policy.html with matching styling and working static links.

This pull request was created from Copilot chat.