Privacy

Pulse is a free, open-source project by Irfan Shaik. This page explains what a shared Pulse server keeps and why. If you run Pulse on your own machine, nothing leaves it except calls to the platforms you connect.

What is stored

• Your account: name, email and a salted scrypt hash of your password. Never the password itself.
• Your workspace: the demo sandboxes, your guardrail settings, proposals and change log.
• Data you connect: credentials you enter (encrypted with AES-256-GCM, with a key unique to your account) and the last 90 days of numbers Pulse syncs from those sources.
• Usage counts: when you were last active and how many questions, proposals, approvals and syncs you made, so the person running the server can see the tool is used. Not the contents of your questions.

What isn't

• No ads, no tracking scripts, no analytics cookies. Two cookies only: your sign-in session, and a sandbox id if you use the open demo.
• Nothing is sold or shared. Your data is only sent to the platform it belongs to (for example Google or Meta), and, if AI answers are switched on, the numbers in your question go to the AI model to answer it.

Changes to your ad accounts

Pulse only changes an ad account after a person approves a specific proposal, and only if writes are switched on for that account. Every change is logged with its previous value and can be undone.

Deleting your data

On the Sources page, "Forget" removes a source's credentials and synced data at once. To delete your whole account, ask the person who runs the server; they can switch it off and remove it.

The code that does all of this is open for anyone to read.