Privacy+ Settings CLI

Command-line interface for low-level OS privacy and configuration control.

Privacy+ Settings CLI

ame-settings-cli is the command-line interface from the Ameliorated ecosystem that gives you direct, surgical control over Windows privacy settings, system toggles, and registry-level configuration.

JarvisOS installs it automatically as part of the maintenance tools suite.

---

What It Does

The Privacy+ Settings CLI bypasses the Windows Settings UI entirely. Instead of toggling switches in a bloated interface that often doesn’t stick, it directly writes registry overrides and Group Policy nullifications — so when you turn something off, it stays off.

This tool is maintained by the Ameliorated team. JarvisOS bundles it as a convenience — it is not a JarvisOS-specific tool.

---

Basic Usage

ame-settings-cli [command] [target] --state [on|off]

Run as Administrator from an elevated terminal.

---

Common Toggles

Telemetry

Disable residual diagnostic tracking services and data harvesting endpoints.

ame-settings-cli set telemetry --state off

Note: JarvisOS already removes the primary telemetry stack. Use this for fine-tuned control of remaining optional components.

Defender

Toggle Windows Defender on or off. JarvisOS leaves Defender enabled by default for security. Disable only if you have a trusted alternative.

ame-settings-cli set defender --state off

SmartScreen

Disable SmartScreen filtering (sends application hashes to Microsoft).

ame-settings-cli set smartscreen --state off

Updates

Toggle Windows Update connectivity.

ame-settings-cli set updates --state off

Prefer managing updates via the AtlasOS Toolbox for a safer workflow.

---

Batch Configuration

For a full lockdown pass, create a JSON config file and apply all targets at once:

{
  "targets": {
    "telemetry": false,
    "smartscreen": false,
    "cortana": false,
    "advertising-id": false
  }
}

ame-settings-cli apply --config lockdown.json

---

Get Help

ame-settings-cli --help
ame-settings-cli [command] --help

Do not use services.msc or direct registry edits to override settings managed by this tool. Changes may conflict with each other. Use the CLI exclusively for toggling managed settings.