Privacy Policy

Live Beats WebRadio ("the app"), package name com.lbwebradio.radio, is an internet radio and podcast player built to keep your data on your device where possible. This policy explains what stays on your device, what technical data is shared with third parties, and who is responsible for the app. For the terms governing your use of the app itself — including licensing, third-party stream/podcast content, and liability — see our End-User License Agreement.

Data Controller

Live Beats WebRadio is published on Google Play under the developer name WRtec and is developed and maintained by Christian Flach, who acts as the data controller for this app. Contact: livebeatswrp@gmail.com.

Information Stored On Your Device

The following stays on your device and is never transmitted to us:

• Your favorite stations, including any "Super Favorites" and genre tags
• App settings (theme, language, album art preference, data tracking preference, sleep timer, whether crash log sharing is enabled, etc.)
• Listening session history (previous/next station navigation)
• Estimated data usage statistics — bytes consumed per session and month, tracked locally to power the "Data Guard" and usage reporting features, covering both radio streaming and podcast downloads/streaming
• Saved songs, if you use that feature
• Cached server location data (country and flag) for your favorite stations
• A small amount of local state used to time the in-app rating prompt, such as how many favorites you've added and when you were last asked
• A short local record of which stations you've recently voted for, used only to apply a cooldown so you can't vote for the same station repeatedly — this record is never sent anywhere
• Your podcast subscriptions (podcast titles and their feed URLs)
• Downloaded podcast episode audio files, stored in the app's private, app-scoped storage on your device — not a shared or public folder, so no additional device storage permission is required to use this feature
• Podcast playback progress and "finished" status for individual episodes, your podcast listening history, and your "Listen Later" queue

Backing up or moving your favorites to the desktop app uses .lbrx files. That file gets created and read locally, wherever you choose to save it — your device, or somewhere like Google Drive if you pick that as the destination. We never see a copy.

Audio compression for downloaded podcast episodes happens entirely on your device, using Android's built-in Media3 Transformer API. No audio file or podcast content is ever uploaded to us or to any third-party server for this processing — both the temporary and final compressed files stay in the app's private on-device storage.

Information Sent to Third Parties

To work, the app talks to a handful of outside services. As with any internet request, your IP address is automatically visible to each receiving server, and every request identifies the app name, version, and that it's running on Android via a standard User-Agent string. Under some data protection laws (including the GDPR), an IP address is itself considered personal data, so this exposure is treated as personal data processing below, not merely "technical" data — see the Legal Basis section for how we justify it.

You can turn most of these off. Three settings control the optional lookups: turning off "Show Album Art" stops the album art lookups to iTunes and Last.fm for radio tracks, turning off "Show Server Location" stops the server location lookups to ipwho.is, and turning off "Help improve the app by sending crash logs" stops crash and diagnostic data going to Firebase Crashlytics. Podcast search, episode feeds, and downloads only happen when you actively use the Podcasts tab — if you don't use podcast features, no podcast-related requests are made. The in-app rating prompt doesn't currently have its own on/off setting; if you dismiss it enough times, the app stops showing it automatically.

About the Google Play Data safety label. The Data safety section of our Google Play listing reflects the same information as this policy. Search history and some in-app actions (votes, play counts, and now-playing lookups) are shown as shared with other companies because those requests go to Radio-Browser, Apple, and Last.fm. Crash logs, diagnostics, and identifiers are shown as optional collected data because crash reporting through Firebase Crashlytics can be switched off at any time in Settings.

This Website

This website (lbwebradio.github.io) is hosted on GitHub Pages and loads its fonts from Google Fonts, so your IP address and browser details are visible to GitHub and Google when you visit. The site doesn't use cookies, analytics, or advertising. It stores your chosen accent color in your browser's local storage so it stays consistent across pages; this never leaves your browser.

Contacting Support

Tapping the email icon under Settings → About opens your own email app with a support email pre-addressed to us, pre-filled with a small amount of diagnostic information: app version, radio database version, Android version, device manufacturer and model, and whether you're a Pro or Free user. This is meant to help us assist you faster without you having to look up these details yourself.

This information is only ever sent if you choose to send that email — nothing is transmitted automatically. You can review, edit, or delete any of the pre-filled text in your email app before sending, the same as with any other email. No account, name, or personal identifier is added by the app beyond whatever is already part of your own email account and message.

Legal Basis for Processing (GDPR)

For users in the European Economic Area, we rely on legitimate interest (GDPR Article 6(1)(f)) to provide the core app functionality you've requested, limited to what's necessary to deliver streaming, station and podcast directory, and metadata services. This includes the technical data described above, such as IP addresses visible to third-party services (including podcast publishers and any tracking redirects they embed) during these requests, which we recognize as personal data under the GDPR even though no account or identity information is attached to it. Crash and diagnostic reporting via Firebase Crashlytics — including the minimal session signal used for stability metrics — is also based on legitimate interest, namely identifying and fixing app stability issues, and is limited to technical diagnostic data; it can be disabled at any time in Settings. The diagnostic info pre-filled into support emails is provided at your own initiative and under your control before sending, so no separate legal basis analysis applies beyond your own action in sending it. Where the app processes a PRO purchase, this is instead based on the necessity to perform a contract (GDPR Article 6(1)(b)) — fulfilling the purchase you initiated via Google Play Billing. The in-app rating prompt is also based on legitimate interest, limited to minimal on-device usage signals (such as your favorites count and when you were last asked) used only to decide when to show the prompt; nothing about it is sent off your device.

