Privacy Policy

1Who we are

Ditlamp is an offline Morse code translator, decoder and trainer for Android, developed by Zydeno. You type text and the app plays it as sound, a lamp on the screen, the phone’s flashlight, vibration and screen flash; you hold the phone near a tone or a blinking light and it reads the code; and you learn Morse code in short daily sessions. This policy explains what the app keeps on your phone, how it uses the microphone and camera, and what happens if you contact us at [email protected].

Ditlamp is an independent app. It is not affiliated with or endorsed by any amateur-radio organisation, standards body or equipment maker, and it is a learning and practice tool, not a safety or emergency device.

2What this policy covers

This policy covers the Ditlamp Android app. It does not cover your phone’s operating system, the keyboard, browser, e-mail, file and print apps you use, any document or cloud storage provider you save to, or the web host that serves this page, whose own terms and privacy policies govern the data you give them.

The app works without an account or an internet connection. The app has no ads and no analytics.

3What the developer does not collect

The app does not send the developer your messages, decoded text, lesson results, settings, sound, camera images, location, device identifiers or any other information. It has no account registration, no advertising SDK, no analytics SDK and no third-party crash reporter. It does not request internet, location, contacts, phone, notification, photo-library or storage access.

We do not receive, sell or share your in-app data, use it for advertising or train models on it. Ditlamp never asks for your name or contact details.

4What is stored on your phone

Ditlamp keeps its working data in Android app-private storage, in a single preferences store (Android Jetpack DataStore) that holds text entries. The app has no database. Depending on how you use the app, this includes:

• Log: the messages you sent, read or translated, with their letters and Morse code, the date, speed, alphabet, source (for example Send, Key or Listen) and outputs used, and the ones you marked as saved.
• Current work: the text you last typed, your choices on the Send, Chart and Listen screens (such as alphabet, outputs and speed), the screen you were on and, for Listen, the letters decoded so far in the current reading, so the app can resume where you left off. If you choose a recording to decode, this also holds the file’s name and its Android address (URI), not its content.
• Learning progress: which characters you have reached on the Koch board, your results per character and per session, the pairs you mix up and your streak.
• Settings: language, each unit choice, theme, sound, speed, tone pitch, haptics, enabled alphabets and the state of the introduction.

The app also creates two kinds of temporary files in its private storage: a sound clip (WAV) in the cache when you share a message as a sound clip, and a safety copy of your previous data when you import a backup, so that you can undo the import. The safety copy is kept until you undo, use Delete all or clear the app’s storage.

Messages are free text; do not enter information you would not want kept on the phone. All translating, decoding and lesson scoring run on your phone. This data is removed when you uninstall the app or clear its storage.

5Microphone (Listen, optional)

The microphone is optional. Ditlamp uses it only on the Listen screen, to hear a Morse tone from a speaker, a key or a recording and print the letters. Translating, sending, learning and the chart all work without it.

• Asked in context. Nothing is requested when the app starts. When you open Listen with the microphone, or tap “Try with your microphone” in the introduction, the app first shows a screen titled “Read Morse from a sound” with this text: “Hold the phone near the speaker or radio. Audio is analysed on the phone and never saved or sent.” Only if you tap “Allow microphone” does Android show its permission prompt.
• Analysed in memory. While Listen is open, the app finds the tone in the incoming sound, estimates the speed and decodes the code. This uses a short buffer in memory that is continuously overwritten. The sound is not written to storage, not kept as a recording and not sent anywhere: the app has no internet access.
• Not speech recognition. The app looks only for a steady tone and its on-off timing. It does not recognise words, voices or speakers, and it does not keep the sound.
• What you can save. If you tap Save, the decoded text is added to your Log with its date and speed. The decoded letters of the current reading are also kept on the phone with the Listen screen state (see section 4) until you start a new reading, clear it or delete your data. The sound itself is never saved.
• Foreground only. Listening stops when you pause, leave the screen or send the app to the background. Ditlamp has no foreground service, never listens in the background and cannot record phone calls.
• Your control. Android shows its microphone indicator while the microphone is in use. You can say Not now, refuse, or withdraw the permission at any time in Android Settings, Apps, Ditlamp, Permissions. If it is off, the app says “Microphone is off for Ditlamp”, and sending, the trainer and reading from a file still work.

