Your data stays yours.

What happens to your content?

Text, files, filenames, encoded data, and decoded data are processed in temporary memory on your device. There is no backend, database, API, account system, or server-side conversion. User-provided content is shown as plain text; decoded HTML and JavaScript are never rendered or executed by the converter.

No persistent user content

Base64Baboon does not save input or output in cookies, localStorage, sessionStorage, IndexedDB, or a database. Refreshing the page discards the workspace. The app also clears its content when leaving the page and when the browser restores it from its back/forward cache.

If you choose Copy or Download, the result is placed in your system clipboard or saved through your browser. You manage those copies, including clipboard history, downloads, and any device backup or clipboard sync settings. Clearing this app is not a secure erase of your device’s memory.

No tracking or third-party dependencies

This site includes no analytics, advertising scripts, tracking pixels, third-party fonts, or external libraries. It sets no cookies. The theme follows your system preference by default; a manual theme change is held only for the current page and is not stored.

The website still has to load

Visiting the hosted site requests its static HTML, CSS, JavaScript, and image assets. Like any web host, the hosting provider may receive ordinary connection information such as your IP address, requested page, browser information, and request time, and may keep access or security logs. Conversion content and filenames are never included in these requests.

This policy describes the supplied application. The site operator should verify their hosting configuration and avoid adding analytics, injected scripts, or other services that would change this behavior.

Base64 is not encryption

Base64 is an encoding format, not encryption. Anyone with the Base64 text can decode it. Base64Baboon protects privacy by performing the conversion locally in your browser rather than transmitting your data to a server.

Using it at work

Local processing is useful in environments where sending sensitive strings to a conversion service would be undesirable. Always follow your organisation’s security policies and use a trusted device and browser. Browser extensions, compromised devices, and copies you create are outside this application’s control. We make no security certification or blanket compliance claims.

How can I verify this?

1. Open Developer Tools → Network in your browser.
2. Let the page finish loading, then clear the network log.
3. Encode and decode text. Repeat with both file conversion modes.
4. No conversion should make a network request. There should be no request containing content or filenames.

The application also includes a Content Security Policy with connect-src 'none', which blocks scripted network connections. All runtime source files are readable and hosted with the page.

Using your own local copy

You can download the complete static site folder and open index.html locally. A complete local copy does not require internet access for conversion. The hosted site does not install a service worker or promise offline reloads. Clipboard permissions vary by browser; manual copy and paste remain available.