Privacy

Last updated 2026-05-18

Static Radio is a small independent project. We don't sell data, run ad networks, build profiles, or share anything with anyone except the handful of services we need to keep the lights on. This page lays out, in plain terms, what we collect, why, and where it goes.

If you just listen

You don't sign in. You don't give us your name, email, or location. The mobile app does send a few things to our servers while you listen:

A random per-install ID (not tied to your name or device serial) used for two things: a live "how many people are tuned to this station right now" heartbeat, and the It Stinks! button — when you tap it on an episode, we know which install tapped it so the same install can't spam the block list. You can uninstall the app and the ID is gone.
Anonymous, aggregated playback events (which station you turned to, how long you listened, whether you muted, whether you skipped a community bulletin). These flow to Firebase Analytics as counts — we use them to see which stations get use and whether bulletins are working. No names, no contacts, no location, no other-app activity.
Crash reports through Firebase Crashlytics if the app falls over. These are stack traces — the technical breadcrumbs the crash left — not your audio or anything you typed.

If you post a community bulletin

The community-bulletin form is where we collect the most. You give us:

Your email address — to confirm receipt, send the approval / rejection, and email you the next-morning play summary.
A sender name — shown on the public schedule and on the player while your bulletin airs. This one is public.
Your audio file, plus optional cover image, link URL, button text, and location text if you choose to include them. The audio and image are stored in Cloudflare R2; the rest sits in a small database.
Payment — handled by Stripe. We never see card numbers; Stripe sends us back a session ID and a payment intent. We do forward your email and the booking metadata (station, date, tier) to Stripe so the receipt makes sense.

We use this data to schedule, broadcast, and report on your bulletin. Your email isn't added to any marketing list.

The website

The bulletin-board website (this site) sends two streams of telemetry as you use it:

Firebase Analytics (GA4): anonymous, aggregated events — page views, which form steps you completed, whether a purchase finished. We use these to see if the form is broken for a class of users. A first-party browser cookie / localStorage entry (sr_cid + Google's standard _ga) is used to stitch a session together. Any cookie-blocker stops it; Google's opt-out add-on also works.
Sentry: if a page errors or the worker throws an exception, Sentry catches the stack trace so we can fix it. We strip query parameters from the captured URL before sending so form values don't leak. No audio, no card data, no email body.

Who we share with

We share data with the providers we use to run the service. They act as our processors — no marketing, no resale.

Cloudflare — hosts the site and worker, stores the audio/image files in R2, and runs the database.
Stripe — processes payments.
Resend — sends our transactional email (confirmations, approvals, daily summaries).
Google / Firebase — Analytics, Crashlytics, and the Realtime Database that holds the live listener-count heartbeats.
Sentry — error reporting.

Retention

Bulletin records (audio, image, scheduling rows, play counts) are kept while the project is operating so we can answer receipt questions later.
Internal admin and email logs are pruned automatically after 90 days.
Firebase Analytics events stay in Google's systems for up to 14 months.
Sentry events stay 90 days.
Email us and we'll delete your bulletin data on request.

Things we deliberately don't do

No third-party ad networks. No retargeting pixels.
No selling, renting, or licensing of your data.
No profile building beyond the aggregate counts above.
No collection of contacts, calendar, photos, microphone, or precise device location. We only ever receive an audio file when you deliberately submit one as a community bulletin — nothing else gets recorded from your device.

Contact

Privacy questions, deletion requests, or just curious — email admin@staticradio.app. We read every one.