Privacy

What you type is never sent anywhere

The translator, decoder, name generator, bracelet maker and practice drill all run entirely inside your browser using JavaScript that is downloaded once with the page. Nothing you type is transmitted, logged or stored — not on a server, not in a database, not anywhere. There is no server here to receive it: this is a set of static files.

That means you can paste a private name, a message meant for a card, or anything else, and it goes no further than your own device. You can verify this yourself: open your browser's network tab and type into any tool. No requests are made.

What is measured

This site uses Google Analytics 4 to count page visits and see which pages people actually find useful. That informs what gets built next — which letters people look up, whether the printable chart or the translator gets used more.

Google Analytics sets cookies and collects the standard set: pages viewed, approximate location derived from IP address, referring site, and device and browser type. Google states that in Google Analytics, IP addresses are not logged or stored.

Three things beyond page visits are counted, and it is worth being exact about them, because "we don't track anything" is the sort of claim sites make and then quietly break:

• that a tool was used — which tool, and which of the five braille codes. Typing into the translator sends the word translator, not the word you typed.
• that output was copied — which tool the copy button belonged to.
• that a cell diagram was downloaded — which section it was on.

Each is sent once per page visit however many times you do it, so the numbers count people rather than keystrokes. None of them carries a character you typed, a name you looked up, or anything you could be identified by. That is not a policy — the events are assembled from the page's own address and a fixed list of tool names, so nothing typed into a tool is ever read into one.

Google Analytics also records one thing on its own: that a link to another site was followed, and the address it pointed to — a Morse code page, or an Amazon product. It records the link, never anything typed. Its other automatic measurements — scrolling, form interactions, site search, video and file downloads — are switched off.

What is not here

• No advertising network, and no display ads.
• No session recording, heatmaps or scroll tracking.
• No cross-site tracking, and nothing that follows you to another site.
• No accounts, no sign-up, no email collection.
• No third-party fonts, images or embeds — every asset is served from this domain.

The embeddable translator widget carries no Google Analytics. Cloudflare's two scripts, described below, are added to it as they are to every page, so a site that embeds the widget should know they are there.

Amazon affiliate links

A few pages link to a book or a tool on Amazon, and those links carry this site's Amazon Associates tag. Each one is labelled where it appears. Nothing is loaded from Amazon until you click: there is no Amazon script, image or cookie on these pages. If you follow one, Amazon can see that the visit came from this site and may set its own cookies under its own privacy notice, and if you buy something, this site earns a commission. The price you pay is the same.

As an Amazon Associate I earn from qualifying purchases.

Two scripts this site does not control

Cloudflare serves this site, and its bot detection inserts a small script into every page from /cdn-cgi/challenge-platform/. It collects signals about the browser — the sort of thing that distinguishes an automated client from a person — and reports them back to Cloudflare, not to this site. Nothing about it is under the control of the files published here: it is added at the network edge, after the page leaves the repository.

Whether that counts as fingerprinting is arguable. That it is browser profiling is not, so this page names it rather than leaving a tidier claim standing. It is disclosed here for the same reason the translator's error rate is published: a reference site that describes itself inaccurately has no business asking anyone to trust its tables.

It does not identify you to this site and it is not used for analytics or advertising. It is on every page, including this one. A content blocker will stop it, and the site works identically without it.

The second is Cloudflare Web Analytics. Its beacon, a script from static.cloudflareinsights.com, is also added at the network edge to every page. Cloudflare says it collects metrics using the browser's Performance API — timing metrics, the minimum it needs to show how the site performs — and that Web Analytics does not collect or use visitors' personal data. It reports to Cloudflare, and a content blocker stops it too.

Opting out

Any browser-level content blocker, tracking protection, or Google's own opt-out browser add-on will stop the analytics script loading. The site works exactly the same with it blocked — nothing here depends on analytics running.

Your theme preference (light or dark) is stored in your browser's local storage. That never leaves your device and is not analytics.

Contact

If you want more detail about anything here, or you think something on this site handles data in a way this page does not describe, that is worth flagging — the description above is meant to be complete.