Privacy Policy
1. Scope and developer
This policy is intended to cover software applications published by LMBR, including current and future releases distributed through Google Play or other channels. It applies only insofar as the data practices described here accurately reflect the particular application and its version. Where an application processes information differently, this policy must be updated or supplemented with an application-specific notice before that version is published. The publisher is LMBR; its legal identity and contact information should be consistent with the details provided in the relevant app store.
2. Information handled by the applications
Depending on the application and features selected by the user, the software may process user-entered information, measurements, sensor readings, equipment data, settings, calculation results and files created or imported by the user. Such information is used to provide the functions requested by the user. Whether any such data are stored locally, transmitted or accessible to the developer depends on the individual application version and must be verified before publication.
3. Device permissions and connections
Depending on its functions, an application may request access to Bluetooth, USB connections, device sensors, storage or other device features. Permissions should be requested only where necessary for the relevant functionality. The permissions actually used and their purposes must be confirmed separately for each published application and version.
4. Collection, sharing and third-party services
App-specific verification is required: confirm whether the published app or its embedded libraries collect, transmit or share personal data, device identifiers, diagnostics, usage data, location-related information, or other information. If analytics, crash reporting, advertising, cloud services or other third-party SDKs are present, identify the data involved, the purpose and the recipients here. Do not assume that data remain only on the device without testing the app and its dependencies.
5. Storage, retention and deletion
Depending on the features provided, an app may save measurement records or configuration information on the user's device. Before publication, describe the actual storage locations and retention periods, explain how users may delete locally stored data, and disclose the retention and deletion rules for any information held by the developer or third parties. If the app provides accounts, describe how accounts and associated data can be deleted.
6. Security
Security measures must reflect the actual application implementation. In particular, confirm whether user information is transferred from the device and, where relevant, how it is protected in transit and at rest. No absolute guarantee of security is given.
7. Children's privacy
Any age restrictions or child-directed features, where applicable, must be stated according to the actual intended audience and functionality of each application.
8. Updates
This policy may be updated when application functionality, third-party components or data practices change. The revision date will be displayed above.
9. Contact
For privacy-related questions, requests regarding personal information, or developer contact details, use the LMBR contact page. Verify that this page provides a working contact method before publication.