Neutrope Protected Audio Player lets you publish MP3 audio on your WordPress site without exposing the real file URL in your page source. Files are stored in a protected uploads folder that denies direct access, and the player streams audio through a short-lived, signed playback URL instead of a permanent, guessable link.

This is not DRM. It makes casual downloading harder, but it cannot provide DRM or perfect copy protection. If audio can be played in a browser, it can potentially be captured by determined users. The goal is simply to stop ordinary visitors from finding and saving the MP3 with a right-click or a quick look at the page source.

What it does

Adds a “Protected Audio” item type where you upload an MP3 and get a shortcode.
Stores uploads in wp-content/uploads/neutrope-protected-audio-player/, protected by an .htaccess file.
Serves audio through a signed URL such as /npap-stream/123/.../.../ that expires after 10 minutes.
Outputs an <audio> player with controlslist="nodownload" so the browser’s download button is hidden.
Keeps an anonymous play count per item.

What this plugin can and cannot do

This is not DRM.
This plugin makes casual downloading harder, but cannot provide DRM or perfect copy protection.
If users can play audio in a browser, advanced users may still capture it.
No external services.
No tracking.
No cookies.
No personal data stored by default.
Apache/LiteSpeed uses .htaccess protection.
Nginx may require additional server configuration.

Privacy

No external services, CDNs, scripts or APIs are used. Everything runs on your own server.
No tracking.
No cookies are set.
No personal data is stored by default. The plugin records only an aggregate play count per item. It never stores IP addresses and never sets cookies.

Server requirements

On Apache and LiteSpeed, direct access to the protected folder is blocked automatically with the .htaccess file the plugin creates.
On Nginx, .htaccess files are ignored. You will need to add server configuration to deny direct access to the protected uploads folder. The admin screen shows a reminder when it detects Nginx.
On some Nginx or reverse proxy configurations, byte-range responses may be buffered or altered by the server. Audio playback can still work, but seeking behavior may depend on server configuration.
Pretty permalinks are recommended. When they are disabled, the plugin falls back to a query-string playback URL.