Privacy Policy for Bubble Level with Camera
Last updated: 11 July 2026
This Privacy Policy applies to the Android app “Bubble Level with Camera”, which may be offered under translated names in other languages and is identified by the package name com.androho.levelbuddy, in its current version and, where technically applicable, to older versions that remain installed.
Individual features, services, permissions or privacy options may vary depending on the app version, Android version, device configuration, region and user choices. 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 the processing of personal data is:
Androho Software – Matthias Höpfler
Ziegelweg 1
84164 Moosthenning
Germany
Email: info@androho.com
Website: www.androho.com
2. General Data Processing in the App
The app can generally be used without creating a user account. No account is created with Androho Software. We do not operate our own cloud storage service for user data for this app.
For the bubble level and camera features, the app processes sensor readings and, when camera mode is used, the current live camera image. This processing generally takes place locally on the device. Measurement data and camera images are not automatically transmitted to Androho Software servers.
Many app data items are stored exclusively on the device, for example:
- app settings
- design and colour selections
- calibration or zero-point values
- camera and measurement mode settings
- other locally stored feature states
This locally stored data is not automatically transmitted to our own servers.
3. Services Used
The app may use the following services:
- Google Firebase Analytics
- Google Firebase Crashlytics
- Google AdMob
- Google User Messaging Platform / Consent SDK
- Google Play Billing for optional in-app purchases
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:
Camera
The CAMERA permission is used for the app’s camera mode. The live camera image may be displayed as a visual aid behind or alongside the measurement indicators. Camera image processing generally takes place locally on the device. Camera images or video recordings are not automatically transmitted to Androho Software, Google Analytics, Firebase Crashlytics or Google AdMob.
Internet and Network Status
The INTERNET and ACCESS_NETWORK_STATE permissions are required for advertising, consent management, analytics, crash analysis, in-app purchases and technical communication with the Google services used for these purposes.
Storage Access on Older Android Versions
The WRITE_EXTERNAL_STORAGE permission is used exclusively on Android 9, corresponding to API level 28, and earlier Android versions. It enables a screenshot created by the user to be saved in local device storage. The screenshot may contain the camera view together with the displayed axis indicator and the measured angle.
Saving takes place only when the user explicitly activates the corresponding function. Saved images are not automatically transmitted to our servers or to analytics, crash analysis or advertising services.
Android Backups
Depending on the Android version, device settings and the backup rules defined in the app, certain local app settings may be backed up by Android’s system backup function and restored after reinstallation or on another device. Such system backups are performed and stored by Android or the backup service selected by the user, not by a cloud service operated by Androho Software.
5. Local Sensor and Camera Processing
To determine tilt, orientation or position, the app may access motion, position or orientation sensors provided by the Android system. A separate Android permission is generally not required for these sensors.
The resulting measurements are processed locally on the device for the display and operation of the bubble level. We do not deliberately transmit specific bubble level, tilt, calibration or zero-point measurements to our own servers or to advertising and analytics services.
When the camera is enabled, the live camera image is processed locally to provide visual assistance during measurement. The camera permission does not mean that photos or videos are automatically captured, uploaded or shared with third parties.
If the user activates the screenshot function, the current camera view may be saved locally together with the axis indicator and measured angle. The user initiates this storage operation. The resulting image is not automatically uploaded by the app.
6. 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.
7. 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.
8. 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.
9. 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.
10. In-App Purchases through Google Play
The app may offer optional in-app purchases through Google Play Billing, for example to unlock an ad-free version or additional features.
Payments are processed through Google Play. We do not receive complete payment information such as credit card or bank account details.
However, the app and the Google Play Console may process or display technical purchase and order information where this is necessary for purchase processing, unlocking, restoration, support, fraud prevention, accounting or legal record-keeping obligations. This may include:
- purchase status
- product ID
- order time
- price and currency
- country or region
- order, purchase or transaction identifiers
A purchase is voluntary. Purchase-related data is processed only where a user completes or restores a purchase or where a corresponding purchase check is required.
The legal bases are Article 6(1)(b) GDPR for performance of the contract and activation of the purchased feature, Article 6(1)(c) GDPR for legal obligations, and Article 6(1)(f) GDPR for support, evidence and fraud prevention.
11. Recipients and Categories of Recipients
Depending on the region, consent status and feature used, 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
- Google Play and its payment and processing services, where in-app purchases are concerned
- Android or device backup services, where the user has enabled system backups and the app data is covered by the applicable backup rules
Further information about data processing by Google is available in the Google Privacy Policy and in the privacy and security information for Firebase.
12. Transfers to Third Countries
When the Google services listed above are used, personal data may be transferred to countries outside the European Union or the European Economic Area, in particular to the United States.
Such transfers may be based on appropriate safeguards, including an adequacy decision, the EU-U.S. Data Privacy Framework, Standard Contractual Clauses or other mechanisms provided by law.
13. Retention Periods
Local app settings, calibration values, saved screenshots and other local app data generally remain on the device until the user resets them in the app, deletes the app data through the Android settings, manually deletes saved images or uninstalls the app. Android system backups may restore certain settings after reinstallation.
Firebase Analytics data is stored in accordance with the retention settings configured in Google Analytics or Firebase. For standard properties, the configurable retention period for user-level and certain event-level data is generally 2 or 14 months. Aggregated reports may remain available for longer.
Firebase Crashlytics generally retains crash stack traces, associated diagnostic data and installation identifiers for 90 days before deletion from live and backup systems begins.
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 Play purchase, payment, billing and order data may be retained in accordance with statutory retention periods, tax obligations, Google policies and billing requirements.
The Google Play Console may provide us with aggregated statistics and reports concerning installations, uninstallations, usage, performance, stability, advertising, reviews, purchases and revenue. These reports may remain available for different periods depending on the Google feature, reporting period, minimum thresholds and account settings.
14. Data Security
Data transmitted by the Google services used by the app is generally transmitted through encrypted HTTPS or TLS connections.
Please note that the security of locally stored data also depends on the security settings of the device, the Android version, the use of a screen lock and, where applicable, the backup service used.
15. Legal Bases for Processing
Where applicable, personal data is processed on the following legal bases:
| Processing activity | Legal basis |
|---|---|
| Local bubble level, sensor, camera, screenshot, calibration and settings features | Article 6(1)(b) GDPR for providing the app features requested 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 |
| Optional in-app purchases | Article 6(1)(b) GDPR for performance of the contract and activation; Article 6(1)(c) GDPR for statutory retention obligations; Article 6(1)(f) GDPR for support, evidence and fraud prevention |
| Compliance with legal obligations, accounting and record-keeping duties | Article 6(1)(c) GDPR |
Where processing is based on Article 6(1)(f) GDPR, our legitimate interests include the technical provision, financing and improvement of the app, its stability and security, troubleshooting, fraud prevention, support and abuse detection.
16. User Rights
Subject to the conditions of the GDPR, you have the following rights in particular:
- the right of access
- the right to rectification
- the right to erasure
- the right to restriction of processing
- the right to data portability
- the right to object to certain processing activities
- the right to withdraw consent with effect for the future
- the right to lodge a complaint with a data protection supervisory authority
To submit a privacy-related request, contact us at:
Please note that much of the data is stored exclusively on your device. This includes settings, design selections, calibration values and locally saved screenshots. We do not have access to this local data. You can delete it by resetting the relevant app settings, deleting saved images, clearing the app data in the Android settings or uninstalling the app.
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.
17. 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.
18. No Automated Decision-Making by Androho Software
Androho Software does not use data processed through the app for its own automated decision-making or profiling that produces legal effects concerning you or similarly significantly affects you. Depending on your consent, advertising services may use their own procedures to select and personalise advertising.
19. Changes to this Privacy Policy
We may update this Privacy Policy if the app’s features, services, permissions, legal requirements or technical processes change. The current version will be made available on our website.
Androho Software