MORSEBOUND · iCharles
Privacy Policy
Effective August 19, 2026
This Privacy Policy explains how Morsebound, an independent educational Morse code app by iCharles, handles information when you use the Web or Android app.
1. Data stored locally
Morsebound stores learning progress and preferences on your device or browser. This can include character mastery and retention state, reaction-time and accuracy statistics, confusion history, streaks, career/progression information, and app settings. Local data remains on that device/browser until you reset it, clear browser/app data, or uninstall the app, subject to platform backup behavior.
2. Accounts and authentication
Morsebound offers account creation and sign-in using email/password and Google Sign-In. Authentication is provided through Google Firebase Authentication. Depending on the sign-in method, Firebase Authentication can process account identifiers such as your email address, Firebase user ID, authentication provider information, and Google profile information made available by the sign-in provider.
3. Cloud synchronization
When you are signed in, Morsebound can store synchronized learning state in Google Cloud Firestore under your authenticated user ID. The synchronized state can include mastery/retention progress, career and streak information, and app settings. Morsebound uses per-user Firestore access rules so authenticated users can access only their own Morsebound user data through the app.
4. How the data is used
- Authenticate your Morsebound account.
- Restore and synchronize learning progress between supported devices.
- Adapt training to weak, slow, confused, and overdue learning material.
- Preserve your settings, streaks, and progression.
- Provide account support, security, and deletion when requested.
5. Advertising, analytics, and sale of data
Morsebound does not include an advertising service or a dedicated analytics service in this release. Morsebound does not sell personal information.
6. Service providers
Morsebound relies on third-party infrastructure needed to operate the service:
- Google Firebase for Authentication and Cloud Firestore synchronization.
- Google Sign-In when you choose Google as your authentication method.
- GitHub / GitHub Pages to host the public Web app, public policy pages, release information, and direct Android release downloads.
Those providers can process normal technical information required to provide their services, such as network requests and service logs, under their own terms and privacy practices.
7. Audio, microphone, camera, and contacts
Morse training audio is generated or bundled for training. Morsebound does not require microphone recording, camera access, phone contacts, or precise location for its current learning modes.
8. Security
Cloud communication uses HTTPS/TLS provided by the platform and service providers. Cloud data access is authenticated and Firestore rules restrict Morsebound user documents by Firebase user ID. No online system can be guaranteed completely secure, so users should protect their account credentials and device access.
9. Retention and deletion
Local data is retained until you reset Morsebound data, clear the browser/app storage, or uninstall the app. Cloud learning data is retained while your Morsebound account remains active unless it is deleted earlier.
You can delete your cloud account from Settings → Account & cloud sync → Delete Cloud Account. Morsebound is designed to delete the synchronized Firestore state associated with the account and then delete the Firebase Authentication account. You may also request deletion without reinstalling the app through the public Account & Data Deletion page.
10. Children
Morsebound is a general educational tool and is not designed to knowingly collect more personal information than is needed for authentication and synchronization. Parents or guardians should supervise account creation by children where required by applicable law or platform policy.
11. Changes to this policy
This policy may be updated when Morsebound’s features, providers, or data practices change. The effective date at the top of this page identifies the current published version.
12. Privacy contact
For privacy questions or deletion requests, contact cselrahc.117@gmail.com. Do not send passwords, authentication codes, or other secret credentials.