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

Firebase Analytics and Firebase Crashlytics may be disabled or restricted depending on the region and technical configuration.

The current version of the app does not use Google AdMob or any other advertising network. It does not use the Google User Messaging Platform or another advertising consent dialog. The app also currently does not offer in-app purchases.

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:

• first opening and launching of the app
• session information
• screen views
• app interactions
• app version
• operating system version
• device model and technical device characteristics
• language and technical region settings
• approximate region derived from technical connection data such as the IP address
• device or app identifiers such as Firebase Installation IDs or app instance IDs

The purpose of this processing is to statistically analyse app usage, identify frequently used features, improve usability and support the technical and functional development of the app.

Firebase Analytics is not used to specifically transmit the audio signal received through the microphone, spoken content, saved measurements, images or CSV files to Google.

Under the current regional and technical configuration, Firebase Analytics remains disabled for user groups and regions where a consent decision would be required before such data collection. The app currently does not display its own consent dialog.

In other regions where prior consent is not required under the applicable legal and technical assessment, Firebase Analytics may be enabled. Where the service is enabled, the app currently does not provide an individual setting that allows users to disable Analytics data collection.

Where the GDPR applies and processing without prior consent is legally permissible, the legal basis is Article 6(1)(f) GDPR. Our legitimate interest lies in the statistical analysis, improvement and further development of the app. Where consent is legally required, data collection remains disabled unless the required consent has been provided.

9. Firebase Crashlytics

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

Firebase Crashlytics may process the following data in particular:

• crash logs and stack traces
• error messages and technical exception information
• the time of a crash or technical error
• app version
• device type and device model
• operating system and operating system version
• technical device information such as processor architecture, memory or available storage space
• technical app states at the time of an error
• information about whether the app was running in the foreground or background
• Firebase Installation ID
• Crashlytics installation UUID and session identifiers

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

Firebase Crashlytics is not used to transmit the microphone signal, voice recordings, exported images, CSV files or the complete contents of the local measurement database to Google.

Under the current regional and technical configuration, Firebase Crashlytics remains disabled for user groups and regions where a consent decision would be required before such data collection. The app currently does not display its own consent dialog.

In other regions where prior consent is not required under the applicable legal and technical assessment, Firebase Crashlytics may be enabled. Where the service is enabled, the app currently does not provide an individual setting that allows users to disable Crashlytics data collection.

Where the GDPR applies and processing without prior consent is legally permissible, the legal basis is Article 6(1)(f) GDPR. Our legitimate interest lies in troubleshooting and in improving the technical stability, security and reliability of the app. Where consent is legally required, data collection remains disabled unless the required consent has been provided.

10. No Consent Dialog and No Advertising

The current version of the app does not include an advertising network and does not display advertisements. It does not use the Google User Messaging Platform or another consent dialog for advertising or data processing.

Under the current configuration, the app uses the integrated Firebase services only in regions and for user groups where no prior consent decision is required. In regions or circumstances where prior consent would be required, Firebase Analytics and Firebase Crashlytics are intended to remain disabled.

If advertising, additional external services, in-app purchases or a consent mechanism are added in the future, the technical configuration and this Privacy Policy will be updated accordingly.

11. 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 Firebase Analytics
• Google Firebase Crashlytics
• 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.

12. 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.

13. 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.

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.

14. 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.

15. 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, where enabled and legally permissible without prior consent	Article 6(1)(f) GDPR for the statistical analysis, improvement and further development of the app
Firebase Crashlytics, where enabled and legally permissible without prior consent	Article 6(1)(f) GDPR for error analysis and for improving the stability, security and reliability of the app
Firebase Analytics or Firebase Crashlytics where consent is required	Article 6(1)(a) GDPR; where the required consent has not been provided, the relevant data collection remains disabled
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.

16. 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 are therefore often unable to directly associate technical data from Google services with a particular person.

Where personal data is processed through Firebase Analytics or Firebase Crashlytics, the handling of access or deletion requests depends on whether a technical association is possible using the available information and whether such an association is legally permissible.

Where Google processes data as an independent controller, users may also exercise their rights directly against Google. This may apply in particular to Google Account, device, backup or other Google service data.

17. 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.

18. 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.