Privacy Policy
Short version: Pirate.FM is a radio site, not a data-harvesting casino. We collect the minimum needed to run the station, handle suggestions/contact, process tips, and understand whether the site works.
What casual listeners send us
You can listen to Pirate.FM without creating an account. Like most web servers, our infrastructure and security logs may temporarily receive basic request metadata such as IP address, user agent, requested URL, timestamp, and error information. We use that for security, abuse prevention, debugging, and uptime troubleshooting.
Analytics
We use Google Analytics / Google Tag Manager to understand aggregate site usage, page performance, and discovery patterns. Google may set cookies or use similar identifiers according to Google's own policies. We do not use analytics to sell listener profiles or run behavioral ad targeting.
Local browser storage
The site may use local browser storage for interface preferences and playback convenience, such as theme selection, install prompts, or player state. This stays in your browser unless you clear it.
Information you voluntarily submit
- Suggestion forms: optional callsign/email, genre or mood, and the suggestion text you provide.
- Press/contact form: name, email, and message. This is forwarded through a third-party form relay to the Pirate.FM inbox.
- Tips/payments: payment handling is processed by Stripe or the active payment provider. Pirate.FM does not store full card numbers.
- Admin uploads: uploader username and track metadata may be stored for internal station operations.
How we use it
- Run and troubleshoot the stream, website, APIs, and admin tools.
- Review listener suggestions and respond if a response address was provided.
- Handle press/rebroadcast/contact requests.
- Process tips or support transactions through the payment provider.
- Protect the site from spam, abuse, scraping, credential attacks, and broken integrations.
Third-party services
Pirate.FM may use third-party services for analytics, email delivery, form forwarding, payments, maps/assets/CDNs, and embedded/player functionality. Current examples may include Google Analytics/Tag Manager, FormSubmit or another form relay, Mailgun or another email provider, Stripe, and public CDN/static asset providers. Those services process data under their own privacy terms.
What we do not do
- We do not sell listener data.
- We do not publish private contact-form messages.
- We do not intentionally expose admin-only upload paths, raw server paths, credentials, or private operational data.
Retention
Operational logs are kept as long as reasonably needed for debugging, security, analytics, and abuse prevention. Suggestion/contact submissions are retained until they are no longer useful or you request deletion. Track/admin metadata is retained as long as needed for station operations.
Your choices
- You can block analytics with browser privacy controls or extensions.
- You can clear local browser storage in your browser settings.
- You can avoid optional forms if you do not want to provide contact information.
- You can request deletion of personal information you submitted voluntarily.
Deletion/contact requests
Use the contact form on the media kit page and include enough detail for us to identify the submission you want removed. Do not send passwords, API keys, private keys, or other secrets through the form.
Changes
This policy may change as the station changes. Material updates will be posted here.
Last updated: May 15, 2026