Privacy Policy for Profile Equalizer: EQ & Player and Profile Equalizer Pro

Last updated: July 7, 2026

This Privacy Policy applies to the Android apps “Profile Equalizer: EQ & Player” and “Profile Equalizer Pro” in their current versions and, where technically applicable, to older app versions that are still installed.

Individual functions, services, permissions or privacy options may differ depending on the app version, Android version, device configuration, region and user selection. We recommend keeping the app up to date so that the latest features, security improvements and privacy options are available.

1. Controller

The controller responsible for data processing is:

Androho Software – Matthias Höpfler

Ziegelweg 1

84164 Moosthenning

Germany

E-Mail: info@androho.com

Website: www.androho.com

2. General data processing in the app

The app can generally be used without creating a separate user account. No account is created with Androho Software. We do not operate our own cloud storage for user data in this app.

Many app data items are stored exclusively locally on the device, for example:

equalizer profiles
presets
app settings
Bluetooth assignments
playlists and local playback data
favorites
podcast subscriptions and saved podcast episodes
imported visualizer files
local backups or exports

These locally stored data are not automatically transferred by us to our own servers.

3. Differences between the Lite version and the Pro version

Profile Equalizer: EQ & Player (“Lite version”)

The Lite version may use the following services:

Google Firebase Analytics
Google Firebase Crashlytics
Google AdMob
AdMob mediation partners such as Pangle and Meta Audience Network
Google User Messaging Platform / Consent SDK
Google Play Billing for in-app purchases
Google Play services for app updates and in-app reviews
PodcastIndex.org, Radio-Browser.info and external podcast, radio, streaming and image servers

Profile Equalizer Pro (“Pro version”)

The Pro version is ad-free. In the current Pro version, no advertising services such as Google AdMob, Pangle or Meta Audience Network are used.

The current Pro version also does not use Firebase Analytics processing or Firebase Crashlytics processing, provided that these services are technically removed or disabled in the Pro version.

The Pro version may still use online functions, for example podcast search, radio search, podcast downloads, radio streams, cover images, station logos, Google Play app updates and in-app reviews.

4. App permissions

Depending on the Android version, app version and feature used, the app may use the following permissions:

Internet and network status

The INTERNET and ACCESS_NETWORK_STATE permissions are used to provide online functions, for example podcast search, radio search, streaming, downloads, cover images, advertising in the Lite version, app updates, crash reporting and analytics functions.

Microphone / audio recording

The RECORD_AUDIO permission may be used for audio analysis, equalizer, visualizer or similar audio functions. The app does not transmit microphone recordings to our own servers. Audio analysis for the relevant function is performed locally on the device.

Bluetooth

The BLUETOOTH, BLUETOOTH_ADMIN and BLUETOOTH_CONNECT permissions may be used to detect Bluetooth audio devices, take connections into account and enable automatic profile switching for certain devices. Bluetooth assignments are generally stored locally on the device.

Audio settings

The MODIFY_AUDIO_SETTINGS permission is used to provide audio functions in the app and adjust audio output parameters.

Storage access and files

The READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permissions may be used on older Android versions for file, import, export, backup or restore functions. This may include local audio files, playlists, app backups or visualizer files. These files are not automatically transferred to our own servers.

Foreground services, media playback and battery

The FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PLAYBACK, FOREGROUND_SERVICE_DATA_SYNC, FOREGROUND_SERVICE_CONNECTED_DEVICE, WAKE_LOCK and REQUEST_IGNORE_BATTERY_OPTIMIZATIONS permissions may be used so that audio functions, media playback, downloads, Bluetooth functions or ongoing app functions can run more reliably.

Notifications

The POST_NOTIFICATIONS permission may be used to display notifications, for example for active audio functions, media playback, downloads, timers or profile changes.

Notification access

The BIND_NOTIFICATION_LISTENER_SERVICE permission only becomes active if users explicitly enable notification access in the Android system settings. This function may be used to react to media notifications or playback status from other apps. Notification access is not used to transmit notification contents to our own servers.

Automatic start after device restart

The RECEIVE_BOOT_COMPLETED permission may be used to restore necessary app states or notices after a device restart, where enabled by the user or required for app functions.

Vibration

The VIBRATE permission may be used for haptic feedback within the app.

Advertising ID

