Privacy Policy
Morse Room: Learn & Chat (Android application identifier com.morsenepal) and its website, Morse Room, are provided by Lelin Adhikari. This policy describes how the trainer and optional Morse Chat Room handle information.
Effective date: .
Local practice · Chat data · Notifications · Delete your account · Contact
Lessons and practice
Learn, Practice, and the character reference do not require an account. Guest lesson progress, audio speed, Farnsworth speed, frequency, volume, and theme are saved on your device. Practice answers and replay audio are processed on your device. These training modes generate Morse tones without microphone access.
If you sign in, we also store completed lesson numbers, your best lesson scores, the lesson sequence, and completion times with your account in Cloudflare D1. This restores your lessons after reinstalling and syncs them between the app and website. Existing guest lessons can be added when you first sign in on that device. Offline account progress stays on the device and syncs when you reconnect. Different accounts have separate saved lessons.
Clearing browser or app storage removes local records and settings. Signed-in lesson progress can be restored from the server after signing in again. Guest progress has no server copy.
Advanced Radio mode
Advanced Radio mode is also available without an account. When you choose Start receiving, the Android app requests microphone permission to process live audio from your selected microphone or wired/USB audio input. Audio samples are processed on your phone in memory, are not saved as recordings, and are not uploaded. Receiving stops when you leave the app or stop the session. Decoded radio text stays in the current app session unless you copy it yourself.
Your Advanced mode preference, station callsign, optional station name and location, saved callsigns, and radio connection preferences are stored locally on your device. They are not submitted to the chat service. If you connect a supported USB keyer and choose Transmit, your message and timing settings are sent to that connected device for radio transmission. Over-the-air radio signals can be received by other stations and are not private chat messages.
Google sign-in and your profile
Chat is optional. When you choose Sign in with Google, Google authenticates you. We receive and store your Google account identifier and verified email address when Google supplies one. We also store an internal account identifier, the username you choose, and account creation time. This lets us identify your account, keep you signed in, and route friend requests and messages.
The Google sign-in request includes basic profile access. We do not store your Google profile name or photograph, and we never receive your Google password. This sign-in does not give us access to your Gmail messages or Google contacts.
In the installed app, Google sign-in opens your browser and then returns to the app. A temporary sign-in transfer record lets the app receive the verified session without putting a reusable session token in the return link.
A separate Review access sign-in is available for app reviewers. It uses developer-provided credentials and isolated test conversations. It does not connect to a personal Google account or allow contact with ordinary chat accounts.
Your username is visible to people in your conversations and friend requests. Your email is not displayed in conversation profiles. Someone who already knows your exact registered email address or username can use it to find your chat account and send a friend request. An email lookup may therefore confirm that an account exists. There is no phone address book import.
Messages, friends, and groups
We store friend requests, accepted friendships, group names, public or private visibility, invite codes, join requests, membership records, message text, its Morse representation, sender identifiers, message times, and read positions. We use these records to deliver chat, show conversation history, manage access, prevent duplicate messages, and show unread messages and requests.
A direct conversation is available to its members. Every group member can read the group's history. Public group names and member counts appear in group discovery; the creator accepts or declines requests to join. Private groups use invite codes or links. A valid invitation can grant access to that group's history. Share invitations only with people you intend to include. The creator can remove a member.
Conversation members can reveal your original text or the decoded text from a Morse message. Morse is a readable code, not encryption. Messages are not end-to-end encrypted; the developer and hosting service can access stored records as needed to operate the service or address support and abuse reports. Avoid sending passwords or other sensitive information. Other people may retain copies or screenshots of messages they receive.
If you block another person, we store the blocked account identifiers to apply that choice. If you report a message, we store the reported message, the reason you provide, the involved account identifiers, and report time so the developer can review the concern. Reports are not shown to other chat participants.
Optional Android message notifications
Notifications are optional and require a chat account. If you enable them, Google Firebase Cloud Messaging delivers a signal to your Android app when a friend or group member sends a message. We store a push registration token, a random app installation identifier, and the account and session associated with that installation in Cloudflare D1. These identifiers route notifications to your app; they are not advertising identifiers.
Google processes a Firebase installation identifier, app configuration and version, and technical network information needed to operate push delivery. We do not use Firebase Authentication, Firestore, Google Analytics, advertising tracking, or message-delivery analytics for this feature. Firebase messaging starts when you use the notification feature, rather than automatically during lessons or practice. Google's handling is described in its Firebase privacy information.
The push payload contains message and conversation identifiers. It does not include your message text, Morse content, username, email, or chat credential. The app retrieves the message through our authenticated HTTPS API. Show text, Listen, and Reply can use that message from the notification. A reply is stored and delivered under the same rules as a message sent inside Chat. Morse audio is generated on the device and is not a recording.
The Android app encrypts its notification credential, cached message previews, and reply drafts using Android Keystore. The preview cache is limited to 20 messages and previews older than seven days are pruned during notification processing. Notification previews and actions follow the device's lock-screen and notification settings. Signing out or deleting your account clears account-specific notification data on that app and revokes the server credential. The installation identifier and push token may remain on the device for reuse without an active chat account association.
You can decline the notification prompt or turn notifications off in Android's app notification settings. Lessons, practice, and Chat remain available. Pending delivery jobs expire after 24 hours. Android settings, battery restrictions, connectivity, and Google's delivery service can delay or prevent a notification.
Storage, network information, and service providers
Android app builds with automatic updates use Expo's EAS Update service to check for and download compatible app code and assets when the app opens. Requests include technical information such as the operating system, app project and runtime version, and a random update token. Expo may also process network information such as your IP address. These update requests do not send your chat messages, Google sign-in credentials, or lesson answers to Expo. Downloaded updates take effect on a later app launch; the installed trainer remains available offline. See Expo's Privacy Policy and its explanation of app update data.
Cloudflare hosts the website and chat API and stores chat records in its D1 database. Cloudflare processes network information such as IP addresses, request traffic, and system information to deliver and protect its services. At the start of Google sign-in, our service stores a hashed IP address with a short-lived request count to limit repeated sign-in attempts. Other chat request limits use your internal account identifier.
Google processes sign-in and optional Firebase push delivery under its Privacy Policy and applicable service terms. Cloudflare processes hosting and network data under its Privacy Policy. Expo processes app update requests as described above. These providers may process information outside your country.
We do not sell your information or use your account or messages for advertising. The trainer and chat do not include advertising or behavioral analytics trackers. We disclose information to the conversation participants you choose, the providers needed to operate the service, and when required by applicable law.
Cookies and security
Chat uses an essential session cookie and a short-lived Google sign-in cookie. Session tokens are stored as hashes on the server. Production cookies use Secure and HttpOnly protections. The live website and its API use HTTPS to protect data in transit. Conversation APIs check signed-in membership before returning messages.
A sign-in session expires after 30 days. Signing out removes the current session and cookie; it does not delete your account or conversations. Temporary sign-in verification expires after 10 minutes. Expired server sessions, sign-in records, and request-limit records are removed during later sign-in cleanup. We do not use these cookies for advertising.
Retention and account deletion
Chat accounts, friendships, memberships, messages, block records, and safety reports have no scheduled automatic expiry. They remain in the live database until you delete your account or the developer removes them in response to a verified request or a service issue.
To delete your Morse Room: Learn & Chat account and its associated data, visit Delete account. You can also use the Delete account option in your account menu. Signing in verifies which account you wish to delete. If you cannot sign in, email lelin.adhikari45@gmail.com with your username and registered email. We may ask you to verify ownership before acting on an email request. Never send your password.
Deletion removes your live account profile, Google sign-in identity, sessions, friendships, friend requests, group join requests, memberships, blocks, messages you sent, safety reports associated with your account or removed messages, registered notification devices, their pending delivery jobs, and synced lesson progress. It also removes your direct conversations. A group with other members remains under another member's ownership; an empty group is removed. This does not delete your Google account, other members' unrelated group messages, or copies people have already saved. We do not deliberately retain a separate copy of your deleted live account data.
Cloudflare's automatic D1 recovery history on the current free plan can retain earlier database records for up to seven days after live deletion. Those records are held for recovery, are not available through the app, and expire from that recovery window. Data handled independently by Google or Cloudflare is subject to their own retention rules. Deleting a chat account does not clear local training progress on other devices; clear the local browser or app storage to remove it.
Your choices and questions
You can use the trainer without Google sign-in, choose whether to send a friend request or message, decline requests, block a person, report a message, turn notifications off, sign out, and delete your chat account. Contact us to ask about your stored information, request a correction or a copy, or raise a privacy concern. We may verify your account ownership before disclosing or changing account data.
If a parent or guardian believes a child has provided personal information that should be removed, contact us using the details below. Google sign-in is subject to Google's account eligibility rules.
Contact the developer
Lelin Adhikari
Email: lelin.adhikari45@gmail.com
Website: lelinadhikari.com.np
We will update this page and its effective date when data handling changes. New permissions or material changes to collection will also be explained in the app when needed.