Privacy Policy

1. Controller

Androho Software – Matthias Höpfler
Ziegelweg 1
84164 Moosthenning
Germany

2. Processing of Personal Data on This Website

2.1 Hosting

Hosting by Hostinger

We host our website with the service provider Hostinger Operations, UAB, Švitrigailos g. 34, 03230 Vilnius, Lithuania (hereinafter referred to as “Hostinger”).

When you visit our website, Hostinger collects various log files, including your IP addresses.

For more details, please refer to the Hostinger privacy policy: https://www.hostinger.com/legal/privacy-policy.

The use of Hostinger is based on Art. 6 (1) (f) GDPR. We have a legitimate interest in the most reliable presentation of our website. If appropriate consent has been obtained, the processing is carried out exclusively on the basis of Art. 6 (1) (a) GDPR; this consent can be revoked at any time.

Data Processing Agreement

We have concluded a Data Processing Agreement (DPA) with the above-mentioned provider. This is a contract required by data protection law, which guarantees that the provider processes the personal data of our website visitors only in accordance with our instructions and in compliance with the GDPR.

2.2 Server Log Files

When accessing the website, the following data are automatically collected and stored in server log files:

IP address
Date/time of access
Accessed page/file
Referrer URL
Browser type/version
Operating system

Purpose/Legal basis: Ensuring technical operation and IT security (Art. 6 (1) lit. f GDPR).
Retention: Up to 14 days.

2.3 Cookies

We only use technically necessary cookies (e.g., to secure the contact form or for session management). These do not require user consent.
No analytics or marketing cookies are used on this website.

2.4 Contact Form and E-Mail

If you use the contact form or send us an e-mail directly, the following data will be processed:

E-mail address
Content of the message
Name (optional)

Purpose/Legal basis: Response to your inquiry, Art. 6 (1) lit. b GDPR (pre-contractual communication) or Art. 6 (1) lit. f GDPR (general inquiries).
Retention: Until the request has been handled, and thereafter according to statutory retention obligations.

3. Processing of Personal Data in Our Apps

This privacy notice applies to the following apps:

Profile Equalizer: Audio EQ (com.androho.profileequalizer)
Profile Equalizer Pro (com.androho.profileequalizerpro)
Level Buddy (com.androho.levelbuddy)
Video Converter & Compressor (com.androho.simplevideoconverter)

3.1 Firebase Analytics (Profile Equalizer: Audio EQ & Profile Equalizer Pro)

We use Google Firebase Analytics (Google Ireland Ltd., Dublin, Ireland).

Data: pseudonymous usage data (app events, screens, interactions), app instance ID, device information, country/region.
Purpose: Analysis of app usage to improve functionality and stability.
Legal basis: In the EU/EEA based on consent (Art. 6 (1) lit. a GDPR) via the Consent SDK; outside the EU/EEA based on Art. 6 (1) lit. f GDPR.
Retention: 2–14 months depending on Firebase configuration.

3.2 Firebase Crashlytics (Profile Equalizer: Audio EQ & Profile Equalizer Pro)

We use Google Firebase Crashlytics for error analysis.

Data: crash reports, device type, OS version, timestamps, stack traces.
Purpose: Improving app stability.
Legal basis: Legitimate interest (Art. 6 (1) lit. f GDPR).

3.3 Google AdMob (Profile Equalizer: Audio EQ)

The Lite version uses Google AdMob for advertising.

Data: advertising ID (AAID), IP address, device data, inferred location, ad interactions.
Legal basis: In the EU/EEA only with consent (Art. 6 (1) lit. a GDPR) via the Google UMP/Consent SDK. Without consent, only non-personalized ads are shown.

3.4 Podcast and radio search (Profile Equalizer: Audio EQ & Profile Equalizer Pro)

The Profile Equalizer apps may use external services to search for, display and play podcasts, podcast episodes and internet radio stations.

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

Podcast content:
Podcast titles, descriptions, artwork, episode information and audio files are provided by the respective podcast providers, publishers or hosting providers. When 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, request time, requested file/URL, device/app information and similar technical data.

Radio-Browser.info:
We use Radio-Browser.info for radio station search and station metadata. When using radio search, search terms, filter settings, technical connection data such as IP address, request time, device/app information and technically required request information may be transmitted to Radio-Browser.info or one of the Radio-Browser API servers.

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

The app does not provide a radio recording feature. Radio streams are not stored as files unless a separately described and legally reviewed feature is provided for this purpose.

