Conversation
Add a dedicated Privacy Policy page to the website, addressing user feedback about privacy information being hard to find on repomix.com. Changes: - Create Privacy Policy page with content from README - Add sidebar links for all supported languages - Non-English pages include English content via @include - Simplify README Privacy Policy section to link only Related Discord feedback requested clearer privacy documentation on the website for users who need to verify data handling before using Repomix in their work environment.
WalkthroughThis PR adds comprehensive privacy policy documentation to the website across multiple languages. It updates the README with a privacy policy link, adds localized Privacy Policy navigation items to all language-specific VitePress configs, creates privacy guide pages (one English source with localized stub files containing includes), and removes detailed privacy subsections from the README in favor of a centralized policy page. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes
Possibly related PRs
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
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. Comment |
Summary of ChangesHello @yamadashy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly improves the accessibility of privacy information on repomix.com by migrating the detailed privacy policy from the README to a dedicated, easily navigable page on the website. This change directly addresses user feedback regarding the difficulty of locating privacy documentation, making it more prominent and available across all language versions of the site. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
| { text: 'Community-Projekte', link: '/de/guide/community-projects' }, | ||
| { text: 'Zu Repomix beitragen', link: '/de/guide/development/' }, | ||
| { text: 'Sponsoren', link: '/de/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/de/guide/privacy' }, |
There was a problem hiding this comment.
The Privacy Policy link text should be translated to German for consistency with the rest of the navigation. Consider using 'Datenschutzerklärung' instead of 'Privacy Policy'.
| { text: 'Privacy Policy', link: '/de/guide/privacy' }, | |
| { text: 'Datenschutzerklärung', link: '/de/guide/privacy' }, |
| { text: 'Proyectos de la Comunidad', link: '/es/guide/community-projects' }, | ||
| { text: 'Contribuir a Repomix', link: '/es/guide/development/' }, | ||
| { text: 'Patrocinadores', link: '/es/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/es/guide/privacy' }, |
There was a problem hiding this comment.
The Privacy Policy link text should be translated to Spanish for consistency. Consider using 'Política de privacidad'.
| { text: 'Privacy Policy', link: '/es/guide/privacy' }, | |
| { text: 'Política de privacidad', link: '/es/guide/privacy' }, |
| { text: 'Projets de la Communauté', link: '/fr/guide/community-projects' }, | ||
| { text: 'Contribuer à Repomix', link: '/fr/guide/development/' }, | ||
| { text: 'Sponsors', link: '/fr/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/fr/guide/privacy' }, |
There was a problem hiding this comment.
The Privacy Policy link text should be translated to French. Consider using 'Politique de confidentialité'.
| { text: 'Privacy Policy', link: '/fr/guide/privacy' }, | |
| { text: 'Politique de confidentialité', link: '/fr/guide/privacy' }, |
| { text: 'コミュニティプロジェクト', link: '/ja/guide/community-projects' }, | ||
| { text: 'Repomixに貢献する', link: '/ja/guide/development/' }, | ||
| { text: 'スポンサー', link: '/ja/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/ja/guide/privacy' }, |
There was a problem hiding this comment.
The Privacy Policy link text should be translated to Japanese. Consider using 'プライバシーポリシー'.
| { text: 'Privacy Policy', link: '/ja/guide/privacy' }, | |
| { text: 'プライバシーポリシー', link: '/ja/guide/privacy' }, |
There was a problem hiding this comment.
Code Review
This pull request effectively addresses user feedback by creating a dedicated Privacy Policy page on the website, making this important information more discoverable. The changes are well-structured: the privacy content is moved from the README.md to a new page, sidebar links are added for all supported languages, and non-English pages correctly reuse the English content to avoid duplication.
My review focuses on improving the internationalization of the new sidebar links. While the page content is intentionally in English for all languages, the link text in the sidebar should be translated to match the language of the other navigation items for a consistent user experience. I've left specific suggestions for each language configuration file.
Overall, this is a great improvement to the website's documentation and user-friendliness.
| { text: 'Community-Projekte', link: '/de/guide/community-projects' }, | ||
| { text: 'Zu Repomix beitragen', link: '/de/guide/development/' }, | ||
| { text: 'Sponsoren', link: '/de/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/de/guide/privacy' }, |
| { text: 'Proyectos de la Comunidad', link: '/es/guide/community-projects' }, | ||
| { text: 'Contribuir a Repomix', link: '/es/guide/development/' }, | ||
| { text: 'Patrocinadores', link: '/es/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/es/guide/privacy' }, |
| { text: 'Projets de la Communauté', link: '/fr/guide/community-projects' }, | ||
| { text: 'Contribuer à Repomix', link: '/fr/guide/development/' }, | ||
| { text: 'Sponsors', link: '/fr/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/fr/guide/privacy' }, |
| { text: 'समुदाय प्रोजेक्ट्स', link: '/hi/guide/community-projects' }, | ||
| { text: 'Repomix में योगदान', link: '/hi/guide/development/' }, | ||
| { text: 'प्रायोजक', link: '/hi/guide/sponsors' }, | ||
| { text: 'Privacy Policy', link: '/hi/guide/privacy' }, |
Deploying repomix with
|
| Latest commit: |
265a510
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://70137e7c.repomix.pages.dev |
| Branch Preview URL: | https://docs-privacy-policy.repomix.pages.dev |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #981 +/- ##
=======================================
Coverage 90.38% 90.38%
=======================================
Files 110 110
Lines 7890 7890
Branches 1528 1528
=======================================
Hits 7131 7131
Misses 759 759 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Code Review SummaryThank you for this PR! The addition of a dedicated Privacy Policy page addresses an important user need and significantly improves the discoverability of privacy information. The implementation is clean and follows the existing website structure well. ✅ Strengths
🔧 Suggestions for Improvement1. **Localization Consistency**I've left inline comments on the configuration files - the "Privacy Policy" link text should be translated to match each language's navigation. This maintains consistency with the localized user experience. 2. **Consider Adding Metadata**Consider adding page metadata (title, description) to the English privacy.md file for better SEO: ---
title: Privacy Policy
description: Learn about Repomix's privacy practices for the CLI tool, website, and browser extension
---3. **Future Enhancement: Privacy Page Translations**While using 🔍 Premortem AnalysisPotential Failure Scenarios
✅ Test CoverageThe PR checklist confirms:
🎯 Overall AssessmentThis is a well-executed improvement that directly addresses user feedback. With the minor localization adjustments suggested above, this PR will provide excellent value to users who need quick access to privacy information. Great work on implementing this user-requested feature! 🚀 |
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (5)
website/client/.vitepress/config/configDe.ts (1)
51-57: Link path is correct; consider localizing labelThe new sidebar item correctly links to
/de/guide/privacyand fits the existing structure. You may optionally want to localize the label (e.g., “Datenschutzerklärung”) for consistency with the rest of the German UI.website/client/.vitepress/config/configHi.ts (1)
51-57: Route is consistent; optional Hindi translation for labelThe
/hi/guide/privacylink is consistent with the rest of the Hindi guide routes. If you’d like full localization in the sidebar, you could translate the label (e.g., a Hindi equivalent of “Privacy Policy”) while keeping the slug as is.website/client/.vitepress/config/configId.ts (1)
54-60: Correct Indonesian route; label can optionally be localizedThe new entry correctly targets
/id/guide/privacyand is aligned with the existing sidebar structure. Consider localizing “Privacy Policy” into Indonesian for consistency with the rest of the “Komunitas” section if you prefer fully localized nav text.website/client/.vitepress/config/configZhCn.ts (1)
48-54: Route is correct; consider Chinese label for consistencyThe
/zh-cn/guide/privacylink integrates properly under the 社区 section. If you prefer full localization, you might rename the text to a Chinese equivalent (e.g., “隐私政策”) while keeping the same path.website/client/src/en/guide/privacy.md (1)
1-25: Add contact information and regulatory compliance details.The privacy policy is clear and well-structured, but is missing some standard elements that strengthen user trust and legal compliance:
- No contact method for privacy inquiries – users may have questions or requests (e.g., data deletion under GDPR/CCPA)
- No mention of regulatory compliance – frameworks like GDPR (EU users), CCPA (California), or other applicable laws
- Liability disclaimer is minimal – consider expanding to clarify responsibility boundaries for data misuse or breaches
Consider adding a footer section with contact information (e.g., privacy inquiry email) and a brief statement on compliance with applicable privacy regulations.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (25)
README.md(1 hunks)website/client/.vitepress/config/configDe.ts(1 hunks)website/client/.vitepress/config/configEnUs.ts(1 hunks)website/client/.vitepress/config/configEs.ts(1 hunks)website/client/.vitepress/config/configFr.ts(1 hunks)website/client/.vitepress/config/configHi.ts(1 hunks)website/client/.vitepress/config/configId.ts(1 hunks)website/client/.vitepress/config/configJa.ts(1 hunks)website/client/.vitepress/config/configKo.ts(1 hunks)website/client/.vitepress/config/configPtBr.ts(1 hunks)website/client/.vitepress/config/configVi.ts(1 hunks)website/client/.vitepress/config/configZhCn.ts(1 hunks)website/client/.vitepress/config/configZhTw.ts(1 hunks)website/client/src/de/guide/privacy.md(1 hunks)website/client/src/en/guide/privacy.md(1 hunks)website/client/src/es/guide/privacy.md(1 hunks)website/client/src/fr/guide/privacy.md(1 hunks)website/client/src/hi/guide/privacy.md(1 hunks)website/client/src/id/guide/privacy.md(1 hunks)website/client/src/ja/guide/privacy.md(1 hunks)website/client/src/ko/guide/privacy.md(1 hunks)website/client/src/pt-br/guide/privacy.md(1 hunks)website/client/src/vi/guide/privacy.md(1 hunks)website/client/src/zh-cn/guide/privacy.md(1 hunks)website/client/src/zh-tw/guide/privacy.md(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (15)
- GitHub Check: Test (macos-latest, 24.x)
- GitHub Check: Test (windows-latest, 20.x)
- GitHub Check: Test (ubuntu-latest, 25.x)
- GitHub Check: Test (windows-latest, 25.x)
- GitHub Check: Test (windows-latest, 24.x)
- GitHub Check: Test (windows-latest, 22.x)
- GitHub Check: Build and run (ubuntu-latest, 24.x)
- GitHub Check: Lint Browser Extension
- GitHub Check: Lint GitHub Actions
- GitHub Check: Lint Secretlint
- GitHub Check: Build and run with Bun (windows-latest, latest)
- GitHub Check: Test with Bun (windows-latest, latest)
- GitHub Check: Update configuration json schema
- GitHub Check: claude-review
- GitHub Check: Cloudflare Pages
🔇 Additional comments (13)
website/client/src/ja/guide/privacy.md (1)
1-1: Include path and reuse look correctThe include directive correctly points to the English source privacy page and keeps content centralized; this is a clean, low-maintenance setup.
website/client/.vitepress/config/configEnUs.ts (1)
51-57: Canonical privacy nav entry looks goodThe “Privacy Policy” item under Community correctly links to
/guide/privacyand matches the existing English navigation patterns.website/client/src/zh-tw/guide/privacy.md (1)
1-1: Shared English source include is correctly wiredThe include directive cleanly reuses the English privacy content, keeping the Traditional Chinese page in sync without duplication.
website/client/src/fr/guide/privacy.md (1)
1-1: Centralized privacy content via include is fine hereThe French page correctly includes the English privacy source, avoiding content drift and keeping maintenance simple.
website/client/src/es/guide/privacy.md (1)
1-1: LGTM! Clean content reuse approach.The VitePress include directive correctly references the English privacy content, enabling consistent privacy information across locales.
website/client/src/de/guide/privacy.md (1)
1-1: LGTM! Consistent with other locale implementations.The include directive correctly references the centralized English privacy content.
website/client/src/pt-br/guide/privacy.md (1)
1-1: LGTM! Follows the established pattern.The include directive correctly reuses the English privacy documentation.
website/client/src/ko/guide/privacy.md (1)
1-1: LGTM! Consistent implementation.The include directive correctly references the centralized English privacy content.
README.md (1)
1652-1652: LGTM! Privacy policy successfully centralized.The change effectively consolidates detailed privacy information into a single, discoverable location on the website. This addresses the user feedback mentioned in the PR objectives about privacy documentation being hard to find.
website/client/src/zh-cn/guide/privacy.md (1)
1-1: English privacy guide exists with complete content.The verification confirms that
website/client/src/en/guide/privacy.mdexists and contains a well-structured privacy policy covering the CLI tool, website, and browser extension. The include directive in the Chinese localized version will function correctly.website/client/src/en/guide/privacy.md (3)
12-15: Verify the file deletion claim and expand website privacy details.The statement that uploaded files are "automatically deleted immediately after processing" is a strong claim that directly affects user trust. Additionally, the website privacy section lacks important details:
- Data retention policy for Google Analytics
- Clarification on whether files are truly deleted with zero delay (or if there's any temporary storage, backups, or logging)
- Other tracking mechanisms (cookies, pixels, etc.)
- Data sharing policies with third parties
Please verify:
- What is the exact backend behavior for uploaded file cleanup (timing, logging, backups)?
- Are there other tracking methods besides Google Analytics (cookies, session tracking, etc.)?
- What is the data retention policy for analytics data?
Once verified, consider expanding this section to include these details for full transparency.
3-10: CLI tool privacy section looks good.Clear, concise, and accurate. The offline-first design and transparent list of when internet is needed build confidence.
17-20: Browser extension privacy section is well-documented.Clearly states minimal data collection and permissions model. Good transparency.
Add a dedicated Privacy Policy page to the website, addressing user feedback about privacy information being hard to find on repomix.com.
Changes
@includedirectiveBackground
Discord user feedback indicated that privacy documentation was not easily discoverable on the website. Users who need to verify data handling for their work environment had to dig into the README to find this information.
Checklist
npm run testnpm run lint