MORSE CODE TRANSLATOR / TRUST

Privacy Policy

Privacy policy for morsecodetranslator.tools.

Published Aug 18, 2026

Effective date: November 14, 2026

Translation data

Text and Morse code entered in the translator are processed locally in your browser. They are not sent to our server, stored in Cloudflare D1, written to application logs or included in analytics events. If you allow analytics, Microsoft Clarity recordings mask the translator panels, so the text and Morse code in them are not recorded (see Microsoft Clarity).

Shared translations use the URL fragment after #. Browsers do not send that fragment in the normal HTTP request to this website. Anyone you intentionally share the complete link with can still read its fragment.

Audio playback and WAV generation use the current Morse sequence and playback settings in your browser. TXT and WAV downloads are created on your device. The application does not upload those generated files before downloading them.

Clipboard access happens only when you use a copy action and the browser permits it. The site does not read unrelated clipboard content. Browser share features may pass the link you choose to the operating system or another app selected by you; that destination handles the link under its own privacy terms.

Local preferences

The site may save theme and playback preferences such as WPM, tone frequency and volume in browser storage. It does not save your translation history.

The analytics consent choice may also be stored in the browser so that the site can apply it on later visits. Clearing this site's browser data removes locally stored preferences and may cause the consent choice to be shown again. A private administrator sign-in uses authentication storage needed for that restricted account; the administrator's browser also gets a cookie named mct_staff (value 1, no identity) so Microsoft Clarity skips it. Public visitors do not need an account to use the translator.

Information received with a web request

Like other websites, the hosting and security infrastructure receives request information needed to deliver a page. This can include the requested URL, time, browser and device details, network address and security signals. The URL fragment containing an intentionally shared translation is not part of the normal HTTP request.

Cloudflare provides hosting, network delivery, security and aggregate Web Analytics for the site. Its systems process request information according to Cloudflare's services and policies. The application does not add raw translator text or Morse code to those requests.

Analytics

We use Cloudflare Web Analytics for privacy-friendly aggregate traffic measurement. If you choose “Allow analytics,” Google Analytics 4 also records aggregate page and feature usage, and Microsoft Clarity records how pages are used (described below). If you choose “Necessary only,” neither Google Analytics nor Microsoft Clarity is loaded on a new visit; if they were already loaded after consent, withdrawing disables optional tracking. Outside the EEA, UK and Switzerland, or if Google’s consent message does not load, you can change or withdraw this choice using “Analytics preferences” at the bottom of the page. When Google reports that GDPR applies, its consent message replaces our analytics prompt: Google Analytics requires consent to TCF purposes 1 (device storage), 8 (content measurement) and 9 (audience statistics) and Google (vendor 755); Microsoft Clarity requires purpose 1 and Microsoft (vendor 1126). Until a choice is available, neither loads. Reopening a message keeps the existing choice until you submit a new one. Withdrawing stops optional Google Analytics and Microsoft Clarity tracking and removes their first-party cookies.

Events may include page type, translation direction, coarse length or time buckets, playback settings buckets, device capability and result state. They must not include raw text, Morse code, clipboard contents, URL fragments, email addresses or other free text.

Analytics helps answer broad questions such as whether a page loads, which translation direction is used and whether a playback or download action succeeds. Length and timing values are grouped into coarse buckets rather than sent as the message itself. Analytics data is not used to reconstruct a visitor's translation.

Google Analytics 4 and Microsoft Clarity are controlled by the consent choice described above. Google, Microsoft and Cloudflare may handle measurement and request information under their own service terms. Browser privacy controls, content blockers or disabled JavaScript may also prevent optional measurement.

Microsoft Clarity

We use Microsoft Clarity, only after the applicable analytics consent described above, to see how people actually use the site, for example where the translator controls are confusing or where a page stops working, so we can fix it.

  • What it records. Clarity's script records clicks, taps, mouse movements and scrolling, and the content and layout of the page as it appeared to you, so we can replay a visit and view heatmaps. It also collects technical details such as browser, device, screen size and approximate location.
  • What is masked. The translator's text and Morse panels, its playback readout and the quick translator on Blog articles are masked in your browser, so their contents are never sent to Clarity. Whatever you type into other input boxes, and numbers and email addresses shown on the page, are masked too. Other page text, such as articles and the alphabet chart, is recorded.
  • Where it does not run. Clarity is turned off in the private administration area and sign-in pages, on pages whose address can carry a one-time sign-in, password-reset or email-verification code, on a page opened from a shared translation link (the link's fragment holds the message), and for the signed-in administrator.
  • Consent. Outside Google’s GDPR consent flow, Clarity follows the same “Allow analytics” / “Necessary only” choice as Google Analytics. In that flow, it follows device-storage and Microsoft vendor consent. Advertising storage is always reported to Clarity as denied.
  • Who processes it. Microsoft Corporation provides Clarity and stores the data in its Azure cloud. Microsoft's handling of this data is described in the Microsoft Privacy Statement. According to Microsoft, recordings are available to us for 30 days, except that Microsoft keeps recordings we mark as favorites and a random sample of recordings for up to 9 months.
  • Cookies. Clarity sets two first-party cookies: _clck, which keeps a random Clarity user ID for one year, and _clsk, which joins the pages of one visit into a single recording and lasts one day. Microsoft lists further cookies it may set on its own domains in its Clarity cookie list. Choosing “Necessary only” removes _clck and _clsk.

Private administration

The site has one private administrator account used to manage Blog content and settings. There is no public account registration or payment system.

Administrator authentication data and Blog records are separate from public translator input. Cloudflare D1 may store administrator, role, settings, taxonomy and published-content records. It is not used for visitor messages, Morse translations, playback history, downloads or shared fragments.

Messages you send to support

If you email support, the message, sender address and any information you include are received through the email services involved in delivery. Provide the page URL, browser details and a harmless reproducible sample when reporting a problem. Do not send a private translation, password, authentication code or other sensitive content.

Support information is used to understand and respond to the request, investigate reproducible defects and make documented corrections. It is not a substitute source for analytics about all visitors.

Your choices

You can use the core translator without a public account. You can choose Necessary only for optional Google Analytics and Microsoft Clarity, clear browser storage to remove local preferences and avoid using Share when a message should not be placed in a link. You can also copy a neutral test message when asking for support.

Contact

Questions about this policy can be sent to support@morsecodetranslator.tools.

Google advertising

We display Google AdSense automatic ads: bottom anchor ads and vignette ads between page visits. We do not place manual ad units in the translator. Google and its partners may use third-party cookies, web beacons, IP addresses and other identifiers to deliver and measure ads, limit frequency, prevent fraud and, where permitted and with required consent, personalize ads based on visits to this and other websites.

In the EEA, UK and Switzerland, Google’s consent message provides advertising choices and governs the optional analytics consent described above. You can change or withdraw your choices by reopening that message here:

Where applicable in the United States, Google’s state privacy message provides choices such as “Do not sell or share my personal information” and advertising opt-outs. The message and available choices depend on your region. The Google privacy preferences button reopens the message when Google makes it available; a content blocker may prevent it from loading.

You can manage personalized Google ads in My Ad Center and opt out of participating third-party vendors’ personalized advertising through AboutAds choices. Browser cookie controls may also limit advertising cookies. The site’s own “Necessary only” control covers optional analytics; it does not replace Google’s advertising choices.

See Google's use of partner-site data and My Ad Center for advertising information and personalization controls.