Artwork, station logos and favicons:
Podcast artwork, episode images, station logos or favicons may be loaded from external servers and cached locally. This may establish a connection to the respective image, podcast, station or hosting servers.

Local storage:
Favorites, search results, saved podcast episodes, playback data and related metadata may be stored locally on the device where required for the respective feature. This data is not transmitted by us to our own servers.

Note:
Podcast and radio content, descriptions, artwork, audio files and streams are provided by the respective providers. Availability and content may change over time.

3.5 In-app purchases, reviews and updates

In the app “Profile Equalizer: Audio EQ”, in-app purchases may be offered via Google Play Billing. These purchases may be used, among other things, to upgrade the app to Pro features or an ad-free Pro version.

Payment processing is carried out via Google Play. We do not receive full payment details such as credit card or bank account information. However, we may receive technical information about the purchase status where required to unlock, restore or manage purchased features.

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

3.4 App Permissions (Profile Equalizer: Audio EQ & Profile Equalizer Pro)

IINTERNET – required for Firebase services, advertising in the app “Profile Equalizer: Audio EQ”, podcast search, radio search, playback of external streams, podcast downloads, artwork, updates and online features.
ACCESS_NETWORK_STATE – checks the network status in order to execute online features only when a connection is available or to better handle connection errors.
RECORD_AUDIO – audio analysis for equalizer, visualizer or similar audio features. The app does not transmit microphone recordings to our own servers.
BLUETOOTH / BLUETOOTH_ADMIN / BLUETOOTH_CONNECT – detection, connection and assignment of Bluetooth audio devices, for example for automatic profile switching.
MODIFY_AUDIO_SETTINGS – control and adjustment of audio output parameters.
READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE – access to files for backup/restore, local file, import or export features on older Android versions.
FOREGROUND_SERVICE – execution of required app features in the foreground.
FOREGROUND_SERVICE_MEDIA_PLAYBACK – media playback and audio features in the foreground.
FOREGROUND_SERVICE_DATA_SYNC – data-related foreground processes, such as downloads or synchronization processes, where used by the app.
FOREGROUND_SERVICE_CONNECTED_DEVICE – foreground processes related to connected devices, especially Bluetooth audio devices.
WAKE_LOCK – maintaining certain functions, such as sleep timer, playback, downloads or ongoing audio features.
VIBRATE – haptic feedback within the app.
MEDIA_CONTENT_CONTROL – control of or response to media playback, where supported by the system.
POST_NOTIFICATIONS – display of notifications, for example for active equalizer processes, media playback, profile changes, downloads or timers.
BIND_NOTIFICATION_LISTENER_SERVICE – only with explicit activation by the user in the Android system settings, where notification-related features are used.
RECEIVE_BOOT_COMPLETED – may be used to restore required app states or notifications after a device restart, where activated by the user or required.
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS – may be used to ask the user for an exemption from battery optimizations so that background, audio or media features run more reliably.
com.google.android.gms.permission.AD_ID – used only in the app “Profile Equalizer: Audio EQ” for Google AdMob/advertising features.

3.7 Recipients and third-country transfers (Profile Equalizer: Audio EQ & Profile Equalizer Pro)

Depending on the feature used, data may be transmitted to the following recipients or categories of recipients:

Google Ireland Ltd., Dublin, Ireland
Google LLC, Mountain View, CA, USA
PodcastIndex.org and its technical operators
Radio-Browser.info and its API servers
Podcast providers, podcast hosting providers and CDN providers
Radio stations and streaming providers
Google Play services for in-app purchases, reviews and updates

Transfers to third countries, in particular the USA, may take place on the basis of the EU-U.S. Data Privacy Framework, standard contractual clauses or other legally provided safeguards.

3.8 Consent Management (Profile Equalizer: Audio EQ & Profile Equalizer Pro)

Upon first launch (EU/EEA), a consent dialog (Google UMP/Consent SDK) is displayed.

Users may grant or refuse consent for analytics/ads.
Consent can be withdrawn or changed at any time in the app settings.

3.9 Firebase Analytics & Crashlytics (Level Buddy)

We use Google Firebase Analytics and Crashlytics (Google Ireland Ltd., Dublin, Ireland).

Analytics data: pseudonymous usage data (app events, screens, interactions), app instance ID, device information, country/region.
Crashlytics data: crash reports, device type, OS version, timestamps, stack traces.
Purpose: Analysis of app usage, improvement of stability and functionality.
Legal basis: In the EU/EEA based on consent (Art. 6 (1) lit. a GDPR) via the Consent SDK; outside the EU/EEA based on Art. 6 (1) lit. f GDPR.

