Privacy Policy for Compass: Map & Camera

Last updated: July 14, 2026

This Privacy Policy applies to the Android app “Compass: Map & Camera”, which may be offered under translated names in other languages and is uniquely identified by the package name com.androho.compass, 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 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 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 for this app to which compass, camera, or location data is automatically uploaded.

The app processes, in particular, sensor values used to determine direction, the current live camera image when camera mode is used, and the device’s current approximate or precise location when location permission has been granted. These functional data are generally processed locally on the device.

Many app data are stored exclusively on the device, for example:

app, design, and display settings
a compass direction saved by the user
a location saved by the user, including geographic coordinates
settings for compass, camera, and map modes
other locally stored functional states

Data processed or stored solely on the device do not give Androho Software automatic access to those data. However, when online services are used, particularly Google Maps, advertising, consent management, analytics, or crash reporting, the technical data described in the following sections are transmitted to the respective providers.

3. Services and Technical Components Used

The app may use the following services and technical components:

Android and Google Play services for location determination
Google Maps SDK for Android to display the online map
Google Firebase Analytics
Google Firebase Crashlytics
Google AdMob
Google User Messaging Platform / Consent SDK
Google Play Billing for optional in-app purchases
Google Play OSS Licenses to display open-source license information

Depending on the region, consent status, app version, and feature used, 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:

Approximate and Precise Location

The permissions ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION are used to determine the device’s current location at the user’s request. This may be necessary in particular to:

display the current geographic coordinates
show the current location on the map
center the online map on the current location
display the compass direction at the current location as a direction cone on the map
store a location locally and display it later on the map
calculate the direction and, where applicable, the distance to a saved location

Location permission is requested at runtime and is optional. On Android 12 and later, users may choose to provide only an approximate location even if precise location is requested. In that case, location-based displays and calculations may be less accurate.

The app does not request permission for continuous background location access. Androho Software does not initiate permanent movement or route tracking. If location permission is not granted or is later revoked, non-location-based features such as the basic compass generally remain available; location-based map and position features may be limited.

Camera

The CAMERA permission is used for camera mode. The live camera image is displayed as a visual background behind or together with the compass display so that users can identify a direction directly within the camera view.

The live camera image is generally processed locally on the device. The app does not automatically take photos or record videos. Camera images or video recordings are not automatically transmitted to Androho Software, Google Maps, Firebase Analytics, Firebase Crashlytics, or Google AdMob.

Internet and Network Status

The permissions INTERNET and ACCESS_NETWORK_STATE are used in particular for the Google Maps online map, advertising, consent management, analytics, crash reporting, optional in-app purchases, and technical communication with the Google services used for these purposes.

The map feature requires an internet connection because map data are loaded online through Google Maps. The basic compass and locally stored data can generally also be used without an internet connection, provided the relevant feature does not require the online map.

Optional Hardware Features

The camera, compass sensor, and GPS are declared as optional hardware features in the app manifest. This allows the app to be installed in principle on devices on which individual hardware components are unavailable or cannot be used. Features that depend on such components may be limited or unavailable on those devices.

5. Local Processing of Compass, Sensor, Camera, and Position Data

To determine direction, the app may access magnetic field, accelerometer, orientation, or other position-related sensors made available by the Android system. A separate Android permission is generally not required for this.

The resulting values, such as compass degrees, cardinal direction, device orientation, or magnetic field strength, are generally processed locally for the display and operation of the app. A compass direction saved by the user is stored locally on the device.

When the camera is active, the live camera image is processed locally to support the compass display visually. Camera permission does not mean that images or videos are automatically captured, uploaded, or shared with third parties.

When users save a location, the geographic latitude and longitude and related local functional data may be stored on the device. The saved location is not automatically uploaded to a server operated by Androho Software.

Androho Software does not intentionally transmit specific compass measurements, saved directions, precise GPS coordinates, saved locations, or live camera images as custom content to Google AdMob, Firebase Analytics, or Firebase Crashlytics and does not use these data to create its own advertising profiles.

