Open-Source Security · undergroundwires

privacy.sexy

privacy.sexy is an open-source desktop and web application that automates privacy and security hardening on Windows, macOS, and Linux through curated, reversible scripts. Users select tweaks from a transparent interface, preview changes, and execute them locally or via a web version without installing software.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/undergroundwires/privacy.sexy

5.7k

GitHub stars

268

Forks

TypeScript

Primary language

AGPL-3.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	undergroundwires/privacy.sexy
Owner	undergroundwires
Primary language	TypeScript
License	AGPL-3.0 — OSI-approved
Stars	5.7k
Forks	268
Open issues	249
Latest release	0.13.8 (2025-03-13)
Last updated	2026-02-13
Source	https://github.com/undergroundwires/privacy.sexy

What privacy.sexy is

TypeScript-based tool generating platform-specific scripts (PowerShell, Bash, AppleScript) with a custom templating language for script composition. Includes unit, integration, and E2E testing; SAST and dependency security checks; and supports both online (web) and offline (Electron desktop) deployment models.

Quickstart

Get the privacy.sexy source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/undergroundwires/privacy.sexy.git2cd privacy.sexy3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Individual privacy hardening workflows

End users seeking granular control over OS telemetry, service disabling, and security tweaks. Ideal for privacy-conscious individuals who want transparency and reversibility without manual registry/config editing.

IT security baseline enforcement

Organizations needing to distribute repeatable, auditable security configurations across Windows/macOS/Linux fleets. The reversible nature and script transparency support compliance auditing and staged rollbacks.

Security research and education

Researchers, trainers, and students studying OS hardening practices. The open-source scripts and templating language serve as learning materials for understanding platform-specific security configurations.

Implementation considerations

AGPL-3.0 licensing: if modifying or extending the tool for distribution, derivative works must also be AGPL-3.0 licensed. Internal-only use does not trigger this obligation.
Script execution risk: thoroughly test scripts in non-production environments first, especially on critical systems. The reversible nature is a mitigating factor but not a guarantee of zero impact.
Platform parity: feature and script coverage may vary across Windows, macOS, and Linux. Test the specific platform-OS version combinations in your environment.
Maintenance cadence: last commit 2026-02-13; actively maintained. Monitor releases for OS update compatibility, especially after major Windows/macOS/Linux versions.

When to avoid it — and what to weigh

Proprietary environment with closed-source requirements — AGPL-3.0 licensing requires source code disclosure for derivative works distributed to end users. Enterprise closed-source deployments require commercial licensing negotiation.
Need for vendor support SLA — Project is community-driven with no formal SLA, vendor support, or guaranteed response times. Organizations requiring contractual support obligations should evaluate alternatives.
Systems requiring zero script execution risk — Tool is inherently designed to modify OS configurations at scale. Environments requiring immutable infrastructure or no local script execution should consider infrastructure-as-code approaches instead.
Complex multi-tenant SaaS deployment — Primary design is single-user or organizational fleet deployment. Multi-tenant SaaS usage patterns would require significant architectural rework.

License & commercial use

AGPL-3.0 (GNU Affero General Public License v3.0). Copyleft license requiring source code disclosure for derivative works distributed to end users. Internal use and unmodified use are unrestricted.

Unrestricted use of the unmodified tool for commercial purposes (as an end user running scripts). If you create a modified or derivative version and distribute it to others (e.g., embedded in a product), you must release source code under AGPL-3.0 or negotiate a separate commercial license. Consult legal counsel for proprietary integrations.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	High

Security considerations

Project includes SAST and dependency security checks in CI/CD and claims security as a top priority (SECURITY.md). Scripts execute with user/admin privileges locally; audit script contents before execution in sensitive environments. No independent third-party security audit or attestation mentioned. Web version eliminates local software risk but depends on browser security and HTTPS. Desktop version requires Electron runtime; evaluate Electron security posture for your deployment model.

Alternatives to consider

O&O ShutUp++ (Windows only)

Closed-source commercial tool with similar Windows privacy/security tweaks. Offers vendor support and pre-tested configurations but lacks transparency and Linux/macOS support.

WPD (W10Privacy-inspired) or similar security hardening scripts

Command-line or batch-based alternatives for OS hardening. Typically less comprehensive, no reversibility guarantees, and no unified UI, but simpler to audit and modify.

Ansible/Terraform + official hardening playbooks

Infrastructure-as-code approach for larger fleet deployments. Better suited for immutable infrastructure and GitOps workflows but higher operational overhead and steeper learning curve.

Software development agency

Build on privacy.sexy with DEV.co software developers

Test the web version at privacy.sexy or download the desktop installer. Review CONTRIBUTING.md and SECURITY.md for extensibility and security practices. If you require commercial licensing or SLA support, contact the maintainer.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Slack libreddit keyshade

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Security Custom Software Development DevOps & Automation Talk to DEV.co

privacy.sexy FAQ

Can I use privacy.sexy in my commercial product without releasing source code?

Not without a separate commercial license. AGPL-3.0 requires you to release source code if you distribute a modified version. Unmodified use of the tool as-is is unrestricted. Contact the maintainer for commercial licensing terms.

What if a script breaks my system? Can I undo it?

Scripts are designed to be reversible, and privacy.sexy provides a revert feature. However, not all OS changes are guaranteed reversible. Always test in non-production first and maintain backups. The tool itself is not responsible for system damage.

Is the web version as feature-complete as the desktop version?

No. See docs/desktop/desktop-vs-web-features.md for a feature comparison. The desktop version offers offline execution and potentially more advanced options; the web version requires internet and a browser but needs no installation.

How do I extend or customize scripts for my organization?

Use the custom templating language documented in docs/templating.md and extend scripts as described in CONTRIBUTING.md. You will need to fork, modify, build, and distribute the modified application or extract and distribute scripts separately.

Software development & web development with DEV.co

From first prototype to production, DEV.co delivers software development services around tools like privacy.sexy. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source security and beyond.

Evaluate privacy.sexy for your security workflow

Talk to DEV.co Schedule a Consultation