RadioFM Pro Privacy Policy

Scope and plain-language summary

This policy explains how RadioFM Pro handles information when you browse the public radio directory, play a third-party station stream, use the map, save favorites, change settings, create an account, or contact support. Basic radio discovery and listening do not require an account. We do not sell personal information, and we do not claim ownership of the audio programmes delivered by broadcasters.

RadioFM Pro combines public station records from Radio Browser with place matching from GeoNames and stores a synchronized catalogue on its own service. Those directory records describe stations, not listeners. They can include a station name, public stream address, homepage, tags, language, codec, bitrate, and an approximate directory location.

Information created by public listening

When you request a page, map tile, API response, or audio stream, servers and delivery providers may process ordinary technical request information such as IP address, date and time, browser user agent, requested URL, referral information, and error status. This information is needed to deliver the service, protect it from abuse, diagnose failures, and understand aggregate reliability. Server logs are not presented as an official audience measurement for any station.

The iOS and iPadOS app receives station metadata from RadioFM Pro and sends the selected broadcaster's eligible public HTTPS address directly to Apple's media player. RadioFM Pro does not relay native-app audio. The browser player may use a same-origin, Web-only compatibility proxy so browsers can handle redirects, legacy HTTP sources, or HLS playlists more consistently. In native playback, the broadcaster or its delivery provider receives the device's stream request information; in Web proxy playback, it receives the proxy server's request information. RadioFM Pro does not control the broadcaster's own logs, advertising, cookies, regional restrictions, or privacy practices. Following a station homepage also takes you to a separate service governed by that site's policy.

Location and map controls

The homepage and local-radio guide may request a coarse country suggestion from the network connection so they can offer a relevant starting point. A coarse suggestion can be wrong, especially with a VPN, mobile network, corporate gateway, or shared connection. It is not represented as a precise position.

Precise browser location is requested only after you activate the map's locate control. Your browser or operating system shows the permission request and lets you deny it. RadioFM Pro uses the coordinates to move the map and find nearby catalogue places; the interface still works through search, country, city, and genre links when permission is denied. Do not treat a directory coordinate as a verified broadcast studio, transmitter, service area, or proof that a station is physically nearby.

Browser storage, favorites, and settings

Favorite identifiers, player volume, current player state, appearance choices, and similar preferences can be stored in local browser storage. This lets the player and preferences persist without requiring an account. Clearing site data, using a private window, changing browsers, or changing devices can remove that local state.

Where a favorites transfer feature is available, a short-lived transfer code can represent public catalogue identifiers so favorites can be merged on another device. The code is not an account password and is not intended to contain precise location. Keep any active transfer code private until it expires.

Essential cookies may be used for authentication and security. If you sign in, account records can include the name, email address, authentication-provider identifiers, session information, and security events needed to operate the account. Do not share credentials or session links. Account and settings pages are private utility areas and are excluded from search indexing.

Analytics and support tools

RadioFM Pro can be configured to use Google Analytics or Plausible to understand aggregate page use and technical performance. If enabled, those services may receive page URLs and ordinary device or network information according to their own configuration and policies. Current analytics is not used to invent listener counts, station ratings, endorsements, or editorial rankings.

Support chat providers may also be enabled. Information you type into a support form or chat, including an email address, page URL, device details, and problem description, is processed so the request can be answered. Send only the information needed to reproduce the issue. Do not submit passwords, payment-card data, or sensitive personal information in a broken-stream report.

Mobile advertising, consent, and tracking

The free iOS and iPadOS app uses Google Mobile Ads to show occasional full-screen RadioFM Pro interstitial advertisements after user-initiated station changes. RadioFM Pro does not pass search terms, selected stations, favorites, microphone input, or device coordinates to Google as custom advertising targeting parameters. A broadcaster may separately include advertising inside its own programme or stream; RadioFM Pro does not select or control that advertising.

Google Mobile Ads may process an IP address, which can be used to infer a coarse location; device identifiers, including an advertising identifier when permission and applicable consent allow it; advertising data such as ads viewed; product interactions such as app launches, taps, or video views; performance information such as launch time, hangs, or energy use; and diagnostic information such as non-user-linked crash logs. Depending on the item and configuration, Google may use this information for third-party advertising, analytics, fraud prevention, SDK operation, performance measurement, and diagnostics. Google acts under its own privacy terms and is required to protect information consistently with applicable law and the protections described in this policy.

Where required, Google's User Messaging Platform (UMP) presents regional advertising choices and records consent before the app requests an ad. The Apple App Tracking Transparency (ATT) prompt is requested only when the user is eligible for personalized advertising after that consent flow. Declining ATT, declining personalized ads, a restricted device setting, or an unresolved authorization state does not block the app; advertising falls back to non-personalized or otherwise limited delivery when Google permits an ad request. The app does not show RadioFM Pro interstitial ads to a user with an active Pro entitlement.

When UMP requires an ongoing control, Settings → Privacy Choices lets the user review or withdraw advertising consent. Users can also change tracking permission in iOS or iPadOS Settings and can report an inappropriate or age-inappropriate ad from the app's Settings screen. Withdrawing consent affects future requests; limited operational records may still be retained where necessary for security, fraud prevention, legal compliance, or aggregate reporting. Privacy and deletion requests can be made through the RadioFM Pro contact page.

How information is used and shared

We use information to deliver pages, station metadata, Web playback, and eligible advertising; maintain sessions and preferences; prevent abuse and advertising fraud; investigate errors; improve accessibility and performance; answer support requests; and correct directory records. Native audio is delivered directly by the selected broadcaster or its delivery provider. Information may be processed by infrastructure, advertising, analytics, authentication, or support providers when their service is enabled. It may also be disclosed when reasonably necessary to comply with law, protect users or the service, investigate fraud or security incidents, or complete a business reorganization subject to applicable safeguards.

We do not promise that every third-party stream is available, lawful in every region, or free of advertising. Directory corrections can be checked against Radio Browser and an available official broadcaster source. Unverified claims are left out rather than added to fill a page.

Retention, security, and your choices

Different records have different retention needs. Local browser preferences remain until you or the browser removes them. Session and account records remain while needed to provide and secure the account, meet legal obligations, resolve disputes, and maintain limited security history. Operational logs and support messages are retained only as reasonably needed for service, security, troubleshooting, and compliance purposes.

We use access controls, secure transport, input validation, and other safeguards appropriate to the service, but no internet system can guarantee absolute security. You can block or clear cookies and local storage, deny location permission, avoid account creation, choose not to open third-party sites, or stop using the service. Some choices can disable the feature that depends on them.

Depending on applicable law, you may request access, correction, deletion, restriction, or export of personal information associated with you. A request may require identity verification, and legal exceptions can apply. Use the RadioFM Pro contact page and identify the relevant account or support interaction without sending credentials.

Updates and questions

The updated date above changes when this policy is materially revised. Product behavior and enabled service providers can change, so review the current page rather than relying on an old copy. Questions about a stream should include the station page and observed error; privacy questions should describe the information or feature involved. The Terms of Service separately explain the rules and limitations for using RadioFM Pro.