Privacy Policy for Sound Meter: dB & Spectrum

This Privacy Policy applies to the Android app “Sound Meter: dB & Spectrum”, which may be offered under translated names in other languages and is uniquely identified by the package name com.androho.decibelmeter, in its current version and, where technically applicable, to older versions that remain installed.

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

1. Controller

The controller responsible for data processing is:

Androho Software – Matthias Höpfler

Ziegelweg 1

84164 Moosthenning

Germany

Email: info@androho.com

Website: www.androho.com

2. General Data Processing within the App

The app can be used without creating a user account. No account is created with Androho Software. We do not operate our own cloud storage or server database for measurements or other user data for this app.

For sound level measurements and the display of the frequency spectrum, the app processes the audio signal received through the device microphone. This processing generally takes place locally on the device and is used exclusively to calculate and display sound level, decibel and frequency values.

The audio signal is not stored as an audio recording. No voice recordings are created, and the app does not use speech recognition or analyse the content of spoken language. Microphone or audio content is not transmitted to servers operated by Androho Software.

The following data may be processed or stored exclusively locally on the device:

• determined measurement values and measurement histories
• saved measurements
• timestamps and other technical information relating to saved measurements
• app settings
• display and visualisation settings
• calibration or correction values
• other locally stored feature states

Locally stored measurements and settings are not automatically transmitted to Androho Software, Firebase Analytics or Firebase Crashlytics.

3. Services Used

The app may use the following Google services:

• Google Firebase Analytics
• Google Firebase Crashlytics
• Google AdMob
• Google User Messaging Platform / Consent SDK

Depending on the region and consent status, individual services may be disabled, restricted or used with reduced data processing.

4. App Permissions

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

Microphone

The RECORD_AUDIO permission is required to analyse the current sound pressure or sound level and to display the frequency spectrum.

During an active measurement, the microphone signal is processed locally and generally only for as long as necessary to perform the current measurement. The app does not save audio recordings and does not transmit microphone or voice recordings to Androho Software or to the Firebase services used.

Foreground service

The FOREGROUND_SERVICE and FOREGROUND_SERVICE_MICROPHONE permissions allow the app to run a microphone measurement started by the user as an Android foreground service.

A foreground service is an Android service that is visible to the user and may display an ongoing system notification while it is running. It is used exclusively for the technical execution and control of an active measurement.

Notifications

The POST_NOTIFICATIONS permission may be required on newer Android versions to display the system notification associated with the active foreground service.

The notification provides information about an ongoing measurement and may contain controls or status information relating to the measurement feature. The permission is not used for advertising messages, marketing notifications or server-based push notifications.

Internet and network connection

The integrated Firebase services may use an internet and network connection to transmit analytics or crash data to Google where the respective service is enabled for the relevant user and region.

The actual sound level measurement, frequency analysis, local storage and export of measurements generally do not require the transmission of measurement content to a server.

5. Local Microphone and Audio Signal Processing

During a measurement, the Android system provides the app with audio data from the device microphone. The app analyses this data to determine, in particular, the volume or sound level and the frequency components contained in the signal.

This processing is used exclusively for the measurement and display functions requested by the user. The app is not designed to record conversations or other audio content, store such content permanently, convert it into text or analyse its meaning.

The quality and accuracy of measurements may depend on the microphone, device construction, Android version, device calibration and environmental conditions. These technical factors do not result in the audio signal being transmitted to Androho Software.

6. Local Database and Saved Measurements

Saved measurements are stored in a local database on the device. The app uses the Android Room database technology for this purpose. Settings and other feature states may also be stored locally using Android DataStore or comparable local storage mechanisms.

The app currently does not offer its own cloud synchronisation or its own backup function for the measurement database. The database is not automatically transmitted to Androho Software, Google Drive or another cloud service.

Local measurements generally remain stored until they are deleted by the user within the app, the app data is removed through the Android settings or the app is uninstalled.

Android system backups

Independently of any backup function provided by the app itself, Android may, depending on the Android version, device settings, backup service and backup rules configured within the app, include certain local app data in a system or device backup.

The creation and storage of such system backups are controlled by Android or by the backup service selected by the user and not by a cloud service operated by Androho Software.

7. Export as an Image or CSV File

Users can manually export measurements as an image or CSV file and save them on their own device.

An export takes place only when the user explicitly selects the corresponding function. Using storage or file selection functions provided by the Android system, the user determines where the exported file is saved.

Exported images may contain displayed measurement values, charts, spectrum displays or other information visible in the measurement view. CSV files may contain measurement values selected by the user or stored in the app in tabular form.

Exported files are not automatically transmitted to Androho Software, Firebase Analytics, Firebase Crashlytics or another external service.