3.10 Google AdMob & In-App Purchases (Level Buddy)

The app uses Google AdMob to display advertisements. An in-app purchase allows users to remove ads.
Prices are adjusted per country based on the average per capita income.

Advertising data: advertising ID (AAID), IP address, device data, inferred location, ad interactions.
Legal basis: In the EU/EEA only with consent (Art. 6 (1) lit. a GDPR). Without consent, only non-personalized ads are shown.

3.11 App Permissions (Level Buddy)

INTERNET / ACCESS_NETWORK_STATE – required for advertisements.
CAMERA – optional, for camera-based angle measurement.

3.12 Google AdMob (Science & IT News)

Science & IT News uses Google AdMob for advertising purposes. Data: Advertising ID (AAID), IP address, device data, location (inferred), and ad interactions. Legal Basis: In the EU/EEA, this data is only processed with your consent (Art. 6 (1) (a) GDPR) via the Google UMP/Consent SDK. If consent is not provided, only non-personalized ads will be displayed. You can restrict the use of the Advertising ID at any time in your device’s Android system settings.

3.13 Firebase Analytics & Crashlytics (Science & IT News)

We use Google Firebase Analytics and Crashlytics (provided by Google Ireland Ltd., Dublin, Ireland). Analytics Data: Pseudonymous usage data (app events, screens, interactions), App Instance ID, device information, and country/region. Crashlytics Data: Crash reports, device type, OS version, timestamps, and stack traces. Purpose: To analyze app usage and improve stability and features. Legal Basis: In the EU/EEA, this processing is based on your consent (Art. 6 (1) (a) GDPR) via the Consent SDK; outside the EU/EEA, it may be based on our legitimate interest (Art. 6 (1) (f) GDPR).

3.14 Permissions (Science & IT News)

INTERNET / ACCESS_NETWORK_STATE – Required for displaying advertisements and retrieving RSS feeds.

3.15 Integration of Third-Party Content (RSS Feeds) (Science & IT News)

This app displays short summaries (RSS feeds) from external news providers. When you access a full article, you will be redirected to the website of the respective provider. From that moment on, the privacy policies of the respective website operator apply. We have no influence over the data collection practices of these external providers.

3.16 Local Storage (Bookmarks) (Science & IT News)

The bookmarking feature for news articles stores the corresponding links and titles exclusively locally in a protected area on your device. No transmission of this selection to our servers takes place.

3.17 Processing of Personal Data in the App “Video Converter FFmpeg”

The following privacy notices also apply to the app “Video Converter FFmpeg.” The related open-source project is published under the name “SimpleVideoConverter.”

3.18 Local Processing of Video Files (Video Converter FFmpeg)

The app allows users to select, trim, convert, and save video files on their device. The actual media processing is performed locally on the device using FFmpeg / FFmpegKit. Based on the documented functionality of the app, no server-side video conversion is carried out by us.

If files selected by the user contain personal data (for example, private videos), such processing is carried out solely for the purpose of performing the function initiated by the user within the app.

3.19 Permissions (Video Converter FFmpeg)

The app uses the following permissions:

INTERNET – required for the integration of Google AdMob and Google Analytics for Firebase.
com.google.android.gms.permission.AD_ID – required to process the Advertising ID for advertising and measurement purposes, insofar as this is technically intended and legally permissible.
READ_EXTERNAL_STORAGE (up to Android 12L / API 32) and READ_MEDIA_VIDEO – required so that video files selected by the user can be read and processed for conversion.
WRITE_EXTERNAL_STORAGE (up to Android 9 / API 28) – required to save exported video files to device storage on older Android versions.

Access to media files takes place only to the extent necessary for the selection, processing, or storage of video files requested by the user.

3.20 Google AdMob (Video Converter FFmpeg)

The app uses Google AdMob (Google Ireland Ltd., Gordon House, Barrow Street, Dublin 4, Ireland) to display advertisements. In this context, the Google Mobile Ads SDK may process, in particular, the IP address, information about user interactions, diagnostic information, as well as device and account identifiers, including the Advertising ID. The Advertising ID is an Android system identifier that can be reset or deleted by the user.

Purpose: Financing the app through advertisements, reach measurement, fraud prevention, and improvement of ad delivery.
Legal basis: In the EU / EEA, the processing of personal data for personalized advertising is generally based on the user’s consent pursuant to Art. 6(1)(a) GDPR. The specific ad delivery depends on the privacy and consent settings chosen by the user. For users in the EEA, the United Kingdom, and Switzerland, Google requires appropriate transparency and consent mechanisms.

