MORSEME

Privacy Policy

Effective 28 April 2026

MorseMe is built around a simple promise: nothing is saved. This page lists exactly what the app does with data, in plain language, so you can verify that promise yourself.

What the app collects

MorseMe collects only what's needed to connect two phones in real time. Specifically:

A 6-digit ID — generated on first launch on your device. It identifies you to peers you choose to share it with. It is not linked to your name, email, phone number, or Apple ID.
An optional display name — only if you choose to set one in the app's user menu. Leave it blank and nothing is sent. You can change or clear it at any time.
Online / offline status — a single boolean flag and a timestamp, used so the person calling you can see whether you're reachable right now.
An active-tap flag during a call — while a call is open, a single boolean (true while you are holding a tap, false when you're not) is mirrored to your peer in real time. This is the entire mechanism by which one phone makes the other one flash.
A push-notification routing token — a Firebase Cloud Messaging (FCM) token used solely to ring your phone when someone calls your ID. It does not identify you to anyone outside the app.

What the app does not collect

No message content. The Morse "messages" you tap are not saved, transmitted as text, or recorded anywhere. The app only sends the on/off tap flag described above. The instant a tap ends, the flag goes back to false and there is no record that the tap happened.
No call history or transcripts. When a call ends, nothing about it is retained — not the duration, not the time, not who you talked to.
No contacts, photos, microphone, camera, location, or health data. The app does not request permission to access any of these and never will.
No analytics, no tracking, no advertising SDKs, no crash-reporting SDKs. There is no third-party tag manager, no Google Analytics, no Facebook SDK, no Crashlytics, no Sentry. Nothing watches what you do inside the app.
No account. There is no email, password, phone number, or social login. Reinstalling the app on a new device generates a new ID; the old ID becomes unreachable.

What's stored only on your device

The following data lives in your iPhone's local storage and is never uploaded to MorseMe's backend:

Your own 6-digit ID and chosen nickname.
A list of peers you've recently connected with, so they show up in the "Recent contacts" list. You can remove individual entries from this list at any time by tapping the minus button next to a contact (or swiping the row). The list is on-device only and is also wiped when you delete the app.
The most recent peer ID you typed, so the input field can pre-fill it next time.

Where data is stored

The small amount of data described under "What the app collects" is stored in Google Firebase Realtime Database, hosted by Google in the europe-west1 region. Push notification tokens are sent to Google Firebase Cloud Messaging for routing only. Google acts as a data processor for MorseMe; their own privacy practices are governed by Google's Privacy Policy and the Firebase Privacy and Security in Firebase page.

MorseMe does not sell, rent, or share any of this data with anyone else.

How long data is retained

The active-tap flag is overwritten in real time and effectively retained for the length of a single tap (typically under a second).
The online flag is updated every time you open or background the app and is automatically cleared when your connection drops.
Your ID and optional nickname remain in the database for as long as your install exists. Delete the app and the records become orphaned; they are not associated with any other identifier and are not exported anywhere.

Your choices

Don't set a nickname if you'd rather only show as a 6-digit ID to peers.
Decline incoming calls from any ID you don't want to talk to. Both sides have to accept for a session to start.
Remove a contact from your "Recent contacts" list at any time by tapping the minus button next to the row (and confirming Remove). This deletes the local record of that peer from your device. They can still call you again with their 6-digit ID — the list is purely a convenience, not a permission gate — but the entry won't reappear unless you reconnect.
Delete the app to stop using MorseMe entirely. There is no separate account-deletion flow because there is no account.
Email knackfalder@gmail.com if you want your records (ID, nickname, online flag, FCM token) deleted from the backend. We will remove them within 7 days.

Children

MorseMe is not directed to children under 13, and we do not knowingly collect data from children under 13. If you are a parent or guardian and believe your child has used MorseMe, email knackfalder@gmail.com and we will remove their record.

Security

Data in transit between the app and Firebase is encrypted with TLS. Data at rest in Firebase Realtime Database is encrypted by Google. Firebase database rules restrict reads and writes so that only the owner of an ID can write under their own node, and tap state can only be written between two peers that are currently in a session together.

Changes to this policy

If this policy changes in any material way, the "Effective" date at the top will change and the new policy will be posted at this same URL. Past versions are available on request to knackfalder@gmail.com.

Contact

Questions, deletion requests, or anything else: knackfalder@gmail.com.