PulsorbBack to Pulsorb

Privacy policy

Last updated 20 October 2026

This policy covers our two apps: Pulsorb, the music visualizer, and Pulsorb Conductor, an app for working with AI agents. Pulsorb runs on your PC and doesn’t track you. It has no analytics, no ads and no account. It downloads album art from Spotify’s image servers and checks GitHub for updates. If you play SoundCloud or YouTube links, their own players run inside Pulsorb; if you redeem a Pro gift code, Pulsorb checks it with pulsorb.app. That’s all it sends. Pulsorb Conductor doesn’t track you either: it has no analytics, no ads and no account, and keeps your chats and settings on your PC. What you and its agents work on goes straight from your PC to the AI provider you choose, never to us. Apart from that and checking GitHub for updates, it connects only to services you and its agents use. This website sets no cookies; it counts visits and download clicks only as totals, and loads its fonts from Google.

The visualizer: what stays on your PC

To draw the visuals, Pulsorb listens to the sound your PC is playing. That sound is analysed in memory as it plays and is never recorded, saved or sent anywhere.

To show what’s playing, Pulsorb reads the song title, artist, album, cover art and playback position from Windows’ media controls, and from Spotify if you turn on the Spicetify integration. This stays on your PC. For sharper cover art it downloads the album image from Spotify’s public image servers, asking only for that image.

In wallpaper mode, Pulsorb reads your current desktop picture from your PC so the visualizer can fade in from it and back. It isn’t copied or sent anywhere.

Your settings, and a short log used to troubleshoot the Spotify connection, are stored in your Windows user folder (%APPDATA%\Pulsorb). Uninstalling Pulsorb leaves them in place so a reinstall keeps your settings; you can delete that folder at any time.

The Spicetify integration

If you turn it on, Pulsorb installs a small extension into the Spotify app. The extension talks only to Pulsorb on your own PC (address 127.0.0.1, protected with a secret key). It reads Spotify’s analysis of the current song, your playlists and Liked Songs when you browse them in Pulsorb, and plays the songs you choose. None of this leaves your PC through Pulsorb. Spotify’s own privacy policy covers what Spotify does.

Links (SoundCloud and YouTube)

If you add a SoundCloud or YouTube link, Pulsorb plays it with SoundCloud’s or YouTube’s own embedded player, inside Pulsorb. Like any embedded player, it connects to that service, which sees your IP address and what you play, and may set its own cookies; those stay in Pulsorb’s player, apart from your web browser. To show your links’ titles, songs and pictures, Pulsorb asks SoundCloud and YouTube for them. Your list of links is saved with your settings on your PC. SoundCloud’s and YouTube’s (Google’s) privacy policies cover what those services do.

Pulsorb Pro (the visualizer)

Pro isn’t on sale yet, so Pulsorb doesn’t handle payments or licences. Before it goes on sale, this policy will be updated to say what’s involved.

Gift codes. If you redeem a Pro gift code, Pulsorb sends the code and a fingerprint of your PC to pulsorb.app. The fingerprint is a one-way scramble (a hash) of an ID Windows gives your PC: it can’t be turned back into that ID and says nothing about you; it only lets a code work on one PC at a time. pulsorb.app stores a fingerprint of the code (never the code itself), your PC’s fingerprint and when the code was redeemed or moved. While the gift is on your PC, Pulsorb checks it with pulsorb.app about every 12 hours, sending the signed pass it was given for your PC. To stop anyone guessing codes, pulsorb.app counts redeem attempts per IP address, kept only as a scrambled value for about two hours. The service runs on Cloudflare, which may keep standard logs (such as IP address and time) for security. To have your gift’s record deleted, email us.

Pulsorb Conductor: what stays on your PC

Pulsorb Conductor keeps what it saves on your PC, in your Windows user folder (%USERPROFILE%\.pulsorb\conductor): your settings and AI providers, your chats, the file snapshots that let you undo an agent’s changes, what agents remember, the Orb’s notes, schedules and activity, your plan and licence key, and its logs. It also keeps its window position and a few display preferences in %APPDATA%\Pulsorb Conductor. Uninstalling Conductor leaves these folders in place; you can delete them at any time.