After a file has been saved, further access is governed by the selected storage location, Android permissions and the apps or cloud services used by the user. If the user subsequently shares or uploads a file or saves it in a synchronised folder, this takes place outside the app's automatic data processing and based on the user's own decision.

8. Firebase Analytics

The app may use Google Firebase Analytics. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Firebase Analytics may process pseudonymous usage and technical data, for example:

• app launches and session information
• screen views and app interactions
• technical device information
• app version and operating system version
• approximate region derived from technical connection data such as the IP address
• device or app identifiers such as Firebase Installation IDs
• purchase events such as product ID, purchase status, price or currency, where a purchase is made and the relevant collection is enabled

The purposes of this processing are to analyse app usage, improve features, identify technical problems and further develop the app.

Firebase Analytics is initially disabled at a technical level when the app starts. If the Google User Messaging Platform determines that a consent dialog must be shown to a particular user, Analytics is enabled only after the relevant consent has been given. If the regional and technical check determines that no consent dialog is required, Analytics may be enabled without a prior dialog where this is permitted under the applicable rules.

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 serve as the legal basis. Our legitimate interests are the analysis, improvement and stabilisation of the app.

9. Firebase Crashlytics

The app may use Google Firebase Crashlytics for error analysis. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Crashlytics may process the following data in particular:

• crash logs and stack traces
• app version
• device type and technical device characteristics
• operating system version
• time of a crash or error
• technical diagnostic and performance data
• Crashlytics and Firebase Installation IDs
• relevant technical app states at the time of an error

The purpose is to identify, analyse and resolve crashes and technical errors and to improve the stability of the app.

Firebase Crashlytics is initially disabled at a technical level when the app starts. If the Google User Messaging Platform determines that a consent dialog must be shown to a particular user, Crashlytics is enabled only after the relevant consent has been given. If the regional and technical check determines that no consent dialog is required, Crashlytics may be enabled without a prior dialog where this is permitted under the applicable rules.

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 serve as the legal basis. Our legitimate interests are the technical stability, security and troubleshooting of the app.

10. Advertising with Google AdMob

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

In particular, the following data may be collected, processed and shared with Google:

• IP address and the approximate location derived from it
• device and app identifiers, including the advertising ID or App Set ID, where available and permitted
• app interactions such as app launches, taps and ad interactions
• device and app information
• diagnostic and performance data, such as app start time, hang rate or energy usage
• ad impressions and information concerning ad delivery
• fraud-prevention, security and compliance data

The purposes of this processing are:

• displaying and technically delivering advertising
• personalising advertising where you have consented
• measuring and analysing advertising performance
• limiting and controlling advertising
• fraud prevention, security and compliance
• financing and further developing the app

In regions where consent is required, personalised advertising is used only on the basis of your consent. If you do not consent, non-personalised or limited ads may be displayed where technically and legally possible. Certain technical data processing may still be required for ad delivery, security, fraud prevention and compliance when non-personalised or limited advertising is used.

The legal basis for personalised advertising and related storage access is Article 6(1)(a) GDPR where the GDPR applies. For technically necessary ad delivery, limited advertising, security, fraud prevention and abuse detection, Article 6(1)(f) GDPR may serve as the legal basis where legally permitted.

11. Consent Management with the Google User Messaging Platform

The app uses the Google User Messaging Platform (UMP) to determine whether a consent or privacy dialog must be shown to a particular user and to manage the corresponding privacy choices.

Depending on the region, app version, device configuration and Google configuration, a dialog concerning advertising, analytics and crash analysis may be displayed. Users can grant or refuse consent in this dialog. Where Google requires or provides a permanently accessible entry point for privacy options, users can later change their choices through the corresponding function in the app.

If consent is not given, Firebase Analytics and Firebase Crashlytics remain disabled where the relevant consent dialog is required for the user. Depending on the consent status, advertising may be non-personalised, limited or, in some cases, not delivered.

UMP may process technically necessary information concerning consent status, regional classification and dialog delivery. The provider is Google Ireland Limited.

12. Recipients and Categories of Recipients

Where Firebase Analytics or Firebase Crashlytics is enabled for the relevant user, technical data may be transmitted to the following recipients or categories of recipients:

• Google Ireland Limited
• Google LLC
• Google AdMob
• Google Firebase Analytics
• Google Firebase Crashlytics
• Google User Messaging Platform
• processors and subprocessors engaged by Google

Further information about data processing by Google can be found in the Google Privacy Policy and in the privacy and security information relating to Firebase.

Locally stored measurements, microphone content and files exported by the user are not automatically transmitted to the recipients listed above.

13. International Data Transfers

When the Google services described above are used, personal data may be transferred to countries outside the European Union or the European Economic Area, particularly to the United States.

Such transfers may be based on appropriate safeguards, including an adequacy decision, the EU-U.S. Data Privacy Framework, Standard Contractual Clauses or other transfer mechanisms provided for by law.