3.21 Google Analytics for Firebase (Video Converter FFmpeg)

The app uses Google Analytics for Firebase (Google Ireland Ltd., Dublin, Ireland). In particular, the following data may be processed: App Instance ID, Advertising ID, pseudonymous usage data, app and device information, and approximate location data derived from masked IP addresses.

Purpose: Analysis of app usage and improvement of functionality, stability, and user experience.
Legal basis: In the EU / EEA, processing is based on the user’s consent pursuant to Art. 6(1)(a) GDPR, insofar as Analytics is activated. Google also states that the Firebase customer is typically the data controller, while Google generally acts as a processor or service provider.

3.22 Recipients and Third-Country Transfers (Video Converter FFmpeg)

In connection with the use of AdMob and Google Analytics for Firebase, data may be transferred to the following recipients:

Google Ireland Ltd., Gordon House, Barrow Street, Dublin 4, Ireland
Google LLC, Mountain View, California, USA

A transfer of data to third countries, in particular to the United States, cannot be excluded. For relevant services, Google states that it complies with the EU-U.S. Data Privacy Framework (DPF) as well as the UK Extension; in addition, further data protection mechanisms may apply depending on the specific service and contractual arrangements.

3.23 Open-Source and Licensing Notice (Video Converter FFmpeg)

The app uses FFmpegKit / FFmpeg as an open-source component for local media processing. FFmpegKit itself is generally licensed under the LGPL v3.0 in its build scripts; however, if GPL components are enabled, FFmpeg as a whole becomes subject to the GPL v3.0. The project published by us under the name “SimpleVideoConverter” is therefore labeled GPL-3.0 and refers to the use of FFmpegKit with x264 (GPL).

The source code of the app is publicly available via the project’s GitHub repository.
https://github.com/Androho24/SimpleVideoConverter

4. Retention Periods

Website server log files: up to 14 days.
Support inquiries: until resolved, thereafter according to statutory obligations.
Firebase/AdMob data: according to provider configuration or until withdrawal of consent.

Video Converter FFmpeg:
Video files selected or created by the user are generally not stored on our own servers. Where files are stored, this is done locally on the user’s device until they are deleted by the user. Data processed via AdMob and Google Analytics for Firebase is stored in accordance with the respective provider settings and project configuration. For Firebase, Google provides service- and project-specific deletion and data control options.

5. Data Subject Rights

You have the following rights under the GDPR:

Right of access (Art. 15)
Right to rectification (Art. 16)
Right to erasure (Art. 17)
Right to restriction of processing (Art. 18)
Right to data portability (Art. 20)
Right to object (Art. 21)
Right to withdraw consent (Art. 7 (3))

You may also lodge a complaint with a supervisory authority, e.g., the Bavarian State Office for Data Protection Supervision (BayLDA).

6. Necessity of Providing Data

Use of the apps requires certain permissions (e.g., audio, Bluetooth). Without these, full functionality cannot be ensured.
The provision of analytics and advertising data is voluntary and only occurs with user consent.

7. Updates

This Privacy Policy is valid from September 2025. Updates will be published on this website.

8. Liability

Disclaimer for Hearing Test Function (Equalizer Apps)
Our apps include a hearing test function that can play tones at various frequencies, including high volumes, through headphones.
Users are responsible for choosing a safe volume setting.
We accept no liability for hearing damage or other health issues resulting from improper use.
This function does not replace medical examination or advice.

Disclaimer for Measurement Functions (Level Buddy)
The measurement values in the Level Buddy app (e.g., spirit level, camera angle) are based on the device’s sensors and camera.
These values are not 100% accurate and may be affected by device characteristics.
The calibration (offset) function is intended solely to adapt the app to the respective device.
We accept no liability for damages or incorrect

9. Additional Tools – Google Search Console

We use Google Search Console (Google Ireland Ltd., Dublin, Ireland) to technically monitor and optimize the visibility of our website in Google search results.
Only aggregated, non-personal data are processed in this context.
It is not possible to identify individual visitors to our website.

10. Data Security

We use technical and organizational security measures in accordance with Art. 32 GDPR to protect your data against accidental or intentional manipulation, loss, destruction, or unauthorized access.
This includes, among other things, encrypted data transmission via TLS/SSL. Our security measures are continuously improved in line with technological developments.