6. Location Services and Google Maps

The app may use Android and Google Play services to determine the current location technically. Depending on the device, Android version, system settings, and permission granted, GPS, Wi-Fi, mobile network, or other location sources provided by the operating system may be used.

The map feature uses the Google Maps SDK for Android. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. The map feature is available only with an active internet connection.

When Google Maps is used, map data and the required map section are loaded from Google. In this context, Google may process in particular:

IP address
device and request metadata, such as operating system, device model, manufacturer, form factor, and SDK version
a pseudonymous identifier specific to the Google Maps SDK
technical crash and stability data relating to the Maps SDK
information about the requested map section
depending on use, interactions with the map, such as panning or zooming

When the map is centered on the current or a saved location, a map section for that area is requested. Depending on the location and zoom level, Google may therefore be able to identify an approximate or precise location area. However, the app does not transmit a complete list of saved locations or a permanent movement or route history to Androho Software.

The exact processing carried out by Google is also governed by Google’s privacy policies and the Google Maps Platform terms. Further information is available in the Google Privacy Policy and the data disclosure information for the Maps SDK for Android.

The legal basis for the map and location feature requested by the user is Art. 6(1)(b) GDPR. Where consent is additionally required, processing is based on Art. 6(1)(a) GDPR. For the technically necessary provision, security, and stability of the online map, Art. 6(1)(f) GDPR may apply where legally permitted.

7. 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, if a purchase is made and the relevant collection is enabled

The purposes of processing are to analyze app usage, improve features, identify technical issues, and further develop the app.

Firebase Analytics is initially disabled technically when the app starts. If the Google User Messaging Platform determines that a consent dialog must be shown to the user, Analytics is enabled only after the corresponding consent has been granted. If no consent dialog is provided after the regional and technical assessment, Analytics may be enabled in accordance with the app configuration without a prior dialog, provided this is permitted under the applicable laws.

Androho Software does not intentionally transmit precise GPS coordinates, saved locations, saved compass directions, or live camera images to Firebase Analytics as custom analytics event parameters.

The legal basis is Art. 6(1)(a) GDPR where consent is obtained. Where processing without consent is legally permitted, Art. 6(1)(f) GDPR may serve as the legal basis. Our legitimate interest lies in analyzing, improving, and stabilizing the app.

8. Firebase Crashlytics

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

Crashlytics may process in particular:

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

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

Firebase Crashlytics is initially disabled technically when the app starts. If the Google User Messaging Platform determines that a consent dialog must be shown to the user, Crashlytics is enabled only after the corresponding consent has been granted. If no consent dialog is provided after the regional and technical assessment, Crashlytics may be enabled in accordance with the app configuration without a prior dialog, provided this is permitted under the applicable laws.

Androho Software does not intentionally add precise GPS coordinates, saved locations, saved compass directions, or live camera images to Crashlytics as custom data. Technical states may nevertheless be processed in connection with a crash insofar as they are automatically collected by the SDK or are expressly added by the app as technical diagnostic data.

9. 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 this context, the following data in particular may be collected, processed, and shared with Google:

IP address and approximate location derived from it
device and app identifiers, including advertising ID or App Set ID, where available and permitted
app interactions such as app launches, taps, advertising interactions, and video views
device, operating system, and app information
diagnostic and performance data, such as app startup time, hang rate, or energy consumption
ad impressions and information relating to ad delivery
fraud prevention, security, and compliance data

The purposes of processing are:

displaying and technically delivering advertising
personalizing advertising where users have consented
measuring and analyzing advertising performance
limiting and controlling advertisements
fraud prevention, security, and compliance
financing and further developing the app

Androho Software does not intentionally transmit the precise GPS coordinates obtained through location permission, saved locations, compass directions, or live camera images to AdMob and does not use these data to personalize advertising. However, AdMob may process the IP address and derive an approximate location from it.

