RadioShake is a free internet radio player for Android and iPhone. We are committed to protecting your privacy. This policy explains what data RadioShake collects and how it is used.
RadioShake does not require an account. We do not ask for your name, email or phone number, use an advertising SDK, or sell data to advertisers. Services you contact may receive your IP address and derive an approximate location.
The Android app does not access your contacts or camera. Optional voice commands request microphone permission and use an Android speech recognition provider; processing may occur on the device or through that provider's service. Local audio uses MediaStore or files you choose. Song identification makes an audio fingerprint on your device from about 12 seconds of the station you are playing (the radio stream, never the microphone) and sends that fingerprint to Shazam's recognition service, which, like any service you connect to, also receives your IP address. It is on by default; you can turn it off in Settings > Playback > Identify songs, and then no fingerprint is sent.
In an upcoming Android release, usage analytics is off by default on new installs, upgrades and restores. You can opt in and change your choice under Settings, Privacy. Listening and other features work with analytics off. That release contains no Crashlytics SDK. Android or Google Play may collect diagnostics separately under their own settings and policies.
Current and older installed Android versions send usage analytics and crash reports automatically in release builds. Those reports can contain stack traces and device and app details.
With usage analytics enabled, Firebase Analytics records automatic events such as first open, session start and updates, and a Supporter purchase event with product and price, not payment details. It also records song_id_result (whether a recognition attempt found a match, without a song or station), review_prompt_eligible, review_flow_result, about_website_tapped, android_auto_connected (an Android Auto connection) and android_auto_playback_session (actual local playback following an Auto play interaction). These Android Auto events contain no station, song or listening content. We do not log what you listen to.
With usage analytics enabled, the Android app will also record recap_viewed (a Monthly Recap was opened) and recap_shared (the share sheet for a recap card was opened). Each carries only two values: access (free or supporter) and kind (monthly or yearly). They contain no station names and no numbers from your recap. A recap is worked out on your phone from listening history that stays there; an image leaves the phone only if you choose to share it. In the next update, after Google Play review.
Firebase uses pseudonymous installation identifiers and device and app information, including an IP-derived approximate region. These identifiers are personal data. We do not use an advertising identifier or cross-app tracking. Changing the choice requests a reset of local analytics data and the app instance identifier; if a save or SDK operation fails, follow the in-app retry message. Withdrawal and reset cannot cancel a request already dispatched to Google, and do not delete data previously uploaded. Google's handling is described in the Firebase privacy documentation.
The RadioShake Android app stores favourites, listening history, cached station data and preferences on the device. RadioShake does not upload favourites or history to its servers. Exports you choose can be saved elsewhere, and Android backup may copy eligible data according to your device settings. The iPhone app is described under "iPhone App" below.
The optional Supporter purchase (see the Terms of Use) is processed entirely by Google Play. We never receive your name, email address or payment details. The app asks Google Play which Supporter purchase your Google account owns and keeps that answer on your device, so your extras keep working offline. RadioShake does not send purchase details to its own services. Firebase Analytics may record a purchase event as described under "Crash Reporting and Product Analytics" above: in older releases automatically, and in the upcoming release only if you opt in.
A thank-you tip is also processed entirely by Google Play, and RadioShake receives no payment details. The app counts your tips on the phone only, and the tip event is not sent to analytics. Tips unlock nothing extra. In the next update, after Google Play review.
RadioShake connects to the following external services to function:
Podcast search, trending lists and episode lists in the Android app go through a small RadioShake-run service at podcasts.radioshake.media, which fetches them from the Podcast Index. This keeps RadioShake's Podcast Index key out of the app.
The RadioShake iPhone app is built separately from the Android app and works differently:
radioshake.media (this site) and the RadioShake web player at app.radioshake.media use Google Analytics only if you accept analytics. Until you accept, no analytics frame is created and nothing is sent to Google. You can accept, reject or change your choice at any time with the Analytics preferences control. Google is the recipient of the measurements, and Google's identifiers are personal data.
Our collector. Analytics runs in a hidden page served from our own collector at measure.radioshake.media, which loads Google's analytics script. The collector accepts only a fixed, reviewed set of page labels and events from this site and the web player. We do not send it station names, search terms, stream addresses, full page addresses or page titles beyond a generic label such as "RadioShake browse".
What is measured. Page views by generic page type, taps on a Google Play link or a web player link, a station page shown as unavailable in your region, and measured local listening: when a local web player stream starts and, while it keeps playing, the seconds of playback in steps of up to 60 seconds. In the web player we also count when a station is added to favourites and when sharing is attempted (including a cancelled share), with only the generic page type and where it happened (station page, station card or Now Playing). Measured local listening counts only time when audio is actually playing on your device through the web player. It excludes pauses, buffering and Chromecast or other Cast playback, and no station, show or song is sent.
Cookies. After you accept, analytics sets these cookies on .radioshake.media, so they are shared by radioshake.media, app.radioshake.media and measure.radioshake.media. They are Secure, SameSite=Lax and not HttpOnly, so they are readable by scripts on any radioshake.media address.
radioshake_analytics_consent_v1 stores your choice (accepted or rejected) for 180 days. We set it when you choose either option._ga is Google's pseudonymous client identifier. It lasts up to 180 days and is set only after you accept._ga_<container> holds Google's session state for our measurement property. It lasts up to 180 days and is set only after you accept.The Google cookies are removed when you reject or withdraw.
Withdrawing. Stopping is asynchronous: the page asks the hidden analytics page to stop and waits for its confirmation. There is no hard deadline for that confirmation. While it is pending the page shows "Stopping analytics in this page". If the confirmation has not arrived after about a second, the page shows "This page has not confirmed that Google Analytics stopped. Playback continues." and does not start analytics again. Analytics then stay off for the rest of that page visit. If you accept again, your choice is saved and analytics can start the next time you open or reload a page. Playback continues throughout.
Where visits come from. When you arrive from a search engine, a social site or one of a short list of named sites, or through a campaign link with the standard utm tags that we recognise, we pass a label such as the source and medium. Anything else from another site is labelled other_referral. We never send referrer addresses, query strings or click identifiers. When you arrive from another RadioShake page (radioshake.media or the web player) or with no referrer, we send no source or campaign fields, so Google keeps your original source. Limits: only visitors who have accepted analytics are counted, so figures are not a full count. Browsers that hide the referrer appear as direct, and the source is read when the first page of a visit loads.
Engagement. Google's own engagement time is calculated by Google's script in the hidden analytics page. It can carry over between pages, so it is not a measure of listening. Use measured local listening for listening time.
Details the browser sends. In Chromium-based browsers, Google's tag also sends device and browser details by itself: device model, platform version and full browser version list, plus screen size and language. In Firefox and Safari it sends screen size and language. Our collector cannot block these.
This website's earlier self-hosted Umami analytics is no longer loaded on either site. The anonymous counts it recorded before these optional analytics remain stored on our own server. This web analytics is separate from the Android app telemetry described under "Crash Reporting and Product Analytics" above. The Android app carries no advertising SDK or cross-app tracking.
To respect music-licensing rules in certain territories, the curated station directory shown in RadioShake varies by region. In the United Kingdom and the European Economic Area (the EU member states plus Iceland, Liechtenstein and Norway), the curated directory is limited to stations from your own country; international browsing, the country picker and the radio map are hidden. Everywhere else, the full global directory is available.
In the Android app, your region is determined on your device from your mobile network or SIM country code, falling back to your device's language/region setting. RadioShake does not use GPS and has no account system. The app downloads a public availability file from radioshake.media when it starts and every few hours, which controls which countries' stations are shown; that request carries no identifiers and no country code, though like any web request it exposes your IP address to Cloudflare, which hosts this site. The podcast service is described under Podcasts. When the directory is region-limited, your country code is included as a filter in the request to radio-browser.info (the same request that, like any web request, exposes your IP address to that service). The directory region setting is not used for advertising or profiling; Firebase may derive an approximate region as described above. The directory setting only affects which curated stations are listed; you can always add and play your own custom stream URLs regardless of region.
RadioShake does not knowingly collect data from children. Firebase telemetry described above can include pseudonymous identifiers and approximate region; it is not targeted at, or aware of, a user's age. Older Android versions send it automatically, while the upcoming release requires a usage analytics choice.
If we update this policy, the changes will be posted on this page with an updated effective date.
If you have questions about this privacy policy, you can reach us at [email protected].
Last updated: 8 November 2026