Privacy Policy

Tomáš Hubálek built the My Android Eargnings app as a freemium and ads-supported app. This service is provided by Tomáš Hubálek and is intended for use as is.

This page is used to inform website visitors regarding my policies with the collection, use, and disclosure of Personal Information if anyone decided to use my Service.

If you choose to use my Service, then you agree to the collection and use of information in relation with this policy. The Personal Information that I collect are used for providing and improving the Service. I will not use or share your information with anyone except as described in this Privacy Policy.

The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which is accessible at My Android Eargnings, unless otherwise defined in this Privacy Policy.

Information Collection and Use

The app itself don't colllect any personally identifiable information but it uses third party services that may collect information used to identify you:

Log Data

I want to inform you that whenever you use my Service, in case of an error in the app I collect data and information (through third party products) on your phone called Log Data. This Log Data may include information such as your devices’s Internet Protocol (“IP”) address, device name, operating system version, configuration of the app when utilising my Service, the time and date of your use of the Service, and other statistics.

Service Providers

I may employ third-party companies and individuals due to the following reasons:

I want to inform users of this Service that these third parties have access to your Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose.


I value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and I cannot guarantee its absolute security.

Links to Other Sites

This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by me. Therefore, I strongly advise you to review the Privacy Policy of these websites. I have no control over, and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.

Children’s Privacy

This Services do not address anyone under the age of 13. I do not knowingly collect personal identifiable information from children under 13. In the case I discover that a child under 13 has provided me with personal information, I immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact me so that I will be able to do necessary actions.

Changes to This Privacy Policy

I may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. I will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately, after they are posted on this page.

Contact Us

If you have any questions or suggestions about my Privacy Policy, do not hesitate to contact me.

Google's Limited Use Requirements

App’s use of information received from Developer Console will adhere to Google API Services User Data Policy including Google's Limited Use Requirements. Here are details:

Allowed Use: We read your data just to store them locally in the application and display reports. Data can leave an app only after user's explicit action (sharing of the chart, exporting table).

Allowed Transfer: The application does not send data anywhere of its own volition. It only remains stored on the device it was downloaded to.

Prohibited Advertising: Data are not used for advertising purposes.

Prohibited Human Interaction: Developer of the application can't read your data. Sensitive data sent to Firebase Crashlytics are obfuscated in the way they can't be restored. Example: email is stored in the log files as my.****com.