Debloat yourbrowser.
The signed macOS app configures Brave. The same policies, as scripts, cover Brave, Chrome, Edge and Firefox. No extension, no patch, nothing injected.
One license. Python standard library only, no dependencies.
Less browser.
More control.
54 policies. Review before applying.
It prints this list before it writes a thing.
The real policy names from the Brave Maximum Privacy preset, read out of the file the tool ships. You approve a list you have read, not a checkbox that says harden.
54 policies · Brave · Maximum Privacy preset
Slim shows each change before it writes. Expand to see the same list the app reviews.
It changes settings your browseralready lets an employer change.It just shows you them first.
Nothing hidden, nothing patched.
It shows the diff before it writes
Every policy it is about to set is printed first, by name. You approve a list you have actually read, rather than a checkbox that says harden.
It uses the browser's own mechanism
These are enterprise managed policies — the same system an IT department uses. No extension to install, no binary to patch, nothing injected into a running browser.
It undoes itself
The policies it wrote can be removed again. A tool that changes your browser and cannot change it back is not a tool you should run.
It has no dependencies
Python standard library only. Nothing is pulled from a package index at install time, which is one fewer place for something to go wrong.
Pick a preset, read it, apply it.
01
Choose a browser and a preset
Brave by default; Chrome, Edge and Firefox with a flag. Presets run from Developer, which touches least, to Maximum Privacy, which touches most.
02
Read what it will change
Every policy is named before anything is written, so you can decline the ones you disagree with.
03
Apply, and restart the browser
The policies take effect on the next launch, and the browser reports them itself on its own policy page.
What is actually in the presets.
Counted out of the preset files in the repository.
- macOS wizard
- Brave
- Scripts
- Brave, Chrome, Edge, Firefox
- Policies in Brave Maximum Privacy
- 54
- Runtime dependencies
- None
The things people ask.
Is this an extension?
No. It writes managed policy files, the mechanism browsers already provide for organisations. Nothing is added to the browser and nothing runs alongside it.
Can I undo it?
Yes. The policies it wrote can be removed again, and the browser returns to its own defaults on the next launch.
Will it break sign-in or sync?
The stricter presets deliberately turn off features some people rely on, which is why every policy is printed before it is applied. Balanced Privacy is the one to start with.
Which browsers?
The macOS wizard detects and configures Brave. The scripts, which is how Slim exists on Windows and Linux, cover Brave, Chrome, Edge and Firefox.
Does it work on Linux and Windows?
Yes. The scripts run on Linux, macOS and Windows. The only published binary is the signed macOS wizard; on Windows and Linux you run the scripts from source. The project's SECURITY.md draws that line deliberately — no Windows or Linux installer will be published.
Why Python with no dependencies?
Because a tool that hardens your browser should not ask you to trust a chain of packages to do it. Standard library only means the code you read is the code that runs.
Read the changes.Then make them.
The macOS wizard is signed and notarised. Everywhere else it runs from source. Needs a Spiral Collection license key.