Skip to content

updated terms and conditions#170

Open
ArshiBansal wants to merge 1 commit into
kunalverma2512:mainfrom
ArshiBansal:terms_page
Open

updated terms and conditions#170
ArshiBansal wants to merge 1 commit into
kunalverma2512:mainfrom
ArshiBansal:terms_page

Conversation

@ArshiBansal

@ArshiBansal ArshiBansal commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

📌 Pull Request Summary

🔗 Related Issue

Closes #165


📝 Description

This PR introduces a fully structured and production-ready Terms of Service page for the application. The previous placeholder content has been replaced with a comprehensive legal document covering key usage, privacy, and liability sections.

Changes Made

Replaced placeholder Terms of Service content with a complete legal structure
Added sections for:

  1. User eligibility and responsibilities
  2. Acceptable use policy
  3. Data usage and privacy disclaimer
  4. Cookies and tracking information
  5. Service availability
  6. Termination policy
  7. Limitation of liability and disclaimers
  8. Changes to terms
  9. Accessibility information
  10. Added versioning and “last updated” metadata
  11. Improved readability with semantic section structure
  12. Enhanced UI formatting using consistent spacing and typography

Motivation

The previous Terms page contained only placeholder text and did not meet basic legal or product requirements. This update ensures the application has a complete baseline legal document that improves transparency, reduces legal risk, and prepares the app for production or public release.


🚀 Type of Change

Select all that apply:

  • Bug Fix
  • [.] New Feature
  • [.] Enhancement
  • [.] Documentation Update
  • [.] Refactoring
  • Performance Improvement
  • DevOps / Tooling
  • Other

🧪 Testing

Verification

  • [.] Tested Locally
  • Existing Tests Passed
  • New Tests Added
  • [.] No Testing Required

Test Details

Describe how the changes were tested and verified.


📸 Screenshots / Demo (If Applicable)

Attach screenshots, GIFs, or recordings that help demonstrate the changes.


✅ Checklist

  • [.] I have read and followed the contribution guidelines.
  • [.] I have self-reviewed my changes.
  • [.] My changes are limited to the scope of this issue.
  • [.] Documentation has been updated where necessary.
  • [.] No unnecessary files or unrelated changes have been included.
  • [.] The related issue has been linked correctly.
  • [.] All applicable testing and validation steps have been completed.

📚 Additional Notes

This Terms page is structured to be easily extensible. Future improvements could include:

Linking a separate Privacy Policy page
Converting to a CMS/Markdown-driven system
Adding localization support for multiple languages

Summary by CodeRabbit

  • Documentation
    • Fully expanded Terms of Service page with 12 comprehensive sections covering user eligibility, account responsibilities, acceptable use policies, data collection and privacy practices, intellectual property rights, service availability, account termination, and accessibility guidelines.
    • Added version and last-updated metadata for transparency and compliance tracking.

@vercel

vercel Bot commented Jun 8, 2026

Copy link
Copy Markdown

@ArshiBansal is attempting to deploy a commit to the Kunal Verma's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown

🚀 PR Received Successfully

Hello @ArshiBansal,

Thank you for taking the initiative to contribute to this project.

Please ensure that your PR follows all project guidelines properly before requesting review.

⚠️ Important Instructions

  • Maintain proper code quality and structure
  • Do not make unnecessary changes/files
  • Ensure responsiveness across devices
  • Follow existing project conventions strictly
  • Attach screenshots/videos for UI-related changes
  • Resolve merge conflicts before requesting review
  • Avoid AI-generated low quality PRs or copied implementations

📌 Mandatory for GSSoC'26 Participants

Joining the community group and announcement channel is compulsory for all contributors participating through GSSoC'26.

Failure to follow contribution guidelines may lead to PR rejection.

We appreciate your effort and wish you a great open-source journey ahead. ✨

@coderabbitai

coderabbitai Bot commented Jun 8, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

TermsPage was expanded from a minimal placeholder to a complete Terms of Service document. The component now defines version and lastUpdated metadata, renders them in a meta section, and provides twelve numbered sections covering eligibility, user accounts, responsibilities, acceptable use, data collection, cookies, intellectual property, service availability, termination, liability disclaimer, policy changes, and accessibility, with a footer contact line.

Changes

Terms of Service Page

Layer / File(s) Summary
Complete Terms of Service Document
frontend/src/pages/TermsPage.jsx
TermsPage replaced from placeholder with full Terms of Service including metadata (version, lastUpdated), twelve numbered sections covering user eligibility, accounts, responsibilities, acceptable use, data & privacy, cookies & tracking, intellectual property, service availability, termination, liability disclaimer, policy changes, and accessibility, plus footer support information; layout containers and styling updated.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

enhancement, Frontend, type:design, level:intermediate

Suggested reviewers

  • kunalverma2512

Poem

🐇 A terms page hops into view,
With twelve clear sections, polished and true—
Version and dates now proudly displayed,
Legal foundations laid without shade! 📜✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'updated terms and conditions' is directly related to the main change—replacing placeholder Terms of Service with comprehensive legal content.
Description check ✅ Passed The description covers all key template sections: related issue, detailed changes, motivation, type of change selection, testing notes, and completion checklist.
Linked Issues check ✅ Passed All primary objectives from issue #165 are met: comprehensive Terms page with user responsibilities, acceptable use, data/privacy disclaimers, liability limitations, versioning, and 'last updated' date.
Out of Scope Changes check ✅ Passed All changes are within scope of issue #165—focused solely on the TermsPage component with legal content, versioning, and UI structure enhancements.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/src/pages/TermsPage.jsx`:
- Around line 75-80: The paragraph in the TermsPage component that currently
says "please refer to our Privacy Policy" should link to the existing /privacy
page; edit the JSX in TermsPage.jsx (the <p> containing "We may collect
personal... please refer to our Privacy Policy.") and replace the plain "Privacy
Policy" text with an internal link (e.g., an anchor tag <a
href="/privacy">Privacy Policy</a> or your app's <Link to="/privacy">Privacy
Policy</Link>) so users can click through to the policy.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1a257e5f-4a30-4afa-8da9-72c96a837f14

📥 Commits

Reviewing files that changed from the base of the PR and between 58213ea and a25bbb2.

📒 Files selected for processing (1)
  • frontend/src/pages/TermsPage.jsx

Comment thread frontend/src/pages/TermsPage.jsx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Add Terms and Conditions Page

1 participant