adding Terms and Conditions page and footer link

[mahimagupta-droid]

Description

Related Issue

Closes #1562

What this does

Adds a standalone /terms page and links it from the footer, following
the existing /privacy page's layout and styling for consistency.

Sections included

• Acceptance of Terms
• User Responsibilities
• Acceptable Use Policy
• Account Restrictions
• Intellectual Property
• Limitation of Liability
• Changes to Terms

Notes

• No onboarding/auth screens exist in this app (no login/accounts), so
  the footer link is the only integration point needed.

• Verified with npm run build — /terms builds as a static route,
  same as /privacy.## Participant Info

• GitHub username: mahimagupta-droid

• Contribution level (Beginner/Intermediate/Advanced): beginner

Screen Recording

How to record: run bun run dev → open http://localhost:3000 → demonstrate the full working flow of your change, including any edge cases.

• macOS: Cmd + Shift + 5 → Record Selected Portion, or use QuickTime Player
• Windows: Win + G → Xbox Game Bar → Capture
• Linux: OBS Studio, GNOME Screenshot tool, or kazam
• Any OS: Loom (free screen recorder, great for sharing)

Reframe.Resize.trim.and.export.videos.in.your.browser.-.Google.Chrome.2026-07-03.02-05-23.mp4

Recording / Loom link: ## Checklist

• [ yes] I have read the contribution guidelines
• [ yes] My changes follow the project structure
• [ yes] I have tested my changes in Chrome, Firefox, and Safari
• [ yes] bun run lint passes (no ESLint errors)
• [ yes] bunx tsc --noEmit passes (no TypeScript errors)
• [ yes] New interactive elements have aria-label / accessible names
• [ yes] No console.log statements left in
• [ yes] This PR is related to a valid issue
• [ yes] Screen recording attached above (required for UI/feature/design changes)

[vercel]

@mahimagupta-droid is attempting to deploy a commit to the magic-peach1's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

⚠️ PR Format Issues — @mahimagupta-droid

Please fix the following before your PR can be reviewed:

• ⚠️ Use a conventional PR title. Examples:
  • feat: add dark mode support
  • fix: resolve aria label missing on slider
  • docs: add deployment guide to README

Push new commits after fixing — this comment will update automatically.

📖 CONTRIBUTING.md

[github-actions]

👋 Thanks for your PR, @mahimagupta-droid!

Welcome to Reframe — a browser-based video editor built for everyone 🎬

What happens next

1. 🤖 Automated checks — build & TypeScript typecheck will run automatically
2. ✅ Vercel preview — a preview deployment will be created (requires maintainer authorization for fork PRs)
3. 👀 Code review — a maintainer will review your changes
4. 🚀 Merge — once approved, your PR will be merged!

Quick checklist

• PR title follows Conventional Commits (e.g. feat: add dark mode)
• Linked the issue this PR closes (e.g. Closes #123)
• Tested the changes locally (bun run dev)
• Build passes (bun run build)

Useful links

• 📖 CONTRIBUTING.md
• 🐛 Open Issues
• ⭐ Star the repo to support the project!

Happy coding! 🎉