Privacy Policy

1. Who we are

Global Radio Plus is operated by Probed Studios Inc. (“Probed Studios,” “we,” “us,” or “our”), a corporation incorporated under the Canada Business Corporations Act with its registered office in Ontario, Canada. The Global Radio Plus applications for Android, iPhone, iPad, and Apple Watch (each an “App” and together, the “Apps”) and the Global Radio Plus website at globalradioplus.com (the “Website”) are together the “Service.” We are the controller responsible for the limited personal information processed in connection with the Service.

For all privacy questions, requests, and complaints, contact: [email protected].

This Privacy Policy explains what information the Service does and does not collect, how it is used, the third parties involved, your rights, and how the law protects you. It applies to the Apps and the Website. Because our users are global, this Policy includes specific sections for Canada (PIPEDA and Quebec Law 25), the EU/EEA/UK (GDPR), and California (CCPA/CPRA).

This Policy does not cover the separate Probed Studios company website, which is governed by its own privacy policy.

1.1 Website-specific scope and disclosures

Sections 2–19 primarily describe the native Apps. When you use the Website, the following disclosures apply and control over any inconsistent App-specific wording elsewhere in this Policy:

• The Website has no accounts, advertising, recording, or sync. Favorites, recents, custom links, and artwork stay in browser-local IndexedDB until you remove them or the browser clears them. First-party locale and theme cookies last up to one year, and a local record stores your analytics choice.
• Vercel hosts the Website and may handle URL requests and connection/security data; Cloudflare provides DNS. Committed search and filter values go to Radio Browser. IP-based country suggestions, direct broadcaster streams, artwork, and links involve independent providers that receive ordinary connection data. We do not request precise device location.
• The Website loads GA4 only after explicit consent. Global Privacy Control keeps it off, and withdrawal stops future collection. Consented analytics uses sanitized route categories and referral origins, not search text, station names or identifiers, private URLs, artwork, stream URLs, or raw errors. We do not use Google Signals, User-ID, or ad personalization. Analytics cookies may last up to 13 months; user/event retention is two months with reset on new activity disabled.
• Cast is optional, user-initiated, and separate from analytics consent. If used, Google's sender SDK sends the chosen stream URL, station name, country, and artwork to the selected receiver, including for a custom station.
• The Firebase disclosures in Sections 5–7 apply only to the native Apps, not the Website. Cloud Messaging is used only by the Android App. The iPhone and iPad Apps use Analytics, Crashlytics, and Remote Config as described below.

See the Website's detailed privacy page for its precise storage, provider, analytics-retention and exclusion, consent, and Cast disclosures.

1.2 iPhone, iPad and Apple Watch disclosures

This section applies to the Apple Apps and controls over any inconsistent general App wording below. No account is required. The Apple Apps have no app-served advertising or Firebase Cloud Messaging; broadcasters may include advertising in their streams. Apple Watch controls the paired iPhone and does not stream independently.

Optional usage analytics and optional crash reporting are separate choices, both off by default. You may enable either during setup or in Settings → Privacy, and withdraw either choice there. Usage Analytics collects bounded screen views, a generic playback-started event, and SDK lifecycle/session information. Turning it off stops optional usage collection and resets Analytics data stored by that SDK on your device. The Crashlytics SDK can record crash diagnostics locally, but automatic report uploading remains disabled. At each launch, the App uses your saved crash-reporting choice to authorize or discard the pending report batch. Turning crash reporting off prevents authorization of future batches and discards still-unsubmitted pending reports at the next launch. Already-authorized or enqueued uploads may finish; changing a choice does not delete the active local crash session or recall reports already transmitted. Contact us for applicable deletion requests.

Installation-linked information. We do not create an account for you or attach your name or email to telemetry. Firebase uses persistent app-instance and installation identifiers for configuration, session and crash processing. Associated information may be linked to your device or installation. Our App Store privacy disclosure treats coarse location, device identifiers, product interaction, crash data and other diagnostic data as linked to you. This does not mean we associate them with a named account or use them for cross-company advertising tracking.

