HooLang

HooLang Privacy Policy

Česká verze

Effective date: 20 November 2026

1. Who is responsible

The controller of personal data is Ondřej Hoos, Školská 660/3, 110 00 Praha, Česko, IČO 05467390 ("we"). Send privacy questions to support@hoolang.app.

2. In short

3. Data that stays on your phone

The app stores the following in its storage on your phone: articles and texts including their source address, your reading position in each text, saved words and their meanings, practice results and settings. It does not send them anywhere. You can delete them in the app (by deleting a text or words) or by uninstalling the app.

On iPhone, the app's storage may be part of your device backup to iCloud or a computer if you have backups turned on. Apple manages that backup according to your settings. On Android, the app turns off backup to Google's cloud. When you transfer data directly from an old phone to a new one, the system may still transfer it.

The dictionaries and pronunciation data are part of the app, so looking up a word happens only on your phone and is not sent anywhere.

4. Loading an article from a link, and pronunciation

When you load an article from a link (or, on Android, share a link to the app), your phone connects directly to that website, just like a browser. The website sees your IP address and ordinary technical connection data and follows its own privacy policy. On Android, the website may store cookies in the app as it would in a browser. They stay on your phone and are deleted when you uninstall the app or clear its data. On iPhone, cookies from loaded pages are not kept. We do not receive the page address or its content. The "Open original" button (Otevřít originál) opens the page in your browser.

Pronunciation is played by your phone's text-to-speech engine (from Apple, or from your phone maker or Google on Android). The app only passes it the word to be read. This processing follows your phone's settings and policies.

5. Crash reports (Firebase Crashlytics)

What is sent: when the app crashes, it sends a technical error record (where in the code it happened and the app state at that moment), device and system information (for example phone model, system version, free memory), the app version, the time and a random installation identifier that tells us how many installations a bug affects. The IP address is processed during transfer.

Why: to find and fix bugs and keep the app reliable.

Legal basis: our legitimate interest in a reliable and secure app (Art. 6(1)(f) GDPR). You can object at any time by turning crash reports off.

How long: Firebase keeps crash records and related identifiers for 90 days and then deletes them.

How to turn off: Settings › Privacy › Send crash reports (Posílat zprávy o pádech).

6. Usage statistics (Google Analytics for Firebase)

When: only if you turn them on in the welcome guide ("Sdílet anonymně") or in Settings › Privacy › Share anonymous statistics (Sdílet anonymní statistiky). Without your consent, no statistics are sent.

What is sent:

Never sent: article texts, words and their meanings, links, your name, e-mail or advertising identifier. According to Google's documentation, Google Analytics does not store the IP addresses of users in the EU and only uses them to derive approximate location.

The app calls these statistics anonymous because they contain nothing that would let us recognise you. Strictly speaking they are pseudonymous: they are linked to a random installation identifier, not to you.

Why: to learn which features are used, where people run into problems and what to improve.

Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time with the switch in Settings › Privacy. Withdrawal does not affect processing before it.

How long: detailed event data and identifiers are kept in Google Analytics for 2 months. Aggregated reports without identifiers (for example the number of users per week) may be kept longer.

What we do not use: Google signals, ad personalisation or links to advertising services. We do not use the data for profiling or automated decision-making.

7. Who processes the data

Crash reports and statistics are processed by Google (Firebase) as our processor under the Firebase data processing and security terms. Under these terms Google is bound to protect the data at least as described in this policy and to use it only on our instructions. Google may process the data outside the EU, in particular in the USA. Transfers are protected by the EU-U.S. Data Privacy Framework, under which Google LLC is certified, or by standard contractual clauses. We do not sell the data or share it for advertising.

8. Deleting data

Crash data is deleted automatically after 90 days and detailed statistics after 2 months. Turning off both switches in Settings › Privacy stops new data from being sent. Uninstalling the app deletes all data on your phone and the random identifiers. Because you have no account and we do not know who you are, we usually cannot find your data in Firebase. If you can help us identify it, we will gladly delete it. Write to support@hoolang.app.

9. Your rights

Under the GDPR you have the right to access your data, to rectification and erasure, to restriction of processing, to data portability, to object and to withdraw consent. Send requests to support@hoolang.app. We will reply within one month. If we cannot link data to you, Art. 11 GDPR does not require us to search for it, but we will tell you. You also have the right to lodge a complaint with the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů, www.uoou.cz) or with the supervisory authority where you live.

10. Children

The app has no content unsuitable for children and is not directed at children under 13. In the Czech Republic, people aged 15 and over can consent to statistics on their own. If you are younger, only turn statistics on with a parent's consent. Crash reports do not depend on consent and can be turned off.

11. Security

Data sent to Firebase is encrypted in transit (HTTPS). Data on your phone is protected by your device's security, so we recommend using a screen lock.

12. Changes to this policy

If we change this policy, we will publish the new version on this page with a new effective date. We will announce significant changes, such as collecting new kinds of data, in the app or in the update notes. If they require new consent, we will ask for it.

13. Contact

Ondřej Hoos, Školská 660/3, 110 00 Praha, Česko, IČO 05467390, support@hoolang.app