The com.google.android.gms.permission.AD_ID permission is used only in the Lite version for advertising, ad measurement, fraud prevention and related Google services. The Pro version does not use this permission, provided that advertising and analytics SDKs are technically removed or disabled there.

5. Firebase Analytics – Lite version only

The Lite version may use Google Firebase Analytics. In current app versions, Firebase Analytics is used in the EU/EEA on the basis of consent where consent is required and where the corresponding consent function is available in the respective app version.

The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Firebase Analytics may process pseudonymous usage data, for example:

app interactions
app starts
screen and session information
technical device information
app version
approximate region derived from technical connection data
device or app IDs such as app instance ID or Firebase installation ID
events related to app functions, where such events are collected in the app

The purpose of processing is to analyze app usage, improve functions, detect technical problems and further develop the app.

In the EU/EEA, this processing takes place only on the basis of your consent where consent is required. You can change your consent in the app settings where the app provides this setting.

The legal basis is Article 6(1)(a) GDPR where consent is obtained. Where processing without consent is legally permitted, Article 6(1)(f) GDPR may be the legal basis. Our legitimate interest lies in improving and stabilizing the app.

6. Firebase Crashlytics – Lite version only

The Lite version may use Google Firebase Crashlytics for crash reporting. In current app versions, Crashlytics is used in the EU/EEA on the basis of consent where consent is required and where the corresponding consent function is available in the respective app version.

The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Crashlytics may process the following data:

crash logs
stack traces
app version
device type
operating system version
time of a crash
technical diagnostic data
Crashlytics installation ID
relevant technical app states at the time of an error

The purpose is to detect, analyze and fix crashes and technical errors.

In the EU/EEA, Crashlytics is used only on the basis of your consent where the app is configured accordingly. You can change your consent in the app settings where the app provides this setting.

7. Advertising with Google AdMob – Lite version only

The Lite version may use Google AdMob to display advertising. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

The following data may be processed:

advertising ID of the device
IP address
approximate location data derived from technical connection data
device information
app information
ad impressions
ad interactions
diagnostic and performance data
fraud prevention and security data

The purposes of processing are:

displaying advertising
personalizing advertising, if you have consented
measuring ad performance
limiting and controlling ads
fraud prevention, security and compliance
financing and further developing the free Lite version

In the EU/EEA, personalized advertising is used only on the basis of your consent. If you do not consent, non-personalized ads may be displayed where technically and legally possible.

The legal basis for personalized advertising is Article 6(1)(a) GDPR. For non-personalized advertising, technical ad delivery, security and fraud prevention, Article 6(1)(f) GDPR may be the legal basis.

8. AdMob mediation: Pangle and Meta Audience Network – Lite version only

The Lite version may include additional advertising partners via Google AdMob, in particular:

Pangle
Meta Audience Network

These partners may be involved in ad delivery and ad measurement through AdMob mediation. Depending on consent, region, device settings and ad request, technical data, advertising IDs, ad interactions, device information, diagnostic information and approximate location data may be processed.

Processing is carried out for ad delivery, ad measurement, fraud prevention, security and compliance. In the EU/EEA, personalized advertising is used only on the basis of your consent.

9. Consent management – Lite version

In current versions of the Lite version, users who are shown a consent dialog or privacy options can grant, refuse or later change consent for advertising, analytics and crash reporting. Changes can be made in the app settings where this function is available in the respective region, app version and device configuration.

Without consent, certain data processing may be disabled or may only take place in a limited manner. Some technically necessary processing may still be required, for example for security, fraud prevention, app functionality or non-personalized advertising.

10. In-app purchases – Lite version only

The Lite version may offer in-app purchases via Google Play Billing, for example to unlock ad-free or extended functions.

Payment processing is carried out by Google Play. We do not receive full payment details such as credit card or bank account data.

However, we may receive or view technical purchase and order information in the Google Play Console where this is required for unlocking, restoring, support, fraud prevention, accounting or legal documentation purposes. This may include:

purchase status
product ID
order time
price and currency
country or region
location or postal code information provided by Google, where applicable
order or transaction identifiers

The legal bases are Article 6(1)(b) GDPR for contract performance, Article 6(1)(c) GDPR for legal obligations and Article 6(1)(f) GDPR for fraud prevention, support and documentation purposes.

11. Google Play services for reviews and app updates

The app may use Google Play services for in-app reviews and app updates. Technical data may be transmitted to Google where necessary to provide these functions.