Crash reports. If you choose to share them, reports can contain stack traces, app state, device model, operating-system and app versions, session information and persistent installation identifiers. The App does not add station names or identifiers, searches, stream or artwork URLs, custom station details, custom user IDs, custom keys or developer logs. If optional Analytics is enabled, Firebase may attach Analytics event breadcrumbs and app-exception events. Google states that it starts deleting Crashlytics data after 90 days; this is not a promise of immediate deletion of every copy on day 90.

Configuration and Google Cast. Firebase Remote Config and installation processing retrieve operational Radio Browser routing and accepted station-removal settings. They can process app, device, operating-system, locale/region, installation and connection information separately from the optional switches; no station searches, saved stations or private custom URLs are supplied to configuration. The bundled Google Cast SDK handles receiver discovery and selected playback information. Its diagnostic collection measures and improves SDK reliability and performance and is separate from optional usage Analytics. We disable optional Cast discovery-diagnostic logging, but this does not stop every SDK data flow. The SDK may process coarse location, device identifiers, diagnostic and interface-interaction information, and performance data for analytics and app functionality. Cast performance data is disclosed as not linked to you. Local Network permission controls receiver discovery; declining it does not prevent on-device radio listening.

Local data and independent providers. Favorites, recents, private custom stations, chosen custom artwork, preferences and timer state are stored locally. Apple backup/device-management settings may govern copies. Paired Watch transfers and user-initiated AirPlay or Cast involve the devices you select. Searches and filters are sent to Radio Browser community mirrors; streams, playlists and artwork connect directly to independent providers. Those providers receive ordinary connection information, including an IP address, and may apply their own logging practices. We do not claim that searches never leave your device or that every independent mirror retains no logs. The country suggestion does not use GPS; manual/worldwide browsing remains available.

Station and rights reports. Settings → About → Report a station or rights issue opens our web form in your browser. Ordinary listing reports do not require sworn copyright statements. If you send a report, its contact details and message go to FormSubmit for email delivery/spam filtering and then to our studio inbox. FormSubmit states that it keeps a submission archive for 30 days. Our website privacy page describes this voluntary reporting flow. You can instead email [email protected]. No report or private library information is sent automatically by opening the link.

2. Summary (the short version)

• The Apps have no user accounts — no sign-up, login, registration, profile, username, or password.
• The Apps are ad-free. We do not use advertising SDKs, and we do not sell or share your personal information.
• Your “recently played” history, favorites, and any custom stations you add are stored only on your device; we do not receive or store them.
• Analytics is off until you turn it on. We ask for your consent during setup, and analytics stays disabled unless you opt in. You can change your choice at any time in Settings.
• The App includes Firebase Crashlytics (a Google service) to detect and fix crashes. In the Apple Apps, crash-report uploading is a separate optional choice, off by default.
• The Android App uses Firebase Cloud Messaging for occasional announcements. The Android, iPhone, and iPad Apps use Firebase Remote Config to adjust operational settings, including resilient station-directory routing.
• The App determines your approximate country (from your IP address, via a geolocation service) to show stations popular in your region.
• When you browse or play stations, your device contacts the Radio Browser community database for listings and connects directly to the broadcaster's stream.

3. No accounts and no user-generated content

The Apps do not offer or require accounts. We do not collect your name, email address, password, date of birth, gender, photographs, or contacts in order to use the Apps. There is no feature to post comments, reviews, or other public content.

4. Information stored locally on your device (not collected by us)

The following information is created and stored only on your device and is not transmitted to us:

