Last updated: August 12, 2026
Hi Morse is a Morse code learning and translation app developed by BaTip. This Privacy Policy explains what information the app handles and how it is used.
Hi Morse does not require an account. Morse text, practice input, keyboard settings, progress, recent patterns, and app preferences are stored locally on your device.
On Android and iOS, limited usage analytics is enabled by default to help understand how the app is used and improve it. You can turn it off or on at any time in More > Privacy > Usage analytics without affecting app features or learning progress.
Hi Morse does not collect names, email addresses, phone numbers, contacts, precise location, photos, audio recordings, camera images, or payment information.
The app does not upload the Morse text you type, translate, copy, paste, or practice. It also does not send answers, practice targets, custom-set names or contents, clipboard contents, feedback contents, audio recordings, or manual keying rhythms to Analytics. Those actions and contents are processed on your device.
Hi Morse may store the following information locally on your device:
This local data is used only to provide app features. It is not sent to BaTip servers.
On Android and iOS, Hi Morse uses Firebase Analytics. Usage analytics is enabled by default. The app does not show a separate data-sharing confirmation prompt. You can turn it off or on at any time in More > Privacy > Usage analytics.
While Usage analytics is enabled, Hi Morse may send limited events about:
Analytics may also include the app version, broad device type and operating system information, an app installation identifier generated by Firebase, the selected app language, and an estimated country or region derived by Google from network information. Granular GA4 location and device collection is disabled, so Hi Morse does not use city-level location, device brand/model, detailed operating-system version, or screen-resolution data for Analytics. The app does not request precise-location permission for Analytics and does not set an account or custom user ID. Usage analytics is used to understand and improve Hi Morse.
Turning Usage analytics off stops future Analytics collection and resets Analytics data stored locally by Firebase on that device. It does not delete learning progress or other app settings, and it does not delete data already transmitted to and processed by Google. Turning it on again resumes collection only for future activity; Hi Morse does not backfill activity from the time it was off. Hi Morse does not send an Analytics event recording your on/off choice.
Hi Morse accesses the clipboard only when you use app actions such as Copy or Paste. Clipboard content is used for the action you requested and is not uploaded by the app.
Hi Morse can use your device flashlight to blink Morse code when you choose flash feedback or flash playback. The app only turns the flashlight on and off. It does not capture photos, videos, or camera images.
Hi Morse uses Firebase Crashlytics to help identify and fix crashes and stability issues. Crashlytics may collect diagnostic information such as crash logs, stack traces, app version, operating system version, device model, device state, and identifiers used for crash reporting.
This information is used only to diagnose and improve app stability. Hi Morse does not use Crashlytics data for advertising.
Firebase Crashlytics is provided by Google. You can learn more about Firebase privacy and data handling here:
When Usage analytics is enabled, Analytics events may also be attached to Crashlytics reports as diagnostic breadcrumbs. They remain limited to the fixed categories described above and do not include Morse or answer content.
If you choose to send feedback, report a bug, or contact the developer, your email app may create a message addressed to the support email address. The message may include app version, operating system, selected language, current screen, and timestamp to help diagnose the issue. You can edit or remove this information before sending the email.
Emails you send are used only to respond to your request and improve the app.
Hi Morse may use the following third-party services:
These third-party services process information under their own privacy policies.
Hi Morse is a general-audience educational utility and is not directed specifically to children under 13. The app does not knowingly collect personal information from children. If you believe a child has provided personal information through a feedback email, please contact us so we can remove it.
Local app data remains on your device until you delete it in the app, clear app data, or uninstall the app.
Crash reports are retained by Firebase Crashlytics according to Firebase retention practices. Feedback emails are retained only as long as needed to respond to support requests and improve the app.
Firebase Analytics user-level and event data is configured for a 14-month retention period. New activity does not reset that retention period. Turning Usage analytics off prevents future collection but does not immediately delete data already transmitted and retained by Google Analytics.
Hi Morse uses standard platform and service-provider security measures. Diagnostic data sent to Firebase is transmitted using secure connections. However, no method of transmission or storage is completely secure.
If this Privacy Policy is translated into other languages, the English version controls in case of any inconsistency.
This Privacy Policy may be updated when the app changes. For example, if Hi Morse adds advertising or in-app purchases in a future version, this policy and the store data-safety declarations will be updated before release.
If you have questions about this Privacy Policy, contact:
nguyenanhtiep12@gmail.com