feat: update privacy policy with targeted advertising disclosures #6451
Conversation
- Updated Last Updated date to January 30, 2025 - Added cookie/advertising disclosure to Quick Summary - Added Marketing & Advertising Data row to information collection table - Added new Section 6 for Targeted Advertising, Sale/Share, and Opt-Out - Renumbered existing sections 6-8 to 7-9 - Added opt-out option to Section 5 (Your Choices) - Added new Section 10 for State-Specific Privacy Rights - Complies with CPRA, CO CPA, CT DPA, VA CDPA, TX Privacy Act requirements
dosubot
bot
added
size:M
|
🚀 Preview deployed! Your changes have been deployed to Vercel: Preview URL: https://roo-code-website-9fnnmoeet-roo-code.vercel.app This preview will be updated automatically when you push new commits to this PR. |
![roomote[bot]](https://avatars.githubusercontent.com/in/1546624?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thank you for this comprehensive privacy policy update! I've reviewed the changes and found several issues that need attention before this can be merged. The legal compliance additions look thorough, but there are some inconsistencies and implementation gaps that should be addressed.
| Roo Code Cloud Privacy Policy | ||
| </h1> | ||
| <p className="text-muted-foreground">Last Updated: June 19, 2025</p> | ||
| <p className="text-muted-foreground">Last Updated: January 30, 2025</p> |
There was a problem hiding this comment.
Is this date intentional? January 30, 2025 appears to be a future date. Should this be January 30, 2024 or today's date instead?
| <ul> | ||
| <li> | ||
| <strong> | ||
| “Do Not Sell or Share My Personal Information / Opt Out of Targeted |
There was a problem hiding this comment.
The policy references footer links that don't exist yet. While the PR description mentions these as "Next Steps," the policy text implies they're already available ("Every page now displays"). Should we update the language to indicate these are coming soon, or implement the links first?
| </h2> | ||
| <p> | ||
| We use Google Ads, Meta (Facebook) Pixel and LinkedIn Insight Tag to show ads to visitors who | ||
| have previously interacted with Roo Code (“retargeting” or “cross‑context |
There was a problem hiding this comment.
For consistency, could we standardize the terminology? The policy uses both "interest‑based advertising" (line 68) and "cross‑context behavioral advertising" (line 270). Would it be clearer to pick one primary term?
This PR updates the Roo Code Cloud privacy policy to comply with 2025 state privacy law requirements for targeted advertising and retargeting disclosures.
Changes Made
1. Updated Last Updated Date
2. Enhanced Quick Summary
3. Expanded Information Collection Table
4. New Section 6: Targeted Advertising
5. Updated Section 5: Your Choices
6. New Section 10: State-Specific Privacy Rights
7. Section Renumbering
Compliance
This update ensures compliance with:
Testing
Next Steps
Per the instructions, the following UI/footer tasks will need to be implemented separately:
Important
Updates privacy policy in
page.tsxto include targeted advertising disclosures and comply with 2025 state privacy laws.page.tsx.This description was created by
for 8ccba32. You can customize this summary. It will automatically update as commits are pushed.