In regions where consent is required, personalized advertising is used only on the basis of the user’s consent. If users do not consent, non-personalized, restricted, or technically delivered ads may be shown where technically and legally possible. Certain technical processing may also be necessary for ad delivery, security, fraud prevention, and compliance when non-personalized or restricted advertising is used.

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

10. 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 displayed to the respective user and to manage the corresponding privacy choices.

Depending on the region, app version, device configuration, and Google configuration, a dialog for advertising, analytics, and crash reporting may be displayed. Users can grant or refuse consent within that dialog. Where Google requires or provides a permanently accessible entry point for privacy options, choices can later be changed through the corresponding feature in the app.

If a corresponding consent dialog is required for the user and consent has not been granted, Firebase Analytics and Firebase Crashlytics remain disabled. Depending on the consent status, advertising may be non-personalized, restricted, technically delivered, or not delivered at all.

If no consent dialog is provided after the regional and technical assessment, Firebase Analytics and Firebase Crashlytics may be enabled in accordance with the app configuration, provided this is permitted under the applicable laws.

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

11. Optional In-App Purchases through Google Play

The app may offer optional in-app purchases through Google Play Billing, for example to unlock ad-free or additional features.

Payment processing is carried out through Google Play. Androho Software does not receive complete payment details such as credit card or bank account data.

However, the app and the Google Play Console may process or display technical purchase and order information insofar as this is necessary for purchase processing, activation, 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 optional. Purchase-related data are processed only if a user makes or restores a purchase or if a corresponding purchase query is required.

The legal bases are Art. 6(1)(b) GDPR for contract performance and activation, Art. 6(1)(c) GDPR for legal obligations, and Art. 6(1)(f) GDPR for support, evidence purposes, and fraud prevention.

12. Local Storage and Android Backups

A saved compass direction, saved location, app settings, and other local functional data generally remain stored on the device until users delete or reset them within the app, clear the app data through the Android settings, or uninstall the app.

Depending on the Android version, device settings, and the backup rules configured in the app, certain local app data may be included in the Android system backup function and restored after reinstalling the app or on another device. Such system backups are performed and stored by Android or by the backup service selected by the user and not by a cloud service operated by Androho Software.

If saved locations or other local functional data are included under the Android backup rules, they may form part of such a system backup. Users can manage Android backup options in the device settings.

13. Recipients and Categories of Recipients

Depending on the region, consent status, and feature used, data may be transferred to the following recipients or categories of recipients:

Google Ireland Limited and Google LLC
Android and Google Play services for technical location determination
Google Maps Platform and the Maps SDK for Android when the online map is used
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 users have enabled a system backup and app data are covered by the backup rules

Further information about data processing by Google is available in the Google Privacy Policy, the privacy and security information for Firebase, and the information for the Maps SDK for Android.

14. 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, for example an adequacy decision, the EU-U.S. Data Privacy Framework, standard contractual clauses, or other mechanisms provided by law.

15. Retention Periods

Local app settings, saved compass directions, saved locations, and other local app data generally remain stored on the device until users delete or reset them within the app, clear the app data through the Android settings, or uninstall the app. Individual data may be restored after reinstallation through Android system backups.

Firebase Analytics data are stored in accordance with the data 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 periods.

Firebase Crashlytics generally retains crash stack traces, associated diagnostic data, and installation identifiers for 90 days before removal from live and backup systems begins.

Data relating to the Google Maps SDK, location services, AdMob, advertising reports, and related technical data are retained in accordance with the applicable Google policies, account settings, security requirements, and legal obligations. Retention periods may vary depending on the type of data and 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 Androho Software with aggregated statistics and reports relating to installation, uninstallation, 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.

16. Data Security

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

Please note that the security of locally stored data also depends on the device’s security settings, the Android version, any configured screen lock, and the backup service used.