The purpose is to provide app updates, security improvements and review functions.

12. Podcast search, podcast downloads and podcast content

The app may use external services to search, display, download and play podcasts, podcast episodes and podcast metadata.

PodcastIndex.org

PodcastIndex.org may be used for podcast search and podcast metadata. When using podcast search, search terms, filter information, technical connection data such as IP address, time of request, device/app information and technically required request information may be transmitted to PodcastIndex.org.

Podcast providers, hosting providers and CDNs

Podcast titles, descriptions, cover images, episode information and audio files are provided by the respective podcast providers, publishers, hosting providers or CDN providers.

When displaying, playing or downloading podcast episodes, the app connects to the servers of the respective providers. These providers may process technical connection data such as IP address, time of request, requested file/URL, user agent, device/app information and similar technical data.

Podcast episodes may be stored locally on the device at the user’s request. These locally stored files are not automatically transferred by us to our own servers.

13. Radio search and radio streams

The app may use external services to search, display and play internet radio stations.

Radio-Browser.info

Radio-Browser.info may be used for radio search and station metadata. When using radio search, search terms, filter information, technical connection data such as IP address, time of request, device/app information and technically required request information may be transmitted to Radio-Browser.info or to a Radio-Browser API server.

Radio streams

Radio streams are provided by the respective radio stations or streaming providers. When playing a radio stream, the app connects to the relevant stream server. These providers may process technical connection data such as IP address, time of request, stream URL, user agent, device/app information and similar technical data.

The app does not provide a radio recording function. Radio streams are not saved as files unless a separately described function is expressly provided for this purpose.

14. Cover images, station logos, favicons and external images

Podcast covers, episode images, station logos, favicons or other external images may be loaded from the servers of the respective providers and cached locally. This may establish a connection to image, podcast, radio, hosting or CDN servers.

These providers may process technical connection data such as IP address, time of request, requested URL, user agent and similar technical data.

15. Unencrypted HTTP connections for external content

Many connections used by the app and by Google services are encrypted via HTTPS/TLS.

However, external podcast feeds, radio streams, cover images, station logos or other external content may sometimes be provided only via HTTP, or users may access content via HTTP. Such HTTP connections are not encrypted in transit.

We have no control over whether external podcast providers, radio stations, hosting providers or streaming providers make their content available exclusively via encrypted connections.

16. Local files, music files, playlists and visualizer files

The app may use local audio files, playlists, backup files or visualizer files if users select, import or save them themselves.

These files are generally processed locally on the device. We do not automatically transfer local audio files, music files, playlists or visualizer files to our own servers.

If technical errors occur and crash reporting is enabled in the Lite version, technical diagnostic data may be processed. We recommend not using personal information in file names or imported files.

17. Recipients and categories of recipients

Depending on the app version and function used, data may be transferred to the following recipients or categories of recipients:

Google Ireland Limited
Google LLC
Google Play services
Google AdMob, Lite version only
AdMob mediation partners such as Pangle and Meta Audience Network, Lite version only
Firebase Analytics, Lite version only
Firebase Crashlytics, Lite version only
PodcastIndex.org
Radio-Browser.info and its API servers
podcast providers, publishers, hosting providers and CDN providers
radio stations and streaming providers
Google Play payment and processing services, only where relevant for purchases

18. International data transfers

When using external services, personal data may be transferred to countries outside the European Union or the European Economic Area, in particular to the United States.

Such transfers may take place on the basis of appropriate safeguards, for example adequacy decisions, the EU-U.S. Data Privacy Framework, standard contractual clauses or other legally provided mechanisms.

For external podcast, radio, streaming, hosting or CDN providers, the location of processing depends on the respective provider. We have only limited influence over these external providers.

19. Storage periods

Local app data generally remain stored on the device until users delete them in the app, delete the app data via the Android settings or uninstall the app.

Podcast downloads, locally stored files, playlists, profiles, presets, favorites, Bluetooth assignments, imported visualizer files and local backups remain stored until users delete them themselves or the app data are removed.

Firebase Analytics data in the Lite version are stored according to the data retention settings configured in Google Analytics/Firebase. The retention period for user-level and event-level Analytics data is currently set to 2 months. Aggregated standard reports may remain visible for longer.

Firebase Crashlytics data in the Lite version are generally stored for 90 days before Firebase begins removing crash data and associated identifiers from live and backup systems.

