Fix privacy center routing issue

[jpople]

Ticket ENG-2869

Description Of Changes

The privacy center supports multiple properties on custom URL paths (e.g. /mypath). After the page-based privacy request flow was introduced, navigating from a property path home page to the privacy request form, verification, and success pages caused the property path prefix to be dropped from the URL. This fix restores correct routing throughout the full privacy request flow when accessed from a custom property path.

Code Changes

• Added usePathname() in HomePage to preserve the property path prefix when navigating to the privacy request form.
• Updated PrivacyRequestFormPage, VerificationPage, and RequestSubmittedPage to use useParams() so all internal navigation stays within the current property path.
• Added three new server-rendered pages under app/[propertyPath]/privacy-request/ (form, verify, success) that load the property-specific environment, mirroring the existing root-level privacy request routes.

Steps to Confirm

1. Configure a property with a custom path (e.g. /mypath) and a privacy center config in the admin UI.
2. Navigate to localhost:3001/mypath.
3. Click an action card (e.g. Access or Erasure).
4. Confirm the URL becomes localhost:3001/mypath/privacy-request/[actionKey] and the form reflects the property's configured options.
5. Submit the form. If identity verification is enabled, confirm the URL transitions to .../verify and then .../success — all still under /mypath/....
6. On the success page, click "Return home" and confirm it returns to localhost:3001/mypath.
7. Repeat steps 2–6 from the root localhost:3001 to confirm the default (non-property-path) flow is unaffected.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • No UX review needed
• Followup issues:
  • No followup issues
• Database migrations:
  • No migrations
• Documentation:
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ignored	Preview	Mar 3, 2026 4:12pm
fides-privacy-center	Ignored		Mar 3, 2026 4:12pm

[greptile-apps]

Greptile Summary

This PR fixes a routing regression where the property path prefix (e.g., /mypath) was dropped from the URL when navigating through the page-based privacy request flow (form → verify → success).

The fix is applied in two layers:

• HomePage: Now uses usePathname() to preserve the prefix when constructing the initial navigation URL
• Privacy request components (PrivacyRequestFormPage, VerificationPage, RequestSubmittedPage): Derive a basePath from useParams() so that all subsequent in-flow navigations include the prefix
• Server-rendered pages: Three new page files are added under app/[propertyPath]/privacy-request/ to handle these routes and load the property-specific environment

All routing paths are handled correctly: both the root path (/) and property-path (/mypath) flows work properly, with the basePath || "/" fallback ensuring the root flow is unaffected. The implementation is consistent across all three new property-path pages and mirrors the existing root-level privacy request routes.

Confidence Score: 5/5

• This PR is safe to merge. The routing fix is logically correct and does not affect the existing root-path flow.
• The routing logic is end-to-end correct: both root path (/) and property-path (/mypath) flows are handled properly. All navigation paths through the property-path privacy request flow correctly carry the basePath prefix. The three new server-rendered pages properly mirror their root-level counterparts. The basePath || "/" fallback ensures the root flow remains unaffected.
• No files require special attention.

_{Last reviewed commit: 37ea34b}

[greptile-apps]

_{8 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[lucanovera]

@jpople This check looks a bit fragile. Is there a way we can check for the propertyPath param like you do in other components instead?

[jpople]

Good suggestion, fixed.

[lucanovera]

Nice work. The privacy center path works great with the new page navigation. Code changes look good. Approved!