International Data Transfers

Some of the third-party services listed above — including Firebase Crashlytics and Google Play Billing (Google), and the iTunes Search API and Apple Marketing Tools API (Apple) — are operated by companies based in, or that process data in, the United States, outside the European Economic Area (EEA) and United Kingdom. Podcast RSS feeds, episode audio, and any third-party tracking redirects embedded by individual podcast publishers may be hosted anywhere in the world, depending entirely on that publisher's own infrastructure, which is outside our control. Where transfers happen with Google or Apple, they rely on the safeguards those providers make available under the GDPR: Google and Apple participate in or otherwise rely on mechanisms such as the EU-U.S. Data Privacy Framework and/or the European Commission's Standard Contractual Clauses (SCCs), which are legal tools intended to ensure your data continues to receive a level of protection equivalent to what the GDPR requires, even once it leaves the EEA. We don't operate our own servers outside the EEA and don't independently transfer your data anywhere — any cross-border transfer happens as part of using these providers' services, or a podcast publisher's own servers, as described in the table above. You can find more detail on each provider's own safeguards in Google's Privacy Policy and Apple's Privacy Policy.

Notifications

Android's notification system shows playback controls while a station or podcast episode plays in the background, and shows progress while a podcast episode is downloading. That's all handled by the OS — no outside service involved.

Permissions

Downloaded podcast episodes are saved to the app's own private storage area, so the app does not need, and does not request, broad device storage permissions to offer podcast downloads.

Security Note

Some radio stations and podcast publishers still broadcast or host their audio over plain http:// instead of https://. That's a limitation of those individual stations or publishers, not something we can fix on our end — it's common across radio and podcast apps generally. In practice it means your network provider could potentially see which station you're streaming or which podcast episode you're downloading, same as with any unencrypted connection.

If you'd rather avoid unencrypted connections entirely, the HTTPS Only setting blocks playback of any station or episode using an unencrypted http:// link, requiring https:// instead. If you're listening to an http:// stream when you turn this on, playback stops immediately and the app shows "Insecure (HTTP) stream blocked by your settings." Turning it on means some stations or episodes may become unavailable, since not every station or publisher offers an encrypted stream. This setting governs audio playback only; it does not affect background podcast RSS feed or metadata lookups, which may still occur over http:// if a publisher's feed doesn't support encryption. Note that, because this setting checks the type of link being played, it currently also applies to already-downloaded podcast episodes stored on your device; if you use downloaded podcasts and run into an episode that won't play with this setting on, turning it off will resolve that.

Data Retention & Deletion

We don't run servers that store your favorites, settings, podcast subscriptions, downloads, or listening history — there's nothing on our end to retain in the first place. That data lives in Android Room and DataStore on your device and stays there until you delete it yourself, either inside the app or by clearing the app's data/storage in Android settings. Uninstalling the app removes it too.

