Privacy & safety

Local by design. Careful by default.

No account, no cloud service, no telemetry. Here is what PULSE does on its own, what it asks you about first, and what it will not touch.

Your data stays on this PC: Settings, buttons and history live in %APPDATA%\PULSE. Nothing is uploaded.
Online only for updates: PULSE checks GitHub for new versions. OBS connects only if you set it up.
No account, no telemetry: Nothing to sign up for, and nothing about how you use it is collected.

What PULSE does on its own, what it asks first, and what it never touches.

You decide

Runs only what you set up

Buttons and workflows run only the actions you configured.
Every step uses one allowlisted engine. There is no shell or script action.
Typing text into another app needs an explicit consent checkbox, and the text is never logged.

Asks first

You confirm before it happens

Terminating a process: a preview, an impact warning, then your confirmation.
Close Browser, and stopping an OBS stream or recording.
Smart Cleanup and End Streaming Setup show their plan before anything closes.

Never touched

Refused, whatever you click

Windows kernel processes
Essential Windows components
Anything in the Windows folder
Security software
Services and other users’ processes
PULSE itself
Processes it can’t verify
Your protected list

How closing an app works

You choose an app From the System Monitor, a workflow step or Smart Cleanup.
Protected? If so, PULSE refuses and tells you why.
Close windows A normal close request, like clicking ✕. Apps with unsaved work can ask you to save.
Still running? Terminate… shows name, PID, location, memory, windows and child processes, then asks.
Identity re-checked PID, creation time and path are verified again right before termination.

Details

The fine print, answered.

Where your data lives, what goes over the network, and which rights PULSE runs with.

What is stored, and where?

Settings, buttons, workflows, layouts, history, backups and logs live in %APPDATA%\PULSE. No passwords, cookies or tokens are stored, and the OBS password is held in memory only. Updates upgrade that data in place (they only add, never remove), and uninstalling leaves the folder where it is.

What goes over the network?

An installed release checks the public release page for updates and, when a newer version exists, downloads it and verifies its SHA-512 checksum before installing. OBS control connects only to the host you configure. Nothing else is sent, and no usage data is collected.

What permissions does PULSE run with?

Standard user rights. The installer and the app never ask to run as administrator, so PULSE also cannot close, focus or send keys to apps that run elevated; those actions fail with an explanation.

Does PULSE run in the background?

There is no background polling while PULSE is hidden. System statistics pause while it is minimized or in the tray, and process sampling runs only while the System Monitor page is open.

Does PULSE read my browser data?

Only Chrome’s profile list: each profile’s name, folder id and local picture, so you can open the right ones. Never emails, history, cookies, tokens or passwords, and PULSE never writes anything into Chrome.

How do I remove PULSE and everything it stored?

Uninstall it from Windows Settings → Apps. Your settings, buttons and history stay in %APPDATA%\PULSE on purpose, so a reinstall picks up where you left off; delete that folder to remove them too.

Describes PULSE 1.3 as implemented.