Release Notes: v0.1.57 — Privacy Policy Redirect Fix

Release date: v0.1.57
Type: Bug fix
Scope: Routing / URL handling

What Changed

A permanent (301) redirect has been added from /privacy-policy to /privacy.

GET /privacy-policy  →  301  →  /privacy

This is a framework-level change handled entirely by Next.js — there are no runtime code changes and no changes to the privacy policy page content or layout.

Why This Matters

The original project spec defined the privacy policy URL as /privacy-policy. The built application, however, serves the privacy policy page at /privacy (src/app/privacy/page.tsx).

Any external reference pointing to /privacy-policy — such as:

Automated emails (e.g. registration, onboarding, tenancy confirmations)
Agency website footers
Third-party integrations and systems
Existing bookmarks or shared links

…would previously return a 404 Not Found error. Users following those links would hit a dead end rather than reaching the policy.

What You Need to Do

Nothing. The redirect is handled automatically by the framework for all visitors. No configuration changes are required by agencies or end users.

If you maintain external links or documentation that references /privacy-policy, you may update them to point directly to /privacy at your convenience — both paths will continue to work correctly.

Technical Details

The redirect was added to the existing redirects() function in next.config.ts:

// next.config.ts
{
  source: "/privacy-policy",
  destination: "/privacy",
  permanent: true,  // HTTP 301
}

This follows the same pattern used for other legacy route redirects in the application. A permanent: true value instructs browsers and search engines to update any cached references to the old URL.

Files Changed

File	Change
`next.config.ts`	Added `/privacy-policy` → `/privacy` redirect entry