Location data can be particularly sensitive. Users should therefore protect access to the device appropriately and delete saved locations when they are no longer needed.

17. Legal Bases for Processing

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

Processing	Legal basis
Local compass, sensor, camera, settings, and storage features	Art. 6(1)(b) GDPR for providing the app features requested by the user
Optional determination and local processing of approximate or precise location	Art. 6(1)(b) GDPR for providing the position, direction, and distance features requested by the user; where additionally required, Art. 6(1)(a) GDPR
Google Maps and loading the online map	Art. 6(1)(b) GDPR for providing the map feature requested by the user; where consent is required, Art. 6(1)(a) GDPR; otherwise, only where legally permitted, Art. 6(1)(f) GDPR for technical provision, security, and stability
Firebase Analytics	Art. 6(1)(a) GDPR where consent is obtained; otherwise, only where legally permitted, Art. 6(1)(f) GDPR for analyzing and improving the app
Firebase Crashlytics	Art. 6(1)(a) GDPR where consent is obtained; otherwise, only where legally permitted, Art. 6(1)(f) GDPR for crash analysis, stability, and technical security
Personalized advertising and related storage access	Art. 6(1)(a) GDPR where consent is required
Technical ad delivery, restricted or non-personalized advertising, ad measurement, fraud prevention, security, and compliance	Art. 6(1)(a) GDPR where consent is required; otherwise, only where legally permitted, Art. 6(1)(f) GDPR
Optional in-app purchases	Art. 6(1)(b) GDPR for contract performance and activation; Art. 6(1)(c) GDPR for statutory retention obligations; Art. 6(1)(f) GDPR for support, evidence purposes, and fraud prevention
Compliance with legal obligations, accounting, and record-keeping duties	Art. 6(1)(c) GDPR

Where processing is based on Art. 6(1)(f) GDPR, the legitimate interest lies in particular in the technical provision, financing, and improvement of the app, stability and security, troubleshooting, fraud prevention, support, and abuse detection.

18. User Rights

Subject to the requirements of the GDPR, users have in particular the following rights:

right of access
right to rectification
right to erasure
right to restriction of processing
right to data portability
right to object to certain processing
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 many data are stored exclusively on the device. These include in particular app settings, saved compass directions, and saved locations. Androho Software has no access to these local data. Users can delete or reset them within the app, clear the app data through the Android settings, or uninstall the app.

Location and camera permissions can be revoked at any time in the Android settings. Revoking a permission prevents future access but does not automatically delete saved locations or other local app data that already exist.

The app does not have its own user account system or its own personal cloud database. Androho Software can therefore often not directly associate technical data from Google services with a specific individual. Where personal data are processed through Google services, the handling of access or deletion requests depends on whether a technical association is possible and legally permitted based on the available information.

Where data are processed directly by Google as an independent controller, users may also exercise their rights directly against Google. This applies in particular to Google account, map, location service, payment, advertising, device, and system backup data.

Statutory retention obligations, particularly for purchase, billing, tax, or accounting data, may mean that certain data cannot be deleted immediately.

19. Changing Consents, Permissions, and Privacy Options

Where a consent dialog or an entry point for privacy options is displayed, users may grant, refuse, or later change consent for advertising, analytics, and crash reporting. Changes can be made through the corresponding privacy feature in the app where this is available depending on the region, app version, and Google configuration.

Withdrawal of consent applies for the future. The lawfulness of processing carried out on the basis of consent before its withdrawal remains unaffected.

Location and camera permissions can be managed or revoked in the Android system settings. Users can also manage the advertising ID, personalized advertising, Google privacy settings, location services, and Android backup options in the Android or Google settings of the device.

20. 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 users or similarly significantly affects them. Depending on the user’s consent, advertising services may use their own procedures to select and personalize advertisements.

21. Changes to this Privacy Policy

We may amend this Privacy Policy if the app’s features, services used, permissions, legal requirements, or technical processes change. The current version will be made available on our website.