Google Play purchase, payment, billing and order data may be stored according to statutory retention periods, tax obligations, Google policies and billing requirements.

The Google Play Console may show us aggregated statistics and reports about app usage, installations, uninstallations, performance, stability, reviews, purchases and revenue. Depending on the Google feature, reporting period, minimum thresholds and account settings, these reports may be available for different periods of time.

Data processed by external podcast, radio, streaming, hosting or CDN providers are subject to the privacy policies and retention periods of the respective providers.

20. Legal bases for processing

Where applicable, personal data is processed on the following legal bases:

Processing activity	Legal basis
Displaying and technically providing advertising in the Lite version	Article 6(1)(a) GDPR where consent is required, in particular for personalized advertising; additionally Article 6(1)(f) GDPR for technically required ad delivery, fraud prevention, security and abuse detection
Firebase Analytics in the Lite version	Article 6(1)(a) GDPR where consent is obtained
Firebase Crashlytics in the Lite version	Article 6(1)(a) GDPR where consent is obtained; otherwise, where legally permitted, Article 6(1)(f) GDPR for crash analysis, app stability and technical security
In-app purchases in the Lite version	Article 6(1)(b) GDPR for contract performance and unlocking purchased features; Article 6(1)(c) GDPR for statutory retention obligations; Article 6(1)(f) GDPR for support, documentation purposes and fraud prevention
Podcast search, radio search, streaming, podcast downloads, cover images and station logos	Article 6(1)(b) GDPR for providing the app functions requested by the user; Article 6(1)(f) GDPR for technical provision, stability and troubleshooting
Local app functions, profiles, presets, playlists, Bluetooth assignments, settings, imported files and local backups	Article 6(1)(b) GDPR for providing the app functions
App updates and in-app reviews via Google Play	Article 6(1)(f) GDPR for providing updates, security improvements, user feedback and further app development
Compliance with legal obligations, accounting and documentation requirements	Article 6(1)(c) GDPR

Where processing is based on Article 6(1)(f) GDPR, our legitimate interest lies in particular in the technical provision and improvement of the app, the stability and security of the app, troubleshooting, fraud prevention, support, financing the free Lite version and further developing the app.

21. User rights

Subject to the conditions of the GDPR, you have the following rights in particular:

right of access
right to rectification
right to erasure
right to restriction of processing
right to data portability
right to object to certain processing activities
right to withdraw consent with effect for the future
right to lodge a complaint with a data protection supervisory authority

If you would like to submit a privacy request, please contact us at:

info@androho.com

Please note that many app data are stored only locally on your device. This includes, for example, equalizer profiles, presets, app settings, playlists, favorites, podcast subscriptions, saved podcast episodes, imported files and local backups. We do not have access to these local data. You can delete such data directly in the app, via the Android app settings or by uninstalling the app.

Where personal data is processed through Google services, such as Google Play, Google AdMob, Firebase Analytics or Firebase Crashlytics, the handling of access or deletion requests depends on whether we can technically associate the relevant data with a specific person. Many of these data are processed pseudonymously, device-related or in aggregated form. If we cannot identify a data subject based on the data available to us, we will inform you accordingly. In that case, we can only process a request if you provide us with additional information that enables attribution, where this is legally permitted and necessary.

Where data is processed directly by Google or other third-party providers as independent controllers, you may also exercise your rights directly against those providers. This applies in particular to Google account data, payment data, advertising settings and device settings.

Statutory retention obligations, in particular for purchase, billing, tax or accounting data, may mean that certain data cannot be deleted immediately.

22. Changing consent and privacy options

In the Lite version, users who are shown a consent dialog or privacy options can grant, refuse or later change consent for advertising, analytics and crash reporting. Changes can be made in the app settings where this function is available in the respective region, app version and device configuration.

Withdrawal of consent applies with effect for the future. The lawfulness of processing carried out on the basis of consent before withdrawal remains unaffected.

In addition, you can manage the advertising ID, personalized advertising and other privacy options in the Android or Google settings of your device.

In the current Pro version, no advertising services, no Firebase Analytics processing and no Firebase Crashlytics processing are used, provided that these services are technically removed or disabled there. Therefore, the Pro version generally does not display a consent dialog for advertising, analytics or crash reporting.

23. Changes to this Privacy Policy

We may update this Privacy Policy if app functions, services used, legal requirements or technical processes change. The current version will be made available on our website.