Privacy Policy

1. Controller

Androho Software – Matthias Höpfler

Ziegelweg 1

84164 Moosthenning

Germany

E-mail: info@androho.com

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 and Local Storage

This website does not use cookies.

We use only your browser's local storage (localStorage) to remember your language preference (German/English) and whether you have already acknowledged the cookie notice. This data remains solely on your device and is not transmitted to us or to any third party.

No analytics or marketing cookies are used on this website.

2.4 Contact by E-Mail

If you contact us by e-mail (e.g. to info@androho.com), 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)
• Bubble View with Camera (com.androho.levelbuddy)
• Video Converter & Compressor (com.androho.simplevideoconverter)
• Offline Sport Tracker (com.androho.sporttracker)
• Sound Meter: dB & Spectrum (com.androho.)

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 (Bubble level with camera)

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 (Bubble level with camera)

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 (Bubble level with camera)

• 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 & Compressor"

The following privacy notices also apply to the app "Video Converter & Compressor." The related open-source project is published under the name "SimpleVideoConverter."

3.18 Local Processing of Video Files (Video Converter & Compressor)

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 & Compressor)

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 & Compressor)

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 & Compressor)

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 & Compressor)

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 & Compressor)

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

3.24 Processing of Personal Data in the "Offline Sport Tracker" App

The following privacy information also applies to the "Offline Sport Tracker" app (com.androho.sporttracker).

The app is used for the local recording and analysis of sports and outdoor activities, such as running, hiking, cycling or walking. In this context, GPS location data, workout data, map data, statistics data, step information, Health Connect data and data voluntarily entered by the user may be processed.

3.25 Local Processing of Workout and Location Data (Offline Sport Tracker)

The app may process GPS location data in order to record activities, display routes on a map and calculate workout values such as distance, duration, average speed, pace and similar information.

Data:

GPS location data, recorded route, timestamps, duration, distance, speed, pace, sport type, step count, workout notes or workout information entered by the user, and optional weight data for calculating calorie consumption.

Purpose:

Recording, displaying, analyzing and managing sports and outdoor activities.

Storage:

Workout data is stored locally on the user's device. Workout data is not automatically stored on our own servers and recorded activities are not automatically shared with third parties.

If the user enters weight data or other optional information, this data is used to calculate or display the respective workout values and is also stored locally.

3.26 Step Counting and Activity Recognition (Offline Sport Tracker)

The app may collect step information during an active workout recording if the device supports a step counter and the user has granted the required permission.

Data:

Step count or step counter data during an activity.

Purpose:

Displaying and analyzing step information within the workout recording.

Storage:

Step information is stored locally on the device together with the respective activity. The app also works without a step counter or without this permission.

3.27 Health Connect (Offline Sport Tracker)

The app may use Health Connect if the user explicitly activates this function and grants the respective permissions.

The app may write sport-related data to Health Connect, in particular workout data, distance, calorie consumption and steps. The app may also read heart rate data from Health Connect if the user allows this.

Data:

Workout data, distance, calorie consumption, steps and read heart rate data.

Purpose:

Exchange of sport-related data with Health Connect so that workout data can be used in compatible health and fitness apps, or so that additional workout values such as heart rate data can be taken into account in the app.

Notice:

Health Connect is provided by Google or the Android system. The user can manage or revoke Health Connect permissions at any time in the Android or Health Connect settings.

3.28 Maps, Online Maps and Offline Maps (Offline Sport Tracker)

The app may provide map functions in order to display recorded routes and to support orientation during or after an activity.

The map and download files are provided or delivered via Cloudflare services.

Online maps:

When using the online map, technical connection data such as IP address, time of request, requested map sections or map tiles, device/app information and similar technically required data may be transmitted to Cloudflare or the respective map, hosting or CDN servers used. This is technically necessary in order to load and display map data online.

Offline maps:

Users can download available map areas and store them locally on the device. When downloading offline maps, technical connection data such as IP address, time of request, requested map files, device/app information and similar technical data may be transmitted to Cloudflare or the respective download, hosting or CDN servers used.

After downloading, these map areas can be used locally. GPS recording of activities is also possible without a downloaded map.

3.29 Local Backup and Google Drive Backup (Offline Sport Tracker)

The app may provide a local backup and restore function. Workout data and related app data can be stored in a backup file that the user can manage independently.

Local backup:

Local backups are created on the device or in a storage location selected by the user. These backup files are not automatically transferred to our own servers.

Google Drive:

If desired, the user can manually back up or restore backup files using their own Google Drive. In this case, data is transmitted to Google Drive or Google services. The backup file, file name, metadata, technical connection data and information required for authentication may be processed by Google.

The use of Google Drive is optional. Google's privacy policy also applies to processing by Google. We do not receive the user's full Google account login credentials.

3.30 Google AdMob (Offline Sport Tracker)

The app uses Google AdMob (Google Ireland Ltd., Gordon House, Barrow Street, Dublin 4, Ireland) to display advertisements.

Data:

Advertising ID / AAID, IP address, device information, app information, diagnostic information, roughly derived location and information about ad interactions.

Purpose:

Financing the app through advertisements, reach measurement, fraud prevention and improvement of ad delivery.

Legal basis:

In the EU / EEA, processing for personalized advertising is generally based on consent pursuant to Art. 6(1)(a) GDPR. The specific ad delivery depends on the user's privacy and consent settings. Without the corresponding consent, non-personalized ads may be displayed where technically and legally permissible.

According to the intended functionality of the app, no advertisements are displayed during an active GPS recording.

If the ad-free Premium version or an active ad-free subscription is enabled, the Google Mobile Ads SDK is not initialized according to the intended functionality of the app. In this case, the app does not collect or process the Advertising ID for AdMob advertising purposes.

3.31 Google Play Billing, In-App Purchases and Subscriptions (Offline Sport Tracker)

The app may offer in-app purchases or subscriptions via Google Play Billing, for example for ad-free use or to unlock certain app functions.

Payment processing is handled by Google Play. We do not receive complete payment data such as credit card or bank details. However, we may receive technical information about the purchase or subscription status where this is necessary to unlock, restore or manage purchased functions.

3.32 Permissions (Offline Sport Tracker)

The app uses the following permissions:

ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION – required for GPS recording of activities, calculation of route values and display of the recorded route on the map. Location permission is requested at runtime.

FOREGROUND_SERVICE / FOREGROUND_SERVICE_LOCATION – required so that an active GPS recording can be reliably continued as a foreground service, for example when the screen is turned off or the app is not displayed in the foreground.

FOREGROUND_SERVICE_DATA_SYNC – required for data-related foreground processes, for example when downloading offline maps or during backup or synchronization processes, where this function is used.

WAKE_LOCK – required to keep certain device functions awake during an active recording so that GPS positions can be processed reliably even when the screen is turned off. The lock is only used during the operations for which it is required.

REQUEST_IGNORE_BATTERY_OPTIMIZATIONS – may be used to ask the user for an exemption from battery optimizations. This may be necessary to prevent aggressive battery optimizations from certain device manufacturers from interrupting an ongoing GPS recording.

POST_NOTIFICATIONS – required from Android 13 onwards to display notifications, for example during an active GPS recording or active foreground services.

INTERNET – required for online maps, map downloads, advertising, Google Drive functions, Google Play Billing and other online functions.

ACCESS_NETWORK_STATE – required to check the network status, for example for online maps, map downloads, advertising or backup functions.

com.android.vending.BILLING – required for Google Play Billing, in-app purchases and subscriptions.

ACTIVITY_RECOGNITION – required for step counting during an activity where this function is used and the device supports it. From Android 10 onwards, this permission is requested at runtime.

android.permission.health.WRITE_EXERCISE / WRITE_DISTANCE / WRITE_TOTAL_CALORIES_BURNED / WRITE_STEPS – required to write sport-related workout data, distance, calorie consumption and steps to Health Connect, where the user activates and permits this.

android.permission.health.READ_HEART_RATE – required to read heart rate data from Health Connect, where the user activates and permits this.

com.google.android.gms.permission.AD_ID – may be automatically included in the final app manifest by the Google Mobile Ads SDK and is required for Google AdMob or advertising and measurement functions where advertising is active and this is technically and legally permissible. If the ad-free Premium version is active, the Ads SDK is not initialized according to the intended functionality of the app.

3.33 Recipients and Third-Country Transfers (Offline Sport Tracker)

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

Google Ireland Ltd., Dublin, Ireland

Google LLC, Mountain View, California, USA

Google Play services for in-app purchases, subscriptions, reviews and updates

Google AdMob for advertising

Google Drive, where the user uses the optional Google Drive backup function

Health Connect or Android system services, where the user activates Health Connect and grants the corresponding permissions

Cloudflare, Inc. or affiliated Cloudflare companies, where online maps or offline map downloads are provided via Cloudflare services

Map, download, hosting or CDN providers, where online maps or offline map downloads are used

Transfers to third countries, in particular to 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.34 Consent Management (Offline Sport Tracker)

In the EU / EEA, a consent dialog may be displayed when the app is started for the first time, in particular for advertising and related data processing.

Users can grant or refuse consent and later change their consent in the app settings, where the respective function supports this.

Without consent, certain functions, in particular personalized advertising, may be restricted or disabled.

3.35 Processing of Personal Data in the "Sound Meter: dB & Spectrum" App

The following privacy information also applies to the "Sound Meter: dB & Spectrum" app.

The app is used to measure and analyze sound levels as well as to perform frequency analysis using the device microphone. Audio data may be processed temporarily on the device in order to calculate measurement values, level displays, spectrum visualizations and similar analysis values.

3.36 Local Audio Processing, Sound Level Measurement and Frequency Analysis (Sound Meter: dB & Spectrum)

The app uses the device microphone to analyze sound levels and frequency information.

Data:

Temporarily processed microphone audio signals, calculated sound levels, frequency spectrum, measurement values, time histories and similar technical analysis values.

Purpose:

Displaying sound levels, frequency analysis, spectrum display and long-term measurement within the app.

Storage:

Audio processing takes place locally on the device. According to the intended functionality of the app, no microphone recordings are transmitted to our own servers. The app is intended for analyzing and displaying measurement values and is not designed as a recording or surveillance function.

3.37 Long-Term Measurement and Notifications (Sound Meter: dB & Spectrum)

The app may perform a long-term measurement as a foreground process. A notification may be displayed so that the user can see that the measurement is active.

Data:

Measurement values and technical analysis values calculated during the active measurement.

Purpose:

Performing and displaying an ongoing sound level or frequency measurement over a longer period of time.

Notice:

The notification is used for transparency and user control so that an active measurement is visible at all times.

3.38 Firebase Analytics and Firebase Crashlytics (Sound Meter: dB & Spectrum)

The app may use Google Firebase Crashlytics (Google Ireland Ltd., Dublin, Ireland) for crash and error analysis.

Crashlytics data:

Crash reports, device type, OS version, app version, timestamps, stack traces and technical diagnostic information.

Purpose:

Improving stability, security and troubleshooting.

Legal basis:

Legitimate interests pursuant to Art. 6(1)(f) GDPR in order to improve the stability and security of the app.

3.39 Permissions (Sound Meter: dB & Spectrum)

The app uses the following permissions:

RECORD_AUDIO – required for sound level measurement, frequency analysis and spectrum display using the microphone. Audio processing takes place locally on the device. According to the intended functionality of the app, no microphone recordings are transmitted to our own servers.

FOREGROUND_SERVICE – required to run certain measurement functions as a foreground service, especially during active or longer measurements.

FOREGROUND_SERVICE_MICROPHONE – required so that an active microphone measurement can be performed as a foreground service, for example during a long-term measurement.

POST_NOTIFICATIONS – required from Android 13 onwards to display notifications, for example during an active long-term measurement, so that the user can see that the measurement is running.

INTERNET / ACCESS_NETWORK_STATE – may be included in the final app manifest by the Google/Firebase SDKs used and may be required for Firebase Analytics, Firebase Crashlytics and the transmission of technical analytics or crash data, where these services are used.

3.40 Recipients and Third-Country Transfers (Sound Meter: dB & Spectrum)

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

Google Ireland Ltd., Dublin, Ireland

Google LLC, Mountain View, California, USA

Firebase Analytics for usage analysis

Firebase Crashlytics for crash analysis and stability improvement

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

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.

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 decisions resulting from inaccurate measurement results. The app does not replace professional measuring instruments.

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.