Privacy policy

Where processing happens

Input and conversion are processed on this page. We do not send the text you enter or the content you copy.

What is stored in this browser

Favorites, recently used characters and the display language you choose are stored in this browser. They disappear when you delete the browser data, and they do not move to another browser or site address.

Usage records we send

We send usage records such as which feature you started on which page, whether a copy or save finished, when you left the page, and whether you started or stopped Morse code playback, together with the time of each record (in milliseconds). They do not include the text you enter, the content you copy or your search terms. To tell sessions apart we use only a temporary number in browser memory, which is renewed when you reload. We do not use cookies. Connection records (IP addresses) are as described in the section “Connection records, language settings and browser signals” below. If an error occurs we send its type, code, file name and line number, never the error message or stack. The visit data recorded together with browser error reports, and the data excluded from them, are explained in “Connection records, language settings and browser signals” below. What you write in the feedback window opened with the “Feedback / report a problem” button in a corner of the screen is delivered only when you send it. We do not send your input as a hash or grouped by length or range either. What you write in the free-text field of this window is sent with leading and trailing spaces removed and, if you choose a rating, with the rating marker added. Do not write personal data, passwords, authentication keys or payment details there. However, the hosting that serves the site (Cloudflare Pages) generates ordinary access logs (IP address, time, browser information) as part of its operation. These are separate from the usage records above.

Connection records, language settings and browser signals

Browser error reports: On pages and language editions that send usage statistics, error reports sent by a visitor’s browser also record only the country and state- or province-level region of access, one display-language setting reported by the browser (for example, en-US) and the address of the referring site (host only, for example, www.google.com). As with usage statistics, country and region are estimates that Cloudflare determines from the connecting network; cities and coordinates are not recorded. Error reports do not record the referring page path, search terms or query parameters, the full list of preferred languages or raw request headers, IP addresses or browser signals (User-Agent Client Hints). These items are not recorded for feedback submissions. This additional recording applies only to error reports from the visitor’s browser, not to error records sent by the site’s server. Recording these items with error reports is enabled only after this notice is published and is not applied retroactively to error reports before it was enabled. The following describes usage statistics. To improve the service, we record the country and state- or province-level region you visit from, which site you came from and, to produce statistics on which language editions are used, the one display-language setting your browser reports (for example, en-US). Location is recorded only down to country and state or province; cities and exact locations are not recorded. While you use the service, connection records such as IP addresses are generated automatically and kept for safe operation of the service (security) and for detecting abnormal access. The processor for this site is Cloudflare. We also use IP addresses to exclude the operator’s own visits from usage statistics. A flag showing whether a visit was the operator’s may remain after the IP address is removed. Our earlier statement that collection began only after publication of the notice on 24 September 2026 was inaccurate. Usage records containing IP, country and browser language were already collected on the Spanish page /letras/es on 23 September 2026. Dates use Korean time. We record the referring site’s address and the page path supplied, but not the query string (after ?) or fragment (after #) of the address. Words or identifying information within the page path itself may remain in the record. For the display language, we do not record the full list of preferred languages or the raw request header sent by the browser.

We remove IP addresses and referring-page paths from our own usage records during a daily cleanup after 90 days have passed since the server received them. They are therefore not removed at the exact moment the 90-day period ends. We have no fixed retention end date for the remaining usage records. A temporary session identifier disappearing from your browser does not delete records already sent to the server. Backups made before deletion may retain IP addresses and referring-page paths for longer; we currently have no fixed deletion deadline for those backup copies. If a backup is restored, these expired fields become eligible for the next daily cleanup.

The browser’s temporary session number is kept only in memory, and we do not create a persistent identifier in cookies or browser storage to recognise returning visitors. To limit excessive submissions, we use an in-memory hash based on the site and IP that changes with the UTC date. Requests to the same site from the same IP on the same day may share this value; it is not used to store visit histories. IP addresses also remain separately in the connection records described above, so records of different visits may be linked through the same IP address. The same IP address does not necessarily mean the same person.

We do not currently collect browser signals; before enabling collection we will update this notice first. We do not collect them retroactively for use before collection is enabled. If we enable collection, we will collect and use the type and version signals the browser reports about itself and an indication of whether automation tools are being used, to help identify bots. These browser signals are estimates and do not conclusively identify the browser’s type or version or whether automation tools are being used.

When the collection server classifies a request’s country as being in the European Economic Area (EEA), or cannot determine its country, we block new collection of our own usage analytics, error reports and feedback for that request. If a request to load the feedback widget meets this condition, it does not display a new widget. However, a widget cached by the browser or already loaded may appear before that classification or remain visible while the page has not been reloaded. Even if the widget is visible, when a feedback submission request meets this condition, the collection server does not read or store its body, and, if you have not changed your draft since sending it, the widget displays a submission failure. The draft remains in that page’s memory and is not automatically resubmitted. Country classification can be inaccurate. This restriction does not stop hosting operations needed to serve the site or the separate automated-request logging described below.

Separately, for requests whose User-Agent shows the name of a service on a defined list of automated services, we record that string, the service category, the request path, the time and the network and verification information available. These records do not store raw IP addresses, cookies, query strings of addresses or request bodies. This path is separate from the browser-signal collection and the EEA measurement restriction above. There is currently no fixed deletion deadline for these records.

Limits of responsibility

The tools and results on this site are provided as is, and we do not guarantee their accuracy or completeness. Do not use them as the basis for important decisions on tax, finance, medicine or law. We are not responsible for damage arising from their use. By using the service you agree to this.

Operator

Operated by: Dan Kim

Tool descriptions are written with the help of AI; the operator reviews them and is responsible for their content.

The controller for the personal data processing described in this notice on emopu is Dan Kim, the individual operator. “The operator” in this notice means Dan Kim. As a first contact, you can use the site's feedback button for privacy enquiries and rights requests, or email contact@emopu.com. Use email if the button is unavailable, submission fails, or you need a reply.

We have not appointed a representative in the European Union. This is not a claim of exemption from the obligation to appoint one. You can send privacy enquiries and rights requests directly to the operator using the contact above.

We will respond about action on your request without undue delay and no later than one month after receipt. If complexity or the number of requests requires up to two further months, we will explain the extension within the first month. If we do not act, we will explain why and how to complain to a supervisory authority or seek a judicial remedy within that period. A submission only through the feedback form cannot receive an individual reply, so contact the email above for a response.

Revised 2026-10-02 — Added notice of the scope and exclusions for recording estimated country and state/province, one display-language setting and the referring site’s host together with browser error reports. Collection is enabled after the notice is published and is not applied retroactively.

Revised 2026-10-03 — Clarified the retention of usage records, referrals, the collection restriction for the EEA and unknown countries, the purposes of using IP addresses, hashes and temporary identifiers, and how feedback is sent.

Revised 2026-10-04 — Clarified that an already loaded feedback widget may remain visible under the EEA condition.

Revised 2026-10-05 — Clarified that the feedback submission failure message may not be shown depending on conditions.

Revised 2026-10-07 — Reflected the retention period for raw IP addresses and referring-page paths (90 days), the controller and contact, the reply deadline for rights requests, the absence of an EU representative and the correction of the collection start date.