Privacy Policy
Last updated November 14, 2026
- Your library, listening history and settings stay on your PC.
- An account is optional. If you make one, it's stored on Pulse's server, which runs on Cloudflare: your username, email, profile text, the playlists you make public, and a hash of your password, never the password itself.
- The app has no ads, tracking or analytics. The website counts visits with Cloudflare Web Analytics, which uses no cookies and doesn't identify you. We never sell or share your information.
- Delete your account any time and it's gone right away.
Pulse is a free, open-source, non-commercial music player made by one developer. "We" below means the Pulse project. All of Pulse's code, including the accounts server, is public on GitHub, so you can check everything this page says. The rules for using Pulse and accounts are in the Terms of Service.
The Pulse app
Everything the app keeps is on your PC, in %APPDATA%\pulse-player: your likes, playlists, recently played songs, profile, settings, themes, backups, downloaded songs and caches. None of it is uploaded. Uninstalling keeps the folder; delete it to remove everything.
To play music, the app talks to these services. Each one sees your IP address, like any website you visit, and what's asked of it:
- Deezer: song, album and artist info, covers and charts (what you search for and open).
- YouTube, through yt-dlp: finding and streaming each song you play.
- iTunes: covers Deezer doesn't have.
- LRCLIB: lyrics for the song you're playing.
- Google: search suggestions as you type.
- GitHub: checking for and downloading updates and playback tools.
- Pulse's own server (on Cloudflare): fixes for songs the catalog gets wrong (it's sent the song's ID), the list of early supporters, and your account if you have one.
- Discord, only if you turn on Discord status: the app talks to the Discord app on your PC (or Legcord or Vesktop), which shows the song on your profile.
These services have their own privacy policies. Pulse sends them nothing about you beyond what each request needs, and no account details.
Pulse accounts
Accounts are optional and only needed to make playlists public and have a profile. If you make one, our server keeps:
- Your username. Public: it's on your profile and your shared playlists.
- Your email address. Private: only used to send you a code if you forget your password. Never shown to anyone, never used for anything else, no newsletters.
- A hash of your password (salted PBKDF2), never the password itself.
- Your profile picture, if you set one while signed in: a small square copy (256×256), shown on your public profile. Public by design. Remove it from your profile in the app and it's deleted from the server.
- Your profile text and the playlists you make public: their names and songs (title, artist, album and cover links). Public by design. Songs from your own computer are never uploaded.
- Sign-in keys: only a hash of each one, which expires after 90 days or when you sign out.
- When you joined, and whether you're one of the early supporters (the first 100 accounts), which shows a badge on your profile and your username in the app's thank-you list.
Problem reports from the app
If you use Report a problem (or send a report after a crash), the app sends what you wrote and, if you leave it ticked, a diagnostics report: Pulse's version, your Windows version and graphics card, a few settings, how much space Pulse uses, and recent errors, with your Windows user name and any email addresses removed. It goes to a private list on GitHub that only the developer can see, and nothing is sent unless you press Send.
Keeping it safe from abuse
- To limit sign-up spam and password guessing, the server notes the IP address of sign-ups, failed sign-ins, password-reset requests and reports. These notes are deleted after a day.
- When someone reports a public playlist, the server keeps the report's reason and a one-way hash of who reported it, never their IP address itself.
Password reset emails
If you ask for a reset code, we email it to the address on your account through EmailJS, sent from Pulse's Gmail account. The email says roughly where and when the request came from (city, IP address and time, as Cloudflare sees it) so you can tell if it wasn't you. That information is only put in the email, not stored. The code itself is stored only as a hash and stops working after 15 minutes.
Where it's stored
The accounts server runs on Cloudflare (Workers and its D1 database). Cloudflare handles the traffic and may keep its own short-term logs, as described in its privacy policy.
Deleting your account
In the app (Settings → Account) or on the website (Your account), you can delete your account. That removes your account, email, profile, profile picture, sign-ins, reset codes and every playlist you made public, right away. You can also change your email or password, edit your profile and make playlists private there at any time.
This website
- The site is hosted on GitHub Pages. GitHub may log visits, as described in its privacy statement. We have no access to GitHub's visitor logs.
- We count visits with Cloudflare Web Analytics. It sets no cookies, keeps nothing in your browser and doesn't follow you to other sites. It tells us totals like which pages are visited, which site sent you there, your country, and your browser and device type. We can't see who you are. A content blocker can stop it, and the site works the same either way.
- The site keeps a few things in your browser (local storage), never sent anywhere except as noted: your light or dark theme, whether you've seen the intro, your @username for "Welcome back", and, if you sign in on the site, your sign-in key (sent only to the accounts server). Signing out removes the key; clearing your browser's site data removes everything.
- The download button asks GitHub for the newest version.
- Public playlist and profile pages load from the accounts server.
- "Ask about Pulse" answers from a list built into the page; nothing you type is sent while it searches. If you choose to send a question or problem report, a question is posted as a public issue on Pulse's GitHub, and a problem report goes to a private list only the developer sees, after a Cloudflare Turnstile check that you're not a bot. Don't include personal information in it.
Children
Pulse accounts are for people 13 and older. When you make an account, Pulse asks for your birthday only to check this: it isn't saved, in the app or on the server. If you're under 13, please use Pulse without an account. If you believe a child under 13 has made an account, contact us and we'll delete it.
Your choices and rights
You can use Pulse fully without an account. With one, you can see and change everything we keep about you in your account settings, and delete it all at any time. If you want a copy of what's stored or have any other request, contact us and we'll help.
Changes
If this policy changes, the new version will be posted here with a new date. Big changes will also be mentioned in the release notes.
Contact
Questions about privacy: open an issue on GitHub, or use "Ask about Pulse" on the home page. Please don't post personal information publicly; say you'd like to talk privately and we'll find a way.