Privacy Policy Route Change — v0.1.56

Overview

As of v0.1.56, the privacy policy page is accessible at /privacy rather than the originally specified route /privacy-policy. This is a spec deviation that requires a configuration change to avoid broken links and 404 errors for users arriving from emails, footer links, or any external sources.

What You Need to Do

1. Add a Redirect in next.config.ts

To maintain backward compatibility and avoid 404s, add a permanent redirect so that any request to /privacy-policy is automatically forwarded to /privacy:

// next.config.ts
const nextConfig = {
  async redirects() {
    return [
      {
        source: '/privacy-policy',
        destination: '/privacy',
        permanent: true,
      },
    ];
  },
};

export default nextConfig;

Setting permanent: true issues a 308 Permanent Redirect, which tells browsers and search engines to update their records and preserves any SEO value on the original URL.

2. Audit Email Templates

Search all email templates for any hardcoded links to /privacy-policy and update them to /privacy. Common locations include:

• Onboarding / welcome emails
• Tenancy agreement notification emails
• Footer boilerplate in transactional emails

3. Audit External Systems

If any external platforms (CRMs, marketing tools, contractor portals, AgentOS integrations) store or reference the privacy policy URL, update those references to /privacy or rely on the redirect above as a safety net.

Background

The original product specification defined the privacy policy route as GET /privacy-policy. The built application implements this page at src/app/privacy/page.tsx, which Next.js serves at /privacy. The root page.tsx footer already links to /privacy, so in-app navigation is unaffected. The risk is limited to inbound links from outside the application.

File Reference

File	Notes
src/app/privacy/page.tsx	Privacy policy page component
src/app/page.tsx	Root page — footer already uses /privacy
next.config.ts	Add redirect here (see above)