Sound around you can contain other people’s voices or private matters. Hold the phone near the sound you want to read, and do not use Listen to capture conversations. Ditlamp does not keep what it hears, but you are responsible for using it lawfully (see the Terms of Use).

6Camera and flashlight (Light, optional)

The camera is optional. Ditlamp uses it only on the Listen screen in Light mode, to read a blinking lamp or screen. The flashlight is used only when you choose it as a Send output.

• Asked in context. The camera permission is requested only when you open Light mode. The app first shows a screen titled “Read a blinking light” with this text: “Point the camera at a lamp or a flashlight. The picture is analysed on the phone and never saved or sent.” Only if you tap “Allow camera” does Android show its permission prompt.
• Analysed in memory. The app measures the brightness inside a box you place on the preview and decodes the on-off timing. Camera frames are processed in memory and discarded. No photo or video is taken, saved or sent, and the preview is not stored.
• Foreground only. The camera is used only while the Light screen is open and stops when you leave it or the app goes to the background.
• Flashlight output. When you choose the flashlight as an output, Ditlamp switches the phone’s torch on and off through Android’s torch control, which needs no camera permission and takes no pictures. If the flashlight is unavailable, for example because another app is using the camera, the app says so and you can use the lamp view instead.
• Your control. You can refuse the camera or withdraw the permission at any time in Android Settings, Apps, Ditlamp, Permissions. Sending, Listen with the microphone, learning and the chart keep working.

7No internet access from the app

The Android app does not declare the INTERNET permission. It has no backend, no external API requests, no automatic uploads, no remote downloads and no cloud synchronisation. Code tables, word lists, fonts, sounds and help text are bundled in the app.

Links. When you open this policy, the Terms or the support e-mail address, the app hands the address to your own browser or e-mail app. Your browser then visits the site, and the website host can process ordinary web-request data such as your IP address under its own policy. Nothing is sent by Ditlamp itself, and a support e-mail is sent only if you choose to send it.

8Files, sharing, export and printing

Decode from a file. When you choose an audio or video recording to decode, the app reads only the file you select in Android’s file picker, analyses it in memory and does not copy it. To let you replay the file, the app remembers its name and address and asks Android to keep read access to that one file; it does not read other files. No storage permission is needed.

Share. You can share a message as text, as code or as a sound clip (WAV), and share selected messages from the Log as text. A sound clip is created in the app’s private cache only when you tap Share and is handed to the app you choose in Android’s share sheet.

Export and import. In Settings, Your data, Export writes one JSON backup file with your Log, lesson progress and settings. It is created only when you tap Export and is written to the place you choose in the file picker. In the Log, Export saves the text of a message, or of the messages you selected, as a plain text file in the place you choose. Import reads only the backup file you select and replaces the data on the phone with its contents; the previous data are kept for the undo described in section 4.

Print. If you print a code chart, the document is handed to the Android print service you select, which may be a printer, a PDF file or a cloud print service under its own policy.

Your destination matters. A chat app, e-mail app, cloud drive or print service receives what you choose to give it and keeps it under its own policy. Exported files are ordinary, unencrypted files. These are transfers you start, not automatic synchronisation. Zydeno receives no copy unless you deliberately send one to support.

9Permissions and device access

Microphone and camera are the only permissions Android asks you to approve, each is optional and each is requested only when you open the feature that needs it (see the two sections above). The app also declares the ordinary vibration permission, which lets it vibrate as a Send output and as haptic feedback, and which Android grants without a prompt. It does not request internet, location, contacts, phone, SMS, notification, photo or media, storage-wide, all-files, Bluetooth-scanning, exact-alarm or Accessibility-service access, it runs no foreground service, and the advertising-ID permission is removed from the app.

Region. To choose sensible default units, time and date formats and paper size, the app reads a two-letter country code on the device: the country reported by your SIM card or mobile network, which Android makes available without a permission, or otherwise the region of your device’s language settings. It reads no phone number, subscriber or network identifier. The value is used on the device only and is not transmitted. You can change every unit and the language in Settings.

