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. One request goes out, on the first keystroke: the count described below, which names the tool and the braille code and carries nothing you typed. After it nothing is sent, however much you type.

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 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.

Whether it sets a cookie depends on where you are. In the European Economic Area, the United Kingdom and Switzerland, putting a cookie on your device for analytics needs your consent first, and this site does not ask for it — so there it does not set one. Your visit is still counted, but without a cookie and without an identifier, which means it cannot be told apart from anyone else's or connected to a later visit. Everywhere else Google Analytics sets its usual first-party cookies — two of them, _ga and _ga_YW34MYQBZG — which let it tell a returning visitor from a new one.

This is done with Google's consent mode, set on every page before the analytics script can act. The same setting turns off the three advertising signals — ad storage, ad user data and ad personalisation — for every visitor everywhere, because this site carries no advertising and has no use for them. Updated 27 September 2026: before this date the cookie was set in every country.

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 an image or a printable chart was downloaded — which of the five codes its page belongs to. A .brf file made by the translator is not counted.

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 adds its two scripts, described below, to it as to every page, but the widget's own security policy lets only one of them run: the bot-detection script, which is served from this domain. The browser refuses the analytics beacon there. A site that embeds the widget should know that the first is present, and that it sets its cookies there as it does everywhere; Cloudflare says that a cf_clearance cookie issued inside another site's page is stored in a partition keyed to that site.

Amazon affiliate links

A few pages link to a book, a tool or a sign 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.

It also leaves two cookies, wherever you are. On 12 October 2026 five pages of this site, the embedded translator among them, were each opened in a browser holding nothing from any earlier visit. Every one left cf_clearance, which is set to last a year and which a script in the page cannot read, and __cf_ob, which lasts until the browser is closed. Cloudflare's documentation says that the result of this detection is stored in cf_clearance, and that it regards the cookies it lists as strictly necessary; that list, last updated on 5 May 2026, does not mention __cf_ob. Unlike the analytics cookie described above, nothing in this site's files varies these by country. Until 12 October 2026 this page described the script and did not say that it sets a cookie.

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.

Or ask this site not to count you. The button below keeps a note in this browser, and while the note is there no page of this site loads Google Analytics: not its script, and not one request to Google. Opening any page of the site with #not-counted at the end of its address keeps the same note before that page can be counted, and #counted takes it away. The note belongs to this browser alone; another browser, a private window, or clearing this site's data starts without it. It does not reach Cloudflare's two scripts described above, which are added at the network edge and not by this site's pages. With scripts switched off, nothing is loaded from Google either. Added 19 October 2026.

Don't count my visits

Two things are kept in your browser's local storage: your theme preference (light or dark), and your progress in the practice drill — which signs you have answered correctly — which the drill's Reset progress button clears. A third is kept only if you ask for it: the note not to count your visits. None of them leaves your device, and none is 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.