Morseify / Home
Privacy PolicyTerms of ServiceAccount Deletion

Legal

Morseify Privacy Policy

Last updated: 2026-03-30

Morseify is an Android application for learning Morse code, composing messages, and playing Morse signals through audio, light, and vibration. This privacy policy explains what information the app may process, how it is used, and what choices users have.

This policy applies to Morseify on Android and related support channels operated by HandySparkSoft (D. A.).

Summary

  • You can use major parts of Morseify without creating an account.
  • If you choose to sign in, Morseify may process account information such as your email address or Google account identity.
  • Morseify may also create an anonymous Firebase session identifier when cloud-backed features are used without a registered account.
  • Morseify integrates Firebase services for authentication, analytics, crash reporting, remote configuration, and performance monitoring.
  • Morseify integrates Google AdMob to show ads and measure ad delivery.
  • Saved messages and preferences can be stored locally on the device, and some features may also sync through Firebase-backed services.

Information Morseify May Process

Information You Provide

Morseify may process information you actively provide, such as:

  • email address and password if you register with email/password
  • Google account information if you choose Google sign-in
  • Firebase anonymous session identifiers when the app needs a backend-linked session
  • profile preferences you configure in the app
  • messages you create, save, or share through app features
  • feedback you voluntarily send through the support channel

Information Processed Automatically

Morseify and its service providers may automatically process:

  • app usage events and analytics data
  • crash diagnostics and performance information
  • device and app identifiers used by Firebase and AdMob
  • general device metadata required to deliver app features, ads, and service reliability
  • Remote Config state that may be reflected into analytics user properties

Device Features Used

Morseify can use:

  • internet access for Firebase, remote configuration, and ads
  • vibration for haptic Morse playback
  • camera flash and camera capability, when available, for visual Morse signaling
  • file sharing through Android's FileProvider when you export content

Morseify does not declare location access or Health Connect access in the current Android manifest.

How Information Is Used

Morseify may use processed information to:

  • authenticate users and maintain signed-in sessions
  • store and retrieve saved messages and profile-related app data
  • provide Morse playback, sharing, and learning features
  • understand app usage and improve product quality
  • detect crashes, errors, and performance regressions
  • deliver advertising through Google AdMob
  • control feature behavior safely through Remote Config
  • respond to support, legal, and compliance-related requests

Legal Bases And User Choice

Where applicable, processing is based on one or more of the following:

  • your consent, such as when you choose to create an account or use Google sign-in
  • performance of the requested service, such as storing your saved content
  • legitimate interests in app security, reliability, debugging, and improvement

If you do not want optional account processing, use Morseify without signing in where supported.

Third-Party Services

Morseify currently integrates third-party services including:

  • Firebase Authentication
  • Firebase Firestore
  • Firebase Storage
  • Firebase Analytics
  • Firebase Crashlytics
  • Firebase Remote Config
  • Firebase Performance Monitoring
  • Google Mobile Ads (AdMob)
  • Google Sign-In / Credentials APIs

These providers may process information according to their own privacy policies and terms.

At the time of this policy update, the repository documentation indicates Firebase Analytics is active and does not yet document a dedicated analytics consent gate. Review that behavior before wider public release if regional consent requirements apply.

Data Sharing

Morseify does not sell personal information. Information may be shared only as needed with service providers that operate app infrastructure, analytics, crash reporting, performance monitoring, authentication, storage, and ad delivery on behalf of the app.

Data Retention

  • Local preferences remain on the device until you clear app data or uninstall the app.
  • Remote account or content data may remain until it is deleted from the relevant backend systems. In the current codebase, saved messages are stored in Firestore under the authenticated or anonymous Firebase user identifier.
  • Crash, analytics, performance, and advertising data are retained according to the policies and retention settings of the integrated providers.
  • We do not guarantee indefinite storage of user content, account state, or cloud-synced data. You are responsible for keeping your own backups of important content.

Security

Reasonable technical measures are used to reduce unauthorized access, but no system can guarantee absolute security. You should avoid storing sensitive personal or confidential information in saved message content.

Children

Morseify is not intentionally directed to children under the minimum age required by applicable law without parental authorization. Review and configure the Play Console target-audience settings before broader release.

International Users

Depending on the service provider involved, information may be processed outside your country of residence.

Your Rights

Depending on your jurisdiction, you may have rights to access, correct, delete, or restrict the processing of personal data.

Changes To This Policy

This policy may be updated when the product, legal requirements, or integrated services change. The latest version will be published at this page.

Contact

Legal entity: HandySparkSoft (D. A.)

Contact email: handysparksoft@gmail.com

Contact address: Valencia, Spain

Canonical route: /legal/privacy-policy/

Legacy root links stay active through Hosting redirects for compatibility.