Sound and haptics. Sound plays through your phone’s speaker or connected headphones. Haptic feedback and the vibration output can be switched off in the app or in Android.

10Your controls, backups and deletion

You can delete messages from the Log, change every setting, export your data, and use Settings, Your data, Delete all to remove your Log, lesson progress and settings after you confirm; you can undo within a few seconds. Delete all also removes the temporary files described in section 4. Export first if you want to keep a copy.

Automatic Android cloud backup and device-to-device transfer are turned off for the app. To move your data deliberately, use Export and Import. If the phone is lost or the app’s storage is cleared without an export, the developer cannot restore your data.

Uninstalling Ditlamp or clearing its storage in Android Settings removes its private data. Deleting items in the app does not delete files you exported or shared or copies held by other apps or people; remove those separately.

11Legal bases for processing

Where the EU or UK GDPR, or a similar law such as the Swiss FADP or Brazil’s LGPD, applies, these are the legal bases for the limited processing described in this policy:

The app makes no automated decisions that have legal or similarly significant effects on you, does not build a profile of you and does not process special categories of personal data; sound picked up by the microphone and light seen by the camera are analysed in memory on your phone only while you use Listen, are neither saved nor sent, and are used only to decode Morse code, not to identify people or recognise speech.

12How long information is kept

Your Log, learning progress and settings stay on your phone until you remove them, clear the app’s storage or uninstall the app. Sound and camera frames are not kept at all: they exist only in memory while Listen is open. Deleting an item is not a guarantee of forensic erasure of every byte on the device. Files you saved or shared outside the app remain under your control, or the recipient’s, and may outlast uninstallation.

13Security

Ditlamp relies on Android’s application sandbox for its private data. It does not add a password-protected vault or promise encryption beyond what your device provides. Exported files are ordinary files.

No device or storage system is perfectly secure. Someone with access to your phone while it is open, or to a compromised or rooted phone or an exported file, may read it. Use a screen lock, keep your phone updated and share exported files only with people you trust.

14Ads, purchases and future versions

Today. The current version of Ditlamp is free of charge, shows no ads, has no in-app purchases or subscriptions, and contains no advertising, analytics or payment SDKs. This describes the app as it is now, not a promise about future versions. Future versions may introduce advertising, paid features, in-app purchases or subscriptions, or other optional services.

If ads are introduced. Ads would be supplied by a third-party ad network, for example Google AdMob. Ad networks typically process your device’s advertising ID, IP address, approximate location derived from the IP address, device and app information and your interactions with ads, in order to show ads, limit repetition, measure performance and prevent fraud, and, only where you allow it, to personalise ads. Ads would also require the app to connect to the internet, which the current version cannot do.

If purchases or subscriptions are introduced. They would be processed by Google Play’s billing system. Google handles your payment details under the Google Privacy Policy. We would receive only what is needed to deliver and verify a purchase, such as a purchase token, the product, its status, the country and the currency, never your full card or bank details.

Before any such change we will update this policy with a new effective date and version, describing what data is processed, by whom, why and how you can control it; update the Google Play Data safety section; mention the change in the release notes; ask for your consent where the law requires it (for example for personalised ads and non-essential access to your device in the EEA, the UK and Switzerland, through a consent tool that meets Google’s requirements); and offer the opt-outs the law requires (for example under US state privacy laws). The change applies only from the app version that introduces it. Data already stored in the app will not be used for advertising without telling you first and, where required, getting your consent. We will not knowingly show personalised ads to children (§15).

15Age limits

Ditlamp is a learning tool for general use by people aged 13 and over and is not directed to children under 13. It does not collect personal information from anyone, so it holds no information about children. A parent or guardian who believes a child has sent us personal information, for example by e-mail, can contact support to request its deletion.

16Your privacy rights

Privacy laws in many countries give you rights over your personal data. Because Ditlamp keeps your data on your phone and the developer does not receive it, most of these rights are in your own hands: you can view, correct, export and delete everything in the app (§10) and withdraw permissions in Android Settings. For data you have sent us, such as e-mails, write to [email protected].

