diff --git a/website_and_docs/content/blog/2025/selenium-privacy-policy.md b/website_and_docs/content/blog/2025/selenium-privacy-policy.md
new file mode 100644
index 000000000000..bec32b1c66db
--- /dev/null
+++ b/website_and_docs/content/blog/2025/selenium-privacy-policy.md
@@ -0,0 +1,79 @@
+---
+title: "Selenium Privacy Policy"
+linkTitle: "Selenium Privacy Policy"
+date: 2025-02-19
+tags: [ "selenium", "manager", "privacy", "telemetry" ]
+categories: [ "Privacy" ]
+author: Titus Fortner [@titusfortner](https://titusfortner.com)
+description: >
+ Selenium has introduced a Privacy Policy to clarify our data collection practices, why telemetry exists, and how we ensure compliance with GDPR and CCPA.
+---
+
+Selenium has always been committed to open-source transparency and user privacy, but we recognize that
+we could have done a better job communicating the details of Selenium Manager's telemetry collection.
+
+To address this, we have published a comprehensive [Privacy Policy](/privacy) that
+clearly explains:
+* What data is collected (and what isn’t)
+* How we ensure compliance with GDPR and CCPA
+* Why Selenium Manager includes opt-out telemetry
+* How users can easily disable telemetry
+
+The bottom line is that Selenium Manager collects only anonymous technical information to help us improve Selenium.
+
+Additionally, starting in Selenium 4.30, Selenium Manager displays a one-time console message the first time
+telemetry is sent. This obviously and proactively informs users about telemetry, their right to opt out,
+and provides a direct link to the Privacy Policy.
+
+**Quick Recap of what Selenium Manager collects:**
+
+✔ Selenium version (to ensure compatibility across versions)
+✔ Programming language (Java, Python, JavaScript, .NET)
+✔ Operating system and CPU architecture (to prioritize OS support)
+✔ Browser and version (to understand browser usage trends)
+✔ Approximate geolocation (city-level), temporarily inferred from the IP (IP is discarded after processing)
+
+❌ No usernames, emails, or personal identifiers
+❌ No browser history or test execution data
+❌ No full IP addresses (only used temporarily for location inference, then discarded)
+❌ No cookies or persistent tracking
+
+See everything for yourself: [Selenium Manager Public Analytics](https://plausible.io/manager.selenium.dev)
+
+
+## Opting Out of Telemetry
+
+Like many other open-source projects, we use opt-out telemetry to ensure we receive representative, anonymous data that
+helps improve Selenium. We understand that some people prefer opt-in telemetry,
+and we explain our reasoning in detail in the [Privacy Policy](https://www.selenium.dev/privacy/#opt-out)
+
+Regardless, it is quite easy to disable telemetry by either:
+
+1. Setting an environment variable
+
+```sh
+SE_AVOID_STATS=true
+```
+
+2. Using a configuration file
+
+```ini
+avoid-stats = true
+```
+
+Please see the [Selenium Manager documentation](https://www.selenium.dev/documentation/selenium_manager/) for further
+details on how to do this.
+
+## Insights
+
+**Interesting tidbits we’ve learned from having opt-out telemetry over the past year:**
+
+* Selenium gets over 1 million unique users a week
+* The number of unique users is growing at a rate of 10% per month
+* Over 80% of sessions are on Windows
+* Almost 90% of sessions use Chrome
+* Fewer than 1% of sessions are with Safari or Internet Explorer
+* A lot more sessions are with C# and Python than Java, and very few people are using Ruby and JavaScript
+
+Note 1: The data only represents users who have updated to Selenium 4.19 or greater
+Note 2: A unique user represents a unique session from a given IP address for that day
diff --git a/website_and_docs/content/privacy/_index.html b/website_and_docs/content/privacy/_index.html
new file mode 100644
index 000000000000..8b2072c919ef
--- /dev/null
+++ b/website_and_docs/content/privacy/_index.html
@@ -0,0 +1,238 @@
+---
+title: Privacy Policy
+linkTitle: privacy
+aliases:
+ [
+ "/pt-br/privacy/",
+ "/zh-cn/privacy/",
+ "/ja/privacy/",
+ "/other/privacy/",
+ ]
+---
+
+{{< blocks/section color="selenium-green" height="min" >}}
+
+ Selenium is committed to protecting user privacy and ensuring transparency in how we collect and use + data. + This policy explains what data we collect, why we collect it, and how users can control their privacy + preferences. +
++ The Selenium project collects anonymous data from visitors to our website + as well as usage data through Selenium + Manager. + Selenium uses Plausible Analytics + to manage this data due to its focus on privacy. +
++ Selenium uses Plausible's hosted solution to track information + about visitors to our website (selenium.dev). + The following information is collected: +
++ Plausible does not use cookies, does not track users across sites, and does not collect personal + information. +
++ All information we collect is publicly available on the + Selenium Website Plausible Dashboard +
++ This data helps us understand how users engage with the Selenium website to improve our + documentation and content. +
++ Selenium Manager, a tool for managing browser drivers, collects anonymous usage data to + help us understand which platforms and configurations need the most support. +
++ Data Collected: +
++ What is NOT collected: +
++ All information we collect is publicly available on the + Selenium Manager Plausible Dashboard +
++ Selenium Manager’s telemetry is designed to comply with GDPR and CCPA by collecting only anonymized, + non-personal data and providing users full control over their participation. + Below is a detailed breakdown of compliance with key GDPR provisions. +
+ ++ While some open-source projects use opt-in telemetry, Selenium requires a representative dataset to + accurately assess project usage and prioritize improvements. With multiple language implementations and + distribution methods, opt-in telemetry would not provide meaningful insights, particularly for + cross-language comparisons. +
++ Many well-known open-source projects, such as .NET CLI, Homebrew, Next.js, and GitLab, use opt-out + telemetry for similar reasons.
+Additionally, Selenium faces unique challenges in even providing an + opt-in mechanism — there is no universal way to prompt users across all language bindings and package + distribution methods. An unrepresentative dataset would prevent us from accurately assessing project + usage and making informed improvements. For Selenium, the real choice is not + between opt-in and opt-out, but between opt-out and no telemetry at all. +
++ If you prefer not to share anonymous usage data, you can disable telemetry, the detailed instructions + can be found in the Selenium Manager Documentation, + but broadly consists of + methods: +
+SE_AVOID_STATS=true
+
+ avoid-stats = true
+
+ + Once disabled, Selenium Manager will not send any telemetry data. +
++ If you have suggestions for how we can improve out implementations, please reach out to the Selenium + team: +
+ +