API keys and tokens you paste into Conductor’s settings (for AI providers, search services, MCP servers or the Orb’s channels) are saved without encryption in that folder, in config.json and, for the Orb’s channels, orb\config.json, so programs and people with access to your Windows account could read them. For an AI provider, you can instead give Conductor its key through an environment variable or a command that prints it, and search services can take their keys from environment variables too.

Pulsorb Conductor and your AI providers

Conductor works with the AI providers you choose, using your own accounts and keys. When you chat or an agent works, Conductor sends what the AI model needs straight from your PC to that provider: your messages, the files and web pages the agent reads, the output of commands it runs, screenshots when it looks at your browser or screen, and your clipboard or another app’s window text when it reads them. If you choose an agent CLI such as Claude Code or Codex, Conductor runs it on your PC and the CLI sends this to its own service. With a model that runs on your PC, such as one in Ollama or LM Studio, it stays on your PC. Pulsorb has no server in between and never receives any of it. Each provider’s own terms and privacy policy cover what it does with what it receives, so check them before letting agents work with personal or confidential information.

Pulsorb Conductor’s other connections

Apart from your AI providers and update checks, Conductor connects to the internet only for features you or its agents use:

Pulsorb Conductor Pro

The first time Conductor runs under your Windows account, it starts a 14-day Pro trial, recorded in your Conductor folder. Pro isn’t on sale yet, so Conductor doesn’t handle payments. If we give you a licence key, it’s checked on your PC and kept in your Conductor folder; it can carry the name or email address it was issued to. No licence information leaves your PC. Before Pro goes on sale, this policy will be updated to say what’s involved, including which payment provider handles checkout and what it collects.

Once paid Pro is on sale, a bought licence key will be activated and checked online with that payment provider, about once a day: Conductor will send the key and this install’s activation id (a random id given when the key is activated), and the provider will see your IP address, as for any connection. It won’t send your PC’s name, your files or anything about what you do in Conductor.

Pulsorb Conductor’s logs and diagnostics

Conductor keeps logs on your PC, in the logs folder inside its own folder: app.log, which masks API keys and tokens in the formats Conductor recognises, and the output of local servers it starts for you, kept as those servers print it. Copy diagnostics in Settings › About copies a report to your clipboard: Conductor’s version, your Windows version, how much memory your PC has, your plan, where Conductor’s folder is (a path that includes your Windows user name), your default AI provider, model and permission mode, the AI providers (with their web addresses) and MCP servers you’ve set up, without their keys, and recent lines of app.log. Nothing is sent automatically: it’s up to you whether to paste it into a message to us.

Downloads and updates

Both apps’ installers are published on GitHub. The download buttons on this website go through a short link on pulsorb.app (such as pulsorb.app/get/conductor), which counts the click and sends you on to GitHub, where the installer downloads; GitHub sees your IP address, as for any download. The count is a daily total for each app, kept with the tag in the link (such as site, or the name of an ad campaign) and the name of the website the click came from, such as tiktok.com, without the rest of its address. It doesn’t store your IP address, browser details or any cookie, so a count can’t be tied to you. The web host may also keep standard server logs (such as IP address and time) for security.

Pulsorb and Pulsorb Conductor check GitHub for new versions every few hours and download them from there; GitHub sees your IP address, as for any download.

This website

pulsorb.app counts its visits with Cloudflare Web Analytics, which uses no cookies and doesn’t identify or follow you: it records page views, how fast pages load, and which country and website a visit came from, as totals. It counts download clicks as described above. The Pulsorb app itself has no analytics, and neither does Pulsorb Conductor.

The website’s fonts come from Google Fonts, so when you open a page your browser asks Google’s servers (fonts.googleapis.com and fonts.gstatic.com) for them, sending your IP address and your browser’s user agent (which browser and operating system you use), as for any web request. pulsorb.app sets no cookies of its own. Google’s privacy policy covers what Google does with these requests.

Children

Pulsorb and Pulsorb Conductor aren’t directed at children under 13, and we don’t knowingly collect information from them.

Your rights and contact

You can ask what we hold about you, or ask us to delete it, by emailing support@pulsorb.app. We never receive what you do in Conductor, so for what an AI provider or other service holds, ask that provider.

Changes

If this policy changes, the new version will appear on this page with a new date.