EU and UK representative. The individual developer does not process personal data of people in the EU/EEA or the UK except occasional e-mails you choose to send to support. This occasional processing does not involve large-scale processing of special-category or criminal-offence data and is unlikely to result in a risk to your rights and freedoms. Under Article 27(2)(a) GDPR and Article 27(2)(a) UK GDPR, it does not require an EU or UK representative, so none is appointed. Contact us directly at [email protected]; you can also complain to your local supervisory authority.

Rights by region. A summary; the law where you live decides the details.

• European Union, EEA, United Kingdom and Switzerland (GDPR, UK GDPR, Swiss FADP): access, rectification, erasure, restriction of processing, data portability, objection to processing based on legitimate interests, withdrawal of consent at any time, and complaint to a supervisory authority, for example in the country where you live or work (in the UK, the Information Commissioner’s Office).
• United States (California CCPA as amended by the CPRA, and the comprehensive privacy laws of other states such as Virginia, Colorado, Connecticut, Texas and Oregon): to know and access, delete, correct and port personal information; to opt out of its sale or sharing, of targeted advertising and of profiling; to limit the use of sensitive personal information; to appeal a refusal; to use an authorised agent; and not to be discriminated against for using these rights. Notice for California residents: in the last 12 months the developer has not collected personal information through the app, other than e-mails you chose to send us. We have not sold or shared personal information, and we do not use sensitive personal information. Global Privacy Control signals are honoured where the law requires; today there is nothing to opt out of.
• Canada (PIPEDA and provincial laws, including Québec’s Law 25): access, correction and withdrawal of consent; complaints to the Office of the Privacy Commissioner of Canada or, in Québec, the Commission d’accès à l’information.
• Brazil (LGPD): confirmation of processing, access, correction, anonymisation, blocking or deletion, portability, information about sharing and revocation of consent; complaints to the ANPD.
• Japan (APPI): disclosure, correction, suspension of use or deletion; complaints to the Personal Information Protection Commission.
• South Korea (PIPA): access, correction, deletion, suspension of processing and withdrawal of consent; complaints to the Personal Information Protection Commission or the KISA privacy centre. The person responsible for personal information is the developer, reachable at [email protected].
• Australia and New Zealand (Privacy Act 1988, Privacy Act 2020): access and correction; complaints to the OAIC or the New Zealand Privacy Commissioner.
• Other countries (for example India’s DPDP Act, Singapore’s PDPA, South Africa’s POPIA or Türkiye’s KVKK): the rights your local law gives you. Write to us and we will respond in line with it.

How we respond. We answer within one month, or sooner or later where your local law sets another period (for example 45 days under the CCPA), and we may extend it where the law allows. We may ask for information to confirm that a request comes from you. Requests are free unless they are manifestly unfounded or excessive. If we cannot do what you ask, we explain why and how you can appeal or complain.

17International users

Ditlamp is available in many countries. The developer does not receive the data you keep in the app, so we do not transfer it anywhere.

If you e-mail us, your message is processed by our e-mail provider and may be stored on servers outside your country. Where the GDPR or UK GDPR applies to such a transfer, it relies on an adequacy decision, on standard contractual clauses offered by the provider, or on the transfer being necessary to answer your request.

This policy is written in English. If a translation is offered, the English version prevails unless your local law requires otherwise.

18Changes to this policy

We may update this policy when we change the app (including any change described in §14), when the services the app uses change, or when the law changes. The effective date and version at the top of this page show which version applies, and the version history (§19) summarises every change.

For a material change, for example new data leaving your device, ads or purchases, we update this page and the Google Play Data safety section before the app version with that change is published, describe it in the release notes, and ask for your consent in the app where the law requires it. Changes do not apply retroactively to data processed before them. Earlier versions are available on request from [email protected].

19Version history

20Contact

• Developer (controller): Zydeno, the developer of Ditlamp on Google Play
• E-mail for privacy questions and requests: [email protected]
• Website: zydeno.com

We aim to answer within 30 days. If you are not satisfied with our answer, you can contact your local data-protection authority.

See also the Terms of Use.