Morse Code Translator (“the app”) translates text to Morse code and back, plays Morse as sound, flashlight or vibration, and includes a Morse dictionary, practice quizzes, an SOS beacon and a history. This policy explains what the app does with data.
Translation happens on your device. The app keeps a history of up to 200 encoded and 200 decoded messages (the text, its translation and the time) and your settings, stored only on your device and never uploaded. You can delete single entries or clear each history.
This data is excluded from Android cloud backup and from device-to-device transfer, so Android does not copy it to another device or to your Google account.
Sound uses beeps built into the app; the flashlight is switched on and off through Android’s torch control, which needs no camera permission; vibration uses the vibration motor. The app never records audio and never reads your clipboard.
Advertising. The app shows full-screen ads from Google AdMob, with Meta Audience Network as a mediation partner. To select and measure ads, these providers may collect your device’s advertising ID, your IP address and the approximate location it implies, and device, app and ad-interaction information. In the European Economic Area, the United Kingdom and other regions where it is required, the app asks for your choice through Google’s User Messaging Platform before any ad is requested, and you can change it at any time from Privacy options in the app, which appears where it is required.
Google’s policy: policies.google.com/privacy
How Google uses data from apps that use its services: policies.google.com/technologies/partner-sites
Meta’s policy: facebook.com/privacy/policy
Analytics. The app uses Google Analytics for Firebase to see which features are used. Events record which features are used — for example the playback channel and speed, practice answers, and the length of a message rounded into a broad range. Events never contain the text or Morse you entered. Firebase also records some information automatically: an app-instance identifier, the device model, the operating-system and app versions, the app language, and an approximate country derived from your IP address, along with standard events such as the first open and the start of a session. Crash and error reports may also record which output (sound, flashlight or vibration) failed, never a message.
Crash reporting. Firebase Crashlytics receives a report when the app crashes: the error and stack trace, the device model, the operating-system and app versions, and an installation identifier.
Notifications. The app can receive occasional announcements through Firebase
Cloud Messaging. After your first translation the app asks once whether you want notifications; Android asks for permission only if you agree. If you allow notifications, the app subscribes this installation to a
general topic (all_users), and messages go to everyone subscribed to it — the
app does not target individual devices. Firebase may register a messaging token for the
installation; the token identifies the installation, not you. Turning notifications off in Android settings stops them.
The app is not directed at children under 13 and does not knowingly collect personal information from them.
If this policy changes, the updated version is published at this address with a new effective date.