Because we never receive this data, we have no way to retain or delete it on your behalf — your device is the only copy. The one exception is anything you choose to export yourself (like an .lbrx backup file); once it's saved somewhere, deleting it is up to you, the same as any file. Purchase records for the PRO upgrade are retained by Google as part of your Google Play account, separately from anything stored by this app; see Google's Privacy Policy and Play Terms of Service to manage or delete that record. The local, on-device state used to time the in-app rating prompt (such as your favorites count and last-shown date) is deleted the same way as any other app data — clearing storage or uninstalling. If you go on to leave a rating or review through the Play Store after tapping "Rate now," that rating is retained by Google as part of your Google Play account, not by us. Crash and diagnostic data sent to Firebase Crashlytics — including the minimal session signal described above — is retained by Google for a limited period (currently 90 days according to Firebase, after which removal from Google's systems begins); see Firebase's data processing terms for details. Any support email you send, including the pre-filled diagnostic info, is retained in your own email account and ours, like any other email correspondence.

How to Delete Your Data

Live Beats WebRadio does not use accounts, so there is no central account or server-side profile to delete. All app data — favorites, radio and podcast listening history, downloaded episodes, podcast subscriptions and "Listen Later" queue, saved songs, settings, cached server-location info, and the local state behind the in-app rating prompt — is stored locally on your device in Android Room/DataStore and was never sent to us in the first place.

To delete this data yourself:

• In-app: use the "Clear History" and "Delete Favorite" options found in the Favorites and History screens to remove specific items. Podcast listening history has its own separate "Clear Podcast History" action in the Podcast screen, which only clears podcast history and is independent from clearing radio history; you can also remove individual podcast episodes from your history one at a time.
• Full reset: go to Android Settings → Apps → Live Beats WebRadio → Storage & cache → Clear storage. This immediately and permanently erases all app data on your device, including downloaded podcast episodes and any saved state for the in-app rating prompt.
• Uninstalling the app also removes all locally stored data, including any downloaded podcast episodes.

The only data that ever leaves your device — search terms sent to Radio-Browser or Apple's podcast APIs, artist/track lookups sent to iTunes/Last.fm for album art, requests made to a podcast's own RSS feed or audio host (and any tracking redirect a publisher has embedded in it), diagnostic data (including the minimal session signal) sent to Firebase Crashlytics, or diagnostic info included in a support email you choose to send — is not linked to any account of ours. Apart from support emails you choose to send us and crash reports we can view in Firebase, we don't receive or hold a copy of it, so there is nothing else for us to delete on your behalf. Each service handles the data it receives under its own policy and retention rules, which we don't control. (Crashlytics does use an installation-scoped identifier to group reports from the same device install over time, as noted above, but this isn't an account or hardware identifier.) If you disable "Show Album Art" (album art lookups to iTunes and Last.fm), "Show Server Location" (lookups to ipwho.is), or "Help improve the app by sending crash logs" (crash and diagnostic data to Firebase Crashlytics) in Settings, the app stops sending those specific requests going forward. Podcast-related requests to Apple and to podcast publishers are separate and only happen when you use the Podcasts tab. Purchase history for the PRO upgrade is managed through your Google account at Google Play → Payments & subscriptions, not through this app. Any rating or review you've left through the Play Store after using the in-app "Rate now" option can be edited or removed the same way — through your Google Play account — since it was never stored by this app.

Your Rights Under GDPR

If you're in the European Economic Area, the GDPR gives you the following rights over your personal data. Because Live Beats WebRadio doesn't use accounts and doesn't hold a server-side copy of your favorites, settings, podcasts, or listening history, most of these rights are already satisfied by design — there's simply nothing centrally stored for us to act on. Here's how each one applies in practice:

• Right of access — You already have full access to everything the app stores, since it all lives in Android Room/DataStore on your own device. We hold no separate copy to request access to.
• Right to rectification — Anything the app stores (station names, genres, saved song titles, podcast subscriptions, etc.) can be edited directly in-app at any time.
• Right to erasure ("right to be forgotten") — See How to Delete Your Data above for exactly how to remove any or all app data.
• Right to restrict processing — You can disable "Show Album Art" (stops album art lookups to iTunes and Last.fm), "Show Server Location" (stops lookups to ipwho.is), or "Help improve the app by sending crash logs" (stops crash and diagnostic reporting) in Settings at any time, or avoid the Podcasts tab to stop podcast-related requests to Apple and podcast publishers.
• Right to data portability — Your favorites can be exported at any time as a .lbrx file, in a format you control and can move elsewhere.
• Right to object — You can object to any processing based on legitimate interest (see the Legal Basis section above) by disabling the relevant setting, avoiding the relevant feature, or by uninstalling the app, which removes all local data immediately.
• Rights related to automated decision-making and profiling — The app doesn't perform automated decision-making or profiling about you, so this right doesn't apply to anything we do.
• Right to lodge a complaint — If you believe your data has been mishandled, you have the right to complain to your local data protection supervisory authority, regardless of anything above. You can find your national authority via the European Data Protection Board's member list.

For any of the above, or if something isn't covered here, you can also reach out directly — see Contact below.

Your Privacy Rights Under CCPA/CPRA (California)

If you're a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA), gives you rights over your personal information similar to those described above under the GDPR: the right to know what personal information is collected, the right to delete it, the right to correct inaccurate information, and the right to non-discrimination for exercising any of these rights. We do not sell or share your personal information, as those terms are defined under the CCPA/CPRA — we don't exchange it for money, and we don't disclose it to third parties for cross-context behavioral advertising. The limited technical data described in the Information Sent to Third Parties table above is shared only as needed to provide the app's core functionality (station and podcast search, artwork lookup, podcast feed/episode delivery, crash diagnostics), which falls outside the CCPA/CPRA's definition of a "sale" or "share." Because we don't use accounts, most of what you could request access to or deletion of already lives on your device under your control — see How to Delete Your Data above. To exercise any CCPA/CPRA right, or if you have questions about how this applies to you, contact us — see Contact below.

Do Not Track Signals

Some browsers offer a "Do Not Track" (DNT) signal, and some U.S. states have laws addressing how site operators should respond to it. Live Beats WebRadio doesn't run in a browser and doesn't perform behavioral tracking or cross-site/cross-app tracking of any kind, so there's no tracking for a DNT signal to opt you out of — the app simply doesn't respond to DNT signals because it has no tracking behavior to disable in the first place.

Children's Privacy

The app isn't directed at children and doesn't knowingly collect personal information from anyone. The age at which someone can use online services without parental involvement varies by country — for example, 13 in the United States, and up to 16 in some European Union member states (with others setting it as low as 13). We don't gate any content by age beyond whatever individual radio stations or podcast publishers broadcast.

Changes to This Policy

If anything here changes, we'll update the "Last updated" date above. Using the app after a change goes live means you accept the updated version.

Contact

Questions about this policy or the app's data practices can be sent to:
Live Beats WebRadio
Developer: Christian Flach (WRtec)
Email: livebeatswrp@gmail.com