• Recently played stations (your listening history within the App);
• Favorite stations you save to your library;
• Custom stations you choose to add (the stream URL, a label, and any custom logo image you select — custom logos are stored only in the App's private storage and are never uploaded);
• App settings and preferences (such as theme, language, and your analytics-consent choice).

On Apple devices, station information needed for favorites, recents, and playback controls may be transferred directly between your paired iPhone and Apple Watch through Apple's Watch Connectivity system. It remains on your devices and is not sent to Probed Studios. Siri and the Shortcuts app may pass the action, search phrase, or station you request to the App; Apple processes your voice interaction under Apple's own privacy terms, and Probed Studios does not receive an audio recording.

AirPlay is handled by Apple's system services. If you choose Google Cast, the App and Google's sender SDK discover compatible receivers on your local network and send the selected station's stream URL, name, country, and artwork to the receiver. Cast is user-initiated, does not depend on analytics consent, and may require local-network permission.

This information remains under your control. You can clear it at any time within the App (where such a function is provided), or by clearing the App's storage or uninstalling the App through your device settings. Because we never receive this information, we cannot access, retrieve, or delete it for you.

5. Analytics — Firebase Analytics (Google), consent-based

The App uses Google Analytics for Firebase (“Firebase Analytics”) to understand how the App is used in aggregate — for example, which features are popular and where technical problems occur — so we can improve it.

Analytics is opt-in. When you first set up the App, we ask whether you agree to share optional usage analytics. Analytics is disabled by default and remains disabled unless you opt in, regardless of where you are in the world. You can turn it on or off at any time in Settings → Privacy. When usage analytics is off, no optional usage-analytics events are sent. Configuration and applicable SDK diagnostics remain separate, as explained in Section 1.2 for the Apple Apps.

What analytics events contain. When analytics is enabled, the App records limited events for aggregate reporting. The Android App records the feature and playback events listed below. The iPhone and iPad Apps use a narrower set: screen views and a generic playback-started event, without station names or station identifiers.

• which stations you play (event includes the station's name and its Radio Browser identifier, so we can understand listening trends and diagnose playback problems for specific stations);
• playback successes and failures (including a generic error code when playback fails);
• feature usage in a non-identifying form — for example, that a search returned a bucketed count of results (such as “6–20”), that a filter was used (only whether a country/keyword/language filter was applied, not the values you typed), that a station was favorited (only whether it was a community or custom station, not which one), that a sleep timer was set (a bucketed duration), that casting started, that a custom station was added, and which screens were viewed.

What analytics never contains. We do not log your search query text, the URLs of custom stations you add, your name, email, phone number, or any other directly identifying information. The iPhone and iPad Apps also do not log station names or Radio Browser identifiers. Analytics events are associated only with a pseudonymous app-instance identifier generated by Firebase. It may link events to an installation; we do not attach your name or email to it.

How it is processed. Analytics data is transmitted to Google, which processes it as our service provider to provide analytics services to us. It is encrypted in transit. Firebase Analytics' default data-retention period for event and user-level data is short (currently two months, configurable up to fourteen months); aggregated reporting may persist longer. We do not use analytics data to identify you and we do not sell or share it.

6. Crash and diagnostic data — Firebase Crashlytics (Google)

The App includes Firebase Crashlytics, a crash-reporting tool provided by Google, to detect, diagnose, and fix crashes and stability problems. Crashlytics is separate from optional usage analytics. In the iPhone and iPad Apps it is off by default and report uploading requires your separate choice in setup or Settings. The Android App’s crash processing relies on our legitimate interest in providing a secure, functioning App; see Section 10 and your rights in Section 14.

What Crashlytics collects. When the App crashes due to an unhandled error, Crashlytics automatically collects:

• the crash stack trace and relevant application state at the time of the crash;
• device and diagnostic metadata — such as device model and manufacturer, operating-system version, and App version; and
• a Crashlytics installation identifier (a UUID) used to measure how many installations are affected by a given crash. This identifier is associated with the App installation, not with your name, and Google describes the underlying Firebase installation ID as not uniquely identifying a user or physical device.

Crashlytics reports unhandled application crashes and diagnostic state. Firebase may include optional Analytics event breadcrumbs; the Apple-specific limits and choices are described in Section 1.2. It is used by the Android, iPhone, and iPad Apps, not by the Website or Apple Watch App.

How it is processed. This data is transmitted to Google/Firebase, which processes it as our service provider to provide crash-reporting services to us. It is encrypted in transit. Google states that it starts deleting Crashlytics crash data after 90 days. We use the data only to maintain and improve the stability and security of the App, and we do not sell or share it.

7. Notifications and remote configuration — Firebase Cloud Messaging & Remote Config (Google)

Firebase Cloud Messaging (FCM). The Android App uses FCM so we can send occasional announcements (for example, news about the App or important notices). All installations are subscribed to a single general broadcast channel; we send the same message to everyone and do not target individuals. To deliver messages, FCM uses a registration token and standard device metadata (such as App version). FCM operates to provide this notification capability and is not tied to your analytics-consent choice. You can control whether notifications are displayed through your Android device's notification settings. The iPhone, iPad, and Apple Watch Apps do not use FCM.

Firebase Remote Config. The Android, iPhone, and iPad Apps use Remote Config to adjust certain operational settings without requiring an App update, including keeping the Apps' station-directory connection resilient when a community Radio Browser host is unavailable. The iPhone and iPad Apps also use this configuration to enforce accepted public-station removal decisions. When fetching configuration, Remote Config sends standard client metadata to Google (such as language, country/region, time zone, operating-system and App version, and a Firebase installation identifier) so the correct configuration can be returned. It does not transmit your listening history, favorites, or other personal content.

8. Approximate location

To show you stations that are “popular in [your country/region],” the App determines an approximate, country-level location. It does this by sending your device's IP address to a third-party IP-geolocation service over an encrypted (HTTPS) connection, which returns your approximate country. This lookup is used transiently at the time of your request to tailor the station listings shown to you; the resulting location is held only in memory for the current session and is not stored by us as an identifiable location history.

We do not collect precise GPS location, and the App does not request any device location permission. We do not build a location profile and we do not sell or share location information. The geolocation provider processes the request in accordance with its own privacy practices. You may limit this by restricting the App's network access, in which case the App falls back to a generic or manually relevant set of stations.

9. Connecting to Radio Browser and to broadcasters' streams

The Apps are directory/aggregators. To provide station listings, the Apps read station metadata — such as station name, country, codec/bitrate, and logo/favicon URL — from the Radio Browser community database and API (the open-source radio-browser.info project; requests are served from community-operated hosts). When an App contacts Radio Browser, it sends a standard HTTP request that includes a User-Agent identifying the App and platform and your device's IP address (as any internet request does). Radio Browser is an independent third party; its handling of requests is governed by its own practices. These directory requests are necessary for the Apps to function and are not tied to your analytics-consent choice.

When you play a station, your device streams the audio directly from the broadcaster's own stream URL, and station logos are loaded directly from the image servers referenced in the station's metadata. We do not route, host, store, or proxy the audio or the images. Because these connections are made directly to third parties we do not control, the audio streams, playlist files, and station artwork/logos may be delivered over unencrypted (HTTP) connections, which is outside our control. The broadcaster, its hosting/streaming provider, and any logo/image host may receive your IP address and connection information as part of delivering that content, exactly as occurs with any direct web connection. Each such third party's processing of your information is governed by its own privacy practices, over which we have no control. Listening to a station through an App is equivalent to connecting to that station directly.

10. Purposes and legal bases for processing

We process the limited personal information described above for the following purposes:

For operational configuration and residual Cast diagnostics in the Apple Apps, our interest is reliable catalogue access, timely handling of accepted station removals, and working receiver compatibility. Our App does not add custom user IDs, station or search parameters to diagnostics or use these services for advertising profiles or cross-company tracking. We disable optional Cast discovery-diagnostic logging. We considered fixed server routing, app-update-only removal and omitting Cast: these would reduce timely removal handling or the requested output functionality. This limited reliability processing remains separate from optional usage Analytics and optional Apple crash reports. You may object to processing based on legitimate interests by contacting us; we will assess your circumstances and applicable law. A radio stream selected for Cast is transmitted to the receiver you choose, not to our library or analytics systems.

Where we rely on legitimate interests, we have considered your rights and interests and limited our processing accordingly. Analytics relies on your consent, which you give (or decline) during setup and can change at any time in Settings; withdrawing consent does not affect the lawfulness of any processing carried out before withdrawal.

11. Retention

• Locally stored data (recently played, favorites, custom stations, settings) is retained on your device until you clear it or uninstall the App. We never receive it.
• Analytics data processed through Firebase Analytics is retained according to Firebase's retention settings — currently a default of two months for event- and user-level data, configurable up to fourteen months — after which it is deleted or retained only in aggregated form.
• Crash/diagnostic data processed through Crashlytics is subject to Google/Firebase deletion beginning after 90 days.

We keep personal information only as long as necessary for the purposes described in this Policy or as required by law, after which it is deleted or anonymized.

12. International data transfers

We are based in Canada. The Radio Browser project is operated outside Canada, the IP-geolocation provider may process requests outside Canada, and Google/Firebase processes analytics, crash, messaging, and configuration data on servers in the United States and other countries. As a result, the limited information described in this Policy may be processed in, or transferred to, jurisdictions whose data-protection laws differ from those of your home jurisdiction, and where courts, law enforcement, and national-security authorities may, in certain circumstances, be able to access it.

When personal information is transferred internationally, we rely on appropriate safeguards. For transfers from the EEA/UK, transfers to Google are made under recognized transfer mechanisms (such as the European Commission's Standard Contractual Clauses and/or an applicable adequacy framework). For Canadian users, we remain accountable under PIPEDA for information transferred to our service providers for processing. For Quebec users, transfers outside Quebec are assessed in accordance with Law 25.

13. Security

We take reasonable technical and organizational measures appropriate to the limited personal information involved. Connections between the App and the services described in this Policy — Radio Browser, the IP-geolocation provider, and Google/Firebase — use HTTPS encryption in transit. Because we operate no user accounts and store no central database of personal information, the personal-information attack surface is minimal. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security. Audio streams are delivered directly by broadcasters, and station artwork/logos are loaded directly from third-party image hosts; these third-party connections may not always be encrypted, which is outside our control.

14. Your privacy rights

Depending on where you live, you may have some or all of the following rights regarding personal information we control: to access it; to correct it; to delete it; to withdraw consent; to object to or restrict processing; to data portability; and to lodge a complaint with a regulator.

Because we hold almost no identifiable information about individual users (no accounts; local-only storage; pseudonymous analytics and crash identifiers), in many cases we may be unable to locate information that identifies you specifically. You can, however, exercise direct control over the main data flows yourself:

• Analytics: turn it off at any time in Settings → Privacy (this stops optional usage-analytics collection going forward; operational configuration and applicable SDK diagnostics are separate), or decline it during setup.
• Apple crash reports: decline them during setup or turn them off in Settings → Privacy. The next launch discards still-unsubmitted pending reports and does not authorize a new batch. Already-authorized uploads may finish; previously transmitted reports are handled under applicable retention and deletion rules.
• Locally stored data: clear it in the App, clear the App's storage, or uninstall the App.

To exercise any right that requires our action, email [email protected]. We will respond within the timeframe required by applicable law (for example, within 30 days under PIPEDA and Quebec Law 25, and within one month under the GDPR). We will not discriminate or retaliate against you for exercising your rights.

14.1 Canada — PIPEDA

We handle personal information in accordance with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and its fair information principles, including accountability, identifying purposes, consent, limiting collection, limiting use/disclosure/retention, accuracy, safeguards, openness, individual access, and challenging compliance.

• Accountability / privacy contact. The individual accountable for our privacy compliance can be reached at [email protected].
• Access and correction. You may request access to, or correction of, personal information under our control.
• Complaints. If you are not satisfied with our response, you may complain to the Office of the Privacy Commissioner of Canada (OPC) — www.priv.gc.ca; 30 Victoria Street, Gatineau, Quebec K1A 1H3; 1-800-282-1376.

14.2 Quebec — Law 25 (Loi 25)

If you reside in Quebec, the Act respecting the protection of personal information in the private sector, as amended by Law 25, applies. The person responsible for the protection of personal information is reachable at [email protected]. You have rights of access, rectification, withdrawal of consent, and (subject to legal conditions) de-indexation and portability. We assess transfers of personal information outside Quebec as required by Law 25. You may file a complaint with the Commission d'accès à l'information du Québec (CAI) — www.cai.gouv.qc.ca.

14.3 EU / EEA / United Kingdom — GDPR / UK GDPR

If you are in the EEA or the UK, Probed Studios Inc. is the data controller for the limited processing described in this Policy. Our purposes and legal bases are set out in Section 10. You have the rights of access, rectification, erasure, restriction, objection, portability, and (where processing is based on consent, such as analytics) withdrawal of consent at any time without affecting prior lawful processing. You also have the right to lodge a complaint with your local supervisory authority (in the EEA, your national Data Protection Authority; in the UK, the Information Commissioner's Office, ico.org.uk). International transfers are addressed in Section 12.

14.4 California — CCPA / CPRA

This section applies to California residents under the California Consumer Privacy Act, as amended by the CPRA.

• Categories of personal information collected. In the past 12 months, the App has collected, at most: identifiers / device identifiers (e.g., the pseudonymous Firebase app-instance identifier, the Crashlytics installation UUID, the Firebase Cloud Messaging registration token, and the IP address inherent to internet requests); internet/electronic activity (e.g., the analytics events described in Section 5 and crash/diagnostic logs); and coarse geolocation (approximate country, used to show local stations). We do not collect sensitive personal information for the purpose of inferring characteristics.
• Sources. Directly from your device and via our service providers (Google/Firebase; the IP-geolocation provider).
• Business/commercial purposes. To provide and maintain the App, understand usage (with your consent, for analytics), and ensure stability and security (Sections 5–10).
• Disclosures. We disclose data to our service providers (Google/Firebase; the IP-geolocation provider) for the purposes above. We do not sell and do not share (for cross-context behavioral advertising) personal information, and we have not done so in the preceding 12 months.
• Your rights. You have the rights to know/access, to delete, to correct, to opt out of sale/sharing (not applicable, as we do neither), to limit use of sensitive personal information (not applicable), and to non-discrimination.
• How to exercise. Email [email protected]. We will verify and respond as required by law.

15. Children's privacy

The App is a general-audience application and is not directed to children under 13. We do not knowingly collect personal information from children. The App contains no behavioral advertising, no accounts, and no social features.

Consistent with the U.S. Children's Online Privacy Protection Act (COPPA), the Google Play Families policy, and applicable local law, we set a minimum age of 13 to use the App (or higher where your local law sets a higher age of digital consent — for example, 16 in parts of the EEA). If you are under the applicable age, please do not use the App. If we learn that we have inadvertently processed personal information from a child below the applicable age in a manner requiring deletion, we will take reasonable steps to delete it. Parents or guardians who believe a child has provided personal information may contact us at [email protected].

16. What we do NOT do

• We do not display advertising and we do not integrate advertising or ad-identifier SDKs (such as AdMob).
• We do not sell or “share” (as defined under California law) your personal information.
• We do not create marketing profiles, perform cross-context behavioral advertising, or engage in automated decision-making that produces legal or similarly significant effects about you.
• We do not collect optional usage analytics unless you opt in. Operational configuration and applicable SDK diagnostics are separately disclosed in Section 1.2 for the Apple Apps.
• We do not knowingly collect personal information from children (see Section 15).

Future changes. If a future version of an App introduces advertising or any other materially different data practice, we will update this Privacy Policy and the applicable Google Play Data Safety or Apple App Privacy disclosures before that version ships, and we will obtain any consent required by applicable law.

17. Third-party services and links

The Apps rely on the Radio Browser community database, an IP-geolocation provider, Google/Firebase services (Analytics, Crashlytics, Android Cloud Messaging, and Remote Config), Apple system services, and Google Cast, and connect you to independent broadcasters' streams and logo hosts. These third parties — and any websites or resources they link to — are not operated by us and have their own privacy practices, for which we are not responsible. Google's processing of Firebase and Cast data and Apple's processing of Siri, Shortcuts, Watch Connectivity, and AirPlay interactions are also governed by their respective terms and privacy documentation. We encourage you to review their policies.

18. Changes to this Privacy Policy

We may update this Policy from time to time. When we do, we will revise the “Effective date” above and post the current version at the in-App link and at the publicly accessible URLs referenced in our app-store listings. Material changes (including any introduction of advertising) will be reflected before the relevant App version ships, together with any updates to Google Play Data Safety or Apple App Privacy disclosures.

19. Contact us

Probed Studios Inc.
Ontario, Canada
Email (all privacy matters, including access requests and complaints): [email protected]

© 2026 Probed Studios Inc. · Global Radio Plus