Privacy
Last updated: 17 July 2026
Translation and practice run locally. We do not operate an account system. This page explains what can stay on your device, what a production PWA may cache, and when analytics might appear.
Short version
- Text you type into tools is not uploaded to MorseLabBase for encoding, decoding, or scoring.
- There are no user accounts, passwords, or cloud practice sync.
- Optional local storage may remember theme and trainer preferences on this browser.
- Contact uses your own email client - we do not run a message database on the marketing chrome.
What stays in your browser
Clearing site data, using a private window, or switching devices resets local progress. We cannot restore your Koch set from a server backup - there is not one.
- Encode / decode / timing: memory during the session.
- Audio / flash / vibrate schedules: session only, after your gesture.
- Theme and trainer prefs: localStorage when enabled.
- Challenge plaintext: in the ?c= URL you choose to share.
- Telegraph Desk session log: localStorage on this device - not uploaded.
- Clipboard: only when you click Copy.
What we do not collect for the tools
- No Morse practice transcripts uploaded for storage or model training.
- No microphone capture for AI decode.
- No camera frames for photo OCR.
- No social login or mailing-list wall to use the lab.
Hosting, PWA, analytics, ads
The site is served over the public internet. Infrastructure logs may include IP, user-agent, and requested URLs at the host layer - standard operations, not reading your HELLO WORLD.
PWA: in production, a service worker may cache static assets for offline shell use. Local development does not register a service worker.
Analytics: if a measurement ID is configured, aggregate traffic tools may load. They measure visits and paths - not Morse pane contents.
Advertising: reserved slots may appear when ads are enabled. Ad partners have their own policies. Tool math does not depend on ads loading.
Your choices
- Use a private window if you do not want local trainer prefs to persist.
- Clear site storage to wipe theme / progress keys.
- Block third-party scripts if you prefer - core tools should still run once assets are loaded.
- Do not put secrets into Challenge share URLs.
Contact
Privacy questions: Contact. Timing math: Methodology. Acceptable use: Terms.