Firebase services may process data on Google's global infrastructure and at different locations operated by Google or its processors.

14. Storage Period

Local measurements, settings, calibration values and other local app data generally remain stored on the device until users delete them within the app, remove the app data through the Android settings or uninstall the app.

Exported images and CSV files remain stored at the selected storage location until they are deleted by the user or removed by another app, storage service or backup service used by the user.

Firebase Analytics data is stored in accordance with the data retention settings configured in Google Analytics or Firebase. The configured retention period for user-related and certain event-related data is two months. Aggregated reports may remain available for a longer period.

Firebase Crashlytics data, including crash reports, associated diagnostic data and related identifiers, is retained for 90 Days in accordance with the configured data retention settings.

AdMob data, advertising reports and related technical data are retained in accordance with the applicable Google policies, account settings, security requirements and legal obligations. The retention period may vary depending on the type of data and the purpose of processing.

Google may also provide us with aggregated statistics and reports through the Google Play Console relating to installations, uninstalls, devices, app versions, stability and performance. The applicable retention periods and presentation are governed by the settings and terms of Google Play.

15. Data Security

Data transmitted by the Google services used is generally transferred through encrypted HTTPS or TLS connections.

Firebase encrypts data transmitted by the Firebase services described above during transmission. Firebase Crashlytics also uses technical security measures to protect stored data.

The security of locally stored measurements and exported files also depends on the security settings of the device, the Android version, any configured screen lock, the selected storage location and any backup or cloud service used by the user.

16. Legal Bases for Processing

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

Processing activity	Legal basis
Local microphone processing, sound level measurement and frequency analysis	Article 6(1)(b) GDPR for providing the app features requested by the user
Local storage of measurements and settings	Article 6(1)(b) GDPR for providing the storage, history and settings features
Export initiated by the user as an image or CSV file	Article 6(1)(b) GDPR for performing the export function selected by the user
Firebase Analytics	Article 6(1)(a) GDPR where consent is obtained; otherwise, only where legally permitted, Article 6(1)(f) GDPR for analysing and improving the app
Firebase Crashlytics	Article 6(1)(a) GDPR where consent is obtained; otherwise, only where legally permitted, Article 6(1)(f) GDPR for error analysis, stability and technical security
Personalised advertising and related access to device storage or identifiers	Article 6(1)(a) GDPR where consent is required
Technical ad delivery, limited or non-personalised advertising, advertising measurement, fraud prevention, security and compliance	Article 6(1)(a) GDPR where consent is required; otherwise, only where legally permitted, Article 6(1)(f) GDPR
Compliance with legal obligations and handling data protection requests	Article 6(1)(c) GDPR

Where processing is based on Article 6(1)(f) GDPR, our legitimate interests include the technical provision, analysis and improvement of the app, as well as stability, security, troubleshooting and misuse prevention.

17. User Rights

Subject to the requirements of the GDPR, users 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

To submit a privacy-related request, please contact us at:

info@androho.com

Please note that the measurement database, settings and other measurement data are generally stored exclusively locally on the user's device. We do not have access to this local data.

Local data can be deleted in particular by:

• deleting individual measurements within the app, where the corresponding function is available
• deleting the app data through the Android system settings
• uninstalling the app
• manually deleting exported images and CSV files from their respective storage locations

The app does not have its own user account system or its own personal cloud database. We therefore often cannot directly associate technical data from Google services with a specific person. Where personal data is processed through Google services, our ability to handle access or erasure requests depends on whether a technical association is possible and legally permitted based on the information available.

Where Google processes data as an independent controller, you may also exercise your rights directly against Google. This applies in particular to Google account, payment, advertising, device and system backup data.

Statutory retention obligations, particularly for purchase, billing, tax or accounting data, may prevent certain data from being deleted immediately.

18. Changing Consent and Privacy Options

Where a consent dialog or an entry point for privacy options is displayed, users can grant, refuse or later change consent for advertising, analytics and crash analysis. Changes can be made through the relevant privacy function in the app where it is available based on the region, app version and Google configuration.

The withdrawal of consent takes effect for the future. It does not affect the lawfulness of processing carried out on the basis of consent before its withdrawal.

You can also manage the advertising ID, personalised advertising, Google privacy settings and Android backup options in the Android or Google settings on your device.

19. No Automated Decision-Making

Androho Software does not use data processed through the app for automated decision-making or its own profiling that produces legal effects concerning users or similarly significantly affects them.

20. Changes to this Privacy Policy

We may update this Privacy Policy if the app's features, services used, permissions, legal requirements or technical processes change.

This applies in particular if advertising, in-app purchases, cloud backups, additional external services, new export options or a consent mechanism are introduced in the future. The current version of this Privacy Policy will be made available on our website.