# legal-pages Specification

## Purpose
TBD - created by archiving change add-terms-and-privacy-pages. Update Purpose after archive.
## Requirements
### Requirement: Public Accessibility of Legal Pages
The system SHALL provide public, unauthenticated routes for `/terms` and `/privacy` that load the Terms of Use and Privacy Policy pages respectively without requiring user login or team membership.

#### Scenario: Unauthenticated user accesses Terms page
- **WHEN** an unauthenticated visitor navigates to `/terms`
- **THEN** the system SHALL render the Terms of Use page with a status 200 response

#### Scenario: Unauthenticated user accesses Privacy Policy page
- **WHEN** an unauthenticated visitor navigates to `/privacy`
- **THEN** the system SHALL render the Privacy Policy page with a status 200 response

### Requirement: Facebook Developer App Compliance Content
The Privacy Policy page SHALL explicitly disclose Facebook API data usage, data types collected (such as Facebook profile info, page tokens, and user comments/messages), data retention rules, third-party sharing policies, and clear instructions for User Data Deletion per Meta Platform Terms.

#### Scenario: Facebook App Review compliance inspection
- **WHEN** a Facebook App Reviewer evaluates the Privacy Policy page
- **THEN** the page SHALL contain designated sections for "Information Collected via Facebook APIs", "Use of Facebook Data", "Data Retention & Security", and "User Data Deletion Instructions"

### Requirement: Legal Pages UI and Navigation
The Terms of Use and Privacy Policy pages SHALL adhere to the application design system, providing clear readable legal typography, responsive layout, brand logo header, and footer links connecting back to the main landing page (`/`).

#### Scenario: Visitor navigates from footer links
- **WHEN** a user on the landing page clicks "Terms of Service" or "Privacy Policy" in the page footer
- **THEN** the system SHALL navigate to `/terms` or `/privacy